@iowarp/clio-coder 0.3.3 → 0.3.6

package/CHANGELOG.md

@@ -2,6 +2,80 @@
 
 All notable changes to Clio Coder are documented in this file. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and versions follow Semantic Versioning; pre-1.0 minor releases may include incompatible changes.
 
+## 0.3.6 - 2026-08-23
+
+0.3.5 was published by mistake and withdrawn; its content ships here.
+
+### Added
+- `docs/middleware-and-components.md` documents every built-in middleware registration: id, hooks, trigger, and what does not trigger it.
+- Permission and `ask_user` dialogs now derive closed consequence tiers from typed request, scope, reversibility, origin, exposure, and authority facts (#169). Conversational answers, workspace authority, outward consequences, safety-net confirmations, system changes, and worker escalations receive distinct titles and semantic tokens, while caller prose cannot lower a tier or alter the underlying decision protocol.
+- Typed invocation-level dispatch budget envelopes (#175). Recipes keep an exact default unless they author a maximum, dispatch can request a phase and preauthorize a retry, result-contract revision, or review revision ceiling inside both recipe and operator policy, and immutable policy, request, effective, clamp, and escalation facts are sealed into receipts and shown by monitor, fleet status, and the live fleet card. Architect retains its 32-call default and now permits explicitly admitted runs up to its authored maximum.
+- The `Alt+W` Fleet Runs board shows live worker progress on operator request (#168). `Enter` opens the selected run's detail: the phase, the running call as `<tool> <verb> <object>`, and the bounded tail of the worker's own prose with a `/view dispatch:<runId>` link to the rest. The default list stays compact, so a fan-out of scouts costs one card each until an operator opens one.
+- Reviewed task-memory promotion in `/memory` and `clio-coder memory promote` (#176). Selected knowledge and procedural entries can become unapproved durable proposals with explicit validated repo, global, runtime, or agent scope. Promotion redacts before persistence, preserves session and evidence provenance, and keeps private status excluded.
+
+### Changed
+- Python and Cargo project metadata, bootstrap guidance, and verifier discovery now parse TOML through one shared `smol-toml` boundary with an operation-scoped file cache (#153). Parsed structure replaces table-header scanning, and malformed documents fail closed.
+- The Fleet Runs board and the transcript's worker block now read one bounded projection of the dispatch event stream instead of folding it separately, so the two surfaces cannot disagree about what a worker is saying or touching. The projection keeps 40 lines and 4096 bytes of answer tail, 8 distinct tool names, and 4 recent actions, and accepts 16 KB of streamed bytes per 250 ms; what the bounds refuse is counted and named rather than dropped silently.
+- Worker tool activity now carries a redacted action descriptor beside the tool name. The descriptor is composed where the arguments are trusted (the tool registry's admission path, the Claude tool mapper, and the ACP update mapper) from a fixed verb vocabulary and a fixed argument-field allowlist, with credentials scrubbed, escape sequences stripped, and the result bounded to 64 characters. Raw argument objects still never cross the worker stdout seam, and reasoning content is still never displayed.
+
+### Fixed
+- Approval overlays now derive call targets from a per-tool field allowlist. Unlisted arguments are shown only by field name, type, and size, so an unexpected credential or pasted document cannot be copied into the rendered frame (#200).
+- Worker tool starts and finishes now share a call id when their producer has one. The transcript and Fleet Runs pair concurrent calls by that id, while older streams without ids continue to match by tool name (#201).
+- Proactive task memory now reuses deterministic tool-result disposition digests with explicit source provenance (#173). Operation fingerprints remain separate for loop and repeated-failure identity, while redaction and byte caps apply before diagnostics reach the task bank or background policy.
+- The llama.cpp router's `sleeping` state now reads as not resident (#192), and `clio-coder targets` reports `resident: none` while preserving the reported context-slot metadata.
+- Response model-id presence is now an explicit `responseModelIdObservation` state (#193, #202). The short-lived `servedModel` and `servedCalls` names are replaced by requested and attributed model ids plus counts named for each observation state. Pre-#193 ledgers remain readable under the labeled `legacy-difference-only` state, and providers outside the stream tap retain the `responseModel` fallback without implying that presence was observed.
+- The selected live model's capability probe now starts at boot (#195), so the first `/context` view and footer show the probed context window before any model turn.
+- The permission dialog now anchors above the composer (#194) and recomputes that placement when the terminal resizes.
+- Permission dialog clearance now comes from the live editor and footer render heights on every frame instead of a fixed five-row margin. Empty and multiline composers remain unobscured in both terminal modes, including after a resize (#194).
+- Tool-result offload scratch files older than fourteen days are now swept at boot (#196). A resumed transcript now says when the retention sweep removed the file instead of presenting its stale path as a live full-output pointer (#203).
+- A skill suggestion no longer costs the first turn on local models (#184). Every surface that teaches the protocol (the first-turn reminder, the `context(scope="skills")` listing footer, and the operator-gate denial) now says to open with the `Suggested skill:` line and continue the task in the same turn; none instructs the model to wait. A turn that makes the suggestion and stops with only listing calls behind it is continued once with a reminder that only the operator loads a skill.
+- Three envelope noise sources on local targets are gone (#191). An always-on reasoning model printed the thinking clamp three ways (`thinking medium resolved to forced`, `medium was ignored because thinking is always on`, and the combined line); only the combined line prints now, once per target, model, and level change. A workspace with no `CLIO-CODER.md` states `<handbook>none …</handbook>` where the handbook would have been injected, so the model stops spending its first tool call on a read that returns ENOENT. `clio-coder --resume` and `--continue` still fail closed, and the error now says that sessions are resumed from the `/resume` picker inside the app.
+- A turn is attributed to the reported response model id under LM Link peer routing (#185, #202). The response's `model` field is recorded as `responseModel` when it differs from the request. The footer, `/cost`, `clio-coder usage report`, and dispatch receipts use the shared requested model id, attributed model id, and response model id observation vocabulary. The LM Link peer warning is emitted once per distinct fact instead of once per turn.
+- The `/resume` picker previews the operator's first prompt (#188). The first user entry of a session is the composed prompt, with the `<system-reminder>` block and any `[Skill request]` preamble ahead of the operator's words, so every row read `<system-reminder> [Skills] 9 installed…` and the filter matched them all. The preview is now the persisted `operatorText`, the scaffolding-stripped text for older sessions, the next turn when the first carries no operator words, and the first assistant text when none does.
+- The context ledger is populated right after `/resume` (#189). Before the first new turn of a process, `/context` and the footer meter now read the window from the live target resolution (falling back to the window the resumed session recorded) and the token facts from the session's last persisted snapshot, which measured the same messages; the selected model's live capability probe runs at resume so the window is the probed one. `context window unknown · 0 tokens` is reserved for a session with no target and no history.
+- `/context` names the configured working-set policy instead of the last applied one (#190). A fresh session at the shipped default reads `policy structural-v1 · no events yet` rather than `policy none`; `context.workingSet.enabled: false` reads `disabled`; a policy changed after an event shows `(last event by <policy>)`. The eviction trigger stays at `compaction.threshold`: the replay tables price each event by the cold prefix it re-prefills, and batching from the threshold down to the target is what keeps the event count down.
+- A llama.cpp context window is the per-request share, not the server total (#187). `--ctx-size` is split evenly across `--parallel` slots unless `--kv-unified`, so a router started with `--ctx-size 786432 --parallel 4 --no-kv-unified` now resolves to a 196,608-token window instead of 786,432, which is where autocompact was armed at a size the server would never admit. The probe reads the long and short flag spellings and the last kv flag given, `/context` prints `196,608 (786,432 / 4 slots)` with `probed window`, and `clio-coder targets` names the split in its `ctx` note and a probe note.
+- A parked permission request always offers allow, deny, and stop (#186). The composer rail switches to `CONFIRM` and carries the dialog's keys while a prompt owns the keyboard, so the `Enter send` hint can no longer contradict a dialog that sits forty rows away on a tall terminal. `Enter` allows only from an empty composer: with a draft present the habitual send key is inert, both surfaces read `[Backspace] clear draft` in its place, and only deletion keys reach the editor. `Esc` is labeled `deny`, which is what it does. A request that parks while another overlay holds the screen is re-presented as soon as that overlay closes.
+
+## 0.3.4 - 2026-08-22
+
+### Added
+- A typed project verifier catalog at `.clio-coder/verifiers.yaml` (#170). Each check declares a stable id, description, exact argv vector, repository-relative cwd, bounded timeout, and tags. `verify()` lists package scripts and catalog checks through one `DeclaredCheck` projection, and `verify(check=<id>)` runs the admitted argv through safe-exec with no shell, no model-text interpolation, and no widening of workspace authority. Shell strings, escaping cwds, duplicate ids, unknown fields, unsupported versions, and over-cap values fail closed with diagnostics that name the field and the cap.
+- Guided verifier authoring through `clio-coder verifiers discover|author|validate|dry-run|add|edit|rename|remove` (#174). Discovery recognizes package scripts, Cargo manifests, CMake presets, declared Python runners, Go modules, and existing validation-contract commands with source provenance, and proposes argv vectors labeled project-declared or toolchain-defined. Every preview shows path, cwd, timeout, tags, and effective execution authority; nothing is written or executed before `--yes`, validation uses the production catalog parser, and dry runs use the production verify path. Projects with no declared command get an explicit manual-entry path instead of a guessed command.
+- One canonical tool-result disposition contract with independent presentation and model-context axes (#165). A tool declares how the operator sees a result and, separately, whether the model receives full content, a bounded excerpt, a deterministic code-produced summary, or metadata only. Typed result metadata records captured, displayed, and context byte counts, the requested versus applied mode, truncation, the offload path, and summary provenance. Exit status, error state, safety facts, and retrieval instructions survive every context mode.
+- Canonical Bash output dispositions with a tail-biased bounded default, deterministic redacted diagnostic summaries, metadata-only retrieval, budget-admitted full context, and explicit byte and termination facts (#172). `output_policy` is optional on the Bash tool; omitting it preserves the previous tail behavior.
+- A six-axis canonical trust status for runs (#154): artifact integrity, validation grounding, independent review, context provenance, autonomy enforcement, and completion evidence, each with explicit `absent`, `unknown`, and `not_applicable` states and a named source and authority. Composition never promotes one axis from another; the no-promotion rules are enforced at the adapters and the evidence composition boundary. Evidence bundles gain `trust-status.json`.
+- Non-destructive working-set eviction. When context pressure crosses `compaction.threshold`, Clio now records which tool-result bodies and closed-turn thinking blocks leave the model's working set instead of rewriting them out of the session. The bodies stay in the ledger, the transcript keeps showing them, and each one is replaced in model replay by a one-line marker naming the ref, the reason, the size, and the exact call that brings it back.
+- Exact recall by ref. The model reads an evicted body back with `context(scope="recall", ref="<turnId>")`; the operator reads one into the transcript with `/context recall <ref>`, which never enters model context. A recall does not un-evict: the marker stays byte-identical so the provider prefix cache is untouched, and repeated recalls of one ref are the churn signal.
+- Two eviction policies. `structural-v1` is the default: it selects by what the session did since (`stale_after_mutation`, `superseded_read`, `failure_resolved`, `listing_consumed`, `thinking_turn_closed`) and falls back to age only under pressure. `age-horizon` reproduces the previous age-based selection, minus results whose body is below `context.workingSet.minEvictableTokens`. Replayed over the seeded procedural corpora with the summary stage modeled, `structural-v1` cuts the number of lossy summary compactions per 300-turn science trace from 21.5 to 8.8 at a 64k budget and from 8.9 to 3.1 at 128k, retains at or above `age-horizon` at every budget, and beats random eviction on precision by 2.3x or more.
+- `/context` reports the working set: policy, evicted items, evicted tokens, events, recalls, and churn. Evicted tool rows carry a dim `evicted · <reason>` tag in the transcript.
+- Cache-honesty attribution for eviction. An applied event stamps `working_set_evict` on the next assistant entry's `promptCache.expectedColdReasons`, and `/context` reports `last cold turn: working-set eviction (expected)` instead of warning about a cold backend it caused itself.
+- `clio-coder context replay --sessions <path>...` replays Clio ledgers, and `--synthetic <ids>` replays seeded procedural science-coding corpora (`science-long`, `refactor`, `exploration`), through the live eviction code with `none`, `random`, and `oracle` controls and reports retention, precision, tokens evicted, recall tokens, cold prefix tokens, saturation, turns to first summary, and summaries per trace under a modeled summary stage; `clio-coder context working-set --session <id|path>` prints one session's working-set fold and path index. The procedural corpora replace the private Claude Code transcripts the first tables were built on; generated replay tables are local artifacts rather than versioned benchmark results.
+- New guide: `docs/context-working-set.md`.
+
+### Changed
+- Tool offload files are content-addressed: `<stateDir>/scratch/<sessionId>/<sha256 of the captured text>.txt` instead of the tool call id or a timestamp, so identical captures share one file and the `retrieve=` header, the eviction marker, and the resume transcript carry the same bytes every time.
+- Editing an existing `.clio-coder/verifiers.yaml` through `clio-coder verifiers add|edit|rename|remove` now mutates the operator's file in place: comments and on-disk order survive, only changed fields move, and a revision that changes nothing writes the file back byte for byte.
+- Evidence rows, the latest gate decision and finish contract, and the verifier catalog order by code point instead of locale collation, so two machines rebuild the same bundle in the same order.
+- Receipt inspection, evidence bundles, monitor output, and worker evidence derive their trust facts from one canonical derivation (#157). The public `evidence_verification=<state>/<basis>` token is unchanged. An integrity-failed receipt now renders `receipt_integrity=FAILED reason=…` and labels its claims `worker claims (unverified prose)` in both dispatch and monitor output.
+- Session format version 4. The bump is additive: it adds the `contextEviction` and `contextRecall` records and changes no existing entry, so a version 3 session migrates to 4 in place on open with nothing rewritten. Only a session written by a newer build is refused. The bump is one-way for the operator, and a 0.3.3 binary cannot open a session this release wrote.
+- New settings under `context.workingSet`: `enabled` (default `true`), `policy` (default `structural-v1`), `target` (default `0.6`), `protectLastTurns` (default `6`), and `minEvictableTokens` (default `200`). `compaction.excludeLastTurns` now governs only the legacy mask path.
+- Compaction reports a `working_set` stage on `ContextPruned`, and the middleware `on_compaction` hook gains the `working_set_evict` and `working_set_recall` stages.
+
+### Removed
+- The Claude Code transcript loader for `context replay` and its `--format` flag. Replay inputs are Clio ledgers and the seeded procedural corpora.
+- `TRUST_STATUS_NO_PROMOTION_RULES`, `adaptEvidenceFindingsValidationStatus`, and `adaptEvidenceLinkContextStatus` from the evidence barrel. The no-promotion rules are enforced at the adapters and the composition boundary and are written out in `docs/evidence-and-memory.md`; the two adapters were reachable from no builder.
+
+### Security
+- A project-catalog `verify(check=<id>)` no longer sits in the no-prompt set. The policy engine resolves the check against `.clio-coder/verifiers.yaml`, scans the declared argv with the damage-control rules and the zero-access read guard, and tags it unrecognized, so `auto-edit` confirms it once with the argv shown and `full-auto` runs it. Package-script checks and `verify(check="frontend")` are unchanged. `.clio-coder/verifiers.yaml` and `.clio-coder/safety.yaml` are read-only to the model's `write`, `edit`, and bash redirect paths by default: before this, a model at the default `auto-edit` level could write the catalog and run any argv through `verify` without a prompt.
+
+### Fixed
+- A completed conversational offer such as "point me at it and I'll get moving" no longer triggers an automatic continuation or the "turn still has open work" footer warning (#178). The stalled-turn detector now requires an announced concrete action: it recognizes inflected verbs ("I'll be running the tests"), announced paths and commands ("Let me open src/cli/index.ts", "I'll npm run build"), and keeps conditional offers, "let me know" phrasing, questions, and wait statements ("I'll wait for your go-ahead before I touch index.ts") suppressed. The one-continuation cap for genuine stalls is unchanged.
+- A completion-contract audit row can no longer ground validation. The row is the run's own self-report and feeds completion evidence only; validation grounding is filled by executions the session ledger observed. A run whose receipt fails integrity contributes no verified field, its completion self-report downgrades to `unknown`, and the `no-validation` warning is restored. A blank or whitespace-only identifier in one audit row no longer aborts the whole evidence build.
+- Tool-result summaries are honest about omission. Head and tail slices are disjoint, a scratch offload is written only when the model projection actually omits content, whitespace-only output is complete rather than truncated, NUL bytes are removed from model context while presentation and the offload keep the captured bytes, the head-tail strategy honors `redact`, and a throwing disposition resolver fails closed to metadata-only with the cause recorded in the result metadata, the model header, and the transcript row.
+- `clio-coder verifiers … --yes` no longer prints "no file has been written" immediately before writing the catalog; the confirmed preview is rendered after authorization.
+- Auto-compaction no longer destroys observations. The stale-observation mask rewrote persisted bodies through `session.replaceEntries`, so masked content was gone from `/resume`, `/tree`, `/fork`, and the HTML export as well as from the model. `CLIO_CODER_LEGACY_MASK=1` restores that stage for one release as a compatibility escape hatch; it is removed in the next release.
+
 ## 0.3.3 - 2026-08-21
 
 ### Changed

package/CONTRIBUTING.md

@@ -41,7 +41,7 @@ npm run ci:release
 Live LLM smoke validation (manual/opt-in):
 
 ```bash
-CLIO_CODER_LIVE_SMOKE=1 CLIO_CODER_LIVE_TARGET=anthropic ANTHROPIC_API_KEY=your_key npm run test:live
+npm run live:smoke -- --target <configured-target-id>
 ```
 
 ## Testing conventions
@@ -73,14 +73,14 @@ publish is a manual maintainer step. The ordered procedure for a cut lives in
 2. Run `npm run ci:release`. It runs the full `ci` gate, then
    `scripts/check-release.mjs`, which verifies the built `dist/` and audits
    the exact npm package contents.
-3. Land the release commit on `main` and let the `ci` workflow go green on
-   that commit.
+3. Land the release commit on `main`. There is no need to wait on the `ci`
+   workflow before tagging: the release workflow runs the same gate itself.
 4. Tag and push: `git tag -a vX.Y.Z && git push origin vX.Y.Z`. The tag must
    match `package.json`'s version; the release workflow refuses mismatches.
-5. `.github/workflows/release.yml` requires a successful `ci` run for the
-   tagged commit, verifies the tag against `package.json`, builds `dist/`,
-   runs `scripts/check-release.mjs`, and creates the GitHub release with the
-   tarball attached. It does not publish to npm.
+5. `.github/workflows/release.yml` verifies the tag against `package.json`,
+   runs `npm run ci:release` on the tagged tree, and creates the GitHub
+   release with the tarball attached and the version's `CHANGELOG.md` section
+   as the body. It does not publish to npm.
 6. A maintainer publishes from the tagged commit with `npm publish`;
    `prepublishOnly` runs the same `ci:release` gate first.
 

package/README.md

@@ -263,7 +263,7 @@ dist-tag instead.
 From source, pinned to this release:
 
 ```bash
-git clone --branch v0.3.3 https://github.com/iowarp/clio-coder.git
+git clone --branch v0.3.6 https://github.com/iowarp/clio-coder.git
 cd clio-coder
 npm run install:local
 export PATH="$HOME/.local/bin:$PATH"
@@ -289,7 +289,7 @@ Full lifecycle details, including `reset` and the upgrade path, are in
 
 ## Status
 
-The current release is **v0.3.3**, installable from npm as
+The current release is **v0.3.6**, installable from npm as
 [`@iowarp/clio-coder`](https://www.npmjs.com/package/@iowarp/clio-coder) or
 from source. Clio Coder is still experimental: we ship quickly, interfaces may
 change between minor versions, and model-specific behavior varies by target, so
@@ -402,7 +402,7 @@ Conventions worth knowing before your first PR: local imports end in `.js`,
 tests use `node:test`, `any` needs a tracking issue, and compile-time
 boundaries between domains are enforced by the hygiene lint rather than by
 convention. Read [docs/architecture.md](docs/architecture.md) before adding a
-cross-domain import. Live model validation (`npm run test:live`) and the
+cross-domain import. Live model validation (`npm run live:smoke -- --target <id>`) and the
 SWE-bench, SciCode, and Terminal-Bench harnesses under `benchmarks/` are
 separate and opt-in, because no deterministic suite can promise that every
 local model behaves identically.

package/dist/{acp-P2AQILE2.js → acp-2BEHC4DL.js}

@@ -6,17 +6,18 @@ import {
 } from "./chunk-2VTFPG5O.js";
 import {
   runClioCommand
-} from "./chunk-KZWTDYJF.js";
-import "./chunk-CBCAPZAA.js";
+} from "./chunk-XYDYPRZI.js";
+import "./chunk-E25LMLRW.js";
 import "./chunk-HKIYEGME.js";
-import "./chunk-BMEMKKIT.js";
-import "./chunk-YCWGATWI.js";
+import "./chunk-KOHPCX4K.js";
+import "./chunk-24I7BN55.js";
 import {
   printError
-} from "./chunk-ED4KHGC3.js";
+} from "./chunk-PPAMZ32Z.js";
 import "./chunk-5TSRNF4G.js";
-import "./chunk-A3CYT5EX.js";
-import "./chunk-ZDOOVTXZ.js";
+import "./chunk-AD2SYQYC.js";
+import "./chunk-4OC57DA6.js";
+import "./chunk-LL4KHSZI.js";
 import "./chunk-4VP4KH3K.js";
 import {
   MAX_TIMER_DELAY_MS
@@ -125,4 +126,4 @@ export {
   resolveAcpCwd,
   runAcpCommand
 };
-//# sourceMappingURL=acp-P2AQILE2.js.map
+//# sourceMappingURL=acp-2BEHC4DL.js.map

package/dist/{agents-72W3BI7I.js → agents-LNNFTM53.js}

@@ -2,58 +2,62 @@ import { createRequire as __clioCreateRequire } from "node:module"; const requir
 import {
   AgentsDomainModule,
   SafetyDomainModule
-} from "./chunk-PAJK6MAQ.js";
-import "./chunk-5UFT4SUX.js";
+} from "./chunk-LYF7OHWH.js";
+import "./chunk-6XXKFVSN.js";
+import {
+  ensureClioState
+} from "./chunk-KHSFENX2.js";
 import {
   ConfigDomainModule,
   loadDomains
-} from "./chunk-OC7FIQPC.js";
-import {
-  ensureClioState
-} from "./chunk-UFIIWP2H.js";
-import "./chunk-CBCAPZAA.js";
+} from "./chunk-R46L2BIR.js";
+import "./chunk-E25LMLRW.js";
 import "./chunk-QKMUKYO7.js";
 import "./chunk-4BPJXDWC.js";
 import "./chunk-2SFS6XQE.js";
 import "./chunk-ZWLZP4ZT.js";
 import "./chunk-IR4CFBFN.js";
 import "./chunk-UOV2BYIW.js";
-import "./chunk-STBPMHSX.js";
+import "./chunk-EKY57CSP.js";
 import {
   isUserVisibleAgent
-} from "./chunk-5UUP6MWO.js";
-import "./chunk-7MNJORFF.js";
+} from "./chunk-AOCYTWAV.js";
+import "./chunk-MV3K5QF2.js";
+import "./chunk-FYYLNIL5.js";
+import "./chunk-UL3WSD3F.js";
 import "./chunk-ECH6PKUQ.js";
+import "./chunk-HWUFFB6L.js";
 import "./chunk-5B2AEOW5.js";
 import "./chunk-CGKSTWHD.js";
 import "./chunk-XPLRXC72.js";
-import "./chunk-2TLUCQVG.js";
-import "./chunk-BMEMKKIT.js";
-import "./chunk-YCWGATWI.js";
+import "./chunk-RD5U66HV.js";
+import "./chunk-KOHPCX4K.js";
+import "./chunk-24I7BN55.js";
 import {
   printError
-} from "./chunk-ED4KHGC3.js";
+} from "./chunk-PPAMZ32Z.js";
 import "./chunk-5TSRNF4G.js";
-import "./chunk-A3CYT5EX.js";
-import "./chunk-ZDOOVTXZ.js";
+import "./chunk-AD2SYQYC.js";
+import "./chunk-4OC57DA6.js";
+import "./chunk-LL4KHSZI.js";
 import "./chunk-4VP4KH3K.js";
-import "./chunk-M6SHUN7Q.js";
-import "./chunk-R346GLFC.js";
-import "./chunk-VPAYEGVX.js";
-import "./chunk-COU2UHX6.js";
+import "./chunk-VEZEGCGW.js";
 import "./chunk-FQ4SKYE4.js";
 import "./chunk-IKCO5N3L.js";
 import "./chunk-3I7MS7N2.js";
 import "./chunk-IHXBNWMM.js";
 import "./chunk-SST6Z5JA.js";
+import "./chunk-FO5ZOVUY.js";
+import "./chunk-R346GLFC.js";
 import "./chunk-4ZG3XFUR.js";
 import "./chunk-APJ265NV.js";
 import "./chunk-YXLYO42X.js";
 import "./chunk-BNAZZHFG.js";
 import "./chunk-6EJMN2Y3.js";
 import "./chunk-WEPFGWHJ.js";
-import "./chunk-TZTZS7QK.js";
-import "./chunk-OQ33BKR3.js";
+import "./chunk-XE2VEJHX.js";
+import "./chunk-ZGVHUX3M.js";
+import "./chunk-G7MUEIGA.js";
 import "./chunk-IWHMRKLL.js";
 import {
   init_esm_shims
@@ -106,11 +110,12 @@ async function runAgentsCommand(args) {
 function renderLine(spec) {
   const shape = `${spec.audience}/${spec.category}/${spec.capabilityClass}/${spec.latencyClass}`;
   const skills = spec.skills.length > 0 ? ` skills=${spec.skills.join(",")}` : "";
-  const budget = spec.budget ? `${spec.budget.toolCalls}/${spec.budget.readReserve}/${spec.budget.synthesis ? "synthesize" : "stop"}` : "operator-default";
+  const maximum = spec.budget.maximum ? `..${spec.budget.maximum.toolCalls}/${spec.budget.maximum.readReserve}` : "";
+  const budget = `${spec.budget.toolCalls}/${spec.budget.readReserve}${maximum}/${spec.budget.synthesis ? "synthesize" : "stop"}`;
   process.stdout.write(`${spec.id.padEnd(20)} ${shape.padEnd(48)} ${spec.description}${skills} budget=${budget}
 `);
 }
 export {
   runAgentsCommand
 };
-//# sourceMappingURL=agents-72W3BI7I.js.map
+//# sourceMappingURL=agents-LNNFTM53.js.map