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/behavior/agent-behavior.md

@@ -27,10 +27,10 @@ This applies to:
 - debugging discussions
 - corrections to previous understanding
 
-The agent must not wait for a separate promotion command. The agent should proactively update `project-knowledge/` (including 01-current, 02-work-items, 03-context, 04-people, 06-daily) within the same conversational turn when new information is clear, durable, and the destination is obvious.
+The agent must not wait for a separate promotion command. The agent should proactively update `workspaces/fidelity/project-knowledge/` (including 01-current, 02-work-items, 03-context, 04-people, 06-daily) within the same conversational turn when new information is clear, durable, and the destination is obvious.
 
-- When editing `project-knowledge/`, write as a human engineer maintaining shared project documentation.
-- Keep agent-operating logic out of `project-knowledge/`; store that logic in prompts, commands, skills, agents, or `agent-memory/`.
+- When editing `workspaces/fidelity/project-knowledge/`, write as a human engineer maintaining shared project documentation.
+- Keep agent-operating logic out of `workspaces/fidelity/project-knowledge/`; store that logic in prompts, commands, skills, agents, or `agent-memory/`.
 - Answer-first rule: when the user's main goal is analysis, review, translation, or drafting, answer first unless persistence is required to avoid losing a clear durable fact.
 - Do not create a brand-new canonical note during the critical path of the answer unless the user explicitly asked to save the fact or the new note is the smallest correct update.
 - Prefer updating an existing canonical note over creating a new file when both are valid.
@@ -71,7 +71,7 @@ Avoid low-value learning-session questions such as:
 - whether a specific PR was approved today
 - whether a ticket moved columns today
 - what the next standup line should be
-- temporary sequencing questions that belong in `project-knowledge/01-current/` or `project-knowledge/06-daily/`
+- temporary sequencing questions that belong in `workspaces/fidelity/project-knowledge/01-current/` or `workspaces/fidelity/project-knowledge/06-daily/`
 
 Prefer high-value questions such as:
 
@@ -130,7 +130,7 @@ Examples:
 - A standup formatting correction should update `prompts/standup.md` and the shared workflow in `.agents/workflows/standup.md`.
 - A Mattermost freshness correction should update the Mattermost command/plugin instructions.
 - A Copilot prompt-structure correction should update `prompts/copilot-prompt.md`, `.agents/workflows/copilot-prompt.md`, or the shared skill/rule source.
-- A Swift answer-quality correction should update the relevant iOS skill or `project-knowledge/03-context/ios/` guidance.
+- A Swift answer-quality correction should update the relevant iOS skill or `workspaces/fidelity/project-knowledge/03-context/ios/` guidance.
 
 Keep the daily log as evidence of what happened, but make the reusable behavior live in the file that controls that behavior.
 
@@ -138,7 +138,7 @@ Keep the daily log as evidence of what happened, but make the reusable behavior
 
 ## File Selection
 
-### `project-knowledge/06-daily/YYYY-MM-DD.md`
+### `workspaces/fidelity/project-knowledge/06-daily/YYYY-MM-DD.md`
 
 Default destination for:
 
@@ -148,7 +148,7 @@ Default destination for:
 - story and approval movement
 - context that is important now but may evolve later
 
-### `project-knowledge/01-current/current-work.md`
+### `workspaces/fidelity/project-knowledge/01-current/current-work.md`
 
 Use when the fact changes the active work window, including:
 
@@ -157,28 +157,28 @@ Use when the fact changes the active work window, including:
 - current blockers or debugging constraints
 - manager direction that changes the next few days of work
 
-### `project-knowledge/02-work-items/*.md` and `project-knowledge/01-current/work-items.md`
+### `workspaces/fidelity/project-knowledge/02-work-items/*.md` and `workspaces/fidelity/project-knowledge/01-current/work-items.md`
 
-Use `project-knowledge/02-work-items/*.md` as the canonical memory for current Jira-linked work that should remain easy to reference across sessions, especially:
+Use `workspaces/fidelity/project-knowledge/02-work-items/*.md` as the canonical memory for current Jira-linked work that should remain easy to reference across sessions, especially:
 
 - Jira IDs
 - approved or explicit titles
 - currently relevant status notes
 - current points or scope notes
 
-Use `project-knowledge/01-current/work-items.md` as the summary view of what is active now.
+Use `workspaces/fidelity/project-knowledge/01-current/work-items.md` as the summary view of what is active now.
 
 These files should help standups and manager updates mention work items precisely.
 
-### `project-knowledge/03-context/project.md`
+### `workspaces/fidelity/project-knowledge/03-context/project.md`
 
 Use for durable project knowledge that should survive beyond the current work window.
 
-### `project-knowledge/04-people/manager.md`
+### `workspaces/fidelity/project-knowledge/04-people/manager.md`
 
 Use only when a communication preference or manager expectation becomes stable enough to reuse repeatedly.
 
-### `project-knowledge/04-people/index.md` and `project-knowledge/04-people/*.md`
+### `workspaces/fidelity/project-knowledge/04-people/index.md` and `workspaces/fidelity/project-knowledge/04-people/*.md`
 
 Use these files for:
 
@@ -192,7 +192,7 @@ When the role is not explicit, store:
 - what kinds of topics they influence
 - how they affect approvals, scope, debugging, or communication
 
-### `project-knowledge/05-decisions/*.md`
+### `workspaces/fidelity/project-knowledge/05-decisions/*.md`
 
 Use for explicit confirmed decisions with ongoing impact.