refactor: update work item statuses and sprint planning details for PDIAP-15836 and PDIAP-12284

project-knowledge/01-current/current-work.md

@@ -18,7 +18,7 @@ tags:
 - Follow up on active tickets through `project-knowledge/02-work-items/`, especially branch maintenance for `PDIAP-15838` and implementation planning for `PDIAP-15836` / `PDIAP-12284`
 - `PDIAP-15765` is done and `PDIAP-14859` is also done
 - `PDIAP-15838` is Done from a Jira/status perspective after external review feedback was addressed, but its draft PR must remain unmerged and kept current with `main` until REST backend production readiness and the required REST-toggle consumer validation window allow merge
-- `PDIAP-15836` is now paired with `PDIAP-12284` for the UIKit-removal / pure SwiftUI lifecycle implementation path; do not move the story to In Progress until the next sprint starts on Thursday after lunch
+- `PDIAP-15836` is now paired with `PDIAP-12284` for the UIKit-removal / pure SwiftUI lifecycle implementation path; Quy already moved both into next sprint `26Q2.6`, David can start work now, but leave Jira status in To Do and do not move either story to In Progress until Thursday
 - Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of `PDIAP-15765` scope unless later evidence proves it belongs there
 - Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
 - Thoroughly verify current `ApexBridgingAddressComponent` / rule-loading usage before describing it as inactive or dead code

project-knowledge/01-current/work-items.md

@@ -24,11 +24,11 @@ Update the per-ticket files first when scope, status, sequencing, or communicati
 
 - `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
   Detail: `project-knowledge/02-work-items/pdiap-15836.md`
-  Current note: approved at `8` points and now paired with `PDIAP-12284` for the UIKit-removal implementation path. Do not move to In Progress until the next sprint starts on Thursday after lunch. Treat `PDIAP-15836` as blocked by `PDIAP-12284` unless validation proves the lifecycle fix can be implemented independently.
+  Current note: approved at `8` points and now paired with `PDIAP-12284` for the UIKit-removal implementation path. Quy already moved it into next sprint `26Q2.6`; leave it in To Do and do not move to In Progress until Thursday. Treat `PDIAP-15836` as blocked by `PDIAP-12284` unless validation proves the lifecycle fix can be implemented independently.
 
 - `PDIAP-12284` - Remove UIKit wrapping from XFlow
   Detail: `project-knowledge/02-work-items/pdiap-12284.md`
-  Current note: reopened after rollback and should be handled with `PDIAP-15836`. Work can begin, but Jira status movement waits for the next sprint; merge/release waits until after REST-transition consumer validation.
+  Current note: reopened after rollback and should be handled with `PDIAP-15836`. Quy already moved it into next sprint `26Q2.6`; work can begin now, but Jira status stays To Do until Thursday and merge/release waits until after REST-transition consumer validation.
 
 ## Backlog / Future Reference
 

project-knowledge/02-work-items/pdiap-12284.md

@@ -21,7 +21,8 @@ tags:
 ## Status
 
 - Reopened after rollback.
-- Jeff asked David to start working on this with `PDIAP-15836`, but not to move the active story to In Progress until the next sprint starts on Thursday after lunch.
+- 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.
 
 ---
 

project-knowledge/02-work-items/pdiap-15836.md

@@ -20,7 +20,8 @@ tags:
 ## Status
 
 - Approved, but should not be moved to In Progress until the next sprint starts
-- Jeff asked David to start working on the `PDIAP-15836` / `PDIAP-12284` implementation path, with Jira status movement deferred until Thursday after lunch
+- Quy already moved this story into the next sprint (`26Q2.6`); leave it in To Do until the sprint starts on Thursday
+- Jeff confirmed David can start the actual implementation work now, but must not move the story to In Progress until Thursday
 - Sequenced after `PDIAP-15838` source work, but merge/release is delayed until after REST-transition consumer validation
 - Sized at `8` points
 

project-knowledge/06-daily/2026-05-05.md

@@ -33,7 +33,8 @@ tags:
   - 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-12284` is the original UIKit-wrapping removal story and was reopened after rollback. David noted `PDIAP-15836` should be treated as blocked by `PDIAP-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 after lunch.
+  - 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-12284` branch. Expected merge timing is roughly 90-100 days from today unless Fidelity shortens the review windows.
 
 - Backlog triage