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/05-decisions/rest-vs-graphql.md

@@ -0,0 +1,40 @@
+---
+type: decision
+project: fidelity
+status: accepted
+title: "REST vs GraphQL"
+updated: 2026-04-16
+tags:
+  - decision
+  - fidelity
+---
+# REST vs GraphQL
+
+## Decision
+
+Deprecate GraphQL and migrate to REST progressively.
+
+---
+
+## Constraints
+
+- REST is behind a feature flag
+- GraphQL remains fallback
+- Behavior parity matters during migration
+
+---
+
+## Communication Rule
+
+When reporting findings:
+
+- state whether REST was confirmed enabled
+- avoid implying REST is the default path
+- call out when behavior may still come from GraphQL fallback
+
+---
+
+## Follow-up
+
+- Remove Apollo when migration is safe
+- Retire GraphQL-specific tests only after parity is confirmed