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.

.opencode/commands/slack-import.md

@@ -27,14 +27,14 @@ Read:
 @core/README.md
 @core/memory/operational-memory.md
 @core/integrations/communication-model.md
-@vault/01-current/current-work.md
-@vault/01-current/work-items.md
-@vault/03-context/project.md
-@vault/03-context/systems/index.md
-@vault/03-context/workstreams/index.md
-@vault/03-context/process/index.md
-@vault/04-people/index.md
-@vault/04-people/manager.md
+@project-knowledge/01-current/current-work.md
+@project-knowledge/01-current/work-items.md
+@project-knowledge/03-context/project.md
+@project-knowledge/03-context/systems/index.md
+@project-knowledge/03-context/workstreams/index.md
+@project-knowledge/03-context/process/index.md
+@project-knowledge/04-people/index.md
+@project-knowledge/04-people/manager.md
 
 Imported summary, if present:
 
@@ -55,7 +55,7 @@ Instructions:
   - durable role/person associations
   - recurring architecture or debugging patterns
   - past approvals or decisions that still matter
-- create or update `vault/04-people/*.md` when the archive shows a human repeatedly contributing across channels, years, or high-signal technical/process discussions
+- create or update `project-knowledge/04-people/*.md` when the archive shows a human repeatedly contributing across channels, years, or high-signal technical/process discussions
 - store people conservatively:
   - exact role only when explicitly supported by the archive
   - otherwise store collaboration pattern, communication style, and project relationship
@@ -70,7 +70,7 @@ Instructions:
 - avoid promoting outdated daily status unless it changes current understanding
 - update existing memory when the archive clarifies or corrects it
 - if historical facts are ambiguous or likely outdated, summarize them as archived context instead of promoting them
-- write promoted memory to `vault/`
+- write promoted memory to `project-knowledge/`
 
 Return: