feat: Add Fidelity workspace agent and context management commands

- Introduced a primary agent for the Fidelity AI Workspace to maintain context and support daily engineering tasks.
- Created commands for loading workspace context, drafting updates for Jeff, and logging daily notes.
- Implemented translation and standup generation commands to enhance communication clarity.
- Developed a compaction plugin to preserve essential workspace context during sessions.
- Established a structured approach for managing project knowledge, communication rules, and decision-making processes.
- Updated README and project structure to reflect new workflows and usage guidelines.

workflows/daily-context-sync.md

@@ -0,0 +1,16 @@
+# Daily Context Sync
+
+## Goal
+
+Keep this workspace aligned with work happening on another machine so AI output stays current and useful.
+
+---
+
+## Steps
+
+1. Capture the main tasks worked on during the day.
+2. Record key debugging findings and open questions.
+3. Copy relevant Mattermost communication into the daily log as summarized notes.
+4. Update `ai/state/current.md` if priorities or concerns changed.
+5. Add any stable learning to `ai/context/` or `knowledge/`.
+6. Before asking AI for a standup or manager update, confirm the log reflects the latest state.

workflows/debug-flow.md

@@ -0,0 +1,21 @@
+# Debugging Flow Strategy
+
+## Goal
+
+Turn incomplete reports into clear, reproducible debugging context that can be shared accurately.
+
+---
+
+## Steps
+
+1. Identify the entry point.
+2. Confirm whether the user is authenticated or non-authenticated.
+3. Capture the reported behavior exactly as described.
+4. Reproduce the issue if possible.
+5. Compare expected versus actual behavior.
+6. Check whether the same behavior exists in main.
+7. Classify the issue as:
+   - external report
+   - existing behavior
+   - regression
+8. Write the result using Context, Observation, and Action.

workflows/manager-update.md

@@ -0,0 +1,26 @@
+# Manager Update Workflow
+
+## Goal
+
+Prepare a concise, accurate Mattermost update for Jeff.
+
+---
+
+## Checklist
+
+1. Confirm the task or issue being discussed.
+2. State whether the behavior depends on authentication.
+3. Clarify whether this is an external issue or a confirmed regression.
+4. Summarize the current observation in plain language.
+5. End with the next action or decision point.
+
+---
+
+## Quality Bar
+
+The final message should:
+
+- sound natural in US English
+- avoid vague comparisons
+- preserve technical accuracy
+- be short enough for Mattermost

workflows/opencode-entry.md

@@ -0,0 +1,35 @@
+# OpenCode Entry Workflow
+
+## Goal
+
+Use OpenCode as the daily AI entry point for this workspace without losing project context.
+
+---
+
+## Setup
+
+1. Open this repository as its own VS Code workspace.
+2. Run `opencode` from the integrated terminal at the repository root.
+3. Use the `fidelity` primary agent when available.
+4. Let project-level config load from `AGENTS.md`, `opencode.json`, `.opencode/commands/`, and `.opencode/plugins/`.
+
+---
+
+## Recommended Daily Sequence
+
+1. Run `/fidelity-context` at the start of the day.
+2. When new work happens on the main development machine, run `/sync-context ...` or `/log-note ...`.
+3. When you need a supervisor update, run `/jeff-update ...`.
+4. When you need polished English for Mattermost, run `/translate ...`.
+5. When you need a standup, run `/standup`.
+
+---
+
+## Why This Works
+
+- Project instructions load automatically from `opencode.json`.
+- Root rules also load automatically from `AGENTS.md`.
+- The main context command reads the stable workspace files plus today's log.
+- Daily updates go back into the workspace, so later prompts inherit better context.
+- The local compaction plugin helps preserve the most important workspace context during long sessions.
+- This reduces reliance on fragile session memory.