@iowarp/clio-coder 0.3.7 → 0.3.8

package/CHANGELOG.md

@@ -2,6 +2,37 @@
 
 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.8 - 2026-08-29
+
+### Added
+- An extension may ship agents, fleets, and namespaced prompts alongside the skills it already provided. `clio-coder-extension.yaml` accepts `resources.agents` and `resources.fleets` beside `resources.skills`, `resources.prompts`, and `resources.themes`, and every declared root is validated when the manifest loads rather than when a resource is first read: a root must be relative, must resolve inside the extension package, must not be the package root itself, must be a directory, and must not reach outside the package through a symbolic link. The whole resource tree is walked for escaping or unresolvable links, and any failure refuses the install with a named diagnostic instead of installing a package whose resources cannot be trusted. Extension agents merge between the builtin recipes and the operator's own, ordered by extension source, so an extension can add an agent but never shadow a shipped one; an attempt is dropped with `ignore override id=<id> by=extension reason=reserved-builtin`. An extension agent's `skills:` bindings resolve only against that same extension's declared skills root with discovery disabled, so a recipe cannot bind a skill from the operator's roots or from another extension, and a binding that escapes the root is refused by name. An extension that binds skills without declaring a skills root is refused rather than silently resolving nothing. Extension fleets take the same position between builtin and user, and a project or user fleet of the same name still wins. Prompts load under the extension's namespace, so `/wtfp:new-paper` addresses the `wtfp` extension's `new-paper` template with no collision against a same-named project prompt, and a `${extensionRoot}` reference in a prompt body resolves to the installed package so a template can cite files it ships. Only an existing path contained by the declaring package resolves; a reference that is missing or escapes is refused with a diagnostic rather than expanding to a path the operator never granted.
+- Nested state resources survive an extension install. The installer excludes `state.json` because that name is the extension manager's own bookkeeping file, but it now excludes only the one at the package root. An extension that ships, say, `core/templates/state.json` as a project-state template keeps it, where every file of that name was previously dropped.
+
+### Changed
+- Receipt integrity moves from v19 to v20, covering the new `pathProvenance` field on dispatch intent (#159). Receipts sealed by 0.3.7 fail verification under 0.3.8 and are never read as evidence; they are not migrated, on the same terms as every prior integrity bump.
+- Legacy path inference is retained with explicit provenance and confidence, and inferred scope is visible before a supervised dispatch runs (#159). #158 made declared intent authoritative and left the inference path unlabelled, so a receipt recorded which project rules applied but never the path set that selected them: the effect was sealed and the cause was discarded. Dispatch intent moves to version 2 and gains `pathProvenance`, one integrity-sealed entry per policy-bearing path carrying its source, whether the value was declared, derived, or inferred, and a confidence with a deterministic ordering. Receipt integrity moves to v20 to cover it. A receipt records that a path was inferred and from which field, never the sentence it was inferred from, so briefing prose stays out of durable evidence. Declared values always outrank inferred ones and inference never widens a scope a declaration closed; an ambiguous or contradictory inference returns a typed refusal rather than passing as though it had been declared. The approval artifact renders inferred policy-bearing scope in full beside the verification argv it already showed, instead of the bare `intent_sha256` hash, and that artifact plus the sealed `pathProvenance` are the two places it appears. A dispatch that declared no intent gets no transcript notice: it is the ordinary case rather than an anomaly, one receipt in ninety-nine carries an intent key today, and warning on it fired on nearly every dispatch, printed twenty entries carrying identical provenance inline, and buried the one scope notice that does mean something.
+- Typed dispatch intent is authoritative for policy-bearing scope, and one path grammar governs every containment check (#158). `readRoots`, `relevantPaths`, and `expectedOutputs` shipped in 0.3.7 with no consumer at all: they were normalized, hashed, and sealed into the receipt, and nothing read them back. Worker rule selection ran on a regular expression over the task and briefing prose, authority admission never saw declared write scope so every writer was admitted against the whole working directory, and five separate containment predicates used three incompatible grammars, under which the entry `src/` meant a subtree to the fleet write boundary and an opaque literal to intent normalization. One owner now defines the grammar, repository-relative POSIX paths where a trailing slash means a subtree and its absence means an exact file, and admission, project-rule selection, worker enforcement, delegation-plan validation, and boundary verification all ask it. The grammar is the fleet write boundary's existing one, so a contract valid before this release means exactly what it meant before. When a request carries `intent`, the declared set replaces prose inference for rule selection and authority rather than joining it, and a path the inference would have contributed that the declaration does not carry is reported to the operator as a transcript notice naming the omitted paths and stating that they selected no project rules and expanded no worker authority. A request without `intent` keeps prose inference unchanged. Batch intent now merges field by field, and a `tasks[]` entry that would widen the top-level declaration is refused rather than silently replacing it.
+- The fleet write boundary stays post-run by design, and the two request constructors say so (#158). Wiring a fleet step's declared `writes` into `spec.writeRoots` would reach the policy engine's blanket refusal of `bash`, `verify`, and `dispatch` under an active write root, which every fleet step running a command depends on. That refusal is honest because the target check can only prove containment when it is handed a concrete write path; narrowing it to admit a fleet-declared command would claim confinement with no mechanism able to enforce it. Pre-emptive fleet confinement needs a command sandbox and is tracked separately.
+
+### Fixed
+- Extension fleets now resolve their own extension-provided agents during `fleet validate` and `fleet graph`. Those read-only commands rebuilt an agent catalog from built-in, user, and project recipes and omitted the extension slot, even though `agents`, `fleet run`, and dispatch used the domain catalog that contained it; a valid installed fleet therefore listed correctly but failed inspection with `unknown agent`. Discovery is now shared with the run and dispatch surface, preserving the existing built-in-before-extension-before-user-before-project precedence, built-in shadow protection, same-extension skill binding, quarantine behavior, and unknown-agent refusal.
+- `$ARGUMENTS` carries the operator's own text byte-for-byte instead of a shell-tokenized reconstruction of it (#240). Every slash prompt template passed its post-command payload through `parseCommandArgs`, whose tokenizer strips both quote characters and splits on spaces and tabs, and then rebuilt the aggregate placeholder with `args.join(" ")`. The round trip silently destroyed every literal quote, every tab, and every run of more than one space, indentation included, from prose the operator had typed. The defect predates this release and reached every slash command, but 0.3.8 is the release that ships namespaced extension prompts and the first real consumer of that surface hit it immediately: a 1,906-character invocation arrived as 1,904, the two missing bytes being the quote characters around a title. `$ARGUMENTS` now carries the exact payload and is substituted after the parsed placeholders, so placeholder-like operator text such as a literal `$1` stays literal rather than expanding a second time. `$1` through `$9`, `$@`, `${@:N}` and `${@:N:L}` keep the shell-tokenized semantics their names describe: quotes still group, and `$@` still joins parsed arguments with single spaces. The first whitespace character after the command name is the delimiter, counting a CRLF pair as one, and every byte after it belongs to the payload.
+- A live fleet is no longer marked failed by an unrelated Clio process starting up (#235). `assignments.json` is machine-wide, so a row still marked `running` does not prove its opener crashed; it usually means another process holds it. Startup reconciliation read `status === "running"` as proof of an orphan and settled every claimed row `failed`, so a second `clio-coder` anywhere on the machine — a CLI command beside an open TUI, a second fleet, an ACP client — declared every fleet in flight a failure while it kept running. The release test caught it on a four-step fleet whose row went terminal 83 seconds early and named a step whose own result was `succeeded: true`; it reproduces in under thirty seconds with two code-only contracts and no model call. This was a regression against #225, which closed the case where the same row lied optimistically. Every live row now persists the orchestrator pid, a process birth token, and an acquisition time, and reconciliation applies the liveness check the checkout writer lease already uses rather than trusting status alone; the owner is cleared only on a true terminal transition. Legacy ownerless rows and genuinely dead owners still reconcile, so `wait` and `collect` can never hang on a real orphan, and an abandoned claimed fleet now settles against its own fleet root instead of filing a successful child attempt as the failed terminal run.
+- The `vote` ballot directive reaches each council member once (#239). `renderCouncilVoteMemberTask` appends the directive to whatever task it is handed, and both plan admission and the runner called it in sequence with the runner receiving admission's output, so every member's integrity-sealed task carried two verbatim copies of the whole block. The vote still tallied correctly, but the directive is specified as bounded and one of its lines is the precedence instruction that stops a small local model answering in its recipe's shape instead of the ballot's — the exact conflict #230 was resolving — and stating a precedence rule twice works against it. The runner now reuses the per-position task admission already pinned into the resolved plan, composing only for a contract with no resolved artifact, so the task the approval artifact binds and the task the receipt seals are byte-identical. Composition is reused rather than made idempotent on purpose: the plan artifact is authoritative, and detecting an already-present suffix could mistake operator-authored text for system composition. The seat, persona, `shadow` audience, read-only autonomy, `council-read-only` profile, ballot contract, and tally are unchanged.
+- A receipt sealed under a retired integrity version is reported as retired, not as corrupt (#238). Receipt integrity moved from v19 to v20 in this release and 0.3.7 receipts are deliberately not migrated, but an intact, correctly sealed 0.3.7 receipt reported `verify fail … integrity invalid` in the TUI and `error: … receipt integrity: integrity invalid` from `evidence build`, which is exactly what a tampered receipt reports; on the release-test machine 99 of 107 receipts were at a retired version, so the release's first impression for anyone with history was an evidence store full of corruption. The verifier's shape check collapsed a wrong version into the same "invalid" as a malformed block, and nothing named either version. There is now a version-mismatch outcome distinct from a digest mismatch, diagnosed ahead of the verifier and carrying both versions: `receipt integrity v19 is retired; this build verifies v20; the receipt is not read as evidence`. The canonical projection distinguishes the two as well, so a retired-format run does not read like a tampered one anywhere: artifact integrity is `unknown` through a compatibility source that names the retired version, the trust line reads `seal v19 retired (this build verifies v20)` where a tampered receipt reads `seal broken`, the receipt-owned axes are absent as `historical_format` rather than `not_observed`, and the verdict is `unknown` rather than `compromised`. `evidence build` records a `receipt-retired` info finding, prints it as a note, and exits 0, since the receipt is set aside unread exactly as a missing one is; `/view verify` and the receipt view report `verify retired` with both versions in the warning color. The receipt is still not migrated and still not read as evidence; the file's digest is unchanged by every one of these reads. Only the reporting changed.
+- The canonical trust projection is the only renderer of a trust axis, on `evidence inspect` and on dispatch (#233). #162 set out to make one trust verdict render the same way everywhere and named this symptom in its own problem statement, and it was still there: `evidence inspect` printed the projection and then unconditionally appended the legacy provenance transcript, which read the receipt directly and never consulted the projection. On a current receipt one axis rendered three times in two vocabularies, `mediated`, `enforced`, and `autonomy enforcement: mediated autonomy=full-auto`; on a receipt whose seal failed, the projection correctly reported `autonomy not recorded` and the block two lines below published `autonomy enforcement: mediated autonomy=read-only` read from that same unverified receipt. Dispatch output carried the same third rendering as an `enforcement=mediated:auto-edit` suffix that `monitor` on the same run did not print. The provenance renderers now take the canonical status and print only what it admits: pipeline, persona-override, and escalation detail behind a verified seal, and the autonomy detail (`autonomy: full-auto mode=… dangerousBypass=…`) only when the projection reports that axis in a recorded state, without the axis word, which the trust summary alone prints. A bundle whose seal was rejected or retired prints no provenance block, `transcript.md` adds no provenance sentence, and `trace.cleaned.jsonl` carries no provenance fields, for the same reason. Without a projection at hand no axis detail is admitted at all, so the dispatch line stops rendering the axis a third time and agrees with `monitor`. A regression test builds a bundle from a receipt at the previous integrity version, and another from a tampered one, and pins that neither rendered output contains an autonomy value.
+- One trust verdict, worded the same way on every surface (#162). #154 defined the algebra and #157 derived receipts and bundles from it, but nothing projected either: two hand-rolled formatters dumped the same six raw axis states with different separators and different completeness, and neither answered who claims this, what was observed, what was independently checked, and what remains unknown without reading receipt internals. A single `evidence inspect` printed the same autonomy fact twice in two vocabularies two lines apart, and it shipped in four spellings across the codebase. Dispatch and monitor collapsed `failed`, `ungrounded` and `absent` validation grounding into one string while the bundle for the same run distinguished them. Evidence findings read two of the six axes, so twelve local runs finished with incomplete completion evidence and nothing said so. The Alt+W board rendered no canonical trust at all, only `host_verification`, which reads as independently verified beside a run whose canonical `independentReview` is `absent`. There are now one compact human projection and one bounded, versioned machine projection carrying references to the detailed artifacts, and dispatch, monitor, the evidence CLI and its reports, findings, the TUI board, the receipt view, and the eval metrics all render the same verdict for the same input. A trust-status glossary is in the docs.
+- The canonical trust status stops reporting valid context provenance as invalid (#162). A `none`-tier run that received the workspace root records real characters, a content hash, and a section, and the adapter refused exactly that shape, so 58 of 91 local receipts and every evidence bundle on this machine read `contextProvenance: invalid`. The axis was invisible on every surface, so nothing surfaced it until the projection above was built. The adapter's rule was written eight days after the producer's behavior shipped and encoded a docblock that was already stale rather than a deliberate stricter model, so the adapter is widened, the docblock is corrected, and the shape a real workspace-root run produces is pinned by a test taken from an actual receipt.
+- The five standing npm audit advisories are cleared, and the release gate now refuses a shipped high (#199). All five reached the published tarball through `@anthropic-ai/claude-agent-sdk` and its MCP dependency chain rather than stopping at the development surface, contrary to the assumption that had let them stand: `package-lock.json` marked every one `"dev": false`. The remaining high was self-inflicted, since this repository's own `overrides` pinned `ip-address` at exactly `10.2.0`, which sat inside an advisory range that had moved past it while the pin held. Dropping that pin and updating four packages within their already-declared semver ranges takes `npm audit` to zero, and the lockfile diff adds and removes nothing: `ip-address` 10.2.0 to 10.5.0, `fast-uri` 3.1.2 to 3.1.6, `hono` 4.12.25 to 4.13.5, `@hono/node-server` 1.19.14 to 1.19.17. Nothing had ever run `npm audit`: CI installs with `--no-audit`, and `scripts/check-release.mjs` audited package contents without asking whether those contents were vulnerable. It now runs `npm audit --omit=dev`, fails the release on a high or critical in a shipped dependency, and prints moderate and low without blocking. There is no environment-variable escape, so shipping a known high takes a reviewable edit.
+- `/council --synthesis vote` asks its members for the verdict it tallies, and produces a real tally (#230). The vote is a strict majority over the final round's structured `verdict` fields, and nothing ever asked a member for one. A council that names no agent seats the builtin `researcher`, whose `research-report` contract accepts `source` and `findings` and nothing else, so a member that emitted a verdict failed its own postcondition and a member that obeyed it emitted no verdict. Every unnamed council's vote resolved to `no_verdict_field` with an empty tally, on every input; the 0.3.7 release test observed exactly this and read it as the specified deterministic behaviour. A vote council now carries a bounded ballot directive on each member's task and seals a new `council-ballot` postcondition, `{"verdict":"...","text":"..."}`, as a per-request override in place of the seated recipe's contract, the same way `reviewer`, the compete `judge`, and the council synthesis already answer the gate that dispatched them rather than their recipe. The seat, the persona, the `shadow` audience, the read-only autonomy, and the `council-read-only` tool profile are all unchanged, and no agent recipe may declare the kind, so a council still runs the agent the operator seated and any recipe can now be voted with. The verdict is bounded to a single line of 64 bytes and lower-cased at the one place a verdict is read, because a tally groups by the exact string and a verdict that is a sentence can only ever tie with itself. A member that seals no conforming ballot spends its ordinary repair rounds and then fails its own run, so a missing verdict is reported as a failed member instead of vanishing from the count. Plan admission composes the same task suffix as the runner, so the approval artifact the plan hash binds shows the ask the member receives. Two things on the override path had to be corrected for it to work at all. A `resultContractOverride` now reaches the worker whether or not the seated recipe declares a contract of its own, matching the resolution the seal has always used; previously the override was sealed but never sent, so the worker spent no repair round on a shape it was never told about. And the worker re-parses its own `WorkerSpec.resultContract` before its first model call through what was the agent-recipe frontmatter parser, which refuses any kind a recipe may not declare, so the first live vote council died with `[worker] fatal: agent recipe: WorkerSpec.resultContract: resultContract.kind is unsupported`; the wire parser is now its own entry point that admits the recipe kinds plus the ones the coordinator authors, and the frontmatter parser stays exactly as strict as it was.
+- A fleet's `assignments.json` row reports the fleet's own verdict instead of whichever step settled last (#225). Every step of a fleet dispatches under the same `lineage.rootRunId`, so all of them share one durable assignment row, and `settleStoredAssignment` had no once-only guard where the in-memory registry has one. Each agent step overwrote the status in turn, so a run that aborted at step 2 of 7 and a run whose final code step exited 1 were both recorded `succeeded`. The receipt was not lying: a write-boundary verdict is applied by the scheduler after the receipt seals, so the assignment path never saw it. A fleet run now claims its row at open, files every settled step as an attempt including code steps, and settles the row once from its own whole-run verdict on both the normal and the throwing path; an attempt-path settle against a claimed row records its attempt and cannot write the status. Orphan reconciliation no longer resolves a claimed record to `succeeded` on the strength of one green attempt, which would have turned a crashed fleet into a successful one on the next startup.
+- The test harness refuses a `.git` at the system temp root and names whoever tried to make one (#205). A stray empty `/tmp/.git` makes `isInsideGitRepo` report every `mkdtemp` scratch as sitting inside a git repository, which drops `--no-require-git` and fails the ignore-policy contracts from whichever lane happens to run them. The creating test was not identified across 28 full suite runs, live `node:fs` and `node:child_process` instrumentation, and a static sweep, so the guard is the fix instead: an in-process write to `<systemTmp>/.git` or `<runRoot>/.git` throws before the entry exists with the test file and line in the stack, a synchronous spawn that creates one throws with its argv and cwd, an asynchronous one is reported at process exit, and `scripts/shard-tests.mjs` backstops the whole run for a creator outside every lane. The guard never deletes, because a `.git` under the system temp root can belong to somebody else. The run root is guarded alongside the system temp root because the same parent walk passes through it.
+- `/council --synthesis judge` runs, seals, and shares as a council (#221). Three defects sat on the default path. Admission refused the whole council before its first member ran, because the persona-override guard counted any non-empty system prompt and the judge carries the coordinator's own `COUNCIL_JUDGE_PROMPT`, while every unnamed council seats the builtin `researcher`, a `shadow` recipe; the ACP delegation path already exempted a bounded gate-role prompt and the two ordinary paths had drifted from it, so all three now share one predicate that stays pinned to one exact prompt text under one gate role and read-only autonomy. The synthesis slot then kept the seated recipe's result contract, so a correct judge answer of `{verdict, text}` sealed a contract failure against `research-report` and burned the configured retries reproducing it; `synthesis` now joins `reviewer` and `judge` as a gate role that answers the coordinator rather than its recipe. And the whole-council-report seal was guarded to vote and none, so `/share <judge synthesis runId>` rendered the bare judge payload with no member answers or roster labels, the exact state the 0.3.7 release test called unusable; judge now seals on the same terms, and the shared block carries every final member's labelled answer plus `[synthesis judge] verdict … · judge run …`.
+- The write boundary no longer rolls back a file the step never wrote, and no longer certifies a window it could not observe (#219). Enforcement derived violations from the working-tree diff over a step's window alone, so a file an operator edited in their own editor while a fleet ran was attributed to the step and restored from the baseline commit. A change is now blamed on a window only when it intersects what that window's runs recorded writing, drawn from the same tool-call fold that grounds a sealed mutation report; anything else is reported as an unattributed concurrent change and left exactly as it is. The record is treated as closed only when it can be: a run that made a successful call to a tool whose arguments cannot name what it writes (`bash`, `verify`, `dispatch`, `steer`, or any unregistered or MCP name, derived from the action classifier rather than a hand-written list) files no usable record, and its window keeps the previous behavior of blaming the whole diff. A blocked or failed call leaves the record closed, because it never reached the filesystem. The verdict gains `unattributed` and `attributionComplete` so it says which of the two it did. Separately, a declared write path that git ignores is now refused at `fleet validate`, at `fleet run` preflight, in the `/fleet run` preview, and when a delegation plan splices a step in, naming the path and the ignoring rule: `git status` cannot report an ignored path, so such a boundary could only ever certify an unobserved window as clean. The existing refusal to touch a path that was already dirty when the window opened is unchanged.
+- `configure` refuses a model the target does not advertise, and health distinguishes reachable from serving (#220). The command already fetched the server's model list to populate `wireModels`, but validated `--model` against the static provider catalog, which is empty for `lmstudio` and every runtime like it, so `src/cli/validate-model.ts` passed any string and the target saved as `ok`. It now checks the live list where there is one, refuses an unadvertised id while naming the ids the server does list, and takes `--force` to save one anyway. A runtime with neither a catalog nor a live list warns that the id could not be verified rather than implying it was. A loaded LM Studio model is accepted under either its instance id or its model key, since the request path resolves both. `targets --probe` gains a `degraded` health state for a target that answers but cannot serve its own `defaultModel`, judged only from a live list on a runtime with no static catalog so a cloud target can never be misread, and the row prints the reason beside the model. `doctor` reports a configured `defaultModel`, `orchestrator.model`, or `workers.default.model` that the target does not advertise. ACP treats `degraded` as reachable, because a client naming its own model can still use the target. The `README.md` quickstart and the two docs copies stop instructing readers to pass `your-model-id`, which produced a target that saved cleanly and failed on its first turn.
+- A version 5 `kind: gate` step that also declares `writes` is refused by name (#217). The gate derives its whole write boundary from `path`, and the refusal now reads `gate step '<id>' must not declare 'writes'; its write boundary is derived from 'path'` instead of `/steps/0: must have required properties scope`, which named a property the author never touched. The check runs before schema validation, alongside the existing version-gate assertions, so `fleet validate`, `fleet run`, and the `/fleet run` approval preview all print it.
+- Settings Center number editors report a refused value instead of dropping it (#218). Every number row now resolves its bound from one shared rule table (`budget.sessionCeilingUsd`, `watchdog.cadenceToolCalls`, and the three `delegation.defaults.*Ms` rows), and the editor and the apply path read the same rule, so a value the editor forwards is never dropped later. A refused submission keeps the editor open and prints the reason under the input in the words the config validator would use for the same key (`Not applied: expected an integer >= 1, got 0.`); Esc still leaves without applying, and a corrected value clears the reason and continues to the scope prompt. Three previously silent drops on that path become named refusals: a blank on the three timeout rows used to parse as zero and be discarded, a blank on `budget.sessionCeilingUsd` used to set the ceiling to zero, and a fractional `watchdog.cadenceToolCalls` used to be floored. A contract test pins the row set, so a sixth number row added without a rule fails it.
+
 ## 0.3.7 - 2026-08-24
 
 ### Added

package/README.md

@@ -127,7 +127,7 @@ Scripting the same setup the wizard performs:
 
 ```bash
 clio-coder configure --id local-lmstudio --runtime lmstudio \
-  --url http://localhost:1234 --model your-model-id \
+  --url http://localhost:1234 --model qwen3.8-27b \
   --set-orchestrator --set-fleet-default
 clio-coder targets --probe
 
@@ -135,6 +135,11 @@ clio-coder auth login anthropic-max     # or: openai-codex
 clio-coder configure --id claude-sub --runtime anthropic-max --model claude-sonnet-5 --set-orchestrator
 ```
 
+`--model` must name an id the server advertises; `configure` asks the server
+and refuses one it does not list, naming the ids it does. `qwen3.8-27b` is the
+id LM Studio gives the recommended model above; substitute whatever `lms ls`
+shows for yours.
+
 > [!NOTE]
 > Connecting a Claude Pro/Max subscription over OAuth uses the same path as
 > Claude Code. Using subscription credentials outside a vendor's first-party
@@ -274,7 +279,7 @@ dist-tag instead.
 From source, pinned to this release:
 
 ```bash
-git clone --branch v0.3.7 https://github.com/iowarp/clio-coder.git
+git clone --branch v0.3.8 https://github.com/iowarp/clio-coder.git
 cd clio-coder
 npm run install:local
 export PATH="$HOME/.local/bin:$PATH"

package/dist/{acp-SK4MD6MM.js → acp-U67UHUK2.js}

@@ -6,31 +6,31 @@ import {
 } from "./chunk-2VTFPG5O.js";
 import {
   runClioCommand
-} from "./chunk-MXI6J5JF.js";
-import "./chunk-YD734TPH.js";
+} from "./chunk-VWZOAB7K.js";
+import "./chunk-26LEYJZH.js";
 import "./chunk-HKIYEGME.js";
-import "./chunk-DOOEX22V.js";
-import "./chunk-465YSENW.js";
+import "./chunk-IFBNV6H6.js";
+import "./chunk-XWSF374K.js";
 import {
   printError
-} from "./chunk-PPAMZ32Z.js";
+} from "./chunk-XK56QHLX.js";
 import "./chunk-5TSRNF4G.js";
-import "./chunk-JRIO5UD2.js";
-import "./chunk-UHXRNZ2J.js";
-import "./chunk-4DGYLA73.js";
-import "./chunk-LL4KHSZI.js";
-import "./chunk-SST6Z5JA.js";
+import "./chunk-IJ7RPIYJ.js";
 import {
   MAX_TIMER_DELAY_MS
 } from "./chunk-FQ4SKYE4.js";
+import "./chunk-IWHMRKLL.js";
+import "./chunk-4DGYLA73.js";
+import "./chunk-LL4KHSZI.js";
 import "./chunk-4ZG3XFUR.js";
+import "./chunk-EQ63NRB7.js";
+import "./chunk-SST6Z5JA.js";
 import "./chunk-IKCO5N3L.js";
 import "./chunk-3I7MS7N2.js";
 import "./chunk-APJ265NV.js";
-import "./chunk-YXLYO42X.js";
 import "./chunk-BNAZZHFG.js";
 import "./chunk-WEPFGWHJ.js";
-import "./chunk-IWHMRKLL.js";
+import "./chunk-YXLYO42X.js";
 import {
   init_esm_shims
 } from "./chunk-3R73A4XB.js";
@@ -126,4 +126,4 @@ export {
   resolveAcpCwd,
   runAcpCommand
 };
-//# sourceMappingURL=acp-SK4MD6MM.js.map
+//# sourceMappingURL=acp-U67UHUK2.js.map

package/dist/{agents-2FN2K6ME.js → agents-YU6SGALZ.js}

@@ -1,31 +1,32 @@
 import { createRequire as __clioCreateRequire } from "node:module"; const require = __clioCreateRequire(import.meta.url);
 import {
   SafetyDomainModule
-} from "./chunk-J7PIKKWC.js";
-import "./chunk-JTSEDYVQ.js";
+} from "./chunk-EMYUUSFG.js";
+import "./chunk-5Q2VVUKB.js";
 import {
   ensureClioState
-} from "./chunk-3HAPLH5M.js";
+} from "./chunk-WWCZ5F23.js";
 import {
   ConfigDomainModule,
   loadDomains
-} from "./chunk-BMWK7ZIZ.js";
-import "./chunk-YD734TPH.js";
-import "./chunk-RVG5JXAL.js";
+} from "./chunk-FHJEP5SW.js";
 import {
   AgentsDomainModule
-} from "./chunk-UVDSQ6LW.js";
+} from "./chunk-FBVTI2TJ.js";
 import "./chunk-DR52UMZW.js";
-import "./chunk-C4JBQ5SR.js";
-import "./chunk-2SFS6XQE.js";
-import "./chunk-ZWLZP4ZT.js";
-import "./chunk-KCMKRQX4.js";
-import "./chunk-IR4CFBFN.js";
+import "./chunk-TANS5ZJS.js";
+import "./chunk-DGSYXYMX.js";
+import "./chunk-26LEYJZH.js";
+import "./chunk-WXY7KU3G.js";
+import "./chunk-RVG5JXAL.js";
+import "./chunk-E77JEWSD.js";
+import "./chunk-DYIM5TJT.js";
+import "./chunk-VCBR6CU7.js";
 import "./chunk-UOV2BYIW.js";
-import "./chunk-OBMAI2DP.js";
-import "./chunk-GH5622CP.js";
+import "./chunk-5H3GB5BO.js";
+import "./chunk-A2NJGIB3.js";
 import "./chunk-HWUFFB6L.js";
-import "./chunk-DJNLUABN.js";
+import "./chunk-TTHACPOM.js";
 import {
   isUserVisibleAgent
 } from "./chunk-AOCYTWAV.js";
@@ -35,35 +36,36 @@ import "./chunk-ECH6PKUQ.js";
 import "./chunk-5B2AEOW5.js";
 import "./chunk-CGKSTWHD.js";
 import "./chunk-XPLRXC72.js";
-import "./chunk-SROCI7ZU.js";
-import "./chunk-DOOEX22V.js";
-import "./chunk-465YSENW.js";
+import "./chunk-IFBNV6H6.js";
+import "./chunk-GPIEI3LY.js";
+import "./chunk-XWSF374K.js";
 import {
   printError
-} from "./chunk-PPAMZ32Z.js";
+} from "./chunk-XK56QHLX.js";
 import "./chunk-5TSRNF4G.js";
-import "./chunk-JRIO5UD2.js";
+import "./chunk-LU7P4LHA.js";
 import "./chunk-IHXBNWMM.js";
-import "./chunk-UHXRNZ2J.js";
+import "./chunk-B5CSFE7B.js";
+import "./chunk-IJ7RPIYJ.js";
+import "./chunk-FQ4SKYE4.js";
+import "./chunk-ZGVHUX3M.js";
+import "./chunk-TT36MB5S.js";
+import "./chunk-3BINW3FP.js";
+import "./chunk-R346GLFC.js";
+import "./chunk-6EJMN2Y3.js";
+import "./chunk-IWHMRKLL.js";
 import "./chunk-4DGYLA73.js";
 import "./chunk-LL4KHSZI.js";
-import "./chunk-SST6Z5JA.js";
-import "./chunk-FO5ZOVUY.js";
-import "./chunk-R346GLFC.js";
-import "./chunk-D4MDIG46.js";
-import "./chunk-FQ4SKYE4.js";
 import "./chunk-4ZG3XFUR.js";
+import "./chunk-EQ63NRB7.js";
+import "./chunk-SST6Z5JA.js";
 import "./chunk-IKCO5N3L.js";
 import "./chunk-3I7MS7N2.js";
 import "./chunk-APJ265NV.js";
-import "./chunk-YXLYO42X.js";
 import "./chunk-BNAZZHFG.js";
-import "./chunk-6EJMN2Y3.js";
 import "./chunk-WEPFGWHJ.js";
-import "./chunk-X2KV5FXT.js";
-import "./chunk-ZGVHUX3M.js";
-import "./chunk-OB5HIGJY.js";
-import "./chunk-IWHMRKLL.js";
+import "./chunk-NUGM5KR6.js";
+import "./chunk-YXLYO42X.js";
 import {
   init_esm_shims
 } from "./chunk-3R73A4XB.js";
@@ -123,4 +125,4 @@ function renderLine(spec) {
 export {
   runAgentsCommand
 };
-//# sourceMappingURL=agents-2FN2K6ME.js.map
+//# sourceMappingURL=agents-YU6SGALZ.js.map