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.

workflows/daily-context-sync.md

@@ -11,6 +11,6 @@ Keep this workspace aligned with work happening on another machine so AI output
 1. Capture the main tasks worked on during the day.
 2. Record key debugging findings and open questions.
 3. Sync or copy relevant communication evidence into the inbox or daily log as summarized notes.
-4. Update `vault/01-current/current-work.md` if priorities or concerns changed.
-5. Add any stable learning to `vault/03-context/`, `vault/04-people/`, or `vault/05-decisions/`; if the learning changes reusable workspace behavior, update `core/`, commands, prompts, skills, agent rules, or `vault/03-context/process/` too.
+4. Update `project-knowledge/01-current/current-work.md` if priorities or concerns changed.
+5. Add any stable learning to `project-knowledge/03-context/`, `project-knowledge/04-people/`, or `project-knowledge/05-decisions/`; if the learning changes reusable workspace behavior, update `agent-memory/`, `core/`, commands, prompts, skills, or agent rules too.
 6. Before asking AI for a standup or manager update, confirm the log reflects the latest state.