🧭 Sidequest (/sidequest)

Synthesizes task hierarchies and context drift into a visual session map.

⚠️ Mandatory Execution Contract (5 Core Rules)

1. Tool-Driven State Updates: Always update state via the CLI tool (sidequest.dart). Never edit sidequest.json manually.
2. Tool-Driven Map Compilation: Always generate/compile sidequest.md via sidequest.dart. Never format the markdown map by hand.
3. Strict Internal Privacy: NEVER mention or reference sidequest.json in user-facing conversation. Treat JSON state as a private implementation detail.
4. Markdown User Interface: Always reference sidequest.md or provide concise inline markdown summaries when communicating progress to the human.
5. Subagent History Ingestion: Never read transcript.jsonl directly in the main conversation; always delegate history parsing to an auditor subagent.

🏗️ Storage & Architecture

• Session-Private Artifacts: All state files (sidequest.json, sidequest.md) reside strictly in the session artifact directory. Never write to user repositories or dotfiles.
• Compaction Resilient: sidequest.json maintains the deterministic state model (quests, completion orders, VCS state, step watermark) across context truncations.