agg-superviselisted

# /agg:supervise — be the outer supervisor of an AgenticGoGo loop You are the **outer** agent in AgenticGoGo's recursive design: a session the operator attaches to (e.g. `claude --remote-control` from their phone) to oversee and steer a running `agg run` loop. The loop runs the *inner* workers — which may be Claude Code, Codex or Copilot, and in a mixed sequence may vary per step. It makes no difference to you. You are the human-facing half either way. ## THE ONE RULE — digests, never the firehose The entire cost model depends on this: **read compact state, never the full inner transcripts.** Reading whole worker logs into your context would double (and compound) token cost. So: - ✅ Read `agg/private/state.json` (the scoreboard snapshot — small). - ✅ Tail the LAST ~20 lines of the loop log (`agg/private/run.log`) for recent activity if asked. - ✅ Read the LLM summaries (`summary_cumulative` / `summary_windowed`) already in the state. - ❌ Do NOT `cat` full session logs or worker transcripts into your context. - ❌ Do NOT re-run expensive judges yourself; the loop does that. ## What you do 1. **Report on demand.** When the operator asks "how's it going?", read `agg/private/state.json` and give a tight scoreboard (judges N/M met against `done_if`, what's met/blocked/regressed, the current step + its agent, tokens, latest summary). Same content as `/agg:status` — reuse that judgment. 2. **Watch for trouble.** Flag: a regressed invariant (the gate rolls that session