docs: complete accountlink UIKit validation, add daily log, and document force-path testing guide

DECOMMISSIONED.md

@@ -0,0 +1,24 @@
+# Decommissioned Workspace
+
+This repository is no longer the active AIWorkspace runtime.
+
+As of 2026-05-22, the active split is:
+
+- reusable core: `/Users/david/Developer/ai-workspace`
+- Fidelity context pack: `/Users/david/Developer/fidelity-ai-context`
+- local project registry: `~/Library/Application Support/AIWorkspace/projects.json`
+- runtime state: `~/Library/Application Support/AIWorkspace/runtime/`
+- logs: `~/Library/Logs/AIWorkspace/`
+
+Do not start services from this repository unless intentionally rolling back.
+
+Use the new core instead:
+
+```bash
+cd /Users/david/Developer/ai-workspace
+python3 scripts/aiw/services.py status --project fidelity
+python3 scripts/aiw/services.py doctor --project fidelity
+```
+
+The old profile-based service manager may report services as `externally running`
+because the new core owns the same health ports.

README.md

@@ -1,5 +1,10 @@
 # AI Workspace
 
+> **Decommissioned:** this repository is no longer the active AIWorkspace runtime.
+> Active services now run from `/Users/david/Developer/ai-workspace`, and Fidelity
+> context lives in `/Users/david/Developer/fidelity-ai-context`. See
+> [`DECOMMISSIONED.md`](DECOMMISSIONED.md) before using this repo.
+
 AI Workspace is a local, profile-based companion workspace for AI-assisted professional work. It keeps project memory, raw evidence, local services, and AI client integrations organized so agents can work from current, auditable context instead of chat history alone.
 
 The first real profile in this repository is `fidelity`, but the reusable model is intentionally project-independent.

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

@@ -37,9 +37,9 @@ tags:
   - `HybridBrokerageAccountOpening`: Fully validated on both UIKit and SwiftUI hosts with full lifecycle/dismissal confirmed.
   - `HybridYouthAccountOpening`: Fully validated on both UIKit and SwiftUI hosts with full lifecycle/dismissal confirmed, resolving the previous dismissal coverage gap.
 - Remaining validation gaps on the combined PDIAP-12284 / PDIAP-15836 branch include:
-  - `accountlink` (P2P Transfer Flow): UIKit host validation is pending (SwiftUI host and dismissal are validated).
   - `AODeeplinkLaunchView` (AO Deep-Link with Native/Web Toggle): untested on both branches (Native ON/OFF) and dismissal.
   - Fid4 surface attribution for launch wrappers and common-launch flows.
+- Session 017 on May 22 completed `accountlink` (P2P Transfer Flow) validation on UIKit host (confirming dismissal/cleanup) using a forced-path setup, and Copilot updated the validation checklist with a local testing force-path guide for FTP2PTransfer and FTTransfer.
 - Draft PRs were opened for XFlowSDK and XFlowViewMaker on May 20 while validation continues.
 - 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

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

@@ -41,7 +41,7 @@ tags:
   - `HybridBloomAccountOpening` (Affiliation-Gated AO Modal): Fully validated in both UIKit host (Session 008) and SwiftUI host (Session 009) with full dismissal/cleanup confirmed.
   - `HybridBrokerageAccountOpening`: Fully validated on both UIKit and SwiftUI hosts with full lifecycle/dismissal confirmed.
   - `HybridYouthAccountOpening`: Fully validated on both UIKit and SwiftUI hosts with full lifecycle/dismissal confirmed, resolving the previous dismissal coverage gap.
-- Remaining gaps: `accountlink` UIKit host, `AODeeplinkLaunchView` (both toggle branches and dismissal), and launch wrappers/common-launch flows. Draft PRs were opened for XFlowSDK and XFlowViewMaker on May 20 while validation continues.
+- Remaining gaps: `AODeeplinkLaunchView` (both toggle branches and dismissal) and launch wrappers/common-launch flows. `accountlink` UIKit host validation was completed on May 22 (Session 017) using a forced-path setup, and Copilot updated the entry-point validation checklist with a local testing force-path guide. Draft PRs were opened for XFlowSDK and XFlowViewMaker on May 20 while validation continues.
 
 ---
 

workspaces/fidelity/project-knowledge/06-daily/2026-05-22.md

@@ -0,0 +1,29 @@
+---
+type: daily
+project: fidelity
+date: 2026-05-22
+updated: 2026-05-22
+focus:
+  - PDIAP-12284
+  - PDIAP-15836
+work-items:
+  - PDIAP-12284
+  - PDIAP-15836
+blockers: []
+tags:
+  - daily
+  - fidelity
+---
+
+# 2026-05-22
+
+## Findings
+
+- Session 017 validated the deep-link-driven `accountlink` lifecycle on the UIKit host using debug force-path environment variables (`XFLOW_SMOKE_FORCE_LINK_RECIPIENT=1`, `XFLOW_SMOKE_FORCE_P2P_XFLOW=1`) and `iOS_Native_Link` OFF.
+- Verified that the dismissal completion sequence operates correctly on the UIKit host mode, ensuring cleanup and callback execution via `activitySessionCleared`.
+- Copilot updated the `xflow-entrypoint-validation-checklist.md` (adding 39 lines starting at line 317) with a dedicated "Consumer Framework Force-Path Guide" detailing code modifications and debug overrides required in `FTP2PTransfer` (`PaymentsRootViewModel.swift`, `PaymentsExperienceViewModel+ErrorView.swift`, `P2PTransferNetworkClient.swift`) and `FTTransfer` (`BankInformationViewModel.swift`).
+- Reviewed secret scanning alerts: The 1 Critical finding in SecureTrak with a 72-hour deadline belongs to the backend `ap141020-xflow-model-state` repository, not iOS. The iOS repository ([pr100660-xflow-for-ios](file:///Users/david/Developer/fidelity-ai-workspace/workspaces/fidelity/project-knowledge/03-context/systems/xflowsdk.md)) alerts are just the two Google API Key findings in `MockPageWithHiddenToogle` on an orphan branch (backend-provided token flagged as public leak by GitHub) and carry no immediate urgency.
+
+## Validation To Run
+
+- Continue validating remaining untested paths (e.g., `AODeepLinkLaunchView` native branches, common-launch routes like `cd` and `psta`) as planned.