@treeseed/dsh-chapters 0.1.17 → 0.1.20

package/cordis.patch.yml

@@ -10,36 +10,37 @@
 # Two planes, two surfaces:
 #   HOST PLANE  — the `config:` block below (defaults shown commented; set any
 #                 under your profile's plugin entry).
-#   REALM PLANE — the compaction ENGINE row inside the preset's composition
-#                 (src/preset.ts for hosts that register rows; for pre-0.1.7
-#                 hosts, presets/chapters/agent.cordis.yml); shared names behave
-#                 per plane. Design record: docs/knowledge-repo.md §12.
+#   REALM PLANE — the compaction ENGINE row inside the preset's composition (the
+#                 `preset-chapters` row at the foot of this file); shared names behave per
+#                 plane. Design record: docs/knowledge-repo.md §12.
 #
-# PRESET DELIVERY — one mechanism, and the host floor is 0.2.0:
-#   Hosts from 0.1.7-alpha.1 compose presets from '@deepseek-ai/dsh-agent-preset'
-#   DECLARATION ROWS and read nothing in $DSH_HOME/.agent-presets. This plugin registers
-#   the `chapters` row itself at activation, through the host's own agentPresets.register()
-#   — the same call the host's declaration-row plugin makes (src/preset.ts; why not a
-#   shipped patch layer is recorded there with the boot-breaking failures measured on
-#   0.1.5-rc.1). Rows this host cannot import are PRUNED and named in the mount line,
-#   because ONE unresolvable row makes the whole preset broken and every chapters
-#   session unopenable. Hosts below 0.2.0 have no register(): the mount line says
-#   `delivery: REFUSED`, the tools still work, and the preset cannot exist there.
-#   Either way the boot then ASKS THE ROSTER — file presence is not preset existence,
-#   and "declared" is not "usable". Read the `dsh-chapters:` lines at startup.
+# PRESET DELIVERY — the preset is a DECLARATION ROW, exactly like the host's own presets.
+#   `preset-chapters` (the id is the host convention `preset-<id>`) is inserted by this
+#   file, its `config` IS the preset definition (`id/name/description/order/plugins`), and
+#   because it is an ordinary Loader entry you can see it in the plugin list and the config
+#   editor, override it from your profile patch, or `disabled: true` it.
+#     Its row module is ours — '@treeseed/dsh-chapters/preset' (src/preset.ts) — not the
+#   host's '@deepseek-ai/dsh-agent-preset'. It mirrors that plugin line for line (injects
+#   `agentPresets`, preserves child `!!js` expressions, yields the registry disposer to
+#   Cordis) and adds one thing: rows this host cannot import are dropped at boot and NAMED,
+#   because a single unresolvable child row makes the WHOLE preset `broken` — which is the
+#   same user-visible failure as no preset at all (measured: `DECLARED BUT BROKEN —
+#   tool-schedule … never started` on a host where that package was never published). The
+#   host package cannot be named directly because a row that fails to import aborts the
+#   plugin tree of any host predating declaration rows; ours resolves everywhere our
+#   package runs. Support floor: 0.2.0.
+#     After activation the plugin then ASKS THE ROSTER, and the mounted rows: file presence
+#   is not preset existence, and "declared" is not "usable". The `dsh-chapters:` lines at
+#   startup say which of the four states you are in.
 #
 # config:
-#   # ---- identity & install --------------------------------------------
-#   installChaptersPreset: true    # register the chapters declaration row at
-#                                  # activation. Turning it off means a preset you
-#                                  # declare yourself (a patch layer in this or
-#                                  # another bundle); ours then stands down as
-#                                  # "already-declared" rather than throwing a
-#                                  # duplicate-preset error through our own row.
-#   compactionThresholdRatio: 0.9  # the registered preset's engine row: share of the
-#                                  # window that triggers a chapter checkpoint. This is
-#                                  # the knob a preset YAML used to carry in the home.
-#   fallbackPreset: 'chapters'     # preset mounted for children when the
+#   # ---- identity -------------------------------------------------------
+#   installChaptersPreset: true    # INERT since 0.1.18 — the preset is the `preset-chapters`
+#                                  # row above, so `disabled: true` on THAT row is the switch.
+#                                  # Kept so an existing profile patch still parses.
+#   compactionThresholdRatio: 0.9  # INERT since 0.1.18 for the same reason: it is
+#                                  # `thresholdRatio` on the preset's chapters-engine row now.
+#   #   fallbackPreset: 'chapters'     # preset mounted for children when the
 #                                  # caller's own preset cannot be resolved — and
 #                                  # the id the roster check looks for. This id is
 #                                  # DURABLE STATE: every child's log records it,
@@ -121,3 +122,182 @@
 - insert:
     - id: '@treeseed/dsh-chapters'
       name: '@treeseed/dsh-chapters'
+
+# ── the `chapters` agent preset — a DECLARATION ROW, exactly as @deepseek-ai/dsh-web-app
+#    ships its own presets/standard.patch.yml. Row id `preset-chapters` follows the host's
+#    `preset-<id>` convention; `config.id: chapters` is DURABLE STATE (every continuation
+#    child records it as `agent-preset/selected`, so renaming it orphans those sessions).
+#
+#    The row's `name` is OUR plugin (`@treeseed/dsh-chapters/preset`), which mirrors
+#    @deepseek-ai/dsh-agent-preset line for line — `inject: ['agentPresets']`,
+#    `static [EntryGroup.key] = true` so child `!!js` expressions survive until the child
+#    activates, `[Service.init]` yields the registry disposer so Cordis owns its lifetime —
+#    and drops rows THIS host cannot import before registering. Why not the host package
+#    directly: a row naming @deepseek-ai/dsh-agent-preset is unresolvable on a pre-0.1.7
+#    host and an unresolvable row aborts that host's whole plugin tree, while one stale
+#    child row (e.g. @deepseek-ai/dsh-tool-schedule, unpublished at 0.2.0-rc.2) makes the
+#    ENTIRE preset `broken` — measured both ways. Same row, same visibility in
+#    `dsh --dump-default-config`/the config editor, no boot that it can brick.
+#
+#    Four deltas from the host's own standard list, each ours deliberately:
+#      1. compaction-basic -> chapters-engine (the zero-inference summarize())
+#      2. tool-result-pruner.thresholdChars 8192 -> 1000000 (dormant by choice: chapters
+#         defer oversized results at ARCHIVE time; an in-surface prune is a prefix cliff
+#         on local hardware — and that plugin REJECTS unknown config keys, so the three
+#         keys below are the whole surface)
+#      3. the PLOT: persona suffix, with NO {{cwd}} (hosts from 0.2.1-alpha.2 register only
+#         provider/model and an unregistered variable throws at prompt assembly, killing
+#         every turn of every chapters session)
+#      4. tool-ralph ENABLED (the host standard list mounts it disabled)
+#    `noUnusedLocals`-equivalent discipline applies: keys the host dropped between versions
+#    are not carried here (toolFilter was one — alpha.4 throws on it).
+- insert:
+    - id: preset-chapters
+      name: '@treeseed/dsh-chapters/preset'
+      config:
+        id: chapters
+        name: Chapters
+        description: Full coding agent; context relief via zero-inference chapter compaction.
+        order: 0
+        plugins:
+          - id: persona
+            name: '@deepseek-ai/dsh-persona'
+            config:
+              prefix: You are a coding agent powered by the {{model}} model.
+              suffix: "When a task spans multiple turns, end each reply with one line beginning 'PLOT:' (max 60 words — objective, current hypothesis, immediate next step). A checkpoint carries this plot forward; if it looks stale, revise it on your next plot line."
+          - id: agent-instructions
+            name: '@deepseek-ai/dsh-agent-instructions'
+            config:
+              maxBytes: 65536
+          - id: time-context
+            name: '@deepseek-ai/dsh-time-context'
+          - id: tool-bash
+            name: '@deepseek-ai/dsh-tool-bash'
+            disabled: !!js process.platform === 'win32'
+          - id: tool-pwsh
+            name: '@deepseek-ai/dsh-tool-pwsh'
+            disabled: !!js process.platform !== 'win32'
+          - id: tool-fs
+            name: '@deepseek-ai/dsh-tool-fs'
+          - id: tool-fs-search
+            name: '@deepseek-ai/dsh-tool-fs-search'
+            config:
+              sampleOverCapGlobResults: false
+          - id: tool-jobs
+            name: '@deepseek-ai/dsh-tool-jobs'
+          - id: tool-schedule
+            name: '@deepseek-ai/dsh-tool-schedule'
+          - id: skill-filesystem
+            name: '@deepseek-ai/dsh-skill-filesystem'
+          - id: tool-skill
+            name: '@deepseek-ai/dsh-tool-skill'
+          - id: command-goal
+            name: '@deepseek-ai/dsh-command-goal'
+          - id: tool-goal
+            name: '@deepseek-ai/dsh-tool-goal'
+          - id: planning
+            name: cordis:group
+            group: true
+            isolate:
+              planMode: true
+            config:
+              - id: plan-mode
+                name: '@deepseek-ai/dsh-plan-mode'
+                config:
+                  section: |
+                    You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
+
+                    Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
+
+                    The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
+
+                    Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
+
+                    Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
+
+                    When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
+          - id: compaction
+            name: cordis:group
+            group: true
+            isolate:
+              compaction: true
+              toolResultPruner: true
+            config:
+              - id: chapters-engine
+                name: '@treeseed/dsh-chapters/engine'
+                config:
+                  thresholdRatio: 0.9
+              - id: command-compact
+                name: '@deepseek-ai/dsh-command-compact'
+              - id: tool-result-pruner
+                name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
+                config:
+                  thresholdChars: 1000000
+                  headChars: 4096
+                  tailChars: 1024
+          - id: delegation
+            name: cordis:group
+            group: true
+            isolate:
+              workflowEngine: true
+            config:
+              - id: tool-subagent-control
+                name: '@deepseek-ai/dsh-tool-subagent-control'
+              - id: tool-subagent-list-agents
+                name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
+              - id: tool-subagent
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: spawn
+                  toolName: subagent
+                  modelSelectionSettings: true
+                  backgroundMode: continuable
+              - id: tool-subagent-fork
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: fork
+                  toolName: subagent_fork
+                  backgroundMode: continuable
+              - id: tool-subagent-codex
+                name: '@deepseek-ai/dsh-tool-subagent'
+                disabled: true
+                config:
+                  provider: codex
+                  toolName: subagent_codex
+                  backgroundMode: one-shot
+                  maxDepth: provider-managed
+              - id: tool-subagent-claude-code
+                name: '@deepseek-ai/dsh-tool-subagent'
+                disabled: true
+                config:
+                  provider: claude-code
+                  toolName: subagent_claude_code
+                  backgroundMode: one-shot
+                  maxDepth: provider-managed
+              - id: workflow-ptc
+                name: '@deepseek-ai/dsh-workflow-ptc'
+                config:
+                  provider: spawn
+              - id: tool-workflow
+                name: '@deepseek-ai/dsh-tool-workflow'
+              - id: tool-ralph
+                name: '@deepseek-ai/dsh-tool-ralph'
+                config:
+                  subagentProvider: spawn
+                  maxRounds: 64
+          - id: tool-ask-user
+            name: '@deepseek-ai/dsh-tool-ask-user'
+          - id: tool-todo
+            name: '@deepseek-ai/dsh-tool-todo'
+            config:
+              allowParallelInProgress: true
+          - id: tool-web
+            name: '@deepseek-ai/dsh-tool-web'
+            config:
+              fetch: true
+              searchTimeoutMs: 60000
+          - id: present
+            name: '@deepseek-ai/dsh-tool-present'
+          - id: tool-plugin-manager
+            name: '@deepseek-ai/dsh-plugin-manager/tools'
+            disabled: true

package/docs/backlog.md

@@ -121,15 +121,22 @@ NEW host too (measured). Full record: `docs/contract.md` § Presets are declarat
 
 0. **Re-anchor the e2e host, then re-distill the tapes.** `tests/e2e/boot.ts` now refuses by name
    while `dev/dsh-host-lock` pins a pre-0.2.0 host, and the refusal lifts itself when the lock moves —
-   that is the upgrade path, not a TODO. The per-boot row pins (`thresholdRatio`, `enrichmentEnabled`,
+   that is the upgrade path, not a TODO. `ci.yml`'s `host-capability` job reads that same lock and
+   SKIPS the acceptance job with a step-summary reason plus a `::warning::` while the pinned host
+   predates declaration rows: visibly skipped, never red-by-accident, never green-by-omission.
+   Publishing is unaffected — the release gate is the deterministic suite. The per-boot row pins (`thresholdRatio`, `enrichmentEnabled`,
    `auto`, `elicitedPlot`, `toolResultArtifactTokens`) and the `[e2e] boot pins:` line were deleted with
    the YAML they patched; they come back expressed as CONFIG on the registered row (`compactionThresholdRatio`
    exists now; the rest need the same treatment). Until then the browser acceptance chain does not run, and
    `docs/verify.md`'s P23 is retired rather than passing.
-1. **The roster check is the only evidence we have that a preset composes — and it is a boot-time log
-   line.** A user cannot see it without a terminal. Candidate: surface `delivery:` + the roster verdict in
-   `/chapters-status` (and a warning row in the Settings plugin panel), so "installed and running" stops
-   being the whole answer. Nothing else in the plugin reports health to a human today.
+1. **The roster verdict is a boot log line, and a user has no terminal.** 0.1.18 made the preset a
+   visible Loader row (`preset-chapters`) and put the mounted-row count in that line, so the
+   "is it actually usable" fact is one grep away — but it is still a grep. Candidate: surface it in
+   `/chapters-status`. Nothing else in the plugin reports health to a human today.
+2. **`installChaptersPreset` and `compactionThresholdRatio` are accepted-and-inert** since 0.1.18 (the
+   preset is a row; the engine threshold is row config). They must be DELETED in the next minor — a key
+   that silently does nothing is its own drift — and the removal needs the same care: check no shipped
+   profile patch sets them, then drop both from `Config` and from `cordis.patch.yml`'s header.
 2. **`compositionInventory()` is used by the dev witness only.** Making the boot check itself compare
    mounted rows would catch a row that resolves but never activates — the `broken` flag does not always
    cover that, and the witness proves the shape of the answer already.

package/docs/contract.md

@@ -369,35 +369,29 @@ running", the preset is simply absent — and a session's preset id is **durable
 `agent-preset/not-found`, `dsh-agent-preset-registry/lib/index.js:596`), so every chapters session refuses
 to OPEN while its log sits there intact.
 
-**This bundle does NOT ship the row as a patch layer.** It registers the row itself at activation,
-through the host's own `ctx.get('agentPresets').register(definition)` — the same call the host's
-declaration-row plugin makes (`dsh-agent-preset/lib/index.js`, `[Service.init]`). The reason is two
-boot-breaking failures measured on the pinned legacy closure (`@deepseek-ai/dsh 0.1.5-rc.1`, the host
-`dev/dsh-host-lock` freezes for tape bytes) against the installed 0.2.0-rc.2:
+**This bundle DOES ship the row — in its one existing patch layer, with our own row module.**
+`cordis.patch.yml` ends with `- insert: [{id: preset-chapters, name: '@treeseed/dsh-chapters/preset',
+config: <the preset definition>}]`, so the preset is an ordinary Loader entry: visible in the plugin
+list and `dsh --dump-default-config`, overridable or disable-able from a profile patch, positioned by
+`config.order`. The row module (`src/preset.ts`) mirrors `@deepseek-ai/dsh-agent-preset`'s plugin line
+for line and adds the pruning described below. Why not the host package directly, measured on the
+0.1.5-rc.1 closure and on 0.2.0-rc.2:
 
 - `dsh.bundle.patch` as an **array** (what a second layer requires) dies at profile load on a pre-0.1.7
   host: `TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received an
-  instance of Array` — legacy `dsh-app-boot/lib/index.js:853` does `join(packageDir, declared)`. Array
-  support (`bundlePatchFiles`) and declaration rows arrive in the SAME release, 0.1.7-alpha.1, verified
-  across the published `dsh-app-boot` tarballs. A two-layer manifest is therefore exactly as incompatible
-  with 0.1.5/0.1.6 as it looks, and the host does not warn — it just never comes up.
-- The **row itself** in any layer a legacy host reads is fatal the same way:
-  `dsh: plugin tree failed to load: … failed to import loader entry preset-chapters
-  (@deepseek-ai/dsh-agent-preset): Cannot find package` (measured; `@deepseek-ai/dsh-agent-preset` is
-  first published at 0.1.7-alpha.1, and 0.1.5-rc.1 ships `dsh-agent-presets`, plural, whose service has
-  no `register()` — `this.ctx.agentPresets.register is not a function`).
-- **`disabled: !!js` cannot gate the row either**, which is the tempting fix. The Loader evaluates a row's
-  `disabled` before services are mounted (`cordis-plugin-loader/lib/index.js:348` →
-  `evaluate(this.ctx, expr)` = `with (ctx) { eval(expr) }`), so `get('agentPresets')` is undefined *on the
-  modern host too* and the row is disabled everywhere — measured on 0.2.0-rc.2: `preset-v2 … failed to
-  import`, roster without it, while the same row with `disabled: !!js false` registered normally. Bare
-  `get(...)` also throws in that scope (`ctx` is bound, `get` is not).
-
-The registration path is verified on both mechanisms with real boots: on 0.2.0-rc.2 the witness reports
-`register: pruned, roster: present, inventoryRows: 28, unusableRows: []`; on 0.1.5-rc.1 it reports
-and the same build on 0.1.5-rc.1 logs
-`delivery: REFUSED — this host predates preset declaration rows (< 0.2.0)` — the tools work,
-the preset cannot exist there, and 0.2.0 is now the support floor.
+  instance of Array` (`dsh-app-boot/lib/index.js:853`, `join(packageDir, declared)`). Array support and
+  declaration rows arrive in the SAME release, 0.1.7-alpha.1 — so one layer, still a string, is both
+  enough and the only boot-safe shape.
+- a row naming `@deepseek-ai/dsh-agent-preset` in ANY layer a legacy host reads aborts its plugin tree:
+  `plugin tree failed to load: … failed to import loader entry … Cannot find package` (the package is
+  first published at 0.1.7-alpha.1). A row naming our own module resolves wherever our package runs.
+- **`disabled: !!js` cannot capability-gate a root row**: the Loader evaluates `disabled` before services
+  are mounted (`cordis-plugin-loader/lib/index.js:348` → `with (ctx) { eval(expr) }`), so
+  `get('agentPresets')?.register === undefined` is true on the MODERN host too and the row never
+  registers — measured (`preset-v2 … failed to import`, roster without it, while the same row with
+  `disabled: !!js false` registered normally). Bare `get(...)` also throws there; only `ctx` is bound.
+- and the row must be *ours* anyway for the reason below: it is the one place that can drop a child the
+  host cannot load before the mount is attempted.
 
 Three consequences of reading the registry rather than the filesystem:
 

package/docs/development.md

@@ -355,7 +355,7 @@ happened in these notes before it was caught.
 | `src/notice.ts` + `test/notice.test.ts` — TOC-notice builder, kernel-rejection reproduction, vocabulary pins + drift guard (Phase 0b check 5) | **done**, 10 tests |
 | `src/registry.ts` + `src/store.ts` — pure numbering/ancestry/plan state; zod domain spec, storage-domain + node-fs adapters | **done**, 13 + 7 tests; durability witness passed |
 | `src/engine-core.ts` + `src/engine.ts` — ChaptersCompactionEngine | **done & boot-proven** (r18/r19: realm subpath row mounts; real cascade finalizes; catch-path fix — FINDINGS § Phase 1) |
-| preset delivery | **rewritten in 0.1.17**: the row is registered at activation (`src/preset.ts`). The `presets/chapters/` + copy-on-boot mechanism it replaced is deleted with the 0.2.0 support floor (docs/contract.md) |
+| preset delivery | **0.1.18: the preset IS a declaration row** — `preset-chapters` in `cordis.patch.yml`, mounted by `@treeseed/dsh-chapters/preset` (`src/preset.ts`), which registers what the host can load and drops what it cannot. The `presets/chapters/` + copy-on-boot mechanism is deleted with the 0.2.0 floor. Verify.md P24 (rows + three-host boots) |
 | `npm test` (unit + integration) | **188 passing, <2 s** — unit imports no harness services; integration runs the sync loop against a fake git driver AND a real git smart-HTTP server (git-http-backend on loopback; the git binary is test-only scaffolding, the product stays pure-JS) |
 | 20-check verify.md pass | **r26/26b**: 18 mechanical on `.dshdev2` (refusals with numbers, tamper marks, idempotent retry, cross-boot registry + resume); human rows per verify.md evidence map |
 | dsh-session-fork coexistence | **moot at this version** (r26a pair-boot): the example fails to boot the installed host ALONE (unguarded `webServer` read in the installed dsh-client-connection) — assumed-neutral until a version-matched pair-boot |
@@ -492,3 +492,39 @@ Two traps measured while finding that:
   `src/` only).
 
 Never fix a missing test runner by editing the tests. The suite is the contract; the runner is local.
+
+### Verifying against a host version that is not the installed one
+
+A preset/delivery change must be proven on EVERY host release the package claims to serve, and the
+installed host is one data point. Recipe measured 2026-10-16 (this is how 0.1.17 was verified on
+0.2.0-rc.2, 0.2.1-alpha.4 and the pinned 0.1.5-rc.1 in one sitting):
+
+```bash
+# 1. a second host, installed as its own tree — never over the running one
+mkdir -p var/host-versions/a4 && cd var/host-versions/a4
+echo '{"name":"a4-host","private":true,"dependencies":{"@deepseek-ai/dsh":"0.2.1-alpha.4"}}' > package.json
+npm install --no-audit --no-fund           # ~1 min, 616 packages
+# 2. a THROWAWAY home for it (profiles/web/package.json listing the bundles + this plugin),
+#    then boot THAT bin with DSH_HOME pointed at the new home:
+DSH_HOME=$PWD/var/a4-home DSH_CHAPTERS_WITNESS=$PWD/var/a4-home/w.json \
+  node var/host-versions/a4/node_modules/@deepseek-ai/dsh/lib/bin.js web --port 0 --no-open
+```
+
+The witness JSON is the answer — `presetRegister`, `presetDroppedRows`, `presetRoster` and
+`presetInventoryRows`/`presetUnusableRows` say what a log line only hints at, and `presetUnusableRows: []`
+is the assertion that the composition actually ACTIVATES rather than merely being declared.
+
+Three traps, all paid for:
+
+- **Never symlink a host tree into an npm-managed profile's `node_modules`.** `npm install` treats what it
+  does not recognize as extraneous and **deletes it through the link** — it ate a 500-package host closure
+  this way ("the closure is gone, `ls` returns nothing"). Copy instead (`cp -r`), or point the boot's own
+  installation anchor at the other tree and install ONLY the plugin into the profile.
+- **`npm pack` + install-from-tarball, not `file:`-linked sources.** The artifact users get is the packed
+  `files` list; a linked working tree hides a missing `files` entry (e.g. an asset the preset needs).
+- Boot with `timeout 45 …` and read the exit code: **124 means it stayed up** (healthy), `1` means the
+  plugin tree refused to load. A crashed boot and a slow boot both print to the same log; the code is the
+  difference between "no preset" and "no harness".
+
+Prune after: `var/host-versions/`, the throwaway homes and `var/coverage` are all regenerable in minutes and
+together cost ~2 GB — this repository's contract is the *measurements written down*, not their scratch.

package/docs/verify.md

@@ -152,7 +152,8 @@ renderer, the segmentation tool, and the child's notice.
 | P10 | Artifact citations resolve wherever they were written | a chapter's `artifacts/aa/<sha>.txt` reference resolves whether the blob sits at the STORE ROOT (arrival stubs) or inside the ANCESTRY TREE (`<store>/<root>/artifacts/…`, where `writeArchive` puts deferred results and every plan) — before this fix the second form was unreadable through `chapters_artifact`, which is what "every byte remains retrievable" actually promised | `artifact-query.test.ts` rows + integration `plans-carriage.test.ts` (`resolveArtifactWithMirror` over the real tree) |
 | P11 | The browser plane runs in the chain | `/plan <message>` → a real `exit_plan_mode` call → the host's review card opened and answered by a real CLICK → fork; asserts the submission's bytes are the artifact's bytes (or provably only-redacted), `planMode: inactive` from the fold, a `kind: plan` document on disk, and that the BRANCH child carries **no** `## Active plan` and no call-out while still citing the archive; plus a guard that no `compaction/*` entered the journey | `tests/e2e/plans.spec.ts` = chain project `plans` (13 s replay, no LLM; 3-entry tape). **Scope, learned at cost:** the continuation leg was REMOVED from this journey because a tape freezes the model's tool ARGUMENTS — my scripted upstream derived `chapters_continue` ranges from the ceiling the live segment tool reported while distilling (30 here), and the runner's session lands at 29, so `validateRanges` refused the stale input (correctly). A journey whose recorded request embeds a machine-specific seq cannot be hardware-neutral. Continuation semantics — `## Active plan`, `## Previous plans`, the seeded `plan/mode`, the checkpoint carry — are covered by the deterministic plane (`continue-plans`, `plans-engine`, `plan-documents`, the § 10 kernel probe) and the in-place path by the heavy/arrival/enrich/fanout journeys. Tape provenance: scripted upstream, see `tests/fixtures/model-tape/plans/PROVENANCE.md` |
 
-| P23 | **Retired in 0.1.17 with the legacy copy** (support floor 0.2.0): `installChaptersPreset` and `presets/chapters/` are deleted, so there is no installed file set to half-delete. The health evidence is the ROSTER check and the mounted rows — pinned by P24/P25 below | unit `preset-declaration.test.ts` (14 rows) + real boots on 0.2.0-rc.2 and 0.2.1-alpha.4 |
+| P23 | **Retired in 0.1.17 with the legacy copy** (support floor 0.2.0): `installChaptersPreset` and `presets/chapters/` are deleted, so there is no installed file set to half-delete. The key is ACCEPTED-and-inert since 0.1.18 — removing it would make an existing profile patch fail to parse, and a bundle that will not mount is worse than a key that does nothing | see P24 |
+| P24 | The preset is a **visible declaration row**, and the row composes on every host in range | `preset-chapters` is inserted by our own `cordis.patch.yml` with the preset definition in its `config`, mounted by `@treeseed/dsh-chapters/preset` (`src/preset.ts`) — the visible Loader entry the host's own presets are, overridable and `disabled`-able from a profile patch, with the registration's lifetime yielded to Cordis (an `apply()`-scoped disposer un-registered it: measured as `register()` succeeding with the roster WITHOUT `chapters`). Rows the host cannot import are dropped and NAMED, because one unresolvable child makes the whole preset `broken` | 15 rows in `preset-declaration.test.ts`, **each verified to fail on the mutation it guards** (ralph re-disabled, an unknown pruner key, `toolFilter` restored, `{{cwd}}` restored, the durable id renamed) — plus real boots of the packed tarball on 0.2.0-rc.2 (`roster: present`, `inventoryRows: 28`, `unusableRows: []`, tool-schedule pruned), 0.2.1-alpha.4 (`registered`, `inventoryRows: 29`, nothing pruned) and 0.1.5-rc.1 (boots; the row says the host cannot register rows) |
 | P21 | The continuation has a **human-pulled door**, and the two doors cannot drift | `/chapters-continue` = `deterministicCommand({intent:'continue'})`, the same builder as `/chapters-fork`; only name/verbs/intent/no-directive prose differ; archive semantics identical (everything since the watermark). CLIENT SIDE, same discipline: the assistant row registers both doors from ONE runner (`src/client/doors.ts` `makeDoorRunner` + a two-row `DOOR_ACTIONS` table) — a composer-only continue left the user with a created child and no affordance | unit `continue-command.test.ts` (7 rows) incl. the **no-drift row**: same events in ⇒ same ranges, titles and plan facts out of both doors; the no-plan case, the refusal naming its own door, and approved ⇒ NOT seeded vs still-planning ⇒ seeded `['user/message','plan/mode']`. Unit `client-doors.test.ts` (7 rows) pins the two client rows (distinct id/order/label/command, the fork label frozen for the specs), that ONE child-id regex parses BOTH door wordings, that both rows fire their own command through the same body, and — by reading the server's own templates — that the reply wording the client parses is still what `deterministicCommand` emits. Browser: project `fork` asserts BOTH buttons render |
 | P22 | The continuation shape is covered **in the browser**, on every push | the leg that a tape could not carry (§ 15) is back, driven by the command — no model request, no frozen `endSeq`; asserted from the child's durable log without switching the UI: `## Active plan`, the operative plan by title with its real verdict, `plan document:` and `chapters_artifact` citations, `## Finding things`, no seeded gate after approval, exactly one synthetic notice (invariant 2) | `tests/e2e/plans.spec.ts` project `plans` — replays in ~14 s with no LLM/GPU, eight-project chain green |
 | P18 | Search answers **without a pool linked** — the findability audit | `buildLocalCorpus` walks the workspace store (chapters, `kind: plan` documents, rules) and answers through the SAME scorer as the mirror door (`rankEntries`), so ranking cannot drift between doors; artifacts are deliberately not indexed (they answer to `chapters_artifact`); the answer names its door ("searched this machine's store, N docs, no pool mirror") so a session never reads *this machine only* as *the whole project*; "nothing matched" (`documents>0`) is distinguished from "nothing here" (`empty`); a pool miss falls back to the local store before answering empty | unit `local-corpus.test.ts` (5) + integration `find-without-a-pool.test.ts` through the real tool wrapper — the empty answer used to be born in the wrapper, not the pure function |

package/lib/codegraph.d.ts

@@ -0,0 +1,76 @@
+export interface SubprocessLike {
+    resolveExecutable(name: string): Promise<string>;
+    spawn(opts: {
+        argv: string[];
+        cwd: string;
+        stdio: {
+            stdin: string;
+            stdout: {
+                maxBytes: number;
+            };
+            stderr: {
+                maxBytes: number;
+            };
+        };
+        graceMs: number;
+        signal?: AbortSignal;
+    }): {
+        done: Promise<{
+            exitCode: number;
+        }>;
+        collected: {
+            stdout?: {
+                readFrom(n: number): {
+                    text: string;
+                };
+            };
+            stderr?: {
+                readFrom(n: number): {
+                    text: string;
+                };
+            };
+        };
+    };
+}
+/**
+ * Resolve the codegraph CLI executable. Returns null if unavailable.
+ * Cached after first attempt — call freely.
+ */
+export declare function resolveCodegraph(subprocess: SubprocessLike | undefined): Promise<string | null>;
+/** Reset the cached resolution (test seam only). */
+export declare function resetCodegraphResolution(): void;
+/** Check whether a project has a CodeGraph index at or above the given path. */
+export declare function hasCodegraphIndex(cwd: string): boolean;
+/** Find the nearest indexed ancestor directory. */
+export declare function findCodegraphRoot(cwd: string): string | undefined;
+/** Extract code-shaped tokens from text (file names, camelCase, PascalCase, snake_case). */
+export declare function extractCodeTokens(text: string, limit?: number): string[];
+interface RunResult {
+    text: string;
+    ok: boolean;
+}
+/**
+ * Run a codegraph CLI command. Returns empty text on any failure — callers
+ * treat failure as "no data", never as an error.
+ */
+export declare function runCodegraphQuiet(subprocess: SubprocessLike | undefined, argv: string[], cwd: string, timeoutMs: number): Promise<RunResult>;
+/**
+ * Query CodeGraph for symbols matching a token. Returns symbol names that
+ * exist in the index. Fire-and-forget friendly — errors return [].
+ */
+export declare function querySymbols(subprocess: SubprocessLike | undefined, root: string, token: string, limit?: number, timeoutMs?: number): Promise<string[]>;
+/**
+ * Extract CodeGraph symbols from a set of events by verifying code-shaped
+ * tokens against the project index. Budget: max 3 queries, 5s each.
+ * Returns [] on any failure — callers treat this as optional enrichment.
+ */
+export declare function extractCodegraphSymbolsFromEvents(subprocess: SubprocessLike | undefined, cwd: string, events: readonly {
+    type?: string;
+    data?: Record<string, unknown>;
+}[], limit?: number): Promise<string[]>;
+/**
+ * Run codegraph explore and return the raw text output. Capped and
+ * fire-and-forget — errors return ''.
+ */
+export declare function exploreCodegraph(subprocess: SubprocessLike | undefined, root: string, query: string, maxChars?: number, timeoutMs?: number): Promise<string>;
+export {};