geneseed 5.3.0 → 5.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (198) hide show
  1. package/CHANGELOG.md +95 -0
  2. package/README.md +23 -20
  3. package/SHIPPED.md +7 -7
  4. package/adapters/bob/README.md +31 -18
  5. package/adapters/claude-code/README.md +27 -22
  6. package/adapters/openclaude/README.md +18 -8
  7. package/adapters/opencode/HOW-OPENCODE-LOADS.md +8 -3
  8. package/adapters/opencode/README.md +3 -2
  9. package/adapters/opencode/plugins/geneseed-activity.js +20 -21
  10. package/adapters/opencode/plugins/geneseed-context.js +175 -62
  11. package/adapters/opencode/plugins/geneseed-guard.js +419 -205
  12. package/adapters/opencode/plugins/geneseed-workflow.js +3 -2
  13. package/adapters/opencode/workflows/_runtime.js +3 -2
  14. package/bin/geneseed-cli.mjs +7 -0
  15. package/bin/geneseed-hook.mjs +59 -11
  16. package/docs/PRD.md +1 -1
  17. package/docs/README.md +1 -0
  18. package/docs/concepts/agents.md +1 -1
  19. package/docs/concepts/collaboration.md +2 -2
  20. package/docs/concepts/enforcement-table.md +5 -2
  21. package/docs/concepts/exclusions.md +18 -4
  22. package/docs/concepts/footprint.md +11 -1
  23. package/docs/concepts/foreman-mode.md +1 -1
  24. package/docs/concepts/hook-gates.md +5 -5
  25. package/docs/concepts/hooks.md +4 -3
  26. package/docs/concepts/host-matrix.md +24 -6
  27. package/docs/concepts/kits.md +12 -2
  28. package/docs/concepts/loop-bricks.md +3 -3
  29. package/docs/concepts/loops.md +6 -4
  30. package/docs/concepts/ownership.md +1 -1
  31. package/docs/concepts/rules.md +2 -2
  32. package/docs/concepts/skills.md +1 -1
  33. package/docs/design-history.md +8 -0
  34. package/docs/extending.md +112 -35
  35. package/docs/guides/auto-merge.md +100 -0
  36. package/docs/guides/choose-your-setup.md +1 -1
  37. package/docs/guides/headless.md +1 -1
  38. package/docs/guides/install-bob.md +2 -2
  39. package/docs/guides/install-clone.md +1 -1
  40. package/docs/guides/install-openclaude.md +1 -1
  41. package/docs/guides/install.md +1 -1
  42. package/docs/guides/loop-finish.md +3 -3
  43. package/docs/guides/loop-running.md +4 -4
  44. package/docs/guides/project-context.md +1 -1
  45. package/docs/guides/run-a-factory.md +2 -2
  46. package/docs/guides/setup-doctrines.md +2 -2
  47. package/docs/guides/setup-footprint.md +1 -1
  48. package/docs/guides/uninstall.md +3 -3
  49. package/docs/guides/upgrade.md +1 -1
  50. package/docs/guides/verify.md +12 -0
  51. package/docs/guides/worktree.md +1 -1
  52. package/docs/reference/environment.md +5 -2
  53. package/docs/reference/plugin-activity.md +1 -1
  54. package/docs/reference/plugin-guard.md +1 -1
  55. package/docs/reference/plugin-learn.md +1 -1
  56. package/docs/reference/plugin-workflow.md +1 -1
  57. package/docs/reference/troubleshoot-doctor.md +2 -2
  58. package/docs/reference/troubleshoot-hooks.md +2 -2
  59. package/docs/reference/troubleshoot-install.md +3 -3
  60. package/docs/reference/troubleshoot-tools.md +1 -1
  61. package/docs/token-footprint.md +68 -4
  62. package/docs/understand/design-choices-hosts.md +1 -1
  63. package/docs/understand/design-choices-shape.md +1 -0
  64. package/docs/understand/enforced-vs-asked.md +2 -2
  65. package/docs/understand/machine-bob.md +1 -1
  66. package/docs/understand/machine-claude.md +2 -2
  67. package/docs/understand/on-your-machine.md +1 -1
  68. package/docs/web-ui.md +10 -5
  69. package/harness.config.json +1 -1
  70. package/js/README.md +5 -3
  71. package/js/build/args.mjs +13 -2
  72. package/js/build/driver.mjs +34 -7
  73. package/js/build/emit-claude.mjs +9 -5
  74. package/js/build/emit-opencode.mjs +13 -9
  75. package/js/build/generate.mjs +10 -165
  76. package/js/build/profile.mjs +318 -0
  77. package/js/build/render.mjs +81 -3
  78. package/js/build/retired-skills.mjs +60 -13
  79. package/js/build/source.mjs +15 -1
  80. package/js/build/stubs.mjs +4 -1
  81. package/js/cli-table.json +48 -3
  82. package/js/hosts/done-checks.mjs +6 -0
  83. package/js/hosts/geneseed-dir.mjs +3 -2
  84. package/js/hosts/gitref.mjs +5 -3
  85. package/js/hosts/hook-tap.mjs +104 -0
  86. package/js/hosts/hooks-context.mjs +4 -2
  87. package/js/hosts/hooks-done.mjs +345 -55
  88. package/js/hosts/hooks-learn.mjs +51 -19
  89. package/js/hosts/hooks-prims.mjs +5 -3
  90. package/js/hosts/hooks.mjs +172 -19
  91. package/js/hosts/hosts.mjs +80 -12
  92. package/js/hosts/installs.mjs +26 -1
  93. package/js/hosts/native.mjs +33 -7
  94. package/js/hosts/owned.mjs +7 -6
  95. package/js/hosts/ownership-gate.mjs +14 -1
  96. package/js/hosts/settings.mjs +273 -105
  97. package/js/hosts/shim.mjs +4 -4
  98. package/js/hosts/usage.mjs +9 -3
  99. package/js/inspect/checks-constitution.mjs +32 -0
  100. package/js/inspect/checks-probe.mjs +66 -5
  101. package/js/inspect/checks-repo.mjs +196 -2
  102. package/js/inspect/cost.mjs +34 -2
  103. package/js/inspect/diff.mjs +21 -3
  104. package/js/inspect/doctor.mjs +6 -1
  105. package/js/inspect/inventory.mjs +1 -1
  106. package/js/lib/machine-dir.mjs +1 -1
  107. package/js/lib/node-floor.mjs +46 -6
  108. package/js/maintain/setup.mjs +5 -1
  109. package/js/maintain/uninstall.mjs +42 -16
  110. package/js/maintain/update.mjs +4 -2
  111. package/js/web/actions.mjs +17 -12
  112. package/js/web/api.mjs +7 -2
  113. package/package.json +1 -1
  114. package/registry.json +14 -0
  115. package/src/AGENT.md.tmpl +15 -17
  116. package/src/bricks/pr-open.md +3 -2
  117. package/src/doctrines/ops.md +2 -2
  118. package/src/doctrines/process.md +40 -36
  119. package/src/factories/analysis-to-build.json +1 -1
  120. package/src/factories/bug-report-to-fix.json +1 -1
  121. package/src/factories/issue-to-pr.json +1 -1
  122. package/src/kits/terminal-tools/rules.md +10 -0
  123. package/src/kits/terminal-tools.json +13 -0
  124. package/src/licenses/herdr.txt +201 -0
  125. package/src/modes/foreman.md +6 -3
  126. package/src/skills/_self-improvement.md +9 -7
  127. package/src/skills/commit.md +17 -17
  128. package/src/skills/debug/ci.md +1 -1
  129. package/src/skills/dependencies.md +3 -3
  130. package/src/skills/document-project.md +3 -2
  131. package/src/skills/factory.md +13 -4
  132. package/src/skills/geneseed.md +4 -2
  133. package/src/skills/git-history.md +5 -7
  134. package/src/skills/herdr.md +135 -0
  135. package/src/skills/loop.md +3 -2
  136. package/src/skills/opencode-cli.md +84 -0
  137. package/src/skills/pipeline.md +1 -1
  138. package/src/skills/release.md +5 -8
  139. package/src/skills/review-response.md +4 -2
  140. package/src/skills/rule.md +27 -1
  141. package/src/skills/ship.md +54 -7
  142. package/src/skills/worktree.md +2 -2
  143. package/src/upstreams.json +7 -0
  144. package/themes/_TEMPLATE.json +2 -0
  145. package/themes/biker.json +2 -0
  146. package/themes/commentator.json +2 -0
  147. package/themes/cyberpunk.json +2 -0
  148. package/themes/gamer.json +2 -0
  149. package/themes/imperial.json +2 -0
  150. package/themes/joker.json +2 -0
  151. package/themes/marvin.json +2 -0
  152. package/themes/mean.json +2 -0
  153. package/themes/military.json +2 -0
  154. package/themes/neutral.json +2 -0
  155. package/themes/pirate.json +2 -0
  156. package/themes/sports.json +2 -0
  157. package/themes/verstappen.json +2 -0
  158. package/themes/wizard.json +2 -0
  159. package/web/dist/assets/Activity-D2kOc3yi.js +1 -0
  160. package/web/dist/assets/ActivityDetail-By3xOr21.js +1 -0
  161. package/web/dist/assets/{Bonsai-Bfpb6W-1.js → Bonsai-CBWDTBA4.js} +1 -1
  162. package/web/dist/assets/{CopyButton-ByIntFtB.js → CopyButton-BVbpriMB.js} +1 -1
  163. package/web/dist/assets/Dashboard-CIJLPHM9.js +2 -0
  164. package/web/dist/assets/{Docs-DvlMJhpu.js → Docs-CiRRIELs.js} +3 -3
  165. package/web/dist/assets/Factories-DhyK0O8d.js +1 -0
  166. package/web/dist/assets/GreenhouseView-DW3PgTPy.js +1 -0
  167. package/web/dist/assets/Installs-B6nlo-Ly.js +3 -0
  168. package/web/dist/assets/JournalView-O65qEWfp.js +1 -0
  169. package/web/dist/assets/Kits-C5U-yT6Z.js +1 -0
  170. package/web/dist/assets/Laws-CuTw_XNf.js +4 -0
  171. package/web/dist/assets/{LibRows-DEHjIoD-.js → LibRows-D6-CVa3K.js} +1 -1
  172. package/web/dist/assets/Library-CzPlerd6.js +3 -0
  173. package/web/dist/assets/Loops-CqNF_-nS.js +2 -0
  174. package/web/dist/assets/Markdown-CxkA7940.js +71 -0
  175. package/web/dist/assets/OperatorHudView-BNr8K5qj.js +1 -0
  176. package/web/dist/assets/Personal-DeDb9e8O.js +2 -0
  177. package/web/dist/assets/Settings-B8MPN_AD.js +1 -0
  178. package/web/dist/assets/{Tabs-CWeQTADL.js → Tabs-DJzAez4h.js} +1 -1
  179. package/web/dist/assets/index-BL3P-9Rg.js +6 -0
  180. package/web/dist/assets/{index-CsAZq0BQ.css → index-CRWqKxfY.css} +1 -1
  181. package/web/dist/index.html +2 -2
  182. package/adapters/claude-code/settings.json +0 -52
  183. package/web/dist/assets/Activity-CqJiquEq.js +0 -1
  184. package/web/dist/assets/ActivityDetail-BSzevynX.js +0 -1
  185. package/web/dist/assets/Dashboard-DBOEi9lQ.js +0 -2
  186. package/web/dist/assets/Factories-Bpvv7L2H.js +0 -1
  187. package/web/dist/assets/GreenhouseView-GpBsYn50.js +0 -1
  188. package/web/dist/assets/Installs-BlGmVrFK.js +0 -3
  189. package/web/dist/assets/JournalView-iLuLrOxE.js +0 -1
  190. package/web/dist/assets/Kits-DRwpxC-J.js +0 -1
  191. package/web/dist/assets/Laws-CZkiNOWQ.js +0 -4
  192. package/web/dist/assets/Library-B4K-1iNF.js +0 -3
  193. package/web/dist/assets/Loops-BWSzaW8E.js +0 -2
  194. package/web/dist/assets/Markdown-0ORz7tAc.js +0 -69
  195. package/web/dist/assets/OperatorHudView-BAXwCEvY.js +0 -1
  196. package/web/dist/assets/Personal-Bp9nV4GR.js +0 -2
  197. package/web/dist/assets/Settings-CWWuaIp-.js +0 -1
  198. package/web/dist/assets/index-How7SzDZ.js +0 -6
package/CHANGELOG.md CHANGED
@@ -8,6 +8,101 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [5.4.0] — 2026-11-13
12
+
13
+ **Upgrade note.** *Consent Before Push* changes meaning: run `geneseed rebuild-all` after the
14
+ update. An install that excluded *Consent Before Push* because it asked on every commit can switch
15
+ it back on (`--exclude-rules` without it, or its row on the console's Constitution page). A repo
16
+ whose remote was added by hand has no default branch recorded, and every commit there asks:
17
+ `git remote set-head origin --auto` records it.
18
+
19
+ ### Changed
20
+ - **An edited deployed file reads as kept or diverged, and only a diverged one alerts.** "Kept" means the source still renders what the last emit wrote; it shows as neutral in the console and in `geneseed diff`. The base hash survives rebuilds (manifest `kept_hashes`). An edited `.md` file still alerts when kept. The self-improvement text no longer claims the doctor reports such an edit.
21
+ - **Worker briefs never open a command with `cd` into the worktree.** The Foreman worker brief and the pipeline crew brief tell workers to run from the worktree or with absolute paths (`git -C`, `npm --prefix`), because Claude Code asks the user to approve a compound command that opens with `cd` into another folder. Text only; reaches an install on its next emit.
22
+ - **The README opens with a hero image and each main section with a banner.** Seven new SVGs under `docs/assets/` share one dark panel, the brand teal and a gene-seed helix; the terminal demo is redrawn to match, says five targets, types no counts and shows each gate's first two ask lines as the hook prints them. Repository page only: none of it ships in the package.
23
+ - **`herdr` is a skill name again.** It left `RETIRED_SKILL_IDS`, where it sat since its removal in 2026-10: the kit skill drives the same tool, so an install whose `Excluded skills:` line names `herdr` now excludes the kit skill, which is what that line meant. It is listed in the new `REVIVED_SKILL_IDS`, so an old herdr skill folder that no manifest owns is still moved to `archived-skills/` on a global emit: with the kit off nothing replaces it, and with the kit on the current kit copy is written in its place. A herdr skill you edited, and that an emit already kept as yours, is never moved, with the kit on or off.
24
+ - **Consent Before Push guards the main branch, not every commit.** The main branch (`main`,
25
+ `master`, a remote's default, and from a linked worktree the main checkout's branch) changes
26
+ only through a pull request with green checks; a green one is merged on the user's yes or
27
+ under the standing auto-merge rule below, a red, pending or unchecked one never. On any other branch, commits, local merges and plain
28
+ pushes of the checked-out branch run without a prompt, a quoted Conventional Commits message
29
+ (`fix(x): y`) or a bash `-F -` heredoc with a quoted delimiter included.
30
+ - **The git gate follows on Claude Code, OpenClaude and Bob.** It asks for a commit or push onto
31
+ the main branch, a forced push, a bare `git push`, a push of another branch, or a command it
32
+ cannot read; and for everything in a repo with no remote, or a remote with no default branch
33
+ recorded. On Claude Code and OpenClaude a sub-agent's push asks too. Bob sends no sub-agent
34
+ field, so there a worker's push of its own branch passes like a session's; dispatched workers
35
+ are still told never to push. OpenCode keeps its static `git commit*`/`git push*` asks,
36
+ since a glob cannot read the branch, and its carrier says so. The rule id and name stay. The
37
+ `loop/*` exemption now matters only under strict consent.
38
+ - **The done gate may block up to 3 times per continuation, each time only after a new edit or a changed background verdict.** It used to block once per turn. A task notification starts a new continuation with a fresh count. Over the whole turn, up to the next human prompt, it blocks at most 10 times, so a red suite relaunched in the background cannot loop. A Stop with no new edit and no new verdict since the last block ends the turn with the `done-gate-cap` ledger line. A block names the checks whose background run is still running or reported a failure. The count is kept per session (and per sub-agent) in the install's `notebook/done-gate/`.
39
+ - **The startup text states its order without shouting.** The readiness-sigil paragraph loses "required", "MUST", "verbatim" and "do not paraphrase"; §9 loses "not deferrable" and "this is not a suggestion". Every ordering clause stays: read the rules and load the project context before the first reply, begin it with the sigil line, and a matching skill is still the first tool call. Strong current models over-apply emphatic wording; a weak model keeps the same sequence. The sigil line itself is unchanged, so theme detection and Bob's own first-reply override are untouched. Reaches an install on its next emit.
40
+ - **A build no longer resets an install's settings in silence; a bare build over one now exits 1.**
41
+ A `geneseed build` (or `geneseed-build`) over an existing install of the same host compares
42
+ each setting it was not given — theme, footprint, posture, mode, trust, packs, excluded rules
43
+ and skills, kits, shared tier, gate switches — with the install's own. If one would change, it
44
+ refuses before writing anything, exit 1: it lists each change as `name: current -> new` and
45
+ prints the install's own rebuild command with the flags you passed applied on top. A flag you
46
+ pass is never compared. A build that ran before and reset a setting now stops there; the new
47
+ `--reset` flag accepts the defaults for one build. `rebuild-all`, `upgrade`, `migrate` and
48
+ the console's rebuild replay an install's whole profile and run as before; the console's
49
+ install and deploy forms, its Build onto another emit, and the setup wizard, which compose a
50
+ whole selection, pass `--reset`. A rebuild command now spells `--posture` and `--mode`
51
+ unless they equal `harness.config.json`'s default, not the literal `peer`/`direct`. The first
52
+ `geneseed upgrade` into this version still replays with the old code, so an OpenCode project
53
+ bundle with the shared tier on can be refused once: run `geneseed upgrade` again.
54
+ `installProfile`, `setupBuildArgs` and `rebuildCommand` moved to `js/build/profile.mjs` so the
55
+ generator can read an install without reaching a module that spawns.
56
+
57
+ ### Added
58
+ - **A new opt-in kit, `terminal-tools`, for terminal programs the agent drives through their own CLI.** It adds two skills and no agent. `herdr` controls Herdr workspaces, tabs, panes and agents from inside a Herdr pane, gated on `HERDR_ENV=1` and on the user naming Herdr; it is adapted from the official skill of [herdrdev/herdr](https://github.com/herdrdev/herdr) (Apache-2.0), pinned at the v0.9.4 metadata sync, and carries the Windows notes of herdr's own docs page (native support generally available; signed binaries and SmartScreen avoidance unsupported; one x86_64 Windows asset in v0.9.5). `opencode-cli` drives OpenCode V2 from another session: headless `opencode run` with JSON output, the background service against `--standalone` and `--server`, sessions, MCP, plugins, models, stats and debug; it is first-party, verified against the V2 source at v2.3.0, and leaves every credential command to the user. The kit's rules gate on the environment, read live state before acting, close only what the agent opened, and never stop the user's server or service. It is off by default; turn it on with `--kits terminal-tools`.
59
+ - **`--strict-consent`** (the *Strict consent* switch on the console's Constitution page)
60
+ brings back the old behaviour: every commit and push asks, own branch included. The install
61
+ records it (`Own-branch pass: off`), every rebuild and upgrade keeps it, and the carrier
62
+ says so under the rule.
63
+ - **Auto-merge green PRs, off by default.** Say "turn on auto-merge" and the `rule` skill writes a standing rule into `user-rules.md` (global or per project; the project layer wins). With it, the `ship` skill and a factory's close step arm the forge's auto-merge on a PR the agent opens, on the reviewed head, only when the base branch has required checks: docs and tests only can arm at once, other code waits for one approving review (or the blind reviewer, for a solo repo), and a sensitive diff never arms, whatever the rule says. An armed PR is disarmed before any later push. Without the rule nothing changes, and the agent says once per session in a repo how to turn it on. No host gates a merge command, so the rule is text on every host; see `docs/guides/auto-merge.md`.
64
+ - **Sub-agents are judged at SubagentStop.** The done gate reads the sub-agent's own transcript and judges each git root it wrote under against that root's own list. A block keeps the sub-agent working; an inferred check there is a stderr line and a ledger entry only.
65
+ - **The `geneseed` skill covers a reinstall.** Its trigger now names reinstalling, updating,
66
+ upgrading, repairing and re-running the install, and it opens with the rule: start from the
67
+ install's `rebuild` command, change only the named flag, run the command a refusal prints, and
68
+ add `--reset` only when the user asked for the defaults.
69
+
70
+ ### Fixed
71
+ - **Bob prints the readiness banner once.** Bob's first-reply override told it to begin with the sigil line, and Bob also echoed the theme's fenced banner block right under it: two banners in every first reply. The override now says to print the sigil line once and never reproduce the banner block. Reaches a Bob install on its next emit.
72
+ - **`install.cmd` puts `geneseed` on PATH, as `./install` does.** After the setup wizard, when `geneseed` is not on PATH, the Windows installer now runs `geneseed link`, which writes `%LOCALAPPDATA%\Geneseed\bin\geneseed.cmd` and adds that folder to the user Path. Before, a fresh Windows clone had no `geneseed` command until the user found `geneseed.cmd link`. The check is `where $PATH:geneseed`: a bare `where` also searches the current folder and would find the clone's own launcher. A failed link only warns; `geneseed.cmd` still works from the clone. npm installs are unchanged, since npm already puts `geneseed` on PATH.
73
+ - **A background launch is not a pass.** A check started with `run_in_background`, or moved to the background after its foreground timeout, counts only when its task notification says it completed with exit code 0. Before, the launch itself counted, which was 76 of 112 accepted passes in 30 days of real transcripts. A task notification no longer opens a turn.
74
+ - **An excluded rule is no longer cited by the instructions file.** Owner decision D3 (2026-11-11) made an excluded rule off, but the carrier still cited it: an install that excluded process 5 read `(*Consent Before Push*)` in §3, Foreman mode and three process rules. The render now removes a parenthetical citation of an excluded rule, and only that name from a list of citations. The rule files on disk keep every citation. `geneseed doctor` refuses a carrier parenthetical that mixes a doctrine citation with other words; the three such sites (§3 twice, §6) and one in ops 4 were rewritten. Reaches an install on its next emit; a build with no exclusion is unchanged.
75
+ - **Skill and agent descriptions no longer end in `;`.** A description keeps the first clause of the trigger, and a clause that ended at a `;` kept it: six skills (dependencies, geneseed, loop, review-response, skill-forge, wayfinder) ended their `description:` in a `;`, which reads as text cut short. That `;` is now a `.`. Reaches an install on its next emit.
76
+ - **`geneseed help <hook-verb>` prints the hook's help instead of refusing.** `geneseed help context` (and `geneseed context --help`) answered with the hook-verb refusal and exit 2. It now prints one line saying the host runs it as `geneseed-hook context`, then that binary's own help for the verb, and exits 0. A bare `geneseed context` still refuses.
77
+ - **The notebook path names `.claude/` or `.bob/` on a project install.** On a Claude Code or Bob project install the notebook is `.claude/notebook/` or `.bob/notebook/`, but the Foreman mode's ledger and status files and the notes file of every skill and agent self-improvement loop said `notebook/…`, a folder that does not exist at the repo root. They now carry the prefix, as §6 already did; Bob's global `rules/geneseed.md` says `../notebook/`. OpenCode and OpenClaude project installs, plain bundles and the shared tier's notes path are unchanged. Reaches an install on its next emit.
78
+
79
+ ## [5.3.1] — 2026-11-12
80
+
81
+ **Upgrade note.** The fixed hook commands, matchers and plugins reach an install only when it is emitted again: run `geneseed rebuild-all` after the update.
82
+
83
+ ### Fixed
84
+ - **A gate that cannot run asks instead of letting the call through.** A gate verb that cannot parse its arguments, or runs on a Node below the floor, asks (Bob warns and exits 0, because an exit 2 there refuses every tool). An OpenClaude gate that cannot start asks. On OpenCode each guard gate runs alone, and a gate error asks on OpenCode 2.
85
+ - **A Bob call that carries text is a write, whatever the tool is called.** The check went by tool name only, so `create_file` to `user-rules.md` passed.
86
+ - **The OpenCode content scan reads `edits[]` and nested calls.** The ownership gate skips headless `geneseed-*` sessions, and its marker survives a restart.
87
+ - **A read-only agent cannot dispatch or open a shell monitor.** `Monitor` joins the shell matcher, and Bob spawns are counted.
88
+ - **Geneseed's hook handlers are recognised by signature** (shim, verb and this install's root), not by deep equality. A flag change no longer stacks a second group, a field you added such as `timeout` survives, and uninstall removes what it finds. A commented settings file gets the canonical groups printed.
89
+ - **A commented `opencode.json` is refused whatever its extension**, and uninstall removes the bash gates the manifest recorded.
90
+ - **Stop prints one document.** The change report was lost behind raw model output. The `learn` model call is bounded (`GENESEED_LLM_TIMEOUT`, default 120 s), and no lesson is keyed on a dispatch id.
91
+ - **The OpenCode context plugin keeps the prompt prefix stable**: reminders are appended, and the model line is pinned per session.
92
+ - Host docs: one dated "What is verified" block, and Bob's `learn` and `process-1` wording corrected.
93
+
94
+ ### Added
95
+ - **`GENESEED_HOOK_TAP`**, opt-in, records what a host really sends, every string redacted to its type and length. `doctor --probe` sends Bob its own payload shapes.
96
+ - **A ceiling on the skill listing**, gated by the doctor and drawn in the console on a Claude Code install's details row.
97
+ - `tool-gate` takes `--no-consent`.
98
+
99
+ ### Changed
100
+ - The host canary runs the OpenCode guard's deny on the real hosts against a scripted model on loopback. The twins tool writes every plugin copy that can be byte-identical (6 -> 48 rows).
101
+ - Console dependencies: marked 18.1.3, vite 8.3.7, @vitejs/plugin-react 6.3.0, vitest 5.1.0, jsdom 31.0.0, with `web/dist` rebuilt.
102
+
103
+ ### Removed
104
+ - The drifted `adapters/claude-code/settings.json` sample.
105
+
11
106
  ## [5.3.0] — 2026-11-11
12
107
 
13
108
  ### Added
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  <div align="center">
2
2
 
3
- # 🧬 Geneseed
3
+ <h1 align="center"><img src="docs/assets/hero.svg" alt="Geneseed" width="880"></h1>
4
4
 
5
5
  **A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.**
6
6
 
@@ -39,9 +39,9 @@ A hand-written instructions file is prose the model may or may not honour, copie
39
39
 
40
40
  - **Laws are enforced, not suggested.** A force-push to `main`, a `reset --hard` that abandons unpushed commits, or a credential written into a tracked file is caught by a hook *before* the tool runs, in the host's own dialect — a prompt on Claude Code and OpenClaude, a hard block on OpenCode, exit 2 on Bob. The gates fail closed, and every catch is one line in a ledger that `geneseed status` counts.
41
41
  - **The developer stays the owner of the code.** In a production application the agent proposes and the developer decides — per feature, per file or per function, as the team sets in a committed `AGENTS.md`. Interfaces and sensitive zones are always a checkpoint, complex parts are explained before they land, and a hook stops the first write in an application that has not chosen yet. [Ownership →](#-ownership-of-production-code)
42
- - **One source, five targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all 263 emit configurations, and a second emit into the same tree must change nothing.
42
+ - **One source, five targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all 268 emit configurations, and a second emit into the same tree must change nothing.
43
43
  - **Costs are measured, not guessed.** Zero runtime dependencies. The hook path loads in about 14 ms per tool call. The default *lean* footprint keeps the always-on context small and puts the full rationale one read away — the numbers are in [docs/token-footprint.md](docs/token-footprint.md).
44
- - **It follows you.** Install once, globally; every repo inherits it. One `git pull` or `npm install -g geneseed@latest` rebuilds every active install.
44
+ - **It follows you.** Install once, globally; every repo inherits it. One `geneseed upgrade` (a `git pull`), or `npm install -g geneseed@latest` then `geneseed rebuild-all`, rebuilds every active install.
45
45
 
46
46
  This page is the overview. **New to agent harnesses?** Start with [Understand](docs/understand/harness.md) — a short course on what a harness is, what lands on your machine, what changes in your day, and what is enforced versus only asked. Everything else — every install path, configuration knob, and troubleshooting step — is in the **[documentation](docs/README.md)**, which the web console also renders.
47
47
 
@@ -51,7 +51,7 @@ This page is the overview. **New to agent harnesses?** Start with [Understand](d
51
51
 
52
52
  <p align="center"><sub>31 deterministic checks, no LLM — <a href="#ai-harness-scorecard">how this is scored, and how to score your own repo</a></sub></p>
53
53
 
54
- ---
54
+ <p align="center"><img src="docs/assets/banner-why.svg" alt="" width="880"></p>
55
55
 
56
56
  ## 🧬 1 · Why Geneseed
57
57
 
@@ -70,7 +70,7 @@ geneseed-build # default theme (neutral)
70
70
  geneseed-build --theme imperial # Warhammer 40k voice, identical structure
71
71
  ```
72
72
 
73
- ---
73
+ <p align="center"><img src="docs/assets/banner-setup.svg" alt="" width="880"></p>
74
74
 
75
75
  ## 🚀 2 · Setup
76
76
 
@@ -82,7 +82,7 @@ The harness is published on npm as **[`geneseed`](https://www.npmjs.com/package/
82
82
  npx geneseed setup # the guided wizard
83
83
  ```
84
84
 
85
- The wizard asks for a **theme** (each one previewed live — tagline, sigil, voice) and an **install mode** — *OpenCode global* (recommended; every repo inherits it), *per-repo `.opencode/`*, or *plain bundle* for any `AGENT.md` tool — then builds and offers a health check. It works the same on macOS, Linux and Windows (cmd, PowerShell, or a POSIX shell).
85
+ The wizard asks for a **theme** (each one listed with a one-line description) and an **install mode** — a host (OpenCode, Claude Code, IBM Bob or OpenClaude) installed globally or per repo, *OpenCode global* being the recommended one (every repo inherits it), or the *plain bundle* for any `AGENT.md` tool — then builds and offers a health check. It works the same on macOS, Linux and Windows (cmd, PowerShell, or a POSIX shell).
86
86
 
87
87
  Keeping it around is the same command with `npm`:
88
88
 
@@ -137,7 +137,7 @@ Node ≥ 22.7 is the entire dependency list — every command, all six hook verb
137
137
  - **Run it from anywhere** — a global `npm install -g geneseed` already does this; from a checkout see [Run geneseed from anywhere](docs/guides/run-anywhere.md).
138
138
  - **Something wrong?** [Troubleshooting](docs/reference/troubleshooting.md) is organised by what you see.
139
139
 
140
- ---
140
+ <p align="center"><img src="docs/assets/banner-console.svg" alt="" width="880"></p>
141
141
 
142
142
  ## 🖥 3 · Web & terminal
143
143
 
@@ -158,7 +158,7 @@ geneseed web stop # stop the daemon
158
158
  geneseed web status # is it running, and where
159
159
  ```
160
160
 
161
- The sidebar has eight pages: **Overview** (what's deployed, health, recent jobs), **Constitution** (the rules and doctrine switches), **Library** (skills, agents, the wiki), **Kits** (opt-in stack bundles), **Loops** (the loop catalogue), **Personal** (your rules, profile, memory, notebook), **Installs** (hosts, local edits, doctor, server) and **Docs** — this documentation, opening on the Understand track, with a map of what Geneseed put on your machine.
161
+ The sidebar has eleven pages: **Overview** (what's deployed, health, recent jobs), **Constitution** (the rules and doctrine switches), **Library** (skills, agents, the wiki), **Kits** (opt-in stack bundles), **Loops** (the loop catalogue), **Personal** (your rules, profile, memory, notebook), **Installs** (hosts, local edits, doctor, server), **Factories** (the factory catalogue and its runs), **Activity** (what the sessions did), **Settings** and **Docs** — this documentation, opening on the Understand track, with a map of what Geneseed put on your machine.
162
162
 
163
163
  It binds to `127.0.0.1` only and runs entirely offline — no npm needed at runtime; the UI build ships in `web/dist/`. Mutating actions run in the background and report back as toasts (fire-and-notify), guarded by a per-session token so other sites can't trigger them. A global **Spotlight** search in the topbar jumps to any agent, skill, rule, doc, or MCP server. Rebuild the UI after changing anything under `web/src/` with `cd web && npm install && npm run build`. If `web/dist/` is missing (fresh clone, never built), `geneseed web` offers to run that build for you — answer `Y` and it installs, builds, and starts the server; in non-interactive shells it prints the manual recipe instead.
164
164
 
@@ -168,11 +168,11 @@ Full reference — every view, the launch/daemon/PWA surface, the security model
168
168
 
169
169
  No browser? Every action the console offers is also a verb: `build`, `doctor`, `diff`, `rebuild-all`, `status`, `memory`, `catalog`, `exclude`, `mcp`, `link`/`unlink`, `uninstall` (global **or** per-repo). `geneseed setup` runs the install wizard — plain text prompts, every console, every OS; see [Setup](#-2--setup) above for the walkthrough. `geneseed --help` lists every command, and bare `geneseed` (or `./geneseed`) opens the web console when it can, else prints the command list. There is no full-screen panel: `menu` prints the command list (`tui` is retired, and says so).
170
170
 
171
- ---
171
+ <p align="center"><img src="docs/assets/banner-contents.svg" alt="" width="880"></p>
172
172
 
173
173
  ## 📦 4 · What you get
174
174
 
175
- The harness ships as a small set of layers, and the web console's rail is the same shape — Constitution, Skills and Agents each have their own entry; Memory, Notebook and the wiki sit under Library:
175
+ The harness ships as a small set of layers, and the web console's rail is the same shape — Constitution has its own entry; skills, agents and the wiki sit under Library; memory and notebook under Personal:
176
176
 
177
177
  | Layer | What it is |
178
178
  | --- | --- |
@@ -222,7 +222,7 @@ Pick with `--theme NAME` or via the setup wizard; upgrades remember it. More in
222
222
 
223
223
  A second per-install dial sets how much of the constitution the root file carries *inline* every turn — a token-cost knob, not a change to which Rules apply. **lean** (the default) carries each rule's hand-written short form and points to the full text on disk; **full** inlines every rule with its rationale. Every rule is in force either way. More in [Footprint](docs/concepts/footprint.md) and [Footprint, loop trust and changing later](docs/guides/setup-footprint.md).
224
224
 
225
- ---
225
+ <p align="center"><img src="docs/assets/banner-harnesses.svg" alt="" width="880"></p>
226
226
 
227
227
  ## 🔌 Supported harnesses
228
228
 
@@ -243,7 +243,7 @@ is **identical on every host**. What differs is how much of it the host can
243
243
  | **Skills** (byte-identical) | ✅ | ✅ | ✅ | ✅ |
244
244
  | **Memory & Notebook** | ✅ | ✅ | ✅ | ✅ |
245
245
  | **Context injection** | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 🪝 hook³ |
246
- | **Memory write-back** (learn) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 🪝 hook³ |
246
+ | **Memory write-back** (learn) | ⚙️ plugin | 🪝 hook | ➖ wired, inert¹ | 🪝 hook³ |
247
247
  | **Git-gate consent** (process 5) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ (warn) | 🪝 hook³ |
248
248
  | **Rule-gate consent** (process 1) | ⚙️ plugin² | 🪝 hook | 🪝 hook¹ (exit 2) | 🪝 hook³ |
249
249
  | **Laws I / IV at the boundary** | ⚙️ plugin (block) | 🪝 hook (ask) | 🪝 hook¹ (exit 2) | 🪝 hook³ (ask) |
@@ -252,7 +252,7 @@ is **identical on every host**. What differs is how much of it the host can
252
252
  | **Colour themes** | ✅ full palette | ➖ | ➖ | ➖ |
253
253
  | **LSP · workflow runner · primary-agent · `/`-commands** | ✅ | ➖ | ➖ | ➖ |
254
254
 
255
- <sub>✅ native support · ⚙️ OpenCode plugin · 🪝 `settings.json` hook · 📄 carried by preamble prose only · ➖ no host mechanism (harness discipline still applies) · ¹ Bob's own hook contract: global hooks in `~/.bob/settings/settings.json`, Claude's event names but stdout ignored on `PreToolUse` — a refusal is **exit code 2**. So Laws I/IV, rigor-5 (External Gate) and ops-2 (a recursive scan of a whole filesystem) exit 2, the consent rules are a stderr line, `SessionStart` context is plain stdout, `Stop` runs learn; `SubagentStop`/`PreCompact` are not Bob events and are not written. Unverified live (no Bob install on the authoring machine); the harness still holds via the rules preamble. · ² OpenCode's `tool.execute.before` can only allow or throw, with no "ask the user" tier, so the host's own prompt asks there, and the guard refuses a file-tool write that prompt cannot reach. Shell is not a boundary on any host; the host's command permission is the backstop, and a [change report](docs/concepts/hooks.md#the-change-report) tells you afterwards. · ³ OpenClaude is a Claude Code fork: Claude's hook groups and verdicts verbatim, in `~/.openclaude/settings.json` (global) or `.openclaude/settings.local.json` (per repo). Unverified live (no OpenClaude install on the authoring machine).</sub>
255
+ <sub>✅ native support · ⚙️ OpenCode plugin · 🪝 `settings.json` hook · 📄 carried by preamble prose only · ➖ no host mechanism (harness discipline still applies) · ¹ Bob's own hook contract: global hooks in `~/.bob/settings/settings.json`, Claude's event names but stdout ignored on `PreToolUse` — a refusal is **exit code 2**. So the rules whose Bob cell says *block* in the [enforcement table](docs/concepts/enforcement-table.md) exit 2, the commit/push consent is a stderr line, and `SessionStart` context is plain stdout. `Stop` is wired but learns nothing, because Bob's `Stop` carries no transcript; only the change report runs there. `SubagentStop` is not a Bob event; Bob 2.2.3 has `PreCompact`/`PostCompact`, which Geneseed does not wire. The harness still holds via the rules preamble. What was checked against each host: [What is verified](docs/concepts/host-matrix.md#what-is-verified). · ² OpenCode's `tool.execute.before` can only allow or throw, with no "ask the user" tier, so the host's own prompt asks there, and the guard refuses a file-tool write that prompt cannot reach. Shell is not a boundary on any host; the host's command permission is the backstop, and a [change report](docs/concepts/hooks.md#the-change-report) tells you afterwards. · ³ OpenClaude is a Claude Code fork: Claude's hook groups and verdicts verbatim, in `~/.openclaude/settings.json` (global) or `.openclaude/settings.local.json` (per repo). See [What is verified](docs/concepts/host-matrix.md#what-is-verified).</sub>
256
256
 
257
257
  **Reading the matrix.** Everything above the divider is at full parity — no host
258
258
  drops an Agent, Skill, or the memory convention. The asymmetry is entirely in
@@ -306,11 +306,11 @@ Geneseed/
306
306
  ## 🧪 Validate & test
307
307
 
308
308
  ```bash
309
- node bin/geneseed-cli.mjs doctor # every theme + parity + authoring + drift
309
+ node bin/geneseed-cli.mjs doctor --all # every theme + parity + authoring + drift
310
310
  node --test --test-reporter=tap "tests/**/*.test.mjs" # the suites (node expands the glob)
311
311
  ```
312
312
 
313
- `doctor` checks each theme for unresolved tokens, dead/non-hermetic links, theme-key parity, author-time gates (every spec has a purpose line, the plugins parse, the learn-prompt literal stays extractable), and that a committed bundle still matches a fresh render of `src/`. CI (`.github/workflows/ci.yml`) runs both on every push and PR, on both Linux and Windows. Publishing is a separate workflow (`.github/workflows/publish.yml`) that runs when CI finishes green on `main` and releases only a version npm does not have yet — see [Contributing](#-contributing).
313
+ `doctor` checks each theme for unresolved tokens, dead/non-hermetic links, theme-key parity, author-time gates (every spec has a purpose line, the plugins parse, the learn-prompt literal stays extractable), and that a committed bundle still matches a fresh render of `src/`. CI (`.github/workflows/ci.yml`) runs both on every PR and on every push to `main`, on both Linux and Windows. Publishing is a separate workflow (`.github/workflows/publish.yml`) that runs when CI finishes green on `main` and releases only a version npm does not have yet — see [Contributing](#-contributing).
314
314
 
315
315
  ### AI Harness Scorecard
316
316
 
@@ -325,7 +325,7 @@ geneseed scorecard --json # every check with its evidence
325
325
 
326
326
  ## 🔄 Keeping it current
327
327
 
328
- **Installed from npm** — one command, and it rebuilds every active install for you:
328
+ **Installed from npm** — two commands: the second rebuilds every active install for you:
329
329
 
330
330
  ```bash
331
331
  npm install -g geneseed@latest
@@ -335,13 +335,15 @@ geneseed rebuild-all # re-render every registered install in its own theme + m
335
335
  **Installed from a clone** — the `git pull` route, which also refreshes the launchers:
336
336
 
337
337
  ```bash
338
- ./geneseed update # everything in one: refresh the scripts + content, then rebuild
339
- ./geneseed upgrade --setup # update everything, then drop into the setup wizard (was: bootstrap)
340
- ./geneseed upgrade # just the content refresh (remembers theme + emit mode)
338
+ ./geneseed upgrade # git pull, validate, then rebuild every install (remembers theme + emit mode)
339
+ ./geneseed upgrade --setup # the same, then drop into the setup wizard (was: bootstrap)
340
+ ./geneseed update # an alias of upgrade
341
341
  ```
342
342
 
343
343
  **Local edits survive.** The self-improvement loops write to notes under `notebook/`, which no rebuild touches. If you or the agent edited deployed agent/skill files in place anyway, an upgrade exports those edits to an `improvements/` file inside the install; the rebuild then keeps each edited file instead of overwriting it. Details: [Upgrade](docs/guides/upgrade.md).
344
344
 
345
+ <p align="center"><img src="docs/assets/banner-docs.svg" alt="" width="880"></p>
346
+
345
347
  ## 📚 Documentation
346
348
 
347
349
  | Page | Read it when… |
@@ -365,7 +367,7 @@ geneseed rebuild-all # re-render every registered install in its own theme + m
365
367
 
366
368
  ## 🤝 Contributing
367
369
 
368
- Issues and PRs welcome at [github.com/Arylmera/Geneseed](https://github.com/Arylmera/Geneseed). The CI is dependency-free and runs on every push — keep `doctor` green and the test suites passing. Adding a new theme is one JSON file in `themes/` with the same voice-token keys; `doctor` will tell you if any are missing.
370
+ Issues and PRs welcome at [github.com/Arylmera/Geneseed](https://github.com/Arylmera/Geneseed). The CI runs on every PR and on `main`, and the package has zero runtime dependencies — keep `doctor` green and the test suites passing. Adding a new theme is one JSON file in `themes/` with the same voice-token keys; `doctor` will tell you if any are missing.
369
371
 
370
372
  Start with [`AGENTS.md`](AGENTS.md), the repo's working guide (`CLAUDE.md` imports it). Three things that bite when you don't know them:
371
373
 
@@ -387,6 +389,7 @@ Some skills and agents are adapted from other open-source skill collections, und
387
389
  - `vibe-wise` — [nykooi1/vibe-wise](https://github.com/nykooi1/vibe-wise) by Noah Kim (MIT): the state file, levels and checkpoints of learn-mode, and the checkpoint rules ownership shares.
388
390
  - `piomin-spring-boot` — [piomin/claude-ai-spring-boot](https://github.com/piomin/claude-ai-spring-boot) by Piotr Mińkowski (Apache-2.0): the Spring Boot kit's skills and agents, rewritten and condensed for Boot 4.
389
391
  - `everything-claude-code` — [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) by Affaan Mustafa (MIT): the React kit's skills and agents, rewritten and condensed for Vite and Jest, and part of the docker kit's compose-ops skill, rewritten for operations.
392
+ - `herdr` — [herdrdev/herdr](https://github.com/herdrdev/herdr) by herdrdev (Apache-2.0): the terminal-tools kit's herdr skill, condensed into house format with a Windows note.
390
393
  - `i-have-adhd` — [ayghri/i-have-adhd](https://github.com/ayghri/i-have-adhd) by Ayoub Ghriss (MIT): the rules, rule-breaking cases and pre-send check of the adhd mode.
391
394
 
392
395
  ## 📄 License
package/SHIPPED.md CHANGED
@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
20
20
  > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
21
21
  > human-readable label only. The canonical identity of an installed harness is the
22
22
  > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
23
- > string. Current label: **5.3.0**.
23
+ > string. Current label: **5.4.0**.
24
24
 
25
25
  ## Capabilities
26
26
 
@@ -30,12 +30,12 @@ Every row below is present in the tree today; "Spec" names the design record.
30
30
  | --- | --- | --- |
31
31
  | **Themed generator** | One neutral `src/` → 14 themed bundles via `geneseed-build` (zero dependencies); structure stays theme-independent | [DESIGN.md](DESIGN.md) |
32
32
  | **Laws / Agents / Skills / Memory / Notebook** | 9 laws, 20 agents, 51 skills, the memory convention, and the agent's sovereign notebook | `2026-06-11-notebook-sovereign-space` · `2026-06-10-notebook-agent-own-space` |
33
- | **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Ownership, Conduct — the Pact absorbed into Telos), the nine always-on **Invariants**, and five toggleable **Doctrine** packs (craft, rigor, ops, process, comms) addressed `<pack> <n>`. Every rule carries a permanent id; its number is its position, computed at render time, and a citation renders as the rule's principle name. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order: Ontology + Invariants, then the user's `user-rules.md`, then the active Doctrines, then `PROFILE.md`. `doctor`'s `constitutionProblems` gates rule ids (declared, unique, never a retired one), the per-rule Principle column, every `{{LAW:<id>}}` / `{{DOCTRINE:<id>}}` citation in `src/`, and the rule that an always-on tier may never cite a toggleable one | `2026-08-19-three-tier-constitution-design` |
33
+ | **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Ownership, Conduct — the Pact absorbed into Telos), the nine always-on **Invariants**, and five toggleable **Doctrine** packs (craft, rigor, ops, process, comms) addressed `<pack> <n>`. Every rule carries a permanent id; its number is its position, computed at render time, and a citation renders as the rule's principle name. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order: the Invariants, then the user's `user-rules.md`, then the Ontology, then the active Doctrines, then the mode, then `PROFILE.md`, posture and theme, which inform and never bind. `doctor`'s `constitutionProblems` gates rule ids (declared, unique, never a retired one), the per-rule Principle column, every `{{LAW:<id>}}` / `{{DOCTRINE:<id>}}` citation in `src/`, and the rule that an always-on tier may never cite a toggleable one | `2026-08-19-three-tier-constitution-design` |
34
34
  | **`doctor`** | One check: unresolved tokens, dead/non-hermetic links, theme-key parity, authoring gates, rendered-bundle drift | `2026-06-07-theme-aware-doctor-diff` |
35
- | **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements.md` back-port | `2026-06-12-improvements-export` |
35
+ | **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements/improvements-<date>-<time>.md` back-port inside the install | `2026-06-12-improvements-export` |
36
36
  | **`status` / `version`** | Headless dashboard + fingerprint verdict (no TUI needed) | `2026-06-07-status-command` · `2026-06-07-version-and-uninstall` |
37
- | **Terminal rendering** | There is no full-screen control panel: `tui` and `menu` are verbs that say so and print the command list. The display-width and glyph layer ships on, behind `status` and the install animation | `2026-06-07-tui-refactor-polish` · `2026-06-08-tui-modern-refresh` · `2026-06-11-windows-tui` |
38
- | **Web console** | Local browser UI (Dashboard; Codex: Constitution, Rules, Profile, Skills, Agents, Library, Docs; Care: Activity, Changes, Doctor; Setup: Harness, Settings), auto-build, in-app docs menu | `2026-06-12-web-ui-v2` · `2026-06-12-web-auto-build` · `2026-06-13-docs-menu` |
37
+ | **Terminal rendering** | There is no full-screen control panel: `menu` is a verb that says so and prints the command list, and the retired `tui` points at `menu`. The display-width and glyph layer ships on, behind `status` and the install animation | `2026-06-07-tui-refactor-polish` · `2026-06-08-tui-modern-refresh` · `2026-06-11-windows-tui` |
38
+ | **Web console** | Local browser UI (Overview; Govern: Constitution, Personal; Build: Library, Kits, Loops, Factories; Run: Installs, Activity; Help: Docs, Settings), auto-build, in-app docs menu | `2026-06-12-web-ui-v2` · `2026-06-12-web-auto-build` · `2026-06-13-docs-menu` |
39
39
  | **OpenCode adapter** | Native agents/skills mapping + plugins (context, learn, guard, workflow, notify, ponytail, activity); global-emit link integrity; JSONC config target | `2026-06-07-opencode-adapter-features` · `2026-06-07-global-emit-link-integrity` · `2026-06-12-opencode-jsonc-target` · `2026-06-16-ponytail-minimal-code-mode` |
40
40
  | **Host hooks, per dialect** | Every host gets the hook surface its runtime offers, spoken in that runtime's own verdict dialect via `--host`: Claude Code asks (`permissionDecision`), OpenClaude asks exactly as Claude does (a Claude Code fork, under `~/.openclaude` / `.openclaude/`), Bob refuses by exit code 2 (five Claude-named events, nested `~/.bob/settings/settings.json`, no subagent event), OpenCode's guard throws. Laws I/IV are the hard tier everywhere; the consent rules ask where a host can ask and warn where it cannot. `tool-gate` fuses the two gates for hosts that run one command per event; `PreCompact` runs `learn` before Claude compacts; every block or ask lands in `notebook/gates.jsonl` on every host | [bob](adapters/bob/README.md) · [claude-code](adapters/claude-code/README.md) · [candidate hosts](docs/candidate-hosts.md) |
41
41
  | **Workflow primitive** | Saved, code-driven subagent orchestration (`workflow` tool + runtime); shipped scripts include `dispatch` — decompose a goal, route each subtask to its owning agent, converge | `2026-06-09-opencode-workflow-primitive` |
@@ -43,9 +43,9 @@ Every row below is present in the tree today; "Spec" names the design record.
43
43
  | **Wiki integration** | Machine-wide knowledge base (`geneseed-wiki.jsonc`): eager/lazy loading, conventions, protected folders enforced at the tool boundary | `2026-06-11-wiki-knowledge-base` |
44
44
  | **Collaboration layer** | Negotiated postures (peer/mentor/expert/assistant/artisan, chosen at setup, inlined in AGENT.md), the bidirectional Pact, epistemically-typed memory (`force:` + Bridge rule), and a seed-once `PROFILE.md` identity with a web editor tab and a `profile` skill that interviews the user to draft it | `2026-07-12-collaboration-layer` |
45
45
  | **Ownership** | The developer keeps ownership of production code: a Credo section (the code belongs to whoever answers for it), the `ownership` skill (setup from the code and a short interview, `feature`/`file`/`function` granularity, interfaces and sensitive zones always a checkpoint, announce-don't-ask), a `## Ownership` section in the committed root `AGENTS.md` (`mode: on\|off`), and a first-write gate on every host that stops the session's first write once in an application repo without one. learn-mode always comes first; `develop`, the `developer` agent and Foreman hold the checkpoints. Off per repo (`mode: off`), per install (`--no-ownership-gate`), per session ("proceed without") | `2026-10-26-ownership` |
46
- | **Rule front door** | Both durable stores enter through the `rule` skill's fork (*standing rule, or fact to remember?* — always asked, never inferred): the memory branch elicits the binding `force` and shows the file before writing, the rule branch pressure-tests by reformulation and a mandatory counter-example. Doctrine process 1 carries the norm on every host; a `rule-gate` PreToolUse hook (Claude, Bob) and OpenCode's own prompt behind `geneseed-guard` hold it at the tool boundary | `2026-07-30-rule-front-door` |
46
+ | **Rule front door** | Both durable stores enter through the `rule` skill's fork (*standing rule, or fact to remember?* — always asked, never inferred): the memory branch elicits the binding `force` and shows the file before writing, the rule branch pressure-tests by reformulation and a mandatory counter-example. Doctrine process 1 carries the norm on every host; a `rule-gate` PreToolUse hook (Claude, OpenClaude; on Bob inside its `tool-gate`) and OpenCode's own prompt behind `geneseed-guard` hold it at the tool boundary | `2026-07-30-rule-front-door` |
47
47
  | **Entity registry** | `registry.json` records a lifecycle status, version, owner and add-date for every agent and skill in the tree (maintainer-side — never rendered into a bundle, so it costs no session context). `doctor` gates it against `src/` in both directions, sweeps everything that ships for credentials, and holds each vendored skill folder to an immutable upstream commit. The status surfaces as a badge in the web catalog, shown only where it deviates from `approved` | `2026-07-31-entity-registry` |
48
- | **Node runtime + npm package** | The whole harness runs from Node: every command `js/cli-table.json` declares, all five hook verbs, every web-console endpoint (the OS-native folder picker excepted, and declined on purpose) and both generators. Every commit runs the unit suite, `doctor --all` across every theme × host × footprint, and the generator's two self-comparisons, on Linux and Windows both; the frozen emit/cli/web recordings that also gated it retired on 2026-08-17 (see the 2.0.0 entry in [CHANGELOG.md](CHANGELOG.md)). It ships as the zero-dependency `geneseed` package (`geneseed`, `geneseed-hook`, `geneseed-build`), so `npx geneseed setup` needs no clone and nothing else installed; `geneseed migrate` moves an existing checkout install across. Node is the only runtime it asks for: the `token-report` skill's own script is `token_report.mjs`, gated over seeded transcripts for all four hosts, and `daydream` calls `node -e` | `2026-08-06-npx-distribution` |
48
+ | **Node runtime + npm package** | The whole harness runs from Node: every command `js/cli-table.json` declares, all six hook verbs, every web-console endpoint (the OS-native folder picker excepted, and declined on purpose) and both generators. Every commit runs the unit suite, `doctor --all` across every theme × host × footprint, the generator's two self-comparisons and its CLI expectation matrix, on Linux and Windows both; the frozen emit/cli/web recordings that also gated it retired on 2026-08-17 (see the 2.0.0 entry in [CHANGELOG.md](CHANGELOG.md)). It ships as the zero-dependency `geneseed` package (`geneseed`, `geneseed-hook`, `geneseed-build`), so `npx geneseed setup` needs no clone and nothing else installed; `geneseed migrate` moves an existing checkout install across. Node is the only runtime it asks for: the `token-report` skill's own script is `token_report.mjs`, gated over seeded transcripts for all four hosts, and `daydream` calls `node -e` | `2026-08-06-npx-distribution` |
49
49
  | **Runtime awareness** | MCP discovery, web research, tool-call batching, review discipline — carried by the doctrine packs (`ops 1` tool discovery, `process 4` read the docs first, `rigor 2`/`rigor 3` honest tests and cover-and-verify), not by the invariants | `2026-06-07-runtime-awareness-and-review-discipline` |
50
50
  | **Shared tier** | One machine-wide folder (`~/.config/geneseed`) for memory, standing rules, profile, wiki manifest, exclude paths and notes, read by every global install on every host. Layered reads (project over host over shared), a fold in each global emit that moves existing stores aside, `user-rules.draft.md` decided only through the `rule` skill, and `--shared-tier on` for a project install | `2026-11-05-shared-tier` |
51
51
  | **Run from anywhere / uninstall** | `link`/`unlink` onto PATH; global uninstall that keeps the memory store | `2026-06-07-version-and-uninstall` |
@@ -9,7 +9,7 @@ Claude engine** verbatim — only the marker dir (`.bob`) and the instructions
9
9
  filename (`AGENTS.md`) change. There is nothing to install by hand: `geneseed
10
10
  setup` (or `geneseed build --emit bob` / `--emit bob-global`) writes everything.
11
11
 
12
- This page documents the two verified **Bob-isms** the engine handles, and one
12
+ This page documents the **Bob-isms** the engine handles, and one
13
13
  limitation to be aware of on a shared repo.
14
14
 
15
15
  ## What the emit writes
@@ -86,8 +86,7 @@ and fell back to searching the filesystem. The Bob emit therefore writes the dir
86
86
 
87
87
  ## Hooks — Bob's own protocol
88
88
 
89
- Bob documents lifecycle hooks (its hooks page and the 2.0.2 changelog; see
90
- `docs/reviews/bob-global-injection-2026-09.md` for the reading): **five events** —
89
+ Bob documents lifecycle hooks (its hooks page and the 2.0.2 changelog): **five events** —
91
90
  `SessionStart`, `UserPromptSubmit`, `PreToolUse`, `PostToolUse`, `Stop` — with Claude's
92
91
  names but **not Claude's protocol**, and the global file at the **nested**
93
92
  `~/.bob/settings/settings.json`. Two differences decide the emit:
@@ -105,8 +104,8 @@ What the global emit writes into `~/.bob/settings/settings.json`:
105
104
  | event | verb | how the verdict travels |
106
105
  | --- | --- | --- |
107
106
  | `SessionStart` | `context --host bob` | plain stdout, as on Claude |
108
- | `PreToolUse` | `tool-gate --host bob` — one group, no matcher | Laws I/IV, rigor-5 and ops-2: **exit 2**, reason on stderr — it says no chat confirmation lifts the block, since Bob has no ask tier; process 1/5: a stderr line, exit 0; the ownership gate (the session's first write in an application repo with no `## Ownership` section in its root `AGENTS.md`): **exit 2 once**, the same write then passes — off with `--no-ownership-gate`, `mode: off`, or a personal `Setup: declined <YYYY-MM-DD>` line in `.geneseed/ownership.md` |
109
- | `Stop` | `learn` | never a verdict |
107
+ | `PreToolUse` | `tool-gate --host bob` — one group, no matcher | the rules whose Bob cell says *block* in the [enforcement table](../../docs/concepts/enforcement-table.md): **exit 2**, reason on stderr — it says no chat confirmation lifts the block, since Bob has no ask tier; the commit/push consent (process 5) and a parsed shell write to a rule store: a stderr line, exit 0; the ownership gate (the session's first write in an application repo with no `## Ownership` section in its root `AGENTS.md`): **exit 2 once**, the same write then passes — off with `--no-ownership-gate`, `mode: off`, or a personal `Setup: declined <YYYY-MM-DD>` line in `.geneseed/ownership.md` |
108
+ | `Stop` | `learn` | never a verdict. **Wired but inert:** Bob's `Stop` carries no transcript, so nothing is distilled; only the [change report](../../docs/concepts/hooks.md#the-change-report) runs (on stderr). The group is kept so that learning starts if Bob ever sends a transcript |
110
109
  | `UserPromptSubmit` | `activity --host bob` | never a verdict; records the turn for the web console's Activity view |
111
110
 
112
111
  Every hook also feeds the Activity view after it decides (off with `GENESEED_ACTIVITY=off`).
@@ -135,24 +134,38 @@ id), `cwd` (the root workspace, with a lower-case drive letter on Windows), and
135
134
  No matcher on `PreToolUse`, deliberately: Bob's tools page already drifts from its own
136
135
  changelog (`web_fetch`, the 2.1.0 Office/IBM-docs tools are undocumented there), so an
137
136
  allow-list built from it would fail open on the next tool Bob adds, and a deny-list needs a
138
- regex dialect (lookahead) the docs never confirm — bob-verdict.md O1 rates the matcher's own
139
- upside "low, performance only", not worth either risk. `tool-gate` reads the payload's shape
137
+ regex dialect (lookahead) the docs never confirm — and the matcher's own upside is low,
138
+ performance only, not worth either risk. `tool-gate` reads the payload's shape
140
139
  instead — a `command` field gets the git checks, a path gets the rule checks — and defers on
141
- anything it does not recognise. Bob has **no "ask the user" tier**, so the Laws and checks
142
- that admit no judgement call — Laws I and IV, rigor-5 (External Gate, when a project
143
- opts in) and ops-2 (Commands Must Return: a recursive scan rooted at a whole filesystem) —
144
- are refused outright, and the two consent rules become a warning. Because that
145
- warning is all process 5 can be here, the `process` pack toggle changes nothing in Bob's
146
- hooks: the one group only ever exits 2 for Laws I and IV, rigor-5 and ops-2, which every build
147
- carries.
140
+ anything it does not recognise. Bob has **no "ask the user" tier**, so the rules
141
+ that admit no judgement call are refused outright, and the commit/push consent becomes a
142
+ warning. Which rules those are is written in one place, the Bob column of the
143
+ [enforcement table](../../docs/concepts/enforcement-table.md); `geneseed doctor` holds that
144
+ column to `BLOCK_RULES` in `js/hosts/hooks.mjs`. A build without the `process` pack carries
145
+ `--no-rule-store`, which drops the standing-rule block, and `--no-consent` (also when process 5
146
+ alone is excluded): the commit/push warning stops, as Claude's ask does. Nothing else in the
147
+ group changes.
148
+
149
+ **When the hook cannot start** (the shim is gone, node will not load), Bob sees a non-zero
150
+ exit that is not 2 and lets the call through; nothing is added to the command to change that.
151
+ The two ways a command could answer are both wrong here: Bob ignores a `PreToolUse` hook's
152
+ stdout, so a printed ask says nothing, and a tail that exits 2 would refuse every tool call
153
+ with no prompt through which you could lift it. `geneseed doctor --probe` runs the gate and
154
+ reports one that does not start.
155
+
156
+ **What fires.** `tool-gate` also counts skill and sub-agent calls for the web console's
157
+ Overview: `spawn_subagent` by its `name`, `start_subtask` by its `mode`. A subtask's `title` is
158
+ never recorded: it is free text, and the count keeps no prompt.
148
159
 
149
160
  **Migration.** A re-emit over an older install unwires Geneseed's groups from the flat
150
161
  `~/.bob/settings.json` (your own keys there are kept) and writes the new set to the
151
162
  nested file.
152
163
 
153
- **Partly verified.** The payload field names are Claude's: Bob 2.2.3's bundle shows them,
154
- and a live Activity check on 2026-10-25 recorded a Bob session from them. The gates' own
155
- verdicts are still Bob's documented contract. If a field
164
+ **What is verified** about Bob — the bundle read, the two live sessions, and what neither
165
+ covers — is in one place:
166
+ [What is verified](../../docs/concepts/host-matrix.md#what-is-verified). To check your own
167
+ install by hand, and to record what your Bob really sends (`GENESEED_HOOK_TAP`), see
168
+ [Verify it works](../../docs/guides/verify.md). If a field
156
169
  name differs the gate defers rather than misfires, and the harness still holds through
157
170
  the `rules/geneseed.md` preamble — the same behaviour-contract parity every
158
171
  non-OpenCode host gets. `/hooks` in Bob Shell 2.0.2+ lists the hooks it loaded and
@@ -180,7 +193,7 @@ servers from ([Bob docs](https://bob.ibm.com/docs/ide/configuration/mcp/mcp-in-b
180
193
  ## Slash commands
181
194
 
182
195
  Bob documents `.bob/commands/*.md` (project) and `~/.bob/commands/*.md` (global), with
183
- `description` frontmatter (bob-docs.md §6 — no use for `argument-hint` yet: no Geneseed
196
+ `description` frontmatter (Bob's slash-commands docs page — no use for `argument-hint` yet: no Geneseed
184
197
  skill takes positional arguments). Geneseed writes one command per merged skill's OLD name
185
198
  (`/old-name`, the same alias problem OpenCode's `command/` layer solves) and one per
186
199
  genuinely user-only skill (host-compat O2/R1): Bob's skills page documents only
@@ -8,13 +8,23 @@ self-discipline.
8
8
 
9
9
  ## Install
10
10
 
11
- Merge [`settings.json`](settings.json) into your repo's `.claude/settings.json`.
12
- (Not your *user* settings: the hook commands are repo-relative — `node
13
- bin/geneseed-hook.mjs …` — so at user scope they would fire and fail in every
14
- repo that doesn't vendor the harness. A generated global install wires
15
- absolute-path hooks instead — `geneseed setup` does that for you.) It:
11
+ `geneseed setup` (or a `--emit claude` build) merges the hooks into the install's settings
12
+ file: `.claude/settings.local.json` for a project install, `~/.claude/settings.json` for a
13
+ global one. There is no sample file to copy: each command carries this machine's shim path, the
14
+ install's own `--root` and the gate flags the build chose, so only the emit can write it. When
15
+ the settings file has comments the emit does not rewrite it, and prints the exact `hooks` object
16
+ to merge by hand instead.
16
17
 
17
- - on **PreToolUse** (matcher `Bash|PowerShell`), runs `geneseed-hook git-gate` — the tool-boundary
18
+ A re-emit recognises its own handlers by that signature (the shim, a hook verb, this install's
19
+ `--root`), replaces them where they sit and leaves everything else as found: your own hooks, a
20
+ hook you added inside one of these groups, and a field you set on one of ours, such as
21
+ `timeout`. Uninstall removes the same handlers and nothing else. A hook you write yourself that
22
+ runs the shim with this install's `--root` counts as Geneseed's.
23
+
24
+ The wiring:
25
+
26
+ - on **PreToolUse** (matcher `Bash|PowerShell|Monitor`, the three tools that run a shell
27
+ command), runs `geneseed-hook git-gate` — the tool-boundary
18
28
  half of Doctrine process 5 (*consent before every commit and push*) and of the
19
29
  destructive-git Rule. Drop the `process` pack (or exclude process 5) and the hook stays,
20
30
  wired with `--no-consent`: commits and pushes pass without asking (excluding process 1 or ops 2,
@@ -32,15 +42,16 @@ absolute-path hooks instead — `geneseed setup` does that for you.) It:
32
42
  next time regardless. Every other Bash command (and any unreadable payload) is
33
43
  deferred to the normal permission flow — the hook never blocks unrelated work.
34
44
 
35
- **Caveat — the GitHub MCP vector.** The hook matches the `Bash` and `PowerShell` tools
36
- only. If your session has the GitHub MCP server, an agent can commit/push via
37
- `push_files` / `create_or_update_file` / `merge_pull_request`, which bypass both. To
38
- gate those too, widen the matcher to `"Bash|PowerShell|mcp__github__.*"` —
45
+ **Caveat — the GitHub MCP vector.** The hook matches the `Bash`, `PowerShell` and `Monitor`
46
+ tools only. If your session has the GitHub MCP server, an agent can commit/push via
47
+ `push_files` / `create_or_update_file` / `merge_pull_request`, which bypass all three. To
48
+ gate those too, widen the matcher to `"Bash|PowerShell|Monitor|mcp__github__.*"` —
39
49
  `git-gate` ignores any payload it doesn't recognise as a commit/push, so
40
- over-matching the tool surface is harmless.
50
+ over-matching the tool surface is harmless. A re-emit puts the matcher back as it
51
+ wrote it, so widen it again after a rebuild.
41
52
  - on **PreToolUse** (matcher `Write|Edit|NotebookEdit`), runs
42
- `geneseed-hook rule-gate` — refuses a write that would put a credential into a tracked
43
- file, and asks first on a write to `user-rules.md` or the rule draft (a standing rule is
53
+ `geneseed-hook rule-gate` — asks first on a write that would put a credential into a tracked
54
+ file, and on a write to `user-rules.md` or the rule draft (a standing rule is
44
55
  your call; memory is written freely, and you see it afterwards in the web console). In an application repo (a git
45
56
  root holding a build manifest) whose root `AGENTS.md` has no `## Ownership` section, it also
46
57
  denies the session's first write once, with a reason addressed to the agent: propose the
@@ -54,12 +65,9 @@ absolute-path hooks instead — `geneseed setup` does that for you.) It:
54
65
  - on **SessionStart**, every source (`startup`, `resume`, `clear`, `compact`, `fork`), runs
55
66
  `geneseed-hook context` to **inject the project context** directly into the session — so
56
67
  the project-context load is by the hook, not left to the agent to remember (lazy entries
57
- are only listed). This is one matcher-less group, exactly as a generated install wires it:
58
- a matcher list is one more place to miss a source (`fork` once was). A second group,
59
- `startup`/`clear` only — a fresh context — prints `AGENT.md` so the vendored harness is in
60
- context from the first turn. A generated install has no such group: its root file is
61
- `CLAUDE.md`, which Claude Code loads by itself. A resumed or forked conversation already
62
- carries the harness, so re-printing the static file there is pure token waste;
68
+ are only listed). This is one matcher-less group: a matcher list is one more place to miss
69
+ a source (`fork` once was). The harness itself is not printed here: the install's root file
70
+ is `CLAUDE.md`, which Claude Code loads by itself;
63
71
  - on **Stop**, runs `geneseed-hook learn` over the session to capture durable memories.
64
72
  Claude Code pipes the hook payload (with the session's `transcript_path`) to the
65
73
  command on stdin; `learn` reads that, flattens the transcript, distils new
@@ -96,9 +104,6 @@ absolute-path hooks instead — `geneseed setup` does that for you.) It:
96
104
  `learn` finds a project install or bundle in the cwd or `./Harness`. Any other `memory/` is not a store until it is named:
97
105
  `--memory <dir>` or `GENESEED_MEMORY=/abs/path/to/memory`.
98
106
 
99
- Adjust the paths if your harness bundle is not at the repository root. On Windows
100
- the commands are identical (`node bin/geneseed-hook.mjs …`).
101
-
102
107
  Why inject rather than instruct? The constitution tells the agent to read the project
103
108
  context at startup, but startup rituals are exactly what agents skip. The
104
109
  `geneseed-hook context` hook removes the choice: the eager files' contents land in
@@ -55,22 +55,32 @@ global config file.
55
55
 
56
56
  ## Hooks
57
57
 
58
- The Claude group set, unchanged: `PreToolUse` (git gate on `Bash|PowerShell`, rule gate on
59
- writes), `SessionStart` (context on every source — one matcher-less group covers
58
+ The Claude group set: `PreToolUse` (git gate on `Bash|PowerShell|Monitor`, rule gate on
59
+ writes, and a counter on `Skill|Agent|Task` that judges nothing), `SessionStart` (context on every source — one matcher-less group covers
60
60
  `startup`, `resume`, `clear`, `compact` and `fork` alike), `Stop`,
61
61
  `SubagentStop` and `PreCompact` (learn), `SubagentStart` (`context`, which hands a sub-agent
62
62
  your `user-rules.md` layers as `hookSpecificOutput.additionalContext`; OpenClaude 0.32.0's
63
63
  bundle reads that field for this event), and `UserPromptSubmit` and `SessionEnd`
64
64
  (`activity`, which feeds the web console's Activity view). OpenClaude reads Claude's
65
65
  `hookSpecificOutput.permissionDecision`, so the gates **ask** where Claude asks.
66
- The context hook carries `--host openclaude` for one reason. It tells the hook
67
- which root file OpenClaude already loads (`AGENTS.md` when present, else
68
- `CLAUDE.md`), so that file is not injected a second time.
66
+
67
+ **When a gate cannot start** (the shim is gone, node will not load), Claude Code blocks the
68
+ call through `onFailure: "block"`. OpenClaude forked before that field existed and reads the
69
+ empty stdout as "nothing to say", so every call would go through unjudged. Its two gate
70
+ commands therefore end in `|| printf '%s' '<ask>'`: when the gate did not exit 0, the shell
71
+ itself prints a fixed ask, and you are prompted. OpenClaude always runs hooks under Git Bash or
72
+ sh, where that spelling is valid. The counter has no such tail: a counter that cannot start
73
+ must not ask.
74
+
75
+ The context hook carries `--host openclaude` to tell the hook which root file OpenClaude
76
+ already loads (`AGENTS.md` when present, else `CLAUDE.md`), so that file is not injected a
77
+ second time. The other hooks carry it so a relocated install stands down correctly and its
78
+ activity is filed under OpenClaude, not Claude.
69
79
 
70
80
  ## Not supported
71
81
 
72
82
  - **Workflows.** OpenClaude ships its `WorkflowTool` disabled, so the `workflow`
73
83
  skill falls back to parallel agents, as on Bob.
74
- - **Live verification.** The emit follows OpenClaude's source (`src/utils/envUtils.ts`,
75
- `src/utils/claudemd.ts`, `src/utils/config.ts`, `src/types/hooks.ts`) as of
76
- 2026-09. It has not been run against an installed OpenClaude yet.
84
+ - **Hooks that need a model turn** are checked on no host. What was checked against
85
+ OpenClaude itself, how and when, is in one place:
86
+ [What is verified](../../docs/concepts/host-matrix.md#what-is-verified).
@@ -103,7 +103,12 @@ changed for each plugin:
103
103
  The note exists only for the two asks the guard hands to the host: a rule write that reaches a host prompt, and a gate configuration file. Every other outcome here is a refusal, and a refusal goes to the model. A V2 refusal is the renamed tool, and core quotes that name in its `No tool named` error. The history keeps the original tool name, so several lines of text there reach no provider as a name (seen on 2.2.6 with a fake model, through `opencode run`).
104
104
 
105
105
  None of this is checked by a mock alone: `node tests/host_canary.mjs` starts the real V1 and V2
106
- and fails on the host's own `failed to load plugin` log line.
106
+ and fails on the host's own `failed to load plugin` log line. It then runs that refusal on both:
107
+ a scripted model on loopback (`tests/helpers/fake_model.mjs`) asks `opencode run` to write
108
+ `.ssh/id_rsa`, and the canary fails unless the file is absent, the next write lands, and the
109
+ model is sent the refusal — V1's thrown `[geneseed-guard] blocked:`, V2's `No tool named
110
+ "BLOCKED, not a missing tool: …"`. So a V2 that resolves the tool before `execute.before`, or
111
+ drops an unknown name without telling the model, turns the canary red.
107
112
 
108
113
  ## 4. Subagents, skills & commands
109
114
 
@@ -127,8 +132,8 @@ to native **skills**, not slash commands (same `SKILL.md` shape as Claude Code).
127
132
  | --- | --- |
128
133
  | `instructions` → `AGENT.md` | the rules, loaded every session |
129
134
  | `.opencode/agents/`, `.opencode/skills/` | capability agents and native skills |
130
- | plugin on `session.created` | **context plugin (v2)** — auto-discovers & injects the repo's `eager` docs |
131
- | plugin on `experimental.session.compacting` | **context plugin** — re-pushes the `eager` docs so they survive compaction |
135
+ | plugin on `experimental.chat.messages.transform` (V1) / `session.hook("context")` (V2) | **context plugin** — the default delivery: auto-discovers the repo's `eager` docs and prepends them to every request as one synthetic user message, so nothing shows in the conversation and compaction cannot drop it |
136
+ | plugin on `session.created` + `experimental.session.compacting` | **context plugin** — the visible delivery, only with `GENESEED_CONTEXT_VISIBLE=1` or when a V1 build lacks the transform hook: one visible message per session, re-pushed into the compaction context |
132
137
  | plugin on `session.idle` | **learn plugin** — distils memory into `memory/` (debounced to fire once, at session end) |
133
138
  | plugin on `experimental.chat.messages.transform` (V1) | **context plugin** — also adds the done gate's reminder when a check in `.geneseed/done-checks.txt` (or, without it, a check inferred from the root manifests) has not passed since the last edit (Verify Before Asserting); OpenCode 2 turns are not judged |
134
139
  | plugin on `tool.execute.before` | **guard plugin** — blocks secret-file writes and credential-shaped write content (Sealed Secrets), writes to a protected check or the done list (External Gate), catastrophic shell and every other real data loss, judged against the repository's state (Deletion Is Deliberate), a recursive whole-filesystem scan (Commands Must Return), a rule-store write the host cannot prompt for (Persist Insight), protected wiki folders, and the session's first write in an application repo with no `## Ownership` section in its root `AGENTS.md` (the ownership gate, once; a child session defers; off with `--no-ownership-gate` or a personal `Setup: declined <date>` line in `.geneseed/ownership.md`); logs each block to the gate ledger and counts skill/subagent use (`GENESEED_GUARD=off\|warn`) |