docs: Update architecture docs for anchor mechanism [doc-updater]

README.md

@@ -165,6 +165,7 @@ See [action/README.md](action/README.md) for full documentation and [GitHub Auto
 | **Architecture & security model** | [Architecture Overview](docs/architecture/README.md) |
 | **SDLC pipeline details** | [SDLC Pipeline Guide](docs/guides/sdlc-pipeline.md) |
 | **Concurrent execution mode** | [Concurrent Execution Guide](docs/guides/concurrent-execution.md) |
+| **Agent anchor / post-compaction recovery** | [Anchor Recovery Guide](docs/guides/anchor-recovery.md) |
 | **Agent roles & permissions** | [Agent Roles Reference](docs/reference/agent-roles.md) |
 | **Agent recovery & circuit breaker** | [Agent Recovery Reference](docs/reference/agent-recovery.md) |
 | **Post-agent auto-commit** | [Post-Agent Commit Reference](docs/reference/post-agent-commit.md) |

docs/architecture/README.md

@@ -34,6 +34,7 @@ See the [main README](../../README.md) for the architecture diagram.
 - Filesystem-level readonly mounts (phase-protected `.egg-state/` directories mounted readonly)
 - Commit-time validation (staged files checked against phase restrictions before commit)
 - Agent role-based file access (Coder, Tester, Documenter have distinct write permissions; default warn-only, configurable to enforce via `EGG_AGENT_RESTRICTIONS_ENFORCE`)
+- Anchor file write-scoping (agents can only write their own `.egg-state/agent-anchors/{agent-id}.json`, enforced via `AGENT_ANCHOR_ID`)
 - Role-based contract mutations (implementer, reviewer, human roles with field-level permissions)
 - No merge capability (gateway has no merge endpoint)
 - Force push and destructive operations blocked
@@ -60,6 +61,7 @@ Contracts are JSON documents that track issue progress through SDLC phases, task
 - `.egg/schemas/yaml-tasks.schema.json` – Structured appendix format for plan documents (used by plan parser)
 - `.egg/schemas/phase-permissions.schema.json` – Allowed git/gh operations and file restrictions per SDLC phase
 - `.egg/schemas/checkpoint.schema.json` – Agent checkpoint structure (session context, transcripts, tool calls)
+- `.egg/schemas/agent-anchor.schema.json` – Agent anchor structure for post-compaction state recovery
 
 **Role-based ownership**: Each contract field is owned by a specific role:
 - `implementer`: `tasks[].commit`, `tasks[].notes`, `tasks[].files_affected`

docs/architecture/orchestrator.md

@@ -396,6 +396,16 @@ Fixed IPs:
 - `GET /pipelines/{id}/deployment-check/status` - Poll devserver status
 - `POST /pipelines/{id}/deployment-check/teardown` - Tear down devserver
 - `GET /pipelines/{id}/health` - On-demand pipeline health check (all tiers)
+- `GET /pipelines/{id}/health/alerts` - List active health alerts
+- `GET /pipelines/{id}/progress` - Query structured progress events
+- `POST /pipelines/{id}/progress` - Emit a structured progress event (CLI: `egg-orch progress emit`)
+
+**Anchors (`/api/v1/anchors/`)**
+- `POST /anchors/{agent_id}` - Create or update an agent anchor (stored in Redis; validated against schema)
+- `GET /anchors/{agent_id}` - Get an agent's anchor (cross-agent reads via API)
+- `DELETE /anchors/{agent_id}` - Delete an anchor
+- `GET /anchors/team/{pipeline_id}` - Get team anchor (orchestrator-generated projection of all agent anchors)
+- `POST /anchors/gc/{pipeline_id}` - Garbage-collect anchors for a completed/failed pipeline
 
 **MCP Server (`/mcp`)**
 - `GET /health` - MCP server health check