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.

ai/context/decisions/discourse-handling.md

@@ -0,0 +1,38 @@
+# Discourse Issues Handling
+
+## Context
+
+External reports from AO testing or Discourse may:
+
+- already exist in main
+- be partially reproducible
+- depend on authentication
+- reflect backend behavior rather than a new regression
+
+---
+
+## Decision
+
+Treat incoming reports as external issues until scope is confirmed.
+
+---
+
+## Validation Rules
+
+Always confirm:
+
+- reproducibility
+- environment
+- auth state
+- entry point
+- whether the issue exists in main
+
+---
+
+## Communication Rule
+
+Do not say a report is a regression until comparison has been validated.
+
+Preferred framing:
+
+"Investigating external report. Scope, auth state, and reproducibility still being confirmed."

ai/context/decisions/rest-vs-graphql.md

@@ -0,0 +1,30 @@
+# REST vs GraphQL
+
+## Decision
+
+Deprecate GraphQL and migrate to REST progressively.
+
+---
+
+## Constraints
+
+- REST is behind a feature flag
+- GraphQL remains fallback
+- Behavior parity matters during migration
+
+---
+
+## Communication Rule
+
+When reporting findings:
+
+- state whether REST was confirmed enabled
+- avoid implying REST is the default path
+- call out when behavior may still come from GraphQL fallback
+
+---
+
+## Follow-up
+
+- Remove Apollo when migration is safe
+- Retire GraphQL-specific tests only after parity is confirmed

ai/context/people/jeff.md

@@ -0,0 +1,40 @@
+# Jeff
+
+## Role
+
+Direct supervisor.
+
+---
+
+## Communication Requirements
+
+- Native US English
+- Prefers clear, concise updates
+- Needs accurate scope, not vague reassurance
+- Should be informed of meaningful progress from this machine through Mattermost
+
+---
+
+## What Good Updates Include
+
+1. Context
+2. Observation
+3. Action
+
+Good updates usually clarify:
+
+- what issue or task is being discussed
+- whether the behavior is reproducible
+- whether auth state matters
+- whether this looks like an external issue or a regression
+- what the next step is
+
+---
+
+## AI Usage
+
+AI should help:
+
+- translate rough Spanish notes into natural US English
+- tighten wording before sending
+- remove ambiguity without changing technical meaning

ai/context/project.md

@@ -0,0 +1,79 @@
+# Project Context - Fidelity
+
+## Overview
+
+This workspace supports daily iOS engineering work for Fidelity.
+
+The product work happens outside this repository, usually from another machine. This repository exists to preserve context, track communication, and help AI generate accurate output for standups, Mattermost messages, Jira notes, and supervisor updates.
+
+---
+
+## Fidelity Ecosystem
+
+- Fid4 is the main consumer iOS app
+- XFlowSDK powers backend-driven UI flows
+- XFlowViewMaker is an adapter layer under evaluation for removal
+- FTFrameworks contains feature modules such as FTAccountOpen and FTTransfer
+
+---
+
+## Current Priorities
+
+### REST migration
+
+- REST is behind a feature flag
+- GraphQL is still the default fallback
+- REST should never be assumed active unless confirmed
+- Migration must preserve behavior while Apollo is deprecated safely
+
+### Discourse and AO issues
+
+- External reports are often incomplete
+- Many reported issues are not confirmed regressions
+- Some issues reproduce only with authenticated users
+
+### Flow debugging
+
+- XFlow behavior changes based on backend configuration
+- Entry point affects what the user sees
+- Authentication state affects reproducibility
+
+### Testing complexity
+
+- Around 15 entry points have been identified at code level
+- Not all entry points are reachable from visible UI
+- Validation often requires exploratory testing
+
+---
+
+## How This Workspace Is Used
+
+This machine is used to:
+
+- maintain current project context
+- record findings from work performed elsewhere
+- capture Mattermost communication that changes understanding
+- prepare polished updates for Jeff
+- generate standups with better context coverage
+
+This means logs must capture both technical findings and communication context.
+
+---
+
+## Communication Expectations
+
+All important updates should clarify:
+
+- whether the flow is authenticated or non-authenticated
+- whether the issue is reproducible
+- whether the report is external behavior or regression
+- whether behavior is present in main
+- what action is needed next
+
+Avoid phrases that hide scope, such as:
+
+- "same behavior"
+- "looks fixed"
+- "working as expected"
+
+Use explicit framing instead.