pi-goal-list-loop-audit 0.38.113 → 0.39.8

package/CHANGELOG.md

@@ -2,6 +2,140 @@
 
 ## Unreleased
 
+## 0.39.8 — consistent recovery and completed project UI (2026-10-05)
+
+### Preserve work across model changes
+
+- Manually selecting a model during loop recovery leaves a visible, resumable
+  hold with its objective and iteration history retained. Cancellation no
+  longer leaves an invisible loop with an obsolete retry countdown.
+- Existing loops stranded with a main-model recovery stop reason remain
+  visible and can resume through `/loop resume` or `/glla resume`.
+
+### Dismiss completed projects
+
+- Completed projects disappear from the live widget and footer. Their
+  archived summary and `/loop status` remain available for inspection.
+  Unfinished queued work still renders its own UI.
+- Loading terminal-only state no longer engages a work-resume hold or warns
+  that the completed project must resume. Legacy terminal-only load holds
+  clear on restore; explicit supervisor pauses remain intact.
+- Empty or terminal-only blank sessions no longer advertise a work-resume
+  action while waiting for a transcript to load.
+
+### Make recovery commands consistent
+
+- `/glla resume` recognises the same held-loop reasons as `/loop resume`,
+  including stalled project audits, manual pauses, auditor infrastructure
+  failures and project bounds. It delegates to the loop handler, preserving
+  the saved claim, blocker checks and branch restrictions.
+- `/list resume` admits auditing list heads to the existing claim-recovery
+  path. `/goal pause`, `cancel` and `verify` preserve terminal goals.
+- Manual verify and review refuse stale hosts. Decision pickers revalidate
+  both the session and the exact pending decision after selection, execute
+  list/loop control options through their real handlers, and leave work
+  paused when a content choice cannot be delivered.
+- Goal pause, resume and manual verify stop when their state transaction
+  cannot be persisted, avoiding false success messages and dispatches.
+- Explicitly stopped project audits say **Audit stopped** and stop advertising
+  an unavailable resume command.
+- `/goal decide` is discoverable in completion; status points to `/list show`
+  for inspection. Resume descriptions and bound-stop hints match admission.
+- A real command-to-worker regression resumes a stalled project audit and
+  verifies its retained claim through independent approval and archival.
+
+### Explain recovery and updates
+
+- A new recovery guide explains resume command choice, audit progress versus
+  tool waits, manual model changes, completed UI and the opportunistic 200k
+  compaction target.
+- README and installation instructions link to that guide. The docs index
+  leads with practical reading paths; unpublished milestones are consolidated
+  into this release entry.
+
+## 0.39.4 — project builder, audit recovery and opportunistic compaction (2026-10-05)
+
+### check compaction before idle loop dispatch
+
+- Metric loops and project builder turns check the configured context-token
+  threshold at their actual idle dispatch boundary, matching goal/list sends.
+  Hosts without a settled-turn event can still attempt opportunistic compaction.
+- A failed optional compaction resumes the same active loop through a fresh
+  owner context. Busy hosts, queued messages, paused work and audit dispatches
+  retain their guards; an attempted episode is not retried every turn.
+
+### preserve project audit boundaries and recovery evidence
+
+- Startup and manual audit-job cleanup preserve jobs belonging to unresolved
+  goal or project increment claims, including held work. Once those claims
+  settle, ordinary age and worker-identity retention applies again.
+- Health reports exclude claim-protected jobs from cleanup candidates. Cleanup
+  also refuses to delete jobs when the durable claim journal cannot be read.
+- Settled-turn and idle-boundary transcript compaction wait while an exact
+  project increment audit dispatch owns the boundary.
+- The project-audit heartbeat regression now exercises six actual heartbeat
+  ticks during a dispatched worker run, beyond the stall escalation threshold.
+
+### protect project increment audits from continuation stalls
+
+- The main-session heartbeat no longer counts failed continuation attempts
+  while the exact project increment audit dispatch is running. Detached worker
+  timeout handling remains responsible for the audit. A saved claim alone, a
+  replacement claim, or a cancelled dispatch cannot suppress the heartbeat.
+- Held project audits say **Audit held** and show the recorded stop reason
+  instead of displaying an ambiguous auditing phase with generic held text.
+
+### explain long audit tool waits
+
+- Audit cards keep the current tool's ticking elapsed time and timeout visible
+  when it stops producing events. The card says it is waiting on the tool,
+  rather than turning the current call into a historical "last tool" row.
+- Compact footers lead with the tool wait and its elapsed/timeout clock.
+  Waiting is distinct from fresh activity; cancelled, overdue and invalid
+  telemetry cannot claim a healthy wait. Timeout handling stays automatic.
+- Automatic and manual audit progress use the worker's effective granted tool
+  timeout, matching the watchdog rather than showing only the base budget.
+
+### respec project builder
+
+- `/loop respec [project direction]` drafts intended requirements for confirmation,
+  builds coherent increments, runs isolated audits and replans unfinished work.
+  Task claims and spec checkboxes cannot verify requirements. Later audits cover
+  previous capabilities as regressions; completion requires all adopted criteria.
+- Scope refinements require confirmation, retain removal/task history and fence
+  old verdicts by revision. Blockers stay visible; all-blocked projects park,
+  and clearing a blocker preserves pause until explicit resume.
+- Durable audit identities recover saved verdicts across restart, concurrent
+  wakes share one worker, pause/stop cancels audits, and archive failures retain
+  approved evidence for settlement retry. Completion archives the project before
+  exposing terminal state and announces waiting queue items.
+- Project audit cards show live worker/retry state, model, elapsed time and last
+  activity. `/loop status` lists every requirement and its acceptance/evidence.
+  Verified project summaries use semantic colors and bold, archive before
+  delivery, and replay unacknowledged receipts on reload.
+- Full audit fixes persistence rollback, supervisor freeze/retry gating,
+  rapid pause/resume rearming, blocked-project resume and continuous audit
+  visibility. Project receipts use the shared durable outbox across project
+  replacement; large summaries disclose omissions and retain full archives.
+  Generic loop recaps preserve verified project summaries.
+- Project cards/status expose phase, increment, verified/remaining coverage,
+  blockers, evidence and next action using the existing semantic palette.
+- Regression-shield rejection reports unfinished work and carries missing
+  contract evidence into replanning. Stale audit wakes are rejected before
+  model resolution or dispatch.
+
+### semantic summary colors
+
+- Summary emphasis uses bold, including Markdown italic emphasis and quotes;
+  summaries do not render italics.
+- Terminal completion summaries use the active theme’s semantic colors for
+  outcomes, remaining work, next actions and verification results. Unknown
+  verification stays neutral; reported or skipped checks use amber, and
+  failures use red without recoloring unrelated approval references.
+- Styling is applied by a registered renderer. Saved summary Markdown,
+  archive content, receipt identity and headless output retain plain content;
+  continuation messages continue through Pi’s default renderer.
+
 ## 0.38.113 — make background audits clear (2026-10-03)
 
 - The live audit widget uses a compact card, keeping audit state, completed

package/INSTALL.md

@@ -201,7 +201,10 @@ Useful controls:
 ```
 
 `/glla pause` freezes supervisor automation without killing active work.
-`/glla resume` releases it. A BUSY/no-stream Pi turn is aborted and parked by
+`/glla resume` releases it and resumes eligible saved work, including held
+projects through the same recovery path as `/loop resume`.
+See the [recovery guide](docs/RECOVERY.md) for command choice, audit progress,
+model changes, completed projects and compaction. A BUSY/no-stream Pi turn is aborted and parked by
 GLLA, then automatically re-dispatched within the **Zero-stream retries**
 budget (default 3, configurable from 0–10); exhaustion requires an explicit
 mode-correct resume. A user abort means stop; recovery is not silently
@@ -276,7 +279,7 @@ PI_CODING_AGENT_DIR=/tmp/bare-agent pi -p "say ok" --model "provider/model-id"
 ### Work restored but not running
 
 That is a consent/supervision state, not proof of loss. Inspect `/glla status`
-and use `/goal resume`, `/list resume`, `/list next`, or `/loop resume` as
+and use `/glla resume`, or `/goal resume`, `/list resume`, `/list next`, or `/loop resume` as
 appropriate. Keep `Auto-resume` enabled only when automatic restart after
 session load is intentional.
 

package/README.md

@@ -214,6 +214,8 @@ drafting flow. Ambiguous context is never queued automatically.
 /loop start "reduce flaky tests" measure="..." direction=min
 /loop start "keep improving the spec" measure=none max=20 cadence=900
 /loop audit                               # recurring project-audit cadence
+/loop respec [project direction]           # draft intended scope, build, audit and replan
+/loop refine <suggestion>                  # steer the next round; scope changes need confirmation
 /loop status
 /loop stop
 ```
@@ -238,7 +240,42 @@ There are three loop styles:
 - **Project audit:** each iteration looks for the next important finding,
   appends evidence to the audit ledger, and works through the findings.
 
-If the work has a finish line, use `/goal`, not an endless loop.
+Use `/goal` for one defined outcome, `/list` for a known task queue, and
+`/loop respec` for developing a project through evolving build and audit batches.
+
+`/loop respec` develops a project through substantial increments. It researches
+the code and root `SPEC.md` (or `spec.md`), drafts intended capabilities with
+observable acceptance criteria, and asks you to confirm that scope. Existing
+behavior and desired behavior are kept distinct; missing features become work
+to build. `## Rules` remains binding project guidance.
+
+After confirmation, the builder plans a coherent batch, implements it, and
+submits it to the isolated auditor. A task marked implemented is a claim;
+only independent approval verifies its requirements. Failed checks and unfinished
+requirements feed replanning. Each later audit also checks previously verified
+capabilities for regressions. The project finishes only when every adopted
+requirement is independently verified and the project archive is written.
+
+The widget and `/loop status` show phase, increment, verified/remaining coverage
+and blockers. During auditing, the card shows the actual worker state, model,
+elapsed time and last activity, including retries; a restored claim without
+live telemetry is shown as waiting for dispatch. `/loop status` lists every
+requirement, its acceptance criteria, blocker and verification evidence.
+Verified completion posts a semantic summary of shipped capabilities,
+acceptance checks and evidence, saved in the journal and project archive;
+unacknowledged delivery uses the durable outbox and retries on reload, even
+after a new project replaces the old loop, without rerunning the audit. Large
+summary cards name omitted requirements/reports; the archive and `/loop status`
+retain the full criteria and evidence.
+After completion, the project widget and GLLA footer disappear. The archive
+and `/loop status` retain the result; other unfinished work remains visible.
+`/loop pause` holds work, `/loop resume` continues saved state, and
+`/loop stop` stops it without calling unfinished work complete. If all remaining
+work is blocked, automation parks with reasons; clearing a blocker leaves work
+paused until resume. `/loop refine <suggestion>` supplies direction for the next
+round. Changes to adopted requirements show current/proposed acceptance criteria
+and need your confirmation. Text after `respec` is project direction, not metric
+or budget option syntax. Generic `/loop start` remains the metric/bounded path.
 
 ## The autonomy model
 
@@ -420,7 +457,8 @@ proof of a quota or billing state.
   and re-dispatched within the configurable **Zero-stream retries** budget
   (default 3, range 0 to 10), then requires explicit resume;
 - `/goal resume`, `/list resume`, and `/loop resume` are explicit recovery
-  paths;
+  paths; `/glla resume` is the broad recovery command and routes eligible held
+  projects through the same handler as `/loop resume`;
 - a user abort means stop, not “try again behind my back”;
 - a loaded objective can be displayed without injecting stale auditor context
   until continuation consent exists;
@@ -433,6 +471,10 @@ Use `/glla pause` to freeze supervisor automation without killing active work,
 `/glla resume` to release it, `/glla bug [message]` to capture failure context to `bugs/` without touching durable goal state, and `/glla status` or `/goal status` to inspect
 what happened.
 
+See the [recovery guide](docs/RECOVERY.md) for the resume command table,
+audit progress indicators, model changes, completed projects and compaction
+above the default 200k target.
+
 ### Settings worth knowing
 
 Open `/glla` for the settings table. The most important choices are:

package/docs/INDEX.md

@@ -2,58 +2,19 @@
 
 Ordered by reading path, not alphabetically.
 
-## Active focus (recent work, durable artifacts)
-
-Policy contracts and recent changes live in the `audit/` directory of the
-**repository checkout**; that directory is not shipped in the npm tarball
-(see "Repository-only material" below). The shipped entry points are:
-
-- `../CHANGELOG.md`: user-facing changelog; an `Unreleased` section may lead
-  the file, followed by the current released version. v0.35.5 adopted the six-label completion
-  recap; v0.35.6 added typed-boundary regression pins; v0.35.7 added
-  deterministic fast-fail pre-audits, zero-pause autonomous execution, and
-  task milestone gating; v0.35.8 added main-model preferred-primary
-  failback; v0.35.9 hardened cross-version npm tarball checks; v0.35.10
-  handles multi-entry npm dry-run reports; v0.35.11 accepts both npm report
-  shapes; v0.35.12 supports npm 12's keyed pack reports; v0.35.13 fixes stale-API recovery loops.
-  v0.35.14–v0.38.113 continue through the supervisor freeze (`/glla pause`),
-  load hold, auditor picker parity, Windows launch fix, zombie-watchdog
-  subagent carve-out, due-wait backstop, the `/glla agents` visibility panel,
-  durable state-root selection, blank-until-resume auditor context, frozen
-  subagent recovery, bounded repair/replan recovery, production RPC child
-  stopping, mandatory hermetic auditor-extension validation, optional provider
-  extensions, bounded zero-stream retry containment, crash-safe persistence,
-  packed-artifact release verification, and the 2026-09-07 display/lifecycle/
-  settings audit pass (abort-latch send guards, ownership compare-and-swap,
-  auditor inherit/clear parity), the v0.38.25 post-objective summary
-  (canonical approval render, persist + replay, audit-goal counts line), the v0.38.27 selective port of PRs #45/#46 (`/loop pause` soft-hold, widget subtask count), the v0.38.28 provenance-row closure fix, the v0.38.29 compact active-card recovery/judgment projection, and the v0.38.53 consent-safe `glla-delegate`
-  skill/list-drafting release, and the v0.38.54 opt-in context-checkpoint
-  projection (prompt-cache continuity, issue #53), and the v0.38.55 full-parity
-  terminal card, unified auditor-retry envelope, and agent-side resume_goal;
-  and the v0.38.106 audit repairs, versionless companion guidance and refreshed
-  store icon; v0.38.107 recovers completed detached audit results before retry,
-  preserves second-pass visibility, and fits the store thumbnail to its 8:5 card.
-  v0.38.109 keeps work moving after optional compaction failures and fixes
-  settings-editor ownership, narrow rendering, and stale approved-summary text.
-  v0.38.112 audits the full terminal UI: responsive settings, search, focus
-  continuity, picker height, scrollable draft review, and settlement wording.
-  v0.38.111 applies project optional tool arguments with schema validation.
-  v0.38.110 audits /glla menus and commands: model policy, narrow picker
-  rendering, concurrent edits, mutation guards, and accurate option wording.
-  See CHANGELOG.md for the full trail.
-- `../README.md`: what the plugin is, install, quickstart, and the
-  architectural guarantee (drafting + confirm + detached auditor).
-- `../INSTALL.md`: source install / local development setup and the
-  recommended companion plugins.
-
-## Entry points
-- `../README.md`: what the plugin is, install, quickstart
-- `SETTINGS.md`: canonical settings reference (files, precedence, every key)
-- `../INSTALL.md`: source install / local development setup
-- `../skills/glla-delegate/SKILL.md`: normal-chat goal/list delegation and consent ladder
-- `../CHANGELOG.md`: user-facing changelog; the first versioned heading is
-  the current released package version (use `/glla version` to compare with
-  the registry); post-release work may appear in `Unreleased` above it.
+## Start here
+
+- [README](../README.md): install, first goal, and choosing goal/list/loop work.
+- [Recovery guide](RECOVERY.md): resume commands, audit progress, model changes,
+  completed projects and opportunistic compaction.
+- [Settings](SETTINGS.md): settings files, precedence and every option.
+- [Installation and updating](../INSTALL.md): npm/source setup, companions and
+  reloading existing sessions.
+- [Delegation skill](../skills/glla-delegate/SKILL.md): normal-chat goal/list
+  delegation and confirmation.
+- [Changelog](../CHANGELOG.md): changes shipped in each release. The history
+  spans v0.35.14–v0.39.8; `/glla version` shows the installed version and the
+  registry comparison command. A checkout can contain unpublished changes.
 
 ## Architecture
 - `ARCHITECTURE.md`: 20-minute newcomer overview (three loops, audit lifecycle, persistence)

package/docs/RECOVERY.md

@@ -0,0 +1,85 @@
+# Recovering and inspecting work
+
+Start with `/glla status`. For full saved details, use `/goal status`,
+`/list show`, or `/loop status`, depending on the work surface.
+
+## Which resume command?
+
+| Command | Use it for |
+| --- | --- |
+| `/glla resume` | Broad recovery: release supervisor/load holds, retry saved model recovery, or resume the current goal, list item or eligible held loop. If a paused goal and held loop both qualify, the UI asks which one. |
+| `/goal resume` | Resume the current goal through its goal recovery path. |
+| `/list resume` | Resume the current list item, including recovery of its pending completion audit. |
+| `/loop resume` | Resume an eligible held metric loop or project builder, retaining its target, iteration and audit claim. |
+
+For a held project, `/glla resume` delegates to the same loop recovery as
+`/loop resume`. Both retain blocker and branch checks. Neither overrides an
+explicit `/loop stop` or declares unfinished work complete. Resume feedback
+explains when work cannot restart.
+
+After loading a session, **Loaded without starting** means the saved work is
+restored but automation awaits your decision. Load the intended conversation,
+inspect its state, then resume. Enable **Auto-resume** in `/glla` only if you
+want automation to restart after future loads.
+
+## Is an audit progressing?
+
+Read the auditor rows, rather than the main session's spinner alone:
+
+| Display | Meaning and next step |
+| --- | --- |
+| **Auditing**, recent activity | The detached auditor is producing events. Tool completions and changing evidence provide stronger progress evidence than elapsed time alone. A long duration alone does not establish a stall. |
+| Waiting on a tool, elapsed/timeout | A tool is still running. Its ticking timer is a wait indicator; timeout handling remains automatic. |
+| Waiting for dispatch | A saved claim exists, but no live worker activity is observed yet. Inspect status for restoration or recovery holds. |
+| **Audit held** | Automation parked with a recorded reason. Inspect `/loop status`, resolve the cause, then resume through the command shown. |
+| **Audit stopped** | The project was explicitly stopped. Resume is not offered for that stop. |
+| Completion review disapproved | The auditor found an unmet contract. Read its required fixes; repair work can continue automatically. Rejection does not mean approval is stuck. |
+
+If progress stops and the UI reports a wedged main session, follow its recovery
+message: interrupt the stuck turn with Escape if needed, then resume. Use
+`/glla bug <what you observed>` to capture GLLA diagnostics without changing
+the saved objective. A process that has exited cannot reconcile an audit;
+load/resume the original session before inspecting its pending claim again.
+
+## Changing models during recovery
+
+Manually selecting a model cancels the current automatic main-model recovery
+episode. A recovery-held loop keeps its objective and iteration history,
+stays visible, and offers `/loop resume` or `/glla resume` to continue using
+the selected model. Changing the model alone does not resume loop supervision.
+
+If an older loaded extension still hides the objective or shows an obsolete
+retry countdown, update GLLA and run `/reload`, inspect `/loop status`, then
+resume. Saved legacy recovery holds are supported from 0.39.8 onward.
+
+## When a project completes
+
+Project completion requires independent verification of every adopted
+requirement and a written archive. After completion, the project widget and
+GLLA footer disappear; other unfinished work can still show its own UI.
+The semantic completion summary, `/loop status` and archive retain the
+verification evidence. There is no resume action for an already completed
+project. Start a new project when its intended scope changes.
+
+## Why context can exceed 200k
+
+**200,000 tokens is the default opportunistic compaction target.** Configure
+`compactionTokenThreshold` through the global settings; see [SETTINGS.md](SETTINGS.md).
+GLLA checks at safe idle boundaries during supervised work. Active tools,
+audits, queued messages and pauses can defer an attempt. An idle conversation
+without active GLLA work does not start automation simply by crossing the target.
+
+Pi's summarizer can fail, for example when its output hits the model's token
+cap. GLLA records that failure and continues eligible work. It does not retry
+the same failed compaction episode every turn. The episode rearms when a later
+safe check observes context below half the configured target. Pi's `/compact`
+is available for a manual attempt; summarizer success is not guaranteed by
+GLLA's scheduling. Compare current context with the recorded attempt time
+before treating an older high-token sample as the current transcript size.
+
+## Updating a running session
+
+The npm package is also the Pi plugin; there is no separate Pi-only release.
+Follow the [update instructions](../INSTALL.md), run `/reload` in existing
+sessions, and use `/glla version` to check the version actually loaded.
+Publishing a package does not replace code already loaded in a live session.

package/docs/RUNTIME-INVENTORY.md

@@ -2,25 +2,25 @@
 
 Generated by `node scripts/generate-inventory.mjs`. Run with `--check` to detect drift. Counts describe files and literal registrations, not executed coverage.
 
-- Extension/script files: 91
-- Extension/script lines: 64275
-- Top-level test files: 342
+- Extension/script files: 96
+- Extension/script lines: 65038
+- Top-level test files: 348
 - Ambient bridge names: 179 (audit baseline: 183)
 - Commands: `/glla`, `/goal`, `/list`, `/loop`, `/review`
-- Tools: `complete_goal`, `complete_task`, `list_activate`, `list_add`, `list_status`, `pause_goal`, `propose_goal_draft`, `propose_loop_draft`, `propose_loop_refine`, `propose_task_list`, `record_goal_judgment`, `resume_goal`, `update_task_batch`, `update_task_status`
+- Tools: `audit_project_increment`, `block_project_requirement`, `claim_project_task`, `complete_goal`, `complete_task`, `list_activate`, `list_add`, `list_status`, `pause_goal`, `plan_project_increment`, `propose_goal_draft`, `propose_loop_draft`, `propose_loop_refine`, `propose_project_refinement`, `propose_project_requirements`, `propose_task_list`, `record_goal_judgment`, `resume_goal`, `unblock_project_requirement`, `update_task_batch`, `update_task_status`
 
 ## Largest modules
 
 | Module | Lines |
 |---|---:|
 | [extensions/goal-loop-core.ts](../extensions/goal-loop-core.ts) | 4966 |
-| [extensions/loops/goal-tools.ts](../extensions/loops/goal-tools.ts) | 4147 |
-| [extensions/loops/goal-activation.ts](../extensions/loops/goal-activation.ts) | 3738 |
-| [extensions/goal-commands.ts](../extensions/goal-commands.ts) | 3526 |
-| [extensions/goal-loop-display.ts](../extensions/goal-loop-display.ts) | 2685 |
-| [extensions/goal-loop-auditor-process.ts](../extensions/goal-loop-auditor-process.ts) | 2664 |
-| [extensions/loops/goal-auditor-hooks.ts](../extensions/loops/goal-auditor-hooks.ts) | 2655 |
-| [extensions/goal-heartbeat.ts](../extensions/goal-heartbeat.ts) | 2093 |
+| [extensions/loops/goal-tools.ts](../extensions/loops/goal-tools.ts) | 4172 |
+| [extensions/loops/goal-activation.ts](../extensions/loops/goal-activation.ts) | 3762 |
+| [extensions/goal-commands.ts](../extensions/goal-commands.ts) | 3557 |
+| [extensions/goal-loop-display.ts](../extensions/goal-loop-display.ts) | 2747 |
+| [extensions/goal-loop-auditor-process.ts](../extensions/goal-loop-auditor-process.ts) | 2675 |
+| [extensions/loops/goal-auditor-hooks.ts](../extensions/loops/goal-auditor-hooks.ts) | 2656 |
+| [extensions/goal-heartbeat.ts](../extensions/goal-heartbeat.ts) | 2098 |
 | [extensions/loops/goal-session.ts](../extensions/loops/goal-session.ts) | 2062 |
 | [extensions/loops/goal-settings-ui.ts](../extensions/loops/goal-settings-ui.ts) | 2023 |
 

package/extensions/continuous-supervision.ts

@@ -55,6 +55,11 @@ function durableStateSignature(state: State, liveSubagentCount: number): string
       iteration: state.loop.iteration,
       stopReason: state.loop.stopReason,
       bestValue: state.loop.bestValue,
+      builder: state.loop.builder ? {
+        phase: state.loop.builder.phase, revision: state.loop.builder.revision,
+        cycle: state.loop.builder.cycle, attemptId: state.loop.builder.audit?.attemptId,
+        requirements: state.loop.builder.requirements?.map(r => ({ id: r.id, status: r.status })),
+      } : undefined,
     }
     : null;
   const recovery = state.mainModelRecovery
@@ -85,6 +90,7 @@ export function activeSupervisionPlanes(state: State, liveSubagentCount = 0): Su
     if (goal.status === "auditing" || !!goal.pendingCompletion) planes.push("auditor");
   }
   if (state.loop?.active) planes.push("loop");
+  if (state.loop?.builder?.phase === "auditing" && state.loop.builder.audit && !planes.includes("auditor")) planes.push("auditor");
   if ((state.list?.length ?? 0) > 0) planes.push("queue");
   if (state.mainModelRecovery) planes.push("provider-recovery");
   if (liveSubagentCount > 0) planes.push("subagent");