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/03-context/process/pull-requests.md

@@ -0,0 +1,43 @@
+---
+type: process
+project: fidelity
+status: active
+updated: 2026-04-16
+tags:
+  - process
+  - fidelity
+---
+# Pull Requests
+
+## xflow-for-ios PR Template
+
+The `xflow-for-ios` repo PR form uses this structure:
+
+- `## What`
+  - What does the PR do?
+  - Is it a bug fix, new feature, refactor, or something else?
+- `## Why`
+  - Why this PR is needed?
+- `## How`
+  - How is it doing what it does?
+  - How to test, how to integrate, any relevant compromises, etc.?
+- `### Changes details`
+  - bullet list such as `Detail one`, `Detail two`
+- `## Missed anything?`
+  - checklist including:
+    - explained the purpose of the PR
+    - self-reviewed the PR
+    - added or updated test cases
+    - informed of breaking changes, testing, and migrations if applicable
+    - updated documentation if applicable
+    - attached screenshots if applicable
+    - resolved SwiftLint warnings introduced by the commit
+
+## Current Small-Fix Example
+
+For the April 15, 2026 iOS validation fallback fix, the code change is a one-line update in `XFlowViewAdapterRepresentable.swift` for `.apxDateSelect`:
+
+- before: only `validationDictionary?["validations"]`
+- after: `validationDictionary?["validations"] ?? validationDictionary?["birthDate"]`
+
+This should be framed as a small compatibility bug fix for AO-style payloads, not as a broader Android-parity refactor.