Add daily logs and templates for project fidelity

- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.

agent-memory/integrations/mem9.md

@@ -15,7 +15,7 @@ Use mem9 as a cross-session, cross-agent recall layer without replacing the work
 
 ## Source Of Truth
 
-`project-knowledge/` remains the canonical human-readable Fidelity project memory.
+`workspaces/fidelity/project-knowledge/` remains the canonical human-readable Fidelity project memory.
 
 `agent-memory/` remains the canonical operating memory for agent behavior, workflows, promotion rules, and integration guidance.
 
@@ -46,7 +46,7 @@ Do not bulk-import raw inboxes, generated sync output, full chat transcripts, or
 
 1. Recall mem9 early for user preferences and relevant workspace history.
 2. Load hot Markdown context from `AGENTS.md` / `opencode.json` instructions.
-3. For current-work questions, still inspect `project-knowledge/01-current/current-work.md` and the latest relevant daily note.
+3. For current-work questions, still inspect `workspaces/fidelity/project-knowledge/01-current/current-work.md` and the latest relevant daily note.
 4. Answer or act from verified context.
 5. When the interaction adds durable knowledge, update canonical Markdown first; store a compact mem9 memory only if it improves future recall.