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/ios/index.md

@@ -0,0 +1,36 @@
+---
+type: guidance-index
+project: fidelity
+status: active
+updated: 2026-04-17
+tags:
+  - ios
+  - fidelity
+---
+# iOS And Swift Context
+
+## Goal
+
+Help the agent answer Swift and iOS programming questions with current best practices while still respecting Fidelity/XFlow project constraints.
+
+---
+
+## Files
+
+- [current-practices.md](./current-practices.md)
+  Rules for staying current with Apple and Swift best practices.
+
+- [project-swift-guidance.md](./project-swift-guidance.md)
+  Fidelity-specific guidance for applying Swift/iOS advice in this workspace.
+
+- [cocoapods-dependency-management.md](./cocoapods-dependency-management.md)
+  CocoaPods, private podspec repo, and dependency-resolution guidance for Fidelity release and consumer integration work.
+
+---
+
+## Usage
+
+- Use these files before answering Swift, SwiftUI, iOS architecture, testing, concurrency, or debugging questions.
+- Use the CocoaPods guidance whenever the question touches release propagation, podspecs, dependency conflicts, Fid4 resolution, or FTFrameworks consumer updates.
+- When a recommendation depends on current Apple APIs, prefer official Apple or Swift documentation before making strong claims.
+- Keep project constraints visible: XFlow is backend-driven, Fid4 is consumer validation, and REST/GraphQL migration constraints may affect architecture.