feat: Clarify code-owner approval requirements for PDIAP-15765 in documentation

vault/01-current/current-work.md

@@ -18,7 +18,7 @@ tags:
 - Follow up on active tickets through `vault/02-work-items/`, especially `PDIAP-14859`, `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838`
 - Wrap up `PDIAP-14859` by publishing the approved rollout document, linking the spike-result documents and follow-up story, then closing the spike
 - After the immediate `PDIAP-14859` closeout and `PDIAP-15765` resume work, return to `PDIAP-15838`; `PDIAP-15836` comes later
-- Finish `PDIAP-15765` propagation after the XFlow `2.8.48` release by getting the remaining XFlowViewMaker code-owner approval, then run the pipeline and update Fid4 while continuing `PDIAP-15838` in parallel where possible
+- Finish `PDIAP-15765` propagation after the XFlow `2.8.48` release by getting the remaining FTFrameworks code-owner approval on the XFlowViewMaker PR, then run the pipeline and update Fid4 while continuing `PDIAP-15838` in parallel where possible
 - 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
@@ -35,7 +35,7 @@ tags:
 - When describing the XFlowSDK fallback PR, frame it as a compatibility improvement for similar future `birthDate` payloads, not as a fix for the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue
 - The Youth / `TeenIdentityCheck` issue was iOS-only; do not describe it as reproducing on both platforms
 - The service-side payload update and the XFlowSDK fallback PR address the same Youth / `TeenIdentityCheck` issue; do not split them into separate Youth issues when summarizing scope
-- The `PDIAP-15765` compatibility fix is now merged and released in XFlow `2.8.48`; the remaining near-term work is getting the last XFlowViewMaker approval, then running the pipeline and updating Fid4
+- The `PDIAP-15765` compatibility fix is now merged and released in XFlow `2.8.48`; the remaining near-term work is getting the last FTFrameworks code-owner approval on the XFlowViewMaker PR, then running the pipeline and updating Fid4
 - Before closing out the AO thread, send one more working-group Teams reply that summarizes the original iOS issue, links the Jira comment, Discourse comment, and PR, and separates the remaining `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue
 - The `HybridBrokerageAccountOpening` / `JointIdentityCheck` rule-content issue appears unchanged between QA and Production in Cogstore and should be treated as the remaining service-side follow-up
 

vault/01-current/work-items.md

@@ -32,4 +32,4 @@ Update the per-ticket files first when scope, status, sequencing, or communicati
 
 - `PDIAP-15765` - AO DOB field error not showing investigation
   Detail: `vault/02-work-items/pdiap-15765.md`
-  Current note: the small XFlowSDK iOS `birthDate` fallback was merged and released in XFlow `2.8.48`; the XFlowViewMaker follow-up PR is open and partially approved but still needs one code-owner approval before merge, then the pipeline and Fid4 update still need to happen.
+  Current note: the small XFlowSDK iOS `birthDate` fallback was merged and released in XFlow `2.8.48`; the XFlowViewMaker follow-up PR is open and partially approved but still needs one FTFrameworks code-owner approval before merge, then the pipeline and Fid4 update still need to happen.

vault/02-work-items/pdiap-15765.md

@@ -22,7 +22,7 @@ tags:
 - Active closeout
 - Small XFlowSDK compatibility fix merged and released in XFlow `2.8.48`
 - XFlowViewMaker was updated to the new XFlow version and a follow-up PR was opened
-- The XFlowViewMaker PR already has some approvals, but one code-owner approval is still required before merge
+- The XFlowViewMaker PR already has some approvals, but one FTFrameworks code-owner approval is still required before merge
 
 ---
 
@@ -70,7 +70,7 @@ tags:
 
 ## Next Step
 
-- Get the remaining code-owner approval on the XFlowViewMaker follow-up PR.
+- Get the remaining FTFrameworks code-owner approval on the XFlowViewMaker follow-up PR.
 - Run the remaining pipeline/release steps after the PR merges.
 - Update Fid4 so the released XFlow `2.8.48` change propagates through the consumer path.
 - Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of the client-fix scope unless later evidence proves it is part of the same issue.

vault/06-daily/2026-04-17.md

@@ -16,9 +16,10 @@ tags:
 
 - David clarified that the XFlowViewMaker follow-up work for `PDIAP-15765` is further along than the earlier summary implied.
 - The XFlowViewMaker PR is already open and has some approvals.
-- One code-owner approval is still required before the PR can merge.
+- One FTFrameworks code-owner approval is still required before the PR can merge.
 - After that approval, the remaining work is to run the pipeline and update Fid4 so the XFlow `2.8.48` change propagates through the consumer path.
 - `PDIAP-15838` remains the next story after the `PDIAP-15765` propagation steps are in a good place.
+- David's current plan is to ping Tauf for that remaining approval.
 
 ## Standup Wording Feedback