docs: trim generated prose

packages/ui/acp-agent/src/bin.ts

@@ -1,29 +1,8 @@
 #!/usr/bin/env node
 /**
- * The `dsh-acp-agent` bin: boot the ACP server from a leaf `cordis.yml` that
- * loads the {@link @deepseek-ai/dsh-acp-agent} app plugin (plus an LLM adapter
- * and a bash executor), speaking ACP JSON-RPC on stdio. The shared boot glue —
- * `.env` loading, the fail-loud Loader guards, snapshot-aware config
- * resolution, the settle-the-tree boot sequence — lives in
- * {@link @deepseek-ai/dsh-app-boot}; this bin owns only the ACP-specific
- * lifecycle:
- *
- *  - `.env` loading is SKIPPED in snapshot REPLAY so a stray key can never
- *    trigger a live model call.
- *  - `DSH_SNAPSHOT=replay` swaps the given `cordis.yml` for its sibling
- *    `cordis.snapshot.yml` (the keyless replay tree: `llm-replay` in place of
- *    `llm-deepseek`).
- *  - In a snapshot run the harness closes stdin when done, so dispose the
- *    context (flushing persistence) and exit cleanly. In a normal editor
- *    session stdin stays open for the connection's lifetime (the editor kills
- *    the process), so the EOF handler never fires.
- *
- * IMPORTANT: stdout is the ACP JSON-RPC channel. This bin writes diagnostics to
- * STDERR only (the app plugin loads no stdout logger, and the shared guards
- * write to stderr); a stray stdout write corrupts the protocol frames.
- *
- * Usage: `dsh-acp-agent [path-to-cordis.yml]` (default `./cordis.yml`).
- *
+ * The `dsh-acp-agent` bin: boot the ACP server from a leaf `cordis.yml` that loads the {@link
+ * @deepseek-ai/dsh-acp-agent} app plugin (plus an LLM adapter and a bash executor), speaking
+ * ACP JSON-RPC on stdio.
  * @module @deepseek-ai/dsh-acp-agent/bin
  */
 

packages/ui/acp-agent/src/index.ts

@@ -1,32 +1,7 @@
 /**
- * The ACP server app: the default agent spine ({@link
- * @deepseek-ai/dsh-agent-core}) plus the coupled front-door cluster an ACP
- * server needs — JSONL session persistence and the {@link @deepseek-ai/dsh-acp}
- * bridge, and DELIBERATELY NOTHING that writes to stdout.
- *
- * The cluster is the OPPOSITE of {@link @deepseek-ai/dsh-stdio-agent}'s, and
- * baking it in is the whole point: an ACP server speaks JSON-RPC on stdout, so
- * a stray console logger would corrupt the protocol frames (the [stdout-purity
- * footgun]). This package contains NO console-logger entry, NO `hmr` (the editor
- * owns the subprocess), and pre-creates NO agents (ACP `session/new` creates
- * them on demand) — so the default front door has no logger entry to get wrong.
- * (A leaf `cordis.yml` could still add a sibling `@cordisjs/plugin-logger-console`,
- * which this app does not prevent — so the rule "never add a stdout logger to an
- * ACP leaf" still stands; the app just gives the leaf nothing to misconfigure.)
- *
- * The leaf supplies the swappable backends: the LLM adapter (`llm-deepseek` for
- * the real model, `llm-replay` for keyless snapshot replay), the bash executor
- * (`bash-local`), and any optional product tools it wants to expose. This app's
- * {@link Config} (model, system prompt, persistence root) routes each value to
- * where it is wired — model/prompt onto the bridge's per-session agent
- * template, the root onto the JSONL backend.
- *
- * Plugin export shape: named `name`/`Config`/`apply`, NO default export — the
- * cordis Loader's `unwrapExports` does `exports.default ?? exports`, so a stray
- * default would collapse the module to the bare `apply` and drop the `Config`
- * namespace (see docs/postmortem/0001 — the exact bug that shipped here once).
- * The keyless ACP snapshot/Loader-path tests guard this end-to-end.
- *
+ * The ACP server app: the default agent spine ({@link @deepseek-ai/dsh-agent-core}) plus the
+ * coupled front-door cluster an ACP server needs — JSONL session persistence and the {@link
+ * @deepseek-ai/dsh-acp} bridge, and deliberately NOTHING that writes to stdout.
  * @module @deepseek-ai/dsh-acp-agent
  */