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/standup.md

@@ -11,15 +11,15 @@ First, refresh Mattermost context before drafting:
 Read:
 
 @prompts/standup.md
-@vault/00-start/start-here.md
-@vault/01-current/current-work.md
-@vault/01-current/work-items.md
-@vault/03-context/project.md
-@vault/03-context/workstreams/index.md
-@vault/03-context/workstreams/flow-page-references.md
-@vault/03-context/process/communication.md
-@vault/03-context/process/jira-story-rules.md
-@vault/04-people/manager.md
+@project-knowledge/00-start/start-here.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/workstreams/index.md
+@project-knowledge/03-context/workstreams/flow-page-references.md
+@project-knowledge/03-context/process/communication.md
+@project-knowledge/03-context/process/jira-story-rules.md
+@project-knowledge/04-people/manager.md
 
 Previous workday Mattermost context, if present:
 
@@ -27,7 +27,7 @@ Previous workday Mattermost context, if present:
 
 Today's log, if present:
 
-!`if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi`
+!`if [ -f project-knowledge/06-daily/$(date +%F).md ]; then cat project-knowledge/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi`
 
 Latest Mattermost context, preferring inbox and falling back to generated JSONL:
 
@@ -35,7 +35,7 @@ Latest Mattermost context, preferring inbox and falling back to generated JSONL:
 
 Detailed active work item files, if available:
 
-!`if [ -d vault/02-work-items ]; then for f in vault/02-work-items/*.md; do case "$f" in *README.md|*index.md) continue;; esac; echo "\n### $f"; cat "$f"; done; else echo "No work item files available."; fi`
+!`if [ -d project-knowledge/02-work-items ]; then for f in project-knowledge/02-work-items/*.md; do case "$f" in *README.md|*index.md) continue;; esac; echo "\n### $f"; cat "$f"; done; else echo "No work item files available."; fi`
 
 Before drafting:
 
@@ -48,7 +48,7 @@ Before drafting:
 - if documentation or root cause updates directly support a story, roll them into that story's update instead of listing them separately
 - exclude items that are not directly tied to a story unless they are true blockers
 - when one Jira item has multiple concrete updates, group them under one top-level `JIRA-ID - Title` bullet with indented markdown sub-bullets instead of repeating the same Jira line
-- use `vault/03-context/workstreams/flow-page-references.md` to preserve real flow/page identifiers when shorthand appears in logs or messages
+- use `project-knowledge/03-context/workstreams/flow-page-references.md` to preserve real flow/page identifiers when shorthand appears in logs or messages
 - for standups that will also be sent to Teams, prefer plain language over internal implementation jargon; avoid unexplained terms like `fallback`
 - if work is in release-process waiting state, show the parallel story work explicitly instead of implying idle waiting