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/workflows/obsidian-mcp-migration.md

@@ -11,7 +11,7 @@ tags: [obsidian, mcp, migration, memory]
 
 Replace the current Obsidian CLI-backed adapter path with an Obsidian MCP-first integration while preserving the workspace memory model:
 
-- `project-knowledge/` remains the canonical source of truth
+- `workspaces/fidelity/project-knowledge/` remains the canonical source of truth
 - `scripts/memory/` remains the stable workspace memory contract
 - direct Markdown edits remain the safe fallback for precise curation
 - Obsidian stays an adapter/navigation layer, not a second memory store
@@ -66,7 +66,7 @@ The migration should change the adapter, not the memory model.
 
 - Do not move canonical memory out of Markdown
 - Do not encode promotion rules into the MCP layer
-- Do not make `project-knowledge/` depend on Obsidian-only storage
+- Do not make `workspaces/fidelity/project-knowledge/` depend on Obsidian-only storage
 - Do not remove direct Markdown editing as a fallback
 - Do not delete the current scripts until MCP coverage is validated in real use
 
@@ -116,7 +116,7 @@ Current Phase 1 checklist:
 - [x] Add OpenCode MCP config using `OBSIDIAN_API_KEY` environment substitution.
 - [x] Export `OBSIDIAN_API_KEY` in the shell that launches OpenCode.
 - [x] Restart OpenCode and confirm `opencode mcp list` shows `obsidian` connected.
-- [x] Validate read/search tools against `project-knowledge/` notes.
+- [x] Validate read/search tools against `workspaces/fidelity/project-knowledge/` notes.
 - [x] Validate write/append/delete behavior on a disposable test note before touching canonical memory.
 - [ ] Determine whether Bases/properties/backlinks/template behavior needs to remain on the existing CLI/direct-Markdown path.
 
@@ -208,9 +208,9 @@ Delete later only if truly unused:
 
 ### Keep
 
-- `project-knowledge/.obsidian/`
-- `project-knowledge/08-bases/*.base`
-- `project-knowledge/09-templates/`
+- `workspaces/fidelity/project-knowledge/.obsidian/`
+- `workspaces/fidelity/project-knowledge/08-bases/*.base`
+- `workspaces/fidelity/project-knowledge/09-templates/`
 - `scripts/memory/`
 
 ### Deprecate then remove