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/skills/copilot-prompt-engineering/SKILL.md

@@ -18,10 +18,10 @@ Use this skill when the user wants a prompt for another AI assistant, GitHub Cop
    - test strategy
    - story/PR drafting
 2. Pull only the relevant context:
-   - `vault/02-work-items/` for ticket-specific context
-   - `vault/03-context/systems/` for component context
-   - `vault/03-context/workstreams/` for recurring constraints
-   - `vault/03-context/ios/` for Swift/iOS guidance
+   - `project-knowledge/02-work-items/` for ticket-specific context
+   - `project-knowledge/03-context/systems/` for component context
+   - `project-knowledge/03-context/workstreams/` for recurring constraints
+   - `project-knowledge/03-context/ios/` for Swift/iOS guidance
 3. Make the prompt self-contained.
 4. Tell the target AI what to inspect before acting.
 5. State constraints, non-goals, and validation expectations.