Add project-knowledge structure and templates

- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People."
- Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views.
- Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation.
- Updated scripts and prompts to reflect the new project-knowledge directory structure.
- Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps.
- Ensured all references in workflows and scripts point to the new project-knowledge paths.

project-knowledge/02-work-items/index.md

@@ -0,0 +1,39 @@
+---
+type: work-item-index
+project: fidelity
+updated: 2026-04-16
+tags:
+  - work-item
+  - map
+---
+# Work Item Index
+
+## Goal
+
+Provide a quick view of active and recently relevant Jira-linked work while keeping the full detail in one file per ticket.
+
+---
+
+## Active
+
+- [pdiap-14859.md](./pdiap-14859.md)
+  `PDIAP-14859` `Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation` spike wrap-up work around dual UIKit/SwiftUI support, dynamic `UIHostingController` removal, consumer rollout planning, and linking the final result documents.
+
+- [pdiap-15838.md](./pdiap-15838.md)
+  `PDIAP-15838` next story to work on; approved scope removes Apollo and GraphQL-specific iOS transport code while leaving REST.
+
+- [pdiap-15836.md](./pdiap-15836.md)
+  `PDIAP-15836` approved follow-up story for dismissal delegate lifecycle sequencing in pure SwiftUI; comes after `PDIAP-15838`.
+
+## Active / Reopened
+
+- [pdiap-15765.md](./pdiap-15765.md)
+  `PDIAP-15765` authenticated-only DOB issue in `HybridYouthAccountOpening` / `TeenIdentityCheck`; reopened around the iOS-only handling gap while the separate cross-platform `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario stays out of scope.
+
+---
+
+## Usage
+
+- Read this file first for active ticket context.
+- Open the specific ticket file when you need exact scope, sequencing, or communication wording.
+- Update the per-ticket file first when ticket context changes materially.