- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
4.7 KiB
4.7 KiB
type, project, date, updated, focus, work-items, blockers, tags
| type | project | date | updated | focus | work-items | blockers | tags | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| daily | fidelity | 2026-05-05 | 2026-05-05 |
|
|
|
|
2026-05-05
Mattermost Evidence Promoted
-
PDIAP-16167 - AccountLink - XFlow causing web view rewrites investigation- Daily scrum reported minor Confluence report adjustments and planned publication.
- The Confluence report was published and the proposed Jira/Discourse/DM wording was sent to Zachary.
- Final external framing: root cause is a consumer-side SwiftUI presentation-topology / view-identity invalidation in
BankInformationView, not XFlow or XFlowViewMaker. The issue reproduces onXFlowSDK v0.1.0, predating REST and Apollo-related changes, and Flagship does not appear to show the same behavior because presentation ownership is behind a more stable boundary. - David moved
PDIAP-16167to Done.
-
PDIAP-15838 - Remove Apollo for iOS- Daily scrum reported the draft PR was sent for external review.
- Bruce left minor feedback; David addressed it and pushed the suggested change.
- One review change set
responseKey: String? = nilas the default inFlowRESTOperationContract, so operations such asupdateSlots,storeString, andpublishEventcan omitresponseKeywhen not needed. - David kept the file that now serves as the canonical location for XFlow domain enums after removal of GraphQL-generated code.
- Jeff directed David to move the ticket to Done, while keeping the PR unmerged for at least 30 days.
- Jeff clarified that the GraphQL-removal branch must stay up to date with
mainuntil REST backend is live in production with REST toggles enabled and the 30-day validation window is complete.
-
PDIAP-15836 - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environmentandPDIAP-12284- Jeff initially noted that starting this work now could create a long-lived branch, because UIKit-removal work needs feature flags, consumer testing, and a later merge/release window after the REST transition finishes.
- David clarified that the spike identified and documented the root cause, but no code changes have been published yet.
PDIAP-12284is the original UIKit-wrapping removal story and was reopened after rollback. David notedPDIAP-15836should be treated as blocked byPDIAP-12284, although the Jira link was not yet present.- Jeff later asked David to start working on
PDIAP-15836/PDIAP-12284, but not to move the stories to In Progress until the next sprint starts on Thursday. - Quy had already moved the stories into the next sprint (
26Q2.6); David will leave them in To Do until the sprint starts. - Jeff's branch-management guidance: after implementation, maintain the branch until consumer-testing approval; merge the GraphQL-removal branch first after the REST validation period, then merge that into the
PDIAP-15836/PDIAP-12284branch. Expected merge timing is roughly 90-100 days from today unless Fidelity shortens the review windows.
-
Backlog triage
- Jeff asked for previously assigned backlog work because there are no other in-progress stories after
PDIAP-16167andPDIAP-15838move to Done. PDIAP-11962 - Closure of secret scanning alerts: David found an October 9, 2025 email confirming submission; Matthew closed the earlier alerts/story on March 5, 2026. Two Google API Key alerts remain open and were not part of that closure.PDIAP-11961 - Remediation of Exposed Secrets in XFlow iOS SDK - Request for Rotation/Invalidation: related story for the remaining Google API Key alerts; not assigned yet. Jeff said this is not a priority yet but should be noted for future.PDIAP-11562 - investigate if XFlow is being built as debug: David identified it as related to XFlow podspec configuration and Fid4 consumption, not Sparta-team work.- Sparta backlog notes:
PDIAP-12226decoding is partially complete with a strict-decoding refactor still in progress;PDIAP-12227rendering has a working grid-layout base and is partially done;PDIAP-12228interactive components is blocked by unresolved mobile JavaScript execution.
- Jeff asked for previously assigned backlog work because there are no other in-progress stories after
Slack Archive Backfill
- Checked the historical Slack archive for the newly recreated work-item notes.
- Promoted useful Slack backfill into the relevant work-item notes for
PDIAP-11962,PDIAP-11961,PDIAP-11562,PDIAP-12226,PDIAP-12227,PDIAP-12228, andPDIAP-12284. - Skipped non-Fidelity API-key hits and generic Sparta chatter that did not map cleanly to these Jira items.