From a1cec956abecb0d348a2aa5024970e531611063e Mon Sep 17 00:00:00 2001 From: "david.delagneau" Date: Fri, 17 Apr 2026 07:37:33 -0600 Subject: [PATCH] feat: Update daily logs and work item documentation for PDIAP-15765 and add new daily entry for 2026-04-17 --- vault/01-current/current-work.md | 6 +++--- vault/01-current/work-items.md | 4 ++-- vault/02-work-items/pdiap-15765.md | 19 +++++++++---------- vault/06-daily/2026-04-16.md | 5 ++++- vault/06-daily/2026-04-17.md | 21 +++++++++++++++++++++ 5 files changed, 39 insertions(+), 16 deletions(-) create mode 100644 vault/06-daily/2026-04-17.md diff --git a/vault/01-current/current-work.md b/vault/01-current/current-work.md index e70390f..865b97a 100644 --- a/vault/01-current/current-work.md +++ b/vault/01-current/current-work.md @@ -2,7 +2,7 @@ type: current project: fidelity status: active -updated: 2026-04-16 +updated: 2026-04-17 tags: - current-work - fidelity @@ -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 -- Resume `PDIAP-15765` for the authenticated iOS-only `HybridYouthAccountOpening` / `TeenIdentityCheck` handling gap so iOS aligns with Android behavior +- 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 before returning to `PDIAP-15838` - 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 -- `PDIAP-15765` should stay out of Done until the PR is merged; Santosh approved it, but code-owner approval is still required before merge +- 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 - 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 diff --git a/vault/01-current/work-items.md b/vault/01-current/work-items.md index 989c32e..71dbdd7 100644 --- a/vault/01-current/work-items.md +++ b/vault/01-current/work-items.md @@ -2,7 +2,7 @@ type: current-work-items project: fidelity status: active -updated: 2026-04-16 +updated: 2026-04-17 tags: - current-work - work-item @@ -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: a small XFlowSDK PR is open for the iOS `birthDate` fallback, the immediate `HybridYouthAccountOpening` / `TeenIdentityCheck` issue appears fixed on the service side, and the separate cross-platform `HybridBrokerageAccountOpening` / `JointIdentityCheck` case remains out of scope for this fix. + 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. diff --git a/vault/02-work-items/pdiap-15765.md b/vault/02-work-items/pdiap-15765.md index ee2b0d0..5d06e70 100644 --- a/vault/02-work-items/pdiap-15765.md +++ b/vault/02-work-items/pdiap-15765.md @@ -8,7 +8,7 @@ systems: [xflowsdk, fid4, cogstore] workstreams: [ao-discourse, xflow-debugging] people: [jeff-dewitte, gurram-santosh, raj-sundararaj] related: [] -updated: 2026-04-16 +updated: 2026-04-17 tags: - work-item - fidelity @@ -19,10 +19,10 @@ tags: ## Status -- Active again -- Move back to In Progress on the next workday -- Small XFlowSDK compatibility PR opened for the iOS-side fix -- PR has Santosh approval, but still needs code-owner approval before merge and story completion +- 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 --- @@ -48,6 +48,7 @@ tags: - A minimal XFlowSDK fix was still prepared on April 15 so the iOS `.apxDateSelect` path also falls back to `birthDate` for a future release. - Jeff confirmed on April 15 that this minimal iOS fallback is the right fix direction for the Youth / `TeenIdentityCheck` case and approved opening the PR under the same story. - On April 16, Jeff decided the iOS PR should be the primary fix path for the Youth / `TeenIdentityCheck` issue rather than relying on a separate service rollout. +- Later on April 16, the PR received final approval, was merged, and the XFlow release was cut as version `2.8.48`. --- @@ -69,10 +70,8 @@ tags: ## Next Step -- Get the small XFlowSDK compatibility PR reviewed and released. -- Send one more AO working-group Teams summary that points to the Jira comment, Discourse comment, and PR while keeping the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue clearly out of the original Youth-fix scope. -- Keep the final AO working-group message very explicit about there being two flow scenarios: the Youth iOS-only issue now handled by the service change plus iOS fallback, and the separate cross-platform `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue. -- Update that AO working-group message so it now reflects the final framing: the original Youth issue is fixed on the iOS side, and the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue is the remaining service-side follow-up. -- Close the story with comments explaining that the immediate Youth issue was resolved on the service side and that the XFlowSDK fallback fix will be available in the next release. +- Get the remaining 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. - Consider a separate follow-up ticket for the cross-platform service-side issue if that path still stands after consumer confirmation. diff --git a/vault/06-daily/2026-04-16.md b/vault/06-daily/2026-04-16.md index 741e640..b10f948 100644 --- a/vault/06-daily/2026-04-16.md +++ b/vault/06-daily/2026-04-16.md @@ -4,7 +4,7 @@ project: fidelity date: 2026-04-16 focus: [ao-discourse, xflow-debugging] work-items: [pdiap-15765] -blockers: [code-owner-approval-required] +blockers: [] updated: 2026-04-16 tags: - daily @@ -41,3 +41,6 @@ tags: - Jeff asked Rashmi to revert the Youth-flow service change so the iOS-side PR can remain the single fix path for that issue. - David confirmed Rashmi reverted the QA change by publishing the earlier flow version, and local Fid4 validation with the iOS PR showed the `birthDate`-based validation now works as expected. - Jeff's preferred external summary is now very explicit: we went back and fixed their original iOS-only issue on the iOS side, while the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue is a new service-side problem that still needs its own follow-up. +- The `PDIAP-15765` PR later received final approval, was merged, and the release pipeline produced XFlow `2.8.48`. +- After the XFlow release, David updated XFlowViewMaker to `2.8.48`, opened the follow-up PR, and sent it for review so the fix can propagate through the consumer path. +- David also sent the final AO working-group update with links to the Jira story, Discourse ticket, and PR. diff --git a/vault/06-daily/2026-04-17.md b/vault/06-daily/2026-04-17.md new file mode 100644 index 0000000..b1e35ee --- /dev/null +++ b/vault/06-daily/2026-04-17.md @@ -0,0 +1,21 @@ +--- +type: daily +project: fidelity +date: 2026-04-17 +focus: [ao-discourse, consumer-integration, rest-migration] +work-items: [pdiap-15765, pdiap-15838] +blockers: [xflowviewmaker-code-owner-approval] +updated: 2026-04-17 +tags: + - daily + - fidelity +--- +# 2026-04-17 + +## Standup Draft Clarification + +- 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. +- 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.