1.7 KiB
1.7 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 | backlog-ready | PDIAP-12284 | Remove UIKit wrapping from XFlow |
|
|
|
|
2026-05-05 |
|
PDIAP-12284 - Remove UIKit wrapping from XFlow
Status
- Reopened after rollback.
- Quy already moved this story into the next sprint (
26Q2.6); leave it in To Do until the sprint starts on Thursday. - Jeff asked David to start working on this with
PDIAP-15836, but not to move the active story to In Progress until Thursday.
Context
- This is the original story for removing the UIKit wrapping.
- Current relationship to track:
PDIAP-15836is blocked by this story because the lifecycle-sequencing fix depends on the UIKit removal landing, unless further validation proves part ofPDIAP-15836can be implemented independently on the SwiftUI path.
Historical Slack Context
- November 21, 2025 Slack context says David created
PDIAP-12284andPDIAP-12285to cover remaining UIKit-removal work inside XFlow after reviewing open Sendable and XFlowViewMaker-track stories. - That same backlog refinement closed out pending XFlowViewMaker stories that were no longer needed.
- Current Mattermost context supersedes the old standalone refinement framing: this story is now reopened after rollback and should be handled together with
PDIAP-15836.
Sequencing
- Work can begin, but merge/release should wait until the REST-transition consumer-validation window has completed.
- Keep the implementation branch up to date with
mainwhile waiting for approval to work with consumers and merge.