david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
1.6 KiB
1.6 KiB
type, project, status, ticket, title, systems, workstreams, people, related, updated, tags
| type | project | status | ticket | title | systems | workstreams | people | related | updated | tags | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| work-item | fidelity | active | PDIAP-15836 | Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment |
|
|
|
|
2026-04-16 |
|
PDIAP-15836 - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
Status
- Approved
- Sequenced after
PDIAP-15838 - Sized at
8points
Context
- This story came out of the
AccountLinkroot cause investigation. - It is tied to the dismissal sequencing problem found after UIKit removal in SwiftUI-only paths.
- The root cause document was updated and the revised wording was approved.
Approved Scope
- Modernize dismissal delegate lifecycle sequencing for pure SwiftUI flows.
- Cover the missing lifecycle contract where delegate callbacks can happen before the view is fully removed.
- Validate the change across affected SwiftUI flows rather than only in one narrow reproduction.
Sequencing And Dependencies
- This story should come after
PDIAP-15838. - It is aligned with epic
26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2). - If possible, it should use the same consumer-impact feature flag strategy as the broader UIKit-removal rollout.
Communication Notes
- Keep the scope framed as lifecycle sequencing in a pure SwiftUI environment, not only as a symptom like multiple modal presentation.
- If mentioned externally, keep it separate from
PDIAP-15838.