@iowarp/clio-coder 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -2,6 +2,45 @@
 
 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.4.1 - 2026-09-01
+
+This grew beyond the bug-fix-only patch originally planned. v0.4.1 is a full release led by the version-2 `settings.yaml` contract, its automatic migration, and a smaller grammar-driven slash-command surface. It adds editor and marketplace workflows; fixes the release-blocking configuration, CLI, TUI, and Workbench failures found in final testing; replaces the oversized test and CI machinery with one fast deterministic gate; consolidates evaluation around the shipping eval domain and `evals/` reference suites; and moves machine-facing names into the `clio-coder` namespace without changing the product persona.
+
+### Changed
+- `settings.yaml` is now a strict version-2 document organized around `chat`, `fleet`, `targets`, `context`, `safety`, `interface`, and `integrations`. `clio-coder upgrade` automatically runs the one-time v1 transformation before the strict config domain loads, validates the complete result in memory, refuses source/destination collisions without touching the original, writes atomically, preserves a sibling `settings.yaml.v1.bak`, and records the moved and retired paths in a migration report. Version-2 files execute only canonical paths; old spellings are non-executing tombstones with replacement guidance rather than permanent aliases.
+- Panes, docks, and Yazi integration are experimental and opt-in: fresh homes keep pane mode, layout, and files off, diagnostics stay neutral while they are off, and migration preserves explicit v1 choices.
+- The slash registry now has an explicit `Work`, `Inspect`, `Configure`, and `Session` order and seven canonical Settings deep links: `/settings chat|fleet|targets|context|safety|interface|integrations`. Resource browsing is consolidated under `/resources skills|prompts|library|extensions`; `/library`, `/prompts`, and `/extensions` now stop with targeted `/resources` guidance, while `/targets` points to `/settings targets` and `/scoped-models` to `/settings chat model-picker`. Other split or renamed surfaces follow the same non-executing-tombstone rule, including `/agents connect`, `/archive import|export`, and `/context compact` replacing their retired spellings.
+
+### Added
+- Grammar-aware slash autocomplete now follows the same command specifications used for parsing. It completes commands, subcommands, flags, closed values, and Settings areas; replaces the token under the cursor without discarding suffix text; respects quotes and explicit command order; exposes structured submenus; suppresses submit-ready exact matches; and generation-checks asynchronous results so stale suggestions cannot overwrite a newer prefix.
+- Typing `@` in ordinary editor text opens a workspace-aware file picker with relative paths, metadata, and previews, then inserts the selected `@path` reference into the draft. File-reference spellings are kept distinct from steer targets, and explicit path completion shares the same cursor-aware replacement behavior.
+- The editor's existing bang operators now have an enforceable public/private boundary. `!command` remains part of later model context, while `!!command` runs visibly but its command and output are excluded from replay, token accounting, and compaction summaries and are marked model-private in evidence. Multiline bracketed pastes beginning with `!` or `!!` remain literal user text through Enter, alternate-send keys, interrupts, and subsequent edits instead of arming shell execution.
+- Marketplace self-promotion can locally match an operator request to an uninstalled catalog skill using the shipped catalog's new `triggers` metadata plus a conservative description-token fallback; request text never leaves the process. The coordinator can offer project or user installation, remember “Not now” for the session, or persist “Never offer” by skill name and version. Full-auto may install at project scope, but every consented or autonomous promotion install passes a hard runtime gate that accepts only Clio's shipped catalog or the `iowarp/clio-coder` repository tree; public registries and foreign GitHub sources are refused before installation. Offers are coordinator-only, source and content hash remain visible on autonomous installs, and installation never activates the skill for the model.
+
+### Fixed
+- Fleet CLI help and missing-journal diagnostics name the version-2 `fleet.history.journal` setting instead of its retired `panes.journal` spelling.
+- Marketplace-offer middleware caches installed and catalog skill inventory per session, revalidating only before a real offer, so ordinary `turn_start` evaluation no longer reparses every skill on every turn.
+- Model-picker `[Enter] use` now leaves the session/global confirmation open and applies the selected target/model binding after the operator chooses a scope.
+- The two settings-v2 release blockers found by black-box testing are closed. A migrated v1 home no longer crashes while reading `target`, and a fresh v2 home no longer crashes while reading `agents` or `target`; both reach diagnostics and the interactive editor. The real built-binary matrix passed once at `616b10a2` and was repeated at `9959652c`, including v1 upgrade, empty-home onboarding, all seven Settings deep links, retired-command tombstones, autocomplete, file references, bang context exclusion, paste inertness, and marketplace flows.
+- The SOL-01 through SOL-03 smoke failures are fixed: plain `clio-coder doctor` is read-only unless `--fix` is supplied; absent trace storage preserves JSON contracts for `trace runs --json` and `trace prune --json`; and command, argument, and read-only SQL validation now runs before trace storage opens.
+- The SOL-04 through SOL-07 smoke failures are fixed: Ctrl+C during `clio-coder configure` reports cancellation and exits 130; cancelled first-run onboarding stops instead of entering an unconfigured TUI; `fleet view --help` prints view-specific usage; and non-follow fleet snapshots contain no stray ANSI reset bytes under `NO_COLOR`.
+- Operator-facing TUI prose now wraps to the available width instead of silently losing remedy text across interviews, context and cwd choices, task/evidence reasons, notifications, model diagnostics, decisions, artifacts, dispatch cards, and fleet snapshots. Retry errors preserve normal provider remedies while bounding runaway bodies at 2,000 Unicode characters with an explicit truncation marker.
+- The Settings Center now owns narrow screens without transcript bleed-through, expands help into otherwise unused rows, and hides parent controls while a submenu owns input. Narrow prompt-template columns have a real gap and no duplicated argument synopsis, while long skill-suggestion descriptions end with an explicit truncation marker.
+- Workbench permission handling now uses one host-clock domain for expiry and escalation, honors the earlier of ACP and Workbench deadlines, escalates immediately when the remaining window is shorter than the delay, cancels already-expired requests without publishing an invalid card, and serializes `resolvePermission`, `cancelTurn`, and `abandon` with turn closure.
+- The interactive Fleet settled notice now uses the shared provenance-aware cost formatter, reporting an entirely unpriced run as `not measured` and preserving estimated or partly priced provenance instead of presenting an invented measured `$0.0000`.
+
+### Test-suite diet
+- The automated suite was rebuilt from 557 files and 183,969 physical lines into 35 behavior-focused files and 5,179 lines at the diet landing: 30 contract suites cover the boundaries, lifecycles, migrations, and integrity properties that can break the product, while five smoke suites exercise the CLI, ACP, process lifecycle, installed package, and real binary. The custom 24-lane shard runner, its timing weights and serial lane, repeat/shuffle machinery, test-only seams, and most harness scaffolding are gone; `npm test` is now a plain `node --test` invocation and the warm suite measures about 21.3 seconds. The weekly `flake-hunt` workflow retired with the timing- and order-flake machinery it existed to exercise.
+
+### CI modernization
+- Push and pull-request CI is one Node 22 job that installs once and runs `npm run ci:release`; the tag-only release workflow independently reruns that same gate before packaging. The rebuilt workflow was verified green on GitHub Actions in 1m48s, down from 7m32s for the preceding successful main-branch run. There is no shard matrix, repeat lane, weekly flake hunt, or eval baseline in either CI or the release gate.
+
+### Eval consolidation
+- Clio Coder now ships one evaluation system: the product engine under `src/domains/eval/` owns suites, execution, verdicts, artifacts, comparison, and reporting, and the maintained runnable reference suites ship under `evals/`. The parallel `benchmarks/` tree and its internal campaign harness are retired to `archive/v041-pre-diet`; future external-benchmark adapters enter through the eval engine rather than creating another stack. Evals remain explicit operator-run measurements and do not run in ordinary CI or release gates.
+
+### Clio Coder naming migration
+- Machine-facing identifiers now follow one syntax-aware Clio Coder namespace: `clio-coder` for paths, package and manifest names, schema and event identifiers, tags, and Git refs; `clio_coder` where underscores are required; and `CLIO_CODER` for environment variables. Existing homes receive one idempotent `2026-09-01-clio-coder-naming` migration recorded in `migrations.json`, with an atomic settings backup and a detailed migration report. Canonical writers use the new names immediately, while readers accept released legacy names through the two-minor v0.5/v0.6 compatibility window and preserve longer read support where sealed artifacts, exported archives, host panes, or published Git refs require it. The Clio product persona and its operator-facing identity text are unchanged.
+
 ## 0.4.0 - 2026-08-31
 
 ### Added

package/README.md

@@ -45,7 +45,7 @@ clio-coder                # start the interactive session in any project directo
 ```
 
 Requires Node.js `>=22.19.0`. `configure` lists the runtimes, asks for the
-endpoint and model, probes it, and saves it as the chat and worker target; bare
+endpoint and model, probes it, and saves it as the chat and fleet default; bare
 `clio-coder` opens the same wizard when nothing usable is configured yet. In the
 first session, type a request in plain words or `/help` for the command
 palette. `/settings` changes the model later, `/quit` leaves, and
@@ -56,6 +56,43 @@ proprietary binary, taking the tree from 387MB to 143MB. Everything but the
 `claude-sdk` worker runtime works without it. See
 [Installation and Lifecycle](docs/installation-and-lifecycle.md#optional-dependency-the-claude-agent-sdk).
 
+## What changed in v0.4.1
+
+- **`settings.yaml` v2** replaces the accumulated legacy layout with seven
+  durable areas: `chat`, `fleet`, `targets`, `context`, `safety`, `interface`,
+  and `integrations`. `clio-coder upgrade` automatically migrates a v1 (or
+  unversioned pre-v2) file once, writes it atomically, and keeps the original as
+  `settings.yaml.v1.bak`.
+- **The interactive command surface is smaller and explicit.** `/settings`
+  accepts the same seven area names, resources meet under `/resources`, and
+  retired slash commands stop at targeted tombstones instead of falling
+  through to the model.
+- **The editor operator family is honest about context.** `@` opens a
+  workspace-aware file picker, `!` runs a public shell command whose result can
+  enter model context, and `!!` runs a context-excluded shell command that
+  remains visible to you but is never sent to a model.
+- **The local skills marketplace can meet a request in flight.** Clio may offer
+  a matching uninstalled skill, but every install initiated by that promotion
+  flow is hard-gated to Clio's own shipped catalog or the
+  `iowarp/clio-coder` repository. A public registry or foreign GitHub source is
+  refused before the installer runs.
+- **Evaluation and release validation each have one path.** The product eval
+  engine remains under `src/domains/eval/`, runnable reference suites ship
+  under `evals/`, and evals stay outside CI and release gates. The automated
+  gate is now 35 focused test files driven directly by `node --test` through a
+  single fast CI job.
+- **Machine-facing names use the Clio Coder namespace.** New paths, schemas,
+  tags, environment variables, Git refs, and manifests use syntax-appropriate
+  `clio-coder`, `clio_coder`, or `CLIO_CODER` forms. Upgrade records one naming
+  migration, and readers retain the released legacy spellings through v0.5 and
+  v0.6. The Clio persona and operator-facing identity text are unchanged.
+
+The release also hardens the surfaces that tend to fail outside unit tests:
+plain `doctor` is read-only again, configure cancellation exits correctly,
+trace empty states preserve their JSON contracts, fleet views wrap and honor
+`NO_COLOR`, Settings and other interactive prose stop losing remedy text, and
+the Workbench lifecycle closes its timing and recovery gaps.
+
 |  | You are | Start here |
 | --- | --- | --- |
 | 🔬 | A researcher or developer who wants to use it | [Your models](#your-models-your-choice) → [At the keyboard](#at-the-keyboard) → [Safety](#safety-you-can-read) |
@@ -115,6 +152,7 @@ or the reverse.
 | `lmstudio` | LM Studio |
 | `ollama-native` | Ollama |
 | `vllm`, `sglang` | vLLM and SGLang |
+| `litellm` | LiteLLM gateways with per-alias capability discovery and routed-model attribution |
 | `lemonade`, `lemonade-anthropic` | Lemonade |
 | `openai-compat`, `anthropic-compat` | Any OpenAI- or Anthropic-shaped endpoint |
 | `openai`, `anthropic`, `google`, `groq`, `mistral`, `deepseek`, `openrouter`, `bedrock` | Cloud APIs |
@@ -165,11 +203,12 @@ Run `clio-coder` from the repository you want to work on. The session opens on a
 one-line header that names where Clio is working, which route answers, and
 whether project context is ready, and then the transcript owns the screen.
 Tool calls render as live rows with their verdicts, successful edits render as
-numbered diffs, and `!` runs a shell command in the same transcript.
+numbered diffs, and editor operators put files and local shell output in the
+same transcript.
 
 | You want to | Type |
 | --- | --- |
-| Change model, target, thinking level, autonomy, or terminal options | `/settings`, `/model`, `/thinking` |
+| Change model, target, thinking level, autonomy, or terminal options | `/settings [chat\|fleet\|targets\|context\|safety\|interface\|integrations]`, `/model`, `/thinking` |
 | See what is in the context window and what it costs | `/context`, `/cost` |
 | Branch, revisit, or pick up a session | `/tree`, `/fork`, `/resume`, `/new` |
 | Delegate to a fleet agent and watch it work | `/run coder "..."`, `/tasks`, `Alt+W` |
@@ -177,16 +216,63 @@ numbered diffs, and `!` runs a shell command in the same transcript.
 | Ask a side question without touching the session, or get a read-only second opinion | `/btw <question>`, `/oracle <question>` |
 | Put the same question to several models at once and read one synthesis | `/council --synthesis vote "..."` |
 | Preview and run a multi-step fleet contract, resumable from the CLI | `/fleet run <name>` |
-| Install agents, prompts, fleets, and skills from a catalog | `/library`, `/library agents` |
+| Browse or install agents, prompts, fleets, extensions, and skills | `/resources`, `/resources library agent` |
 | Carry the working state into a fresh session | `/handoff <goal>` |
 | Save a self-contained HTML transcript | `/export` (an explicit `.md` path keeps Markdown) |
 | Everything else | `/help` |
 
 Enter while Clio is running steers the current turn; `Alt+Enter` queues a
-follow-up; `Esc` cancels. Settings → Terminal offers an opt-in fullscreen mode
-with a sticky composer beneath an independently scrollable transcript; regular
-terminal scrollback is the default. The complete command and keybinding
-reference is [docs/commands-and-modes.md](docs/commands-and-modes.md).
+follow-up; `Esc` cancels. `/settings interface` opens the Terminal options,
+including an opt-in fullscreen mode with a sticky composer beneath an
+independently scrollable transcript; regular terminal scrollback is the
+default. The complete command and keybinding reference is
+[docs/commands-and-modes.md](docs/commands-and-modes.md).
+
+### Settings v2 and the seven areas
+
+The user config is a strict `version: 2` YAML document. Its seven top-level
+areas match the seven arguments accepted by `/settings`. Those arguments are
+stable deep links into the current Settings Center; the overlay still divides
+the detailed editor into its existing subsections, while the durable paths on
+disk use the seven-area vocabulary below.
+
+| Area | What it owns |
+| --- | --- |
+| `chat` | Active target and model, thinking, model-picker state, output limits, prewarm, and interactive retry |
+| `fleet` | Worker defaults and profiles, rosters, agent bindings, routing, nodes, permissions, limits, retry, and run history |
+| `targets` | Provider/runtime connections, advertised models, capabilities, and routing roles |
+| `context` | Working-set eviction, compaction, and proactive task memory |
+| `safety` | Autonomy, cost/tool/read ceilings, and the review watchdog |
+| `interface` | Output detail, terminal mode, streaming, notifications, and keybindings |
+| `integrations` | Project resource trust, external agents, runtime plugins, resource libraries, and Git attribution |
+
+When upgrading an existing install, run `clio-coder upgrade`. The v1-to-v2
+migration runs before strict v2 consumers load, records its migration id so it
+does not run twice, writes through an atomic rename, and leaves the byte-exact
+v1 file beside the result as `settings.yaml.v1.bak`. If old and new paths
+collide, it refuses the migration and leaves the original untouched instead of
+guessing which value should win.
+
+The removed slash spellings are non-executing tombstones with exact remedies:
+`/targets` points to `/settings targets`, `/scoped-models` points to
+`/settings chat model-picker`, and `/library`, `/prompts`, and `/extensions`
+point to their `/resources` equivalents. The `clio-coder targets`,
+`clio-coder skills`, and other CLI command families remain available; this
+cleanup applies to slash commands inside the interactive session.
+
+### The operator family today
+
+| Operator | Behavior |
+| --- | --- |
+| `@` | Opens the workspace-aware picker. A bare `@` starts at the workspace root, a name fuzzily searches visible paths, and directory prefixes drill into the tree. Selecting a file inserts a reference that is expanded into the request when submitted. |
+| `! command` | Runs one shell command in the interactive working directory. The durable transcript entry, command, and output are available to model replay and compaction. |
+| `!! command` | Runs the same shell path and keeps the result visible and durable, but marks both command and output `not sent to model`; replay, compaction, and context accounting all exclude it. |
+
+Bang operators arm only for a non-empty, typed, single-line draft. A
+bracketed-pasted `!` or `!!` line, or any multiline draft beginning with one,
+is treated as literal prompt text rather than executed.
+
+Panes, docks, and Yazi integration are experimental and opt-in in v0.4.1; enable them explicitly under `interface.panes` in `settings.yaml`.
 
 Outside the TUI, the same engine runs headless and speaks to editors:
 
@@ -269,6 +355,19 @@ an installed copy verifies against its audited source, and
 `clio-coder skills eval <name>` runs a skill's executable evals instead of
 trusting the prose.
 
+The catalog is also a local marketplace. On a request that matches an
+uninstalled skill and is not already covered by an installed one, the
+coordinator can offer project install, user install, not now, or never for that
+skill version, then continue the task in the same turn. Matching is local and
+lexical; request text does not leave the machine. Full-auto may skip the
+question, but it cannot skip the source gate: consented and autonomous
+promotion installs both accept only the shipped local catalog or this
+repository's own tree, and they install without activating. Dispatch workers
+never receive offers, and only the operator activates a skill with `/skill`.
+Manual `clio-coder skills install <path|github-url>` remains available for a
+source you deliberately choose; the own-marketplace guarantee governs what
+Clio installs on its own initiative.
+
 **Task memory** keeps long runs from drifting: a rules-only tier with no model
 calls watches tool and lifecycle hooks and surfaces advisory reminders at the
 right boundaries, `/memory` inspects it, and durable lessons are reviewed with
@@ -288,7 +387,7 @@ dist-tag instead.
 From source, pinned to this release:
 
 ```bash
-git clone --branch v0.4.0 https://github.com/iowarp/clio-coder.git
+git clone --branch v0.4.1 https://github.com/iowarp/clio-coder.git
 cd clio-coder
 npm run install:local
 export PATH="$HOME/.local/bin:$PATH"
@@ -314,7 +413,7 @@ Full lifecycle details, including `reset` and the upgrade path, are in
 
 ## Status
 
-The current release is **v0.4.0**, installable from npm as
+The current release is **v0.4.1**, 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
@@ -346,8 +445,8 @@ If you are an AI agent operating inside this repository or driving Clio as a
 tool, start here.
 
 **Orient from the index, not from a wide read.** `clio-coder context index`
-builds a codewiki over the roughly 1,200 source and test files; use `code_nav`
-in `entries`, `path`, or `symbol` mode first. The indexed entry points are
+builds a codewiki over the source and test tree; use `code_nav` in `entries`,
+`path`, or `symbol` mode first. The indexed entry points are
 `src/cli/index.ts`, `src/domains/agents/index.ts`,
 `src/domains/components/index.ts`, `src/domains/config/index.ts`,
 `src/domains/context/bootstrap.ts`, `src/domains/context/index.ts`,
@@ -427,10 +526,11 @@ 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 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.
+cross-domain import. Live model validation
+(`npm run live:smoke -- --target <id>`) and the runnable reference suites under
+`evals/` are explicit, opt-in measurements. Neither runs in CI or the release
+gate, because no deterministic suite can promise that every local model
+behaves identically.
 
 ## Documentation
 

package/dist/{acp-G5WJBNCT.js → acp-ZILU3AUO.js}

@@ -6,25 +6,26 @@ import {
 } from "./chunk-2VTFPG5O.js";
 import {
   runClioCommand
-} from "./chunk-GR5G2PVF.js";
-import "./chunk-7MCTRUCE.js";
-import "./chunk-HKIYEGME.js";
-import "./chunk-2OQE55CK.js";
-import "./chunk-2ANTL7MR.js";
+} from "./chunk-GVQJ5CCZ.js";
+import "./chunk-VKRH2TCS.js";
+import "./chunk-ZTJUVLTU.js";
+import "./chunk-7PWAODYW.js";
+import "./chunk-ZW55JB7N.js";
 import {
   printError
 } from "./chunk-VPKWYKEY.js";
 import "./chunk-5TSRNF4G.js";
-import "./chunk-VFA6GDY5.js";
+import "./chunk-EIMVLWB3.js";
+import "./chunk-D7E7WCDF.js";
 import {
   MAX_TIMER_DELAY_MS
-} from "./chunk-FQ4SKYE4.js";
+} from "./chunk-EBY63B7G.js";
 import "./chunk-IWHMRKLL.js";
-import "./chunk-GXNLGKAB.js";
+import "./chunk-BWW4HLO4.js";
 import "./chunk-LL4KHSZI.js";
-import "./chunk-4ZG3XFUR.js";
-import "./chunk-BBVYXMFO.js";
-import "./chunk-SST6Z5JA.js";
+import "./chunk-NLFAQR7Z.js";
+import "./chunk-WNP7O5WZ.js";
+import "./chunk-336NSSKI.js";
 import "./chunk-IKCO5N3L.js";
 import "./chunk-3I7MS7N2.js";
 import "./chunk-APJ265NV.js";
@@ -112,7 +113,7 @@ async function runAcpCommand(args, options = {}) {
         transportOptions: {
           write: writeRawStdout,
           diagnostics: (line) => {
-            process.stderr.write(`[clio:acp] ${line}
+            process.stderr.write(`[clio-coder:acp] ${line}
 `);
           }
         },
@@ -124,7 +125,6 @@ async function runAcpCommand(args, options = {}) {
   }
 }
 export {
-  resolveAcpCwd,
   runAcpCommand
 };
-//# sourceMappingURL=acp-G5WJBNCT.js.map
+//# sourceMappingURL=acp-ZILU3AUO.js.map

package/dist/{agents-FMV2Q5G4.js → agents-HYWGBGQR.js}

@@ -1,39 +1,47 @@
 import { createRequire as __clioCreateRequire } from "node:module"; const require = __clioCreateRequire(import.meta.url);
 import {
   SafetyDomainModule
-} from "./chunk-O6TL7WWY.js";
-import "./chunk-X3YGUTOB.js";
+} from "./chunk-AKB4GYDL.js";
+import "./chunk-VKFQTNDV.js";
+import "./chunk-6HMJX2VU.js";
+import "./chunk-OJTRZGR3.js";
 import {
   ensureClioState
-} from "./chunk-W5VSYASO.js";
+} from "./chunk-QTFGO774.js";
+import "./chunk-AP73CFDC.js";
 import {
   ConfigDomainModule,
   loadDomains
-} from "./chunk-3BT2XMV4.js";
-import "./chunk-7MCTRUCE.js";
-import "./chunk-LDQ2ZF2M.js";
+} from "./chunk-2NM363SV.js";
+import "./chunk-J5LZHVIT.js";
+import "./chunk-VKRH2TCS.js";
+import "./chunk-6FN3E6KX.js";
+import "./chunk-LCGCVYZ4.js";
 import "./chunk-RVG5JXAL.js";
 import "./chunk-3DPEIQKN.js";
 import {
   AgentsDomainModule
-} from "./chunk-Z2RR6MAK.js";
-import "./chunk-Z4TXYIEG.js";
+} from "./chunk-MA3H6DM5.js";
+import "./chunk-ZJLUDYFY.js";
 import "./chunk-DR52UMZW.js";
-import "./chunk-VYMXRQI6.js";
+import "./chunk-HUAS7ITX.js";
+import "./chunk-NDDGJUXD.js";
 import "./chunk-FEFIFZTL.js";
 import "./chunk-CTJ4RNAA.js";
 import "./chunk-RKKLTLYB.js";
 import "./chunk-SUW5DORT.js";
 import "./chunk-5PSMVOLM.js";
 import "./chunk-UOV2BYIW.js";
-import "./chunk-GKF55TAZ.js";
-import "./chunk-32KWKNSF.js";
-import "./chunk-5LXZXPKX.js";
-import "./chunk-RAPCMZL4.js";
+import "./chunk-QSNYB6ZV.js";
+import "./chunk-QDC3K2U3.js";
+import "./chunk-PVAMAVBB.js";
+import "./chunk-IXJT6DCX.js";
+import "./chunk-VN3SHNBN.js";
+import "./chunk-FSP7CMNU.js";
 import "./chunk-HHV2GANA.js";
 import {
   isUserVisibleAgent
-} from "./chunk-DYJP44XW.js";
+} from "./chunk-IG7BCQBA.js";
 import "./chunk-GCSMB2KY.js";
 import "./chunk-UL3WSD3F.js";
 import "./chunk-ECH6PKUQ.js";
@@ -41,29 +49,32 @@ import "./chunk-5B2AEOW5.js";
 import "./chunk-K6BSR66V.js";
 import "./chunk-XPLRXC72.js";
 import "./chunk-NEKRRTYW.js";
-import "./chunk-SP2RXXYO.js";
-import "./chunk-2OQE55CK.js";
-import "./chunk-2ANTL7MR.js";
+import "./chunk-BDPT6GTK.js";
+import "./chunk-7PWAODYW.js";
+import "./chunk-ZW55JB7N.js";
 import {
   printError
 } from "./chunk-VPKWYKEY.js";
 import "./chunk-5TSRNF4G.js";
-import "./chunk-P3FOHJT4.js";
-import "./chunk-ZGVHUX3M.js";
-import "./chunk-HLW2MRKE.js";
-import "./chunk-76ONBSIA.js";
+import "./chunk-72GZI5EV.js";
+import "./chunk-MQXIVJ35.js";
 import "./chunk-R346GLFC.js";
+import "./chunk-PMZVFWSR.js";
+import "./chunk-HLW2MRKE.js";
+import "./chunk-BTK3SSSK.js";
 import "./chunk-IHXBNWMM.js";
-import "./chunk-VFA6GDY5.js";
-import "./chunk-BBVJUZHB.js";
-import "./chunk-FQ4SKYE4.js";
+import "./chunk-EIMVLWB3.js";
+import "./chunk-D7E7WCDF.js";
+import "./chunk-HJWWJ6IL.js";
+import "./chunk-JIEGK6UF.js";
+import "./chunk-EBY63B7G.js";
 import "./chunk-6EJMN2Y3.js";
 import "./chunk-IWHMRKLL.js";
-import "./chunk-GXNLGKAB.js";
+import "./chunk-BWW4HLO4.js";
 import "./chunk-LL4KHSZI.js";
-import "./chunk-4ZG3XFUR.js";
-import "./chunk-BBVYXMFO.js";
-import "./chunk-SST6Z5JA.js";
+import "./chunk-NLFAQR7Z.js";
+import "./chunk-WNP7O5WZ.js";
+import "./chunk-336NSSKI.js";
 import "./chunk-IKCO5N3L.js";
 import "./chunk-3I7MS7N2.js";
 import "./chunk-APJ265NV.js";
@@ -130,4 +141,4 @@ function renderLine(spec) {
 export {
   runAgentsCommand
 };
-//# sourceMappingURL=agents-FMV2Q5G4.js.map
+//# sourceMappingURL=agents-HYWGBGQR.js.map