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.

core/memory/operational-memory.md

@@ -17,7 +17,7 @@ Use for same-day progress, findings, evolving reproduction notes, and work that
 Default path pattern:
 
 ```text
-vault/06-daily/YYYY-MM-DD.md
+project-knowledge/06-daily/YYYY-MM-DD.md
 ```
 
 ### `state`
@@ -27,8 +27,8 @@ Use for current priorities, active blockers, near-term constraints, and communic
 Default paths:
 
 ```text
-vault/01-current/current-work.md
-vault/01-current/work-items.md
+project-knowledge/01-current/current-work.md
+project-knowledge/01-current/work-items.md
 ```
 
 ### `work-items`
@@ -38,7 +38,7 @@ Use for canonical memory about active tickets, tasks, stories, investigations, o
 Default path pattern:
 
 ```text
-vault/02-work-items/<id-or-slug>.md
+project-knowledge/02-work-items/<id-or-slug>.md
 ```
 
 ### `stable-context`
@@ -48,7 +48,7 @@ Use for durable project knowledge that should survive beyond the current work wi
 Default path pattern:
 
 ```text
-vault/03-context/<domain>/*.md
+project-knowledge/03-context/<domain>/*.md
 ```
 
 ### `people`
@@ -58,7 +58,7 @@ Use for repeated collaborators, role mappings, manager/stakeholder context, and
 Default path pattern:
 
 ```text
-vault/04-people/*.md
+project-knowledge/04-people/*.md
 ```
 
 ### `decisions`
@@ -68,7 +68,7 @@ Use for confirmed decisions with ongoing impact.
 Default path pattern:
 
 ```text
-vault/05-decisions/*.md
+project-knowledge/05-decisions/*.md
 ```
 
 ### `tooling-behavior`
@@ -82,11 +82,12 @@ Default path patterns:
 .opencode/agents/*.md
 .opencode/skills/*/SKILL.md
 prompts/*.md
-vault/00-start/*.md
-vault/03-context/process/*.md
+agent-memory/**/*.md
+core/**/*.md
+scripts/**/*.md
 ```
 
-Raw evidence stays outside `vault/`; promoted memory is written to `vault/`.
+Raw evidence stays outside `project-knowledge/`; promoted memory is written to `project-knowledge/`.
 
 ---
 
@@ -171,13 +172,13 @@ Examples:
 - prompt-engineering correction -> update the AI prompt command or skill
 - memory routing correction -> update memory rules and context-maintenance guidance
 
-The daily log may preserve evidence, but reusable behavior must live in the command, prompt, skill, agent, or knowledge file that enforces it.
+The daily log may preserve evidence, but reusable behavior must live in the command, prompt, skill, agent, or agent-memory file that enforces it.
 
 The agent should also identify recurring quality gaps proactively. If an answer reveals that the workspace lacks a rule, source anchor, command behavior, skill guidance, or memory model needed for better future output, the agent should propose the improvement and apply it when the correct destination is clear.
 
 For technical topics, recurring gaps often belong in:
 
-- domain-specific guidance under `vault/03-context/`
+- domain-specific guidance under `project-knowledge/03-context/`
 - reusable skills under `.opencode/skills/`
-- agent behavior rules under `.opencode/agents/` or `AGENTS.md`
+- agent behavior rules under `.opencode/agents/`, `AGENTS.md`, or `agent-memory/`
 - source anchors for official/current documentation