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/project.md

@@ -0,0 +1,72 @@
+---
+type: project-context
+project: fidelity
+updated: 2026-04-17
+tags:
+  - fidelity
+  - context
+---
+# Project Context - Fidelity
+
+## Overview
+
+This workspace supports daily iOS engineering work for Fidelity.
+
+The product work happens outside this repository, usually from another machine. This repository exists to preserve context, track communication, and help AI generate accurate output for standups, Mattermost messages, Jira notes, and supervisor updates.
+
+---
+
+## Fidelity Ecosystem
+
+- Fid4 is the main consumer iOS app
+- XFlowSDK powers backend-driven UI flows
+- XFlowViewMaker is an adapter layer under evaluation for removal
+- FTFrameworks contains feature modules such as FTAccountOpen and FTTransfer
+- Cogstore is the configuration publishing/version-tracking platform used to inspect which flow-definition versions are live in QA or Production
+
+---
+
+## Stable Context Map
+
+- Core systems live under:
+  - `project-knowledge/03-context/systems/`
+- Durable workstreams live under:
+  - `project-knowledge/03-context/workstreams/`
+- Project-facing communication and process rules live under:
+  - `project-knowledge/03-context/process/`
+- Named people and role mapping live under:
+  - `project-knowledge/04-people/`
+
+The Slack archive has already been curated into these files so future sessions do not need to rediscover the same patterns from raw history.
+
+---
+
+## Current Priorities
+
+- REST migration is replacing GraphQL over time, but REST is still behind a feature flag
+- AO and Discourse issues require careful classification because many are incomplete, external, or auth-dependent
+- XFlow debugging remains dynamic because behavior changes by entry point, authentication state, backend configuration, and consumer integration
+- Consumer validation often depends on Fid4, FT modules, and version propagation, not just SDK behavior
+
+---
+
+## Workspace Use
+
+This machine is used to:
+
+- maintain current project context
+- record findings from work performed elsewhere
+- capture communication that changes technical understanding
+- prepare polished updates for the current manager or stakeholder
+- generate standups with better context coverage
+
+This means the context files should hold durable engineering knowledge, while `project-knowledge/06-daily/` and `project-knowledge/01-current/` hold the moving day-to-day view.
+
+---
+
+## First Files To Read
+
+- `project-knowledge/03-context/index.md`
+- `project-knowledge/03-context/workstreams/index.md`
+- `project-knowledge/03-context/process/communication.md`
+- `project-knowledge/04-people/index.md`