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
@@ -20,7 +20,7 @@ Each iteration is one commit on `loop/<slug>`, pushed as it lands. Work done bef
20
20
 
21
21
  The agent ends its turn and shows you what it is waiting on:
22
22
 
23
- - **A blocking score**: the change it plans (before it runs) or the staged diff (after), with the reasons for the score. One file outside the declared write set, more than 20 deleted lines, or a file that matches the loop's `contracts` is enough.
23
+ - **A blocking score**: the change it plans (before it runs) or the staged diff (after), with the reasons for the score. One file outside the declared write set, more than 20 deleted lines, or a file that matches the loop's `contracts` is enough under `prudent` and `balanced`; under `aggressive` each of these lands as a soft score, and a template can lower the deletion weight (`remove-dead-code` does).
24
24
  - **A human gate**: some bricks always stop for you, whatever the preset. An ADR that survived its skeptic (`adr-challenge`), an architecture rule and its allowlist (`fitness-define`), a contract migration plan (`migration-plan`) and a feature spec (`spec`) are all gated.
25
25
  - **Launch**, under `prudent`: the graph it is about to run.
26
26
 
@@ -29,8 +29,8 @@ Answer in the agent's session, in your own words:
29
29
  | You say | What happens |
30
30
  | --- | --- |
31
31
  | ok / go ahead | It continues. On a gate held on a failure, ok follows that failure's edge, which usually stops the loop. |
32
- | no | The loop stops at that node. |
33
- | amend, with a note ("keep the old field until v3") | The same brick runs again with your note added to `LOOP.md`. A gate can be amended three times per iteration; a fourth amend stops the loop. |
32
+ | no | At a gate, at the launch prompt or during a setup unit, the loop stops. On a blocking score, that iteration's change is dropped (the planned one) or discarded (the diff), and the loop goes on from the iteration head. |
33
+ | amend, with a note ("keep the old field until v3") | Your note is added to `LOOP.md`. At a gate the same brick runs again; on a blocking score the brick that changes code runs with your note. A gate can be amended three times per iteration; a fourth amend stops the loop. |
34
34
  | amend, at the `prudent` launch prompt | The loop stops ("graph to amend") with your note: nothing has run yet, so ask again for the loop you want. |
35
35
 
36
36
  The agent passes your answer on as `geneseed loop decide --verdict ok|no|amend --note "<your words>"`. The console never answers for you.
@@ -57,7 +57,7 @@ A loop ends one of two ways:
57
57
  | End | When |
58
58
  | --- | --- |
59
59
  | `$close` | The iteration head reports nothing left to do. Some templates first run an independent `done-check`. |
60
- | `$stop` | A brick reported an outcome wired to stop (a red baseline in `baseline-green`, say), you answered no, a gate was amended a fourth time, two iterations in a row produced no diff, an inner retry ring ran out twice in one iteration, a read-only brick changed files, or the iteration ceiling was reached (the template's `max`, never above 20). |
60
+ | `$stop` | A brick reported an outcome wired to stop (a red baseline in `baseline-green`, say), you answered no at a gate, at launch or during setup, a gate was amended a fourth time, two iterations in a row produced no diff, an inner retry ring ran out twice in one iteration, a read-only brick changed files, or the iteration ceiling was reached (the template's `max`, never above 20). |
61
61
 
62
62
  On `$stop` the agent reports the reason and leaves the branch as it is.
63
63
 
@@ -21,7 +21,7 @@ The context step sorts every doc it finds into one of two lists:
21
21
 
22
22
  With no configuration, the context step finds these files:
23
23
 
24
- - **Eager:** root `AGENTS.md`, `AGENT.md`, `CLAUDE.md` and `.cursorrules`, plus `README.md` and `CONTRIBUTING.md` (or their AsciiDoc `.adoc` twins). The root file your tool already loads by itself is skipped, so you never pay for it twice. On Claude Code that covers `AGENTS.md` too, when `CLAUDE.md` imports it with `@AGENTS.md`, or when the repo has no `CLAUDE.md` and Claude Code is 2.1.277 or newer. If the hook cannot read the version, it injects the file.
24
+ - **Eager:** root `AGENTS.md`, `AGENT.md`, `CLAUDE.md` and `.cursorrules`, plus `README.md` and `CONTRIBUTING.md` (or their AsciiDoc `.adoc` twins), and a repo-root `user-rules.md` and `PROFILE.md`. The root file your tool already loads by itself is skipped, so you never pay for it twice. On Claude Code that covers `AGENTS.md` too, when `CLAUDE.md` imports it with `@AGENTS.md`, or when the repo has no `CLAUDE.md` and Claude Code is 2.1.277 or newer. If the hook cannot read the version, it injects the file.
25
25
  - **Lazy:** `docs/`, `doc/`, `documentation/`, `architecture/`, `adr/` and `ADR/`, monorepo `packages/*/README.md` and `apps/*/README.md`, and any other root `*.md`. AsciiDoc docs (`.adoc`) are found everywhere a `.md` is.
26
26
  - **Never scanned:** `node_modules`, `.git`, `dist`, `build`, `vendor`, `.next`, `target`, `.venv`, `__pycache__`, `.opencode` and `.harness`.
27
27
 
@@ -6,7 +6,7 @@ kind: "concept"
6
6
  section: "Factories"
7
7
  description: "Carry a bug report, an issue or an analysis to an open PR with green CI: what you need, how to ask, and where it stops for you."
8
8
  ---
9
- A **factory** carries one work item to an open pull request with green CI. Each stage is a brick or a whole loop, and a red CI run sends the work back to the loop, a bounded number of times. You ask in plain words. The agent drives `geneseed factory`, which decides every step. No stage merges: at the end the agent asks you once whether to merge, and merges only on your yes.
9
+ A **factory** carries one work item to an open pull request with green CI. Each stage is a brick or a whole loop, and a red CI run sends the work back to the loop, a bounded number of times. You ask in plain words. The agent drives `geneseed factory`, which decides every step. No stage merges: at the end the agent asks you once whether to merge, and merges only on your yes. With your standing auto-merge rule it arms the forge's auto-merge instead ([Auto-merge green PRs](auto-merge.md)).
10
10
 
11
11
  This page is the how-to. For how the engine works (stages, cycles, state files), see [Factories](../concepts/factories.md).
12
12
 
@@ -116,7 +116,7 @@ run the analysis-to-build factory on docs/analysis/export-csv.md
116
116
  | `merge-gate` reports `none` | The repo runs no CI on the PR: `ok` goes on to `retro`, `no` stops the run. Or the finding starts `environment:`: CI was still pending after 30 minutes, or `gh`/`glab` is missing or failed. `amend` waits again (after you fix the tool), `ok` goes on to `retro` without a green verdict (the close step reads CI once more, and proposes the merge only when it is green), `no` stops. |
117
117
  | A `geneseed factory record` line asks | The git gate asks on any command line that holds the word `git` and the word `commit` or `push`. A record line starts with `git status`, so a spec path, a finding's path or an outcome name with `commit` or `push` in it makes the gate ask. On a record line this is a false alarm: answer yes. |
118
118
  | The close commit | The last commit removes `FACTORY.md`, and it asks. Its push runs CI again: the agent reads the checks once more and reports the final state. A run with no loop (the `docs` lane) never committed `FACTORY.md`: the agent deletes the file, there is no close commit, and the final state is the one `merge-gate` read. |
119
- | The merge proposal | Only when that final CI state is green: the agent shows the PR, the CI state and each review seat's verdict, and asks once whether to merge. Only on your explicit yes in chat does it squash-merge (`gh pr merge --squash`); no Geneseed gate asks before that command, so your answer is the only guard. Otherwise the PR stays open. It never turns on auto-merge. |
119
+ | The merge proposal | Only when that final CI state is green: the agent shows the PR, the CI state and each review seat's verdict, and asks once whether to merge. Only on your explicit yes in chat does it squash-merge (`gh pr merge --squash`); no Geneseed gate asks before that command, so your answer is the only guard. Otherwise the PR stays open. With your standing auto-merge rule, it arms the forge's auto-merge on the final head instead (the `review-panel` verdict counts as the `reviewer` pass), and a green head then merges at once; see [Auto-merge green PRs](auto-merge.md). |
120
120
 
121
121
  Red CI does not stop for you: it sends the work back to the run's loop (`bugfix`, or the lane `triage` chose) with the failing checks as its first note, twice at most. A third red result stops the run. A failed holdout scenario works the same way, with its own count of two, and so do a failed `checks` and a failed `review-panel`. A holdout `error` stops the run: the diff touched the holdout folder, or a scenario could not be played.
122
122
 
@@ -31,7 +31,7 @@ The packs always load in the same order (craft, rigor, ops, process, comms), wha
31
31
 
32
32
  **Dropping `process` changes what the machine does, not only what the agent reads.** The *Consent Before Push* rule in that pack is enforced at the tool boundary as well as in the prose:
33
33
 
34
- - On Claude Code and OpenClaude, the git hook stays wired but stops asking before a commit or push.
34
+ - On Claude Code and OpenClaude, the git hook stays wired but stops asking before a commit or push onto the main branch.
35
35
  - On OpenCode, a fresh install no longer gets the `git commit*` and `git push*` ask entries in `opencode.json`. On an existing install, the entries Geneseed recorded adding are removed. Entries you typed, and those on an install made before 5.2.0, are left in place and reported; build once with `--prune-gates` to remove the second kind.
36
36
 
37
37
  The refusals of destructive git and `rm -rf` belong to the always-on Rules, not to the pack, so they stay in every build. See [Enforced vs. asked](../understand/enforced-vs-asked.md).
@@ -48,7 +48,7 @@ geneseed build --emit opencode-global --exclude-rules none
48
48
 
49
49
  The number in an address is the rule's position in its pack, so it can change if a rule is added or removed. To see the current addresses, pass an address that does not exist: the build refuses it and lists every valid address. The web console's **Constitution** page has one switch per rule. You stage the changes there and apply them in a single rebuild.
50
50
 
51
- Excluding *Consent Before Push* (`process 5` today) takes the commit and push consent gate with it, exactly as dropping the whole `process` pack does. The console and the wizard both warn you before applying it. A pack whose every rule is excluded drops out of the build entirely. See [Exclusions](../concepts/exclusions.md) for excluding whole folders instead.
51
+ Excluding *Consent Before Push* (`process 5` today) takes the commit and push consent gate with it, exactly as dropping the whole `process` pack does. To keep the rule but ask for every commit and push, not only those onto the main branch, keep it on and build with `--strict-consent` instead (the *Strict consent* switch on the Constitution page). The console and the wizard both warn you before applying it. A pack whose every rule is excluded drops out of the build entirely. See [Exclusions](../concepts/exclusions.md) for excluding whole folders instead.
52
52
 
53
53
  ---
54
54
 
@@ -41,7 +41,7 @@ You have three ways to change a choice:
41
41
 
42
42
  - **Re-run the wizard** with `geneseed setup`. It pre-selects what the install already has, so holding Enter cannot widen a set you narrowed on purpose. The wizard does not ask about single rules, but it keeps any rule exclusions already in place.
43
43
  - **Use the web console** (`geneseed web`). the **Installs** page changes theme, footprint and the rest per install. **Constitution** toggles packs and rules.
44
- - **Run the build yourself.** Watch out: a flag you leave out takes the *generator's* default, not your install's current value. `geneseed status --json` prints, for every install, the exact `geneseed build` command that rebuilds it as it is. Start from that command and change the one flag you want.
44
+ - **Run the build yourself.** Watch out: a flag you leave out takes the *generator's* default, not your install's current value. So a build over an existing install that would change a setting you did not pass refuses, names each change, and prints the command that keeps them. `geneseed status --json` prints, for every install, the exact `geneseed build` command that rebuilds it as it is. Start from that command and change the one flag you want. `--reset` returns the settings you left out to their defaults, for that one build.
45
45
 
46
46
  ---
47
47
 
@@ -11,12 +11,12 @@ description: "Remove an install, and what stays behind."
11
11
  ## Remove an install
12
12
 
13
13
  ```
14
- geneseed uninstall # the project install in this folder, else the OpenCode global one
14
+ geneseed uninstall # the project install in this folder, else the one global install
15
15
  geneseed uninstall --target /path/to/repo # a project install
16
16
  geneseed uninstall --target ~/.claude # a global install: pass its config directory
17
17
  ```
18
18
 
19
- Without `--target`, the command picks the project install in the current folder if there is one, and the OpenCode global install otherwise. It prints what it will remove and asks before going on. Pass `--yes` to skip the question. In a shell without an interactive terminal, `--yes` is required: without it, the command refuses and exits 1.
19
+ Without `--target`, the command picks the project install in the current folder if there is one, and the one global install on the machine otherwise, whatever its host. With several global installs it refuses (exit code 2) and prints the `--target` command for each. It prints what it will remove and asks before going on. Pass `--yes` to skip the question. In a shell without an interactive terminal, `--yes` is required: without it, the command refuses and exits 1.
20
20
 
21
21
  To see where each install lives, run `geneseed status`. The web console's **Installs** page can also uninstall.
22
22
 
@@ -24,7 +24,7 @@ To see where each install lives, run `geneseed status`. The web console's **Inst
24
24
 
25
25
  Each install keeps a manifest, a list of the files Geneseed wrote. **Uninstall deletes exactly those files and nothing else**, then removes any folders they leave empty. A file of yours that sits in the same folder stays.
26
26
 
27
- - **OpenCode global:** `AGENT.md`, `agents/`, `skills/`, `plugins/`, the marker files, and the `instructions` entry in `opencode.json`.
27
+ - **OpenCode global:** `AGENT.md`, Geneseed's managed block in `AGENTS.md`, `agents/`, `skills/`, `plugins/`, the marker files, and the `instructions` entry in `opencode.json`.
28
28
  - **OpenCode per repo:** `AGENT.md`, `.opencode/`, `laws/`, `agents/`, `skills/`, and the `instructions` entry in `opencode.json`.
29
29
  - **Claude Code, Bob, OpenClaude:** `agents/`, `skills/`, the marker files, Geneseed's managed block in the instructions file (`CLAUDE.md` or `AGENTS.md`), and Geneseed's own hooks and exclusions in `settings.json`. Your own settings keys and hooks stay.
30
30
 
@@ -88,7 +88,7 @@ geneseed diff --full # with line-level diffs
88
88
  geneseed diff --out improvements.md # write the improvements file
89
89
  ```
90
90
 
91
- `diff` compares the global OpenCode install by default. Pass `--target <config dir>` to compare another install. A file you replaced with a link to your own copy (a skill folder junctioned or symlinked elsewhere, say) is listed as `linked`: Geneseed never writes through a link, so it is yours and not drift, and it stays out of the improvements file. A file unmodified since its build that differs only because the source moved on is listed as behind source; a rebuild updates it, and it stays out of the improvements file too. `diff` also lists every non-empty self-improvement note, the tier's included, and `--out` copies them into the improvements file; the upgrade export does not fire on notes alone, since a rebuild cannot lose them. The improvements file is self-contained. To make the changes permanent, hand it to an agent in a Geneseed clone and ask it to fold them back into `src/`. Then they survive every future build. The web console's **Changes** page exports the same file.
91
+ `diff` compares the global install there is by default, whatever its host (with several, the first, which it names on stderr). Pass `--target <config dir>` to compare another install. A file you replaced with a link to your own copy (a skill folder junctioned or symlinked elsewhere, say) is listed as `linked`: Geneseed never writes through a link, so it is yours and not drift, and it stays out of the improvements file. A file unmodified since its build that differs only because the source moved on is listed as behind source; a rebuild updates it, and it stays out of the improvements file too. `diff` also lists every non-empty self-improvement note, the tier's included, and `--out` copies them into the improvements file; the upgrade export does not fire on notes alone, since a rebuild cannot lose them. The improvements file is self-contained. To make the changes permanent, hand it to an agent in a Geneseed clone and ask it to fold them back into `src/`. Then they survive every future build. The **Local edits** tab of the web console's **Installs** page exports the same file.
92
92
 
93
93
  ## Moving from a clone to npm
94
94
 
@@ -52,6 +52,18 @@ Start a session with `GENESEED_DEBUG=1` set. The context plugin then logs what i
52
52
  At session start, the context hook adds the repo's docs to the conversation. Ask the agent what project context it received. It should name your `README.md` and list your `docs/`.
53
53
  <!--/harness-->
54
54
 
55
+ ## Bob, by hand
56
+
57
+ No automated check runs IBM Bob: it is not published on npm, so the host canary cannot install it ([What is verified](../concepts/host-matrix.md#what-is-verified)). `geneseed doctor --probe` runs Bob's installed gate through Bob's shell, which proves the gate. Only Bob can prove that Bob calls it. Five steps, in a scratch repository:
58
+
59
+ 1. **The hooks are loaded.** Type `/hooks` in Bob Shell. For a global install it lists four groups from `~/.bob/settings/settings.json`: `SessionStart`, `PreToolUse`, `Stop` and `UserPromptSubmit`. If Geneseed's are missing, Bob is reading another file.
60
+ 2. **A credential write is refused.** Ask Bob to write a file holding an AWS access key id (the example one from the AWS documentation will do). The write does not happen, and Bob shows the gate's reason, which says that no confirmation in the chat lifts it.
61
+ 3. **A destructive git command is refused.** Ask Bob to run `git reflog expire --expire=now --all`. It is refused the same way.
62
+ 4. **A commit warns.** Ask Bob to commit a change. The commit goes through, and Bob's hook log has a Geneseed line about consent: Bob cannot ask, so this rule is a warning there.
63
+ 5. **Record what Bob sends.** Start Bob with `GENESEED_HOOK_TAP` set to an absolute directory outside any repository, for example `GENESEED_HOOK_TAP=$HOME/geneseed-tap`. Then start a session, send a prompt, let Bob run one command and edit one file, and let the turn end. Each hook call writes one file, `bob-<event>-<n>.json`.
64
+
65
+ A tap file holds the payload's shape and not its content. Every key is kept; every string is replaced by its type and length, except the event name and the tool name. Your prompt, file contents, commands and paths are not in it. Read the files before you send them all the same, then attach them to an issue at <https://github.com/Arylmera/Geneseed/issues>, with your Bob version. One file per event is enough. Unset the variable afterwards: nothing is written without it, and Geneseed never puts it in a settings file. The tap works the same way on Claude Code and OpenClaude.
66
+
55
67
  ## Dry-run a build before you write it
56
68
 
57
69
  `geneseed validate` takes the same flags as `geneseed build`. It renders into a throwaway sandbox and runs every doctor check against the result. Nothing is written under the real `--out` or `--root`: no marker files, no settings merge, no registry record.
@@ -46,4 +46,4 @@ It cannot ride Geneseed's install. Geneseed's plugins are single dependency-free
46
46
 
47
47
  ## Consent
48
48
 
49
- `worktree_delete` **commits before it removes the worktree.** The harness's *Consent Before Push* rule (when the `process` pack is built in) asks before a *shell* `git commit` through `opencode.json` permissions. This plugin commits through its own tool, so that gate never sees the commit. Before you call delete, review what it will commit, or keep the worktree and commit yourself.
49
+ `worktree_delete` **commits before it removes the worktree.** The harness's *Consent Before Push* rule (when the `process` pack is built in) asks before a *shell* `git commit` through `opencode.json` permissions (OpenCode asks for every commit: its globs cannot see the branch). This plugin commits through its own tool, so that gate never sees the commit. Before you call delete, review what it will commit, or keep the worktree and commit yourself.
@@ -20,6 +20,9 @@ Where Geneseed writes an install, and what an upgrade re-renders.
20
20
  | --- | --- | --- |
21
21
  | `GENESEED_HOME` | build / hooks | Directory holding the hook shim `bin/geneseed-hook` (default `~/.geneseed`). Change it, then rebuild, so the emitted hooks point at the new location. |
22
22
  | `GENESEED_ACTIVITY` | hooks, OpenCode plugin | `off` (or `0`, `false`, `no`) stops the activity writer; the hooks then load none of its code. Absent means on. See [geneseed-activity](plugin-activity.md). |
23
+ | `GENESEED_NO_USAGE` | hooks, OpenCode guard plugin, web console | Any value stops the usage counter: no skill or subagent call is appended to `notebook/usage.jsonl`, and the console reports the counter as off. |
24
+ | `GENESEED_LLM_TIMEOUT` | `learn` hook | Seconds the `learn` hook waits for the model CLI before it stops it and drops the partial reply (default 120; anything but a positive number means the default). |
25
+ | `GENESEED_HOOK_TAP` | hooks | An absolute directory outside any repository. Every hook call then writes one file there, `<host>-<event>-<n>.json`, holding the payload's shape: keys kept, every string replaced by its type and length. For recording what a host really sends; unset, nothing is written. A directory inside a git worktree is refused. See [Verify it works](../guides/verify.md#bob-by-hand). |
23
26
  | `GENESEED_NO_SHIM_CHECK` | CLI | `1` silences the warning every `geneseed` command prints when the hook shim points at a path that no longer exists. For scripted callers; the `status` gates row still says `DEAD`. |
24
27
  | `OPENCODE_CONFIG_DIR` | OpenCode emits, `diff`, plugins | OpenCode's config dir — where the global install is written. OpenCode still loads `$XDG_CONFIG_HOME/opencode` beside it, so `status` and `doctor` warn when both hold a Geneseed install. |
25
28
  | `XDG_CONFIG_HOME` | every emit, hooks, plugins, web console | The base of the [shared tier](../concepts/shared-tier.md), `$XDG_CONFIG_HOME/geneseed` (default `~/.config/geneseed`), on every host. Also used when `OPENCODE_CONFIG_DIR` is unset: the install goes to `$XDG_CONFIG_HOME/opencode` (default `~/.config/opencode`). |
@@ -35,7 +38,7 @@ Where Geneseed writes an install, and what an upgrade re-renders.
35
38
 
36
39
  ## OpenCode plugin variables
37
40
 
38
- Each OpenCode plugin's page lists its own switches: [guard](plugin-guard.md) (`GENESEED_GUARD`), [notify](plugin-notify.md) (`GENESEED_NOTIFY`, `GENESEED_NOTIFY_MIN_SECONDS`, `GENESEED_NOTIFY_TITLE`), [ponytail](plugin-ponytail.md) (`GENESEED_PONYTAIL`), [workflow](plugin-workflow.md) (`GENESEED_WORKFLOWS_DIR`) and [activity](plugin-activity.md) (`GENESEED_ACTIVITY`). `GENESEED_DEBUG=1` makes every plugin but guard and learn (which always log) say what it decided on stderr. `OPENCODE_DISABLE_LSP_DOWNLOAD` belongs to OpenCode itself: see [Language servers](../concepts/lsp.md).
41
+ Each OpenCode plugin's page lists its own switches: [guard](plugin-guard.md) (`GENESEED_GUARD`), [notify](plugin-notify.md) (`GENESEED_NOTIFY`, `GENESEED_NOTIFY_MIN_SECONDS`, `GENESEED_NOTIFY_TITLE`), [ponytail](plugin-ponytail.md) (`GENESEED_PONYTAIL`), [workflow](plugin-workflow.md) (`GENESEED_WORKFLOWS_DIR`) and [activity](plugin-activity.md) (`GENESEED_ACTIVITY`). `GENESEED_DEBUG=1` makes every plugin but guard and learn (which always log) say what it decided. Context, notify, ponytail and activity write to stderr; guard, learn and workflow write to OpenCode's own log on OpenCode 1 (service `geneseed-<name>`) and to stderr on OpenCode 2. `OPENCODE_DISABLE_LSP_DOWNLOAD` belongs to OpenCode itself: see [Language servers](../concepts/lsp.md).
39
42
 
40
43
  ## Web console and CLI
41
44
 
@@ -43,7 +46,7 @@ How the `geneseed` command behaves and prints.
43
46
 
44
47
  | Variable | Read by | Effect |
45
48
  | --- | --- | --- |
46
- | `GENESEED_NO_WEB` | `geneseed` (bare) | `1` stops bare `geneseed` opening the web console; it falls back to the terminal menu. |
49
+ | `GENESEED_NO_WEB` | `geneseed` (bare) | Any value stops bare `geneseed` opening the web console; it prints the command list instead. |
47
50
  | `GENESEED_NODE` | `./geneseed`, `geneseed.cmd`, `install` scripts | Node interpreter to run (default `node` on PATH). |
48
51
  | `GENESEED_TUI_ASCII` | CLI output | Pure-ASCII output: no box-drawing or emoji. |
49
52
  | `GENESEED_TUI_PLAIN` | CLI output | Drop emoji and animation. |
@@ -12,7 +12,7 @@ One of the [OpenCode plugins](opencode-plugins.md). [Environment variables](envi
12
12
 
13
13
  **When it runs.** On session events. A sub-agent's child session (one with a `parentID`) is folded into its root session: it becomes an `agents[]` row (`{id, type, status: "running" | "done"}`, the child's id and agent), and its files join the root's `files` with `by` set to the child's id. Only learn's throwaway `geneseed-*` sessions are skipped. On OpenCode 2 the files come from `session.step.ended`, which carries no line counts, so those read `null`. A session whose process died, went stale (30 minutes untouched) or ended leaves the live list and is listed as ended; the reader never deletes a file.
14
14
 
15
- **Claude Code, OpenClaude and Bob.** Their hooks write the same files into `activity/` beside the install (`~/.claude/activity/`, `<repo>/.claude/activity/`, `~/.bob/activity/`). No hook is added per tool call: the writer runs after the hooks that already run — the gates, `context` and `learn` — plus `geneseed-hook activity` on `UserPromptSubmit` and, on Claude Code and OpenClaude, `SessionEnd` (their `SubagentStart` runs `context`, which records the same way). So a Claude session's phase moves on the gated tools (`Bash`, `PowerShell`, `Write`, `Edit`, `NotebookEdit`, `Skill`, `Agent`, `Task`), and the rest of the turn — every tool call, the model, the token totals, the last reply — arrives at `Stop`, read from the transcript where the previous `Stop` left off (at most 2 MB per turn). Bob sends no transcript, so a Bob session shows only the calls its `tool-gate` sees, and leaves the live list by staleness alone (Bob has no `SessionEnd`). Bob's `SessionStart` is recorded only after a compaction (`source: "compact"`, counted as one): a startup or resume fires just before the first prompt, which records the session anyway. Bob 2.2.3 writes every hook's payload to stdin and closes it, so reading it there is safe. These writers have no resident process, so their snapshots carry `pid: null` and stay live by staleness alone. Recorded: tool names, each changed file's path relative to the session's git root (a file outside the root, or a session outside any repo, keeps its basename only; a path is never stored absolute; labels show basenames), who changed it (the session or a subagent's `agent_id`), the subagents, the prompt count, the context size and the compactions, line counts, todo text, and 240-character snippets of the prompt and the last reply — never a shell command, a file's content or an edit's text — and any credential the secrets gate would catch in a snippet is written as `[redacted]`. A project install's `activity/` gets its own `.gitignore` (`*`), and the writer never writes through, or sweeps, an `activity/` or `activity/archive/` that is a link. Nothing is recorded in a repo listed in `excludes.json`, or inside a model CLI that `learn` started.
15
+ **Claude Code, OpenClaude and Bob.** Their hooks write the same files into `activity/` beside the install (`~/.claude/activity/`, `<repo>/.claude/activity/`, `~/.bob/activity/`). No hook is added per tool call: the writer runs after the hooks that already run — the gates, `context` and `learn` — plus `geneseed-hook activity` on `UserPromptSubmit` and, on Claude Code and OpenClaude, `SessionEnd` (their `SubagentStart` runs `context`, which records the same way). So a Claude session's phase moves on the gated tools (`Bash`, `PowerShell`, `Monitor`, `Write`, `Edit`, `NotebookEdit`, `Skill`, `Agent`, `Task`), and the rest of the turn — every tool call, the model, the token totals, the last reply — arrives at `Stop`, read from the transcript where the previous `Stop` left off (at most 2 MB per turn). Bob sends no transcript, so a Bob session shows only the calls its `tool-gate` sees, and leaves the live list by staleness alone (Bob has no `SessionEnd`). Bob's `SessionStart` is recorded only after a compaction (`source: "compact"`, counted as one): a startup or resume fires just before the first prompt, which records the session anyway. Bob 2.2.3 writes every hook's payload to stdin and closes it, so reading it there is safe. These writers have no resident process, so their snapshots carry `pid: null` and stay live by staleness alone. Recorded: tool names, each changed file's path relative to the session's git root (a file outside the root, or a session outside any repo, keeps its basename only; a path is never stored absolute; labels show basenames), who changed it (the session or a subagent's `agent_id`), the subagents, the prompt count, the context size and the compactions, line counts, todo text, and 240-character snippets of the prompt and the last reply — never a shell command, a file's content or an edit's text — and any credential the secrets gate would catch in a snippet is written as `[redacted]`. A project install's `activity/` gets its own `.gitignore` (`*`), and the writer never writes through, or sweeps, an `activity/` or `activity/archive/` that is a link. Nothing is recorded in a repo listed in `excludes.json`, or inside a model CLI that `learn` started.
16
16
 
17
17
  **Archive.** On `SessionStart` and `SessionEnd` the hook writer moves every snapshot that is no longer live into `activity/archive/`, keeping the newest 50 and none older than 7 days. `/api/activity` returns them, with the stale and dead ones still in `activity/`, in its `ended` list — capped there by the same rule, since the OpenCode plugin never sweeps.
18
18
 
@@ -48,7 +48,7 @@ There is no DYNAMIC loop/* exemption on OpenCode — OpenCode 1 declares a `perm
48
48
 
49
49
  [What a prompt says](../concepts/hooks.md#what-a-prompt-says) lists what this text can and cannot tell you.
50
50
 
51
- The guard's reasons are the same words as the hooks'. The reason never names the switches below: the agent reads it, and a switch named there reads as leave to get round the block. The *Persist Insight* reason tells the agent to ask you and that a re-issue changes nothing — never to write the file another way (through a shell command, say). Warnings go to stderr.
51
+ The guard's reasons are the same words as the hooks'. The reason never names the switches below: the agent reads it, and a switch named there reads as leave to get round the block. The *Persist Insight* reason tells the agent to ask you and that a re-issue changes nothing — never to write the file another way (through a shell command, say). Warnings go to OpenCode's own log on OpenCode 1 (service `geneseed-guard`) and to stderr on OpenCode 2.
52
52
 
53
53
  **Switches.**
54
54
  - `GENESEED_GUARD=warn` — log every block, allow the call.
@@ -12,7 +12,7 @@ One of the [OpenCode plugins](opencode-plugins.md). Its switches are also listed
12
12
 
13
13
  **When it runs.** After the session goes quiet. OpenCode signals "idle" after every turn, so each idle re-arms a timer and the distil runs once nothing has happened for `GENESEED_LEARN_DEBOUNCE_MS` (default 60 s). Trivial sessions are skipped.
14
14
 
15
- **What you see.** On stderr: `[geneseed-learn] wrote N memory file(s): …` (or `updated` / `archived`), or `skipped: <reason>`. Total silence means it did not load.
15
+ **What you see.** `wrote N memory file(s): …` (or `updated` / `archived`), or `skipped: <reason>`: in OpenCode's own log on OpenCode 1 (service `geneseed-learn`), on stderr as `[geneseed-learn] …` on OpenCode 2. Total silence in that place means it did not load.
16
16
 
17
17
  **Where it writes** — the first that resolves:
18
18
  1. `GENESEED_MEMORY` — an explicit memory dir;
@@ -20,6 +20,6 @@ One of the [OpenCode plugins](opencode-plugins.md). [Environment variables](envi
20
20
 
21
21
  **Switches.**
22
22
  - `GENESEED_WORKFLOWS_DIR` — load scripts from another directory.
23
- - `GENESEED_DEBUG=1` — log to stderr.
23
+ - `GENESEED_DEBUG=1` — log to OpenCode's own log on OpenCode 1 (service `geneseed-workflow`), to stderr on OpenCode 2.
24
24
 
25
25
  Ask the agent to *"list available workflows"* to check it loaded.
@@ -31,7 +31,7 @@ geneseed build
31
31
  git add Harness
32
32
  ```
33
33
 
34
- If the drift is your own edits, export them first — `geneseed diff` (or the console's **Changes** page) writes them up so they can be folded back into `src/`.
34
+ If the drift is your own edits, export them first — `geneseed diff --out` (or the **Local edits** tab of the console's **Installs** page) writes them up so they can be folded back into `src/`.
35
35
 
36
36
  **Confirm.** `geneseed doctor` no longer reports the bundle.
37
37
 
@@ -44,7 +44,7 @@ settings spell it, through the host's own shell, on `git reflog expire --expire=
44
44
  and `git status` (which must go through). A gate wired with `--no-deletion-gate` lets the first one
45
45
  through by design, so it is probed on `find / -name geneseed-probe` instead — a root-wide scan it
46
46
  must still refuse. `--no-secrets-gate`, `--no-done-gate`, `--no-ownership-gate`, `--no-external-gate` and
47
- `--no-test-note` change nothing here: none judges either probe command. An OpenCode install's guard plugin has no command to
47
+ `--no-test-note` change nothing here: none judges either probe command. A Bob gate is asked twice more, in Bob's own shapes: the same two commands in its older `{event, tool, input}` payload, and a `write_file` carrying a made-up credential, which it must refuse. A problem line from one of those ends with the shape in brackets, and a gate wired `--no-secrets-gate` is not asked the last one. An OpenCode install's guard plugin has no command to
48
48
  run: the probe imports it and calls its hook through both plugin APIs (V1 and V2), with `rm -rf /`
49
49
  as the call it must refuse. `GENESEED_GUARD=off` or `warn` in your terminal makes that a note,
50
50
  not a failure.
@@ -37,7 +37,7 @@ If you moved the shim itself with `GENESEED_HOME`, set it the same way before re
37
37
 
38
38
  ## A Bash/Write/Edit call is refused with `onFailure is "block"`
39
39
 
40
- Claude Code refuses a `Bash`, `PowerShell`, `Write`, `Edit` or `NotebookEdit` call outright, and the transcript carries wording like:
40
+ Claude Code refuses a `Bash`, `PowerShell`, `Monitor`, `Write`, `Edit` or `NotebookEdit` call outright, and the transcript carries wording like:
41
41
 
42
42
  > `PreToolUse:Bash hook error: [...]: failed; blocking because onFailure is "block"`
43
43
 
@@ -127,7 +127,7 @@ export GENESEED_MEMORY=/abs/path/to/memory
127
127
 
128
128
  This variable and `GENESEED_HARNESS` win over the shared store, so leave them unset on a global install. Both are deprecated, with removal planned for 6.0.
129
129
 
130
- **Confirm.** About a minute after the session goes quiet, stderr shows `[geneseed-learn] wrote N memory file(s): …` or a `skipped:` reason. Total silence means the plugin did not load.
130
+ **Confirm.** About a minute after the session goes quiet, OpenCode's own log (OpenCode 1, service `geneseed-learn`) or stderr (OpenCode 2, as `[geneseed-learn] …`) shows `wrote N memory file(s): …` or a `skipped:` reason. Total silence in that place means the plugin did not load.
131
131
  <!--/harness-->
132
132
 
133
133
  Model, read-only agent, document and MCP problems are on [their own page](troubleshoot-tools.md).
@@ -32,7 +32,7 @@ Run without the installer — `npx geneseed`, a global npm install, or a hook
32
32
 
33
33
  > `geneseed needs Node 22.7 or newer; this is Node 20.18.1. Install a current Node from https://nodejs.org (or your package manager), then run the command again.`
34
34
 
35
- **Cause.** The `node` on PATH is older than 22.7. npm only *warns* about the engine requirement, so a global install succeeds anyway. A hook prints the same sentence and lets the tool call through rather than block it, so on Claude Code, Bob or OpenClaude the hooks are off until Node is upgraded.
35
+ **Cause.** The `node` on PATH is older than 22.7. npm only *warns* about the engine requirement, so a global install succeeds anyway. A hook prints the same sentence on stderr and judges nothing: on Claude Code and OpenClaude each gated tool call then asks you, since no gate checked it, and on Bob the call passes. The other hooks (context, learn, activity) do nothing until Node is upgraded.
36
36
 
37
37
  **Fix.** Install the current Node.js LTS (see above), open a **new** terminal, and run the command again.
38
38
 
@@ -59,7 +59,7 @@ See [Install](../guides/install.md) for the emit target that matches your tool.
59
59
 
60
60
  Setup opens with `AI coding tools on this machine:` and an `ok` or `--` per tool.
61
61
 
62
- **Cause.** The check only asks whether the command (`opencode`, `claude`, `bob`, `openclaude`) is on your PATH. A desktop-only install with no command shows as missing; an unrelated program with the same name shows as present.
62
+ **Cause.** The check looks for the command (`opencode`, `claude`, `bob`, `openclaude`) on your PATH, then in the usual per-user folders, where a hit shows as `ok … (<where>, not on PATH)`. When it finds none of the four, it asks "Installed somewhere else?" and takes a path. An install in a folder it does not search shows as missing; an unrelated program with the same name shows as present.
63
63
 
64
64
  **Fix.** Nothing to fix — the line is advisory. Pick the install mode for the tool you actually use; a missing tool among several present is just a line, and you can continue without one.
65
65
 
@@ -85,7 +85,7 @@ reports `version "21` or higher.
85
85
 
86
86
  ## `geneseed: command not found`
87
87
 
88
- **Cause.** The `geneseed` launcher is not on your PATH. A git clone is not put there automatically (an `npm install -g geneseed` install is).
88
+ **Cause.** The `geneseed` launcher is not on your PATH. The clone's installer (`./install`, `install.cmd`) runs `link` for you, but a clone set up with `geneseed setup` alone is not linked, and a terminal opened before `link` ran does not see the change (an `npm install -g geneseed` install is put on PATH by npm).
89
89
 
90
90
  **Fix.** From the cloned folder:
91
91
 
@@ -22,7 +22,7 @@ export GENESEED_MODEL=provider/model
22
22
 
23
23
  ## A read-only agent won't run a command
24
24
 
25
- **Cause.** By design: read-only agents are denied the shell. The few that must run read-only commands (the reviewer, security) are allowed it in their own spec.
25
+ **Cause.** By design: read-only agents are denied the shell. Those that must run read-only commands (the reviewer, security and explorer, for example) are allowed it in their own spec.
26
26
 
27
27
  **Fix.** Hand the task to an agent that can run commands, or run it yourself. See [Agents](../concepts/agents.md).
28
28
 
@@ -8,8 +8,9 @@ chars/4 estimates and shift a little with theme and version.
8
8
  the default doctrine packs, 47 skills (plus 12 alias stubs) and 18 agents, and nothing
9
9
  re-measures this page automatically. For a
10
10
  live figure on your own install, ask the agent for the `token-report` skill —
11
- that is what it is for. A `--footprint full` build runs roughly 5k tokens
12
- heavier on the root file.
11
+ that is what it is for. A `--footprint full` build ran about 7k tokens heavier
12
+ when the whole request was captured on 2026-11-12 (see
13
+ [Why there is no chat mode](#why-there-is-no-chat-mode)).
13
14
 
14
15
  ## Always-on cost per session
15
16
 
@@ -93,14 +94,77 @@ until 2026-09 it did, and the whole harness was paid twice per session.
93
94
  - **User-only skills leave the catalogue.** A skill whose source carries
94
95
  `<!-- invocation: user -->` renders `disable-model-invocation: true`; Claude
95
96
  Code and Bob then drop its description from the always-on skill metadata and
96
- only `/name` opens it. The two teaching skills (`teach`, `learn-mode`)
97
+ only `/name` opens it. Three skills (`teach`, `learn-mode`, `adhd`)
97
98
  carry it today.
98
99
  - **Aliases cost 0 always-on.** A merged skill's old names (`<!-- aliases: -->`)
99
100
  ship as user-only stubs on Claude Code, Bob and OpenClaude, and as `/name` commands
100
101
  on OpenCode — never in the model's catalogue, so a rename or merge is free.
101
- - Plugin JavaScript (OpenCode, ~26k on disk) runs in the host runtime and
102
+ - Plugin JavaScript (OpenCode, about 380 KB on disk) runs in the host runtime and
102
103
  never enters the context window.
103
104
 
105
+ ## Why there is no chat mode
106
+
107
+ A "chat mode" would switch the harness off for a quick question, so a "hey, how are you?"
108
+ does not load the rules. It was measured on 2026-11-12 and turned down: the harness stays
109
+ loaded in every session.
110
+
111
+ **What was measured.** Each host was installed from npm and pointed at a local endpoint that
112
+ captured the request it sent for one short prompt, in an empty folder, with and without a
113
+ default global install. Sizes are characters of the request; tokens are chars/4.
114
+
115
+ | Host | No harness | Lean (default) | Full | Harness share, lean | Harness share, full |
116
+ |---|---|---|---|---|---|
117
+ | Claude Code 2.1.322 | 45,964 | 89,935 | 118,486 | ~11k tokens | ~18k tokens |
118
+ | OpenClaude 0.32.0 | 86,122 | 128,457 | 157,003 | ~11k tokens | ~18k tokens |
119
+ | OpenCode 1.19.5 | 30,435 | 86,811 | 115,599 | ~14k tokens | ~21k tokens |
120
+ | OpenCode 2.2.7 | 22,654 | 70,506 | 99,054 | ~12k tokens | ~19k tokens |
121
+
122
+ Bob was not measured: IBM does not publish Bob Shell on npm.
123
+
124
+ **Why the saving is small.** The harness share is 5–10% of a 200k window. The host re-sends
125
+ it with every message, but where the provider caches prompts it is billed at the full input
126
+ price once per session and at the cached rate after that. A chat mode would save that one
127
+ payment on sessions that stay small talk, and nothing else.
128
+
129
+ **Why it cannot be a command inside the chat.** The harness is in the context before the
130
+ first message, and no host can take text back out of a running conversation. A slash command
131
+ can only tell the model to ignore the rules, which saves no tokens. Switching on a resumed
132
+ conversation was measured too (harness on, resumed without it, resumed with it again):
133
+
134
+ | Host | Resumed without the harness | Resumed with it again |
135
+ |---|---|---|
136
+ | OpenClaude | sheds it (86,390) | back to normal (128,963) |
137
+ | OpenCode 1 | sheds it (30,606) | back to normal (87,250) |
138
+ | Claude Code | keeps it in the history (91,213) | loads it a second time (126,697) |
139
+ | OpenCode 2 | keeps it in the system prompt (68,273) | loads it a second time (118,720) |
140
+
141
+ On Claude Code and OpenCode 2 a toggle therefore costs more than it saves. A plain resume,
142
+ with the same configuration, adds only the new message on all four hosts.
143
+
144
+ **Why not a ready-made excluded folder.** An [excluded folder](concepts/exclusions.md) is for a
145
+ repo that brings its own setup, not for saving tokens. On Claude Code and OpenClaude it
146
+ removes the instructions file but leaves the skill and agent listings (about 3k tokens). On
147
+ OpenCode the request was byte-identical with and without the exclusion.
148
+
149
+ **If you want a session without the harness anyway**, each host has its own launch switch.
150
+ These are the hosts' options, not Geneseed's: they were checked on the versions above, in
151
+ non-interactive mode with an API key, and a host update can change them.
152
+
153
+ | Host | Launch line | Measured |
154
+ |---|---|---|
155
+ | Claude Code | `claude --setting-sources project,local` | 45,963 — the no-harness size |
156
+ | OpenClaude | `openclaude --setting-sources project,local` | 86,124 — the no-harness size |
157
+ | OpenCode 1 | `XDG_CONFIG_HOME=<empty dir> opencode` | 30,435 — the no-harness size |
158
+ | OpenCode 2 | `OPENCODE_CONFIG_DIR=<empty dir> opencode --standalone` | 22,654 — the no-harness size |
159
+
160
+ Such a session has no rules and no gates, and on Claude Code and OpenCode 2 they cannot be
161
+ added back to the same conversation cleanly. `XDG_CONFIG_HOME` is inherited by every program
162
+ the session starts, so git and other tools lose their own configuration too. On OpenCode 1,
163
+ `OPENCODE_CONFIG_DIR` changes nothing. Whether a subscription login survives
164
+ `--setting-sources` on Claude Code was not checked.
165
+
166
+ The decision is recorded in [Considered and refused](design-history.md#considered-and-refused).
167
+
104
168
  ## Why your session may show more
105
169
 
106
170
  The always-on figures above are the *harness's* share. A real session's
@@ -17,5 +17,5 @@ How Geneseed treats each host it installs into. Part of [Why Geneseed works this
17
17
  - **OpenCode gets a one-line managed `AGENTS.md` when that file is missing.** OpenCode falls back to `~/.claude/CLAUDE.md` when `AGENTS.md` is absent, which would load the harness twice beside a Claude install. An existing `AGENTS.md` is left alone. See [Install for OpenCode](../guides/install-opencode.md).
18
18
  - **Per-repo hooks go into the untracked `settings.local.json`.** The hook commands hold paths on your machine, and the team-shared `settings.json` would hand every teammate broken hooks. See [Hook gates](../concepts/hook-gates.md).
19
19
  - **The manifest records which settings file holds the hooks.** Uninstall and the gate stand-down read the manifest's `settings_file` back (`settingsFile` in `js/hosts/hosts.mjs`) rather than assume a path, since the file differs by host and scope (Bob's global one is nested). See [Hook gates](../concepts/hook-gates.md).
20
- - **Copilot was removed in one pass.** It was never verified live, its hook output never reached the model, and it shared no surface with the other hosts. See [ADR 0008](../adr/0008-host-parity-ceiling-of-the-weakest-host.md) and [Candidate hosts](../candidate-hosts.md).
20
+ - **Copilot was removed in one pass.** Nobody had ever run it against a real Copilot, its hook output never reached the model, and it shared no surface with the other hosts. See [ADR 0008](../adr/0008-host-parity-ceiling-of-the-weakest-host.md) and [Candidate hosts](../candidate-hosts.md).
21
21
  - **What belongs to the host stays with the host.** Compaction, sandboxing and the plugin runtime are each host's own territory; Geneseed configures them where a host allows and builds no replacement. See [Hosts](../concepts/hosts.md).
@@ -19,3 +19,4 @@ How the generated harness is assembled, ranked and sized. Part of [Why Geneseed
19
19
  - **Marker lines (`Excluded rules:`, `Excluded skills:`) are written only when non-empty.** A default build then stays byte-identical to one from before the option existed. See [DESIGN.md](../../DESIGN.md) and [Exclusions](../concepts/exclusions.md).
20
20
  - **Session files are injected at start unless still identical to their seed, and the root file is never injected a second time.** The host already loads the root file itself; injecting it again paid for the whole harness twice per session. See [Token footprint](../token-footprint.md).
21
21
  - **The context hook keeps its whole output under `OUTPUT_BUDGET`, counting each line's Windows line ending.** Claude Code moves a longer hook output to a file and shows the model a short preview, so everything past the cut is lost without a warning. Splitting the hook into two commands was measured and turned down (see [Considered and refused](../design-history.md#considered-and-refused)). See [Token footprint](../token-footprint.md).
22
+ - **The harness loads in every session; there is no chat mode.** It adds about 11–14k tokens at lean, billed in full once per session where the provider caches prompts, and no host can unload it inside a conversation. A mode that switches it off was measured and turned down (see [Considered and refused](../design-history.md#considered-and-refused)). See [Token footprint](../token-footprint.md#why-there-is-no-chat-mode).
@@ -29,11 +29,11 @@ On Claude Code and OpenClaude the hooks never block silently. They make the host
29
29
  - **Your rules and memory**: any write by the agent to `user-rules.md` or to the memory store. Whether something is a standing rule or a fact to remember is your call.
30
30
  - **The first write in an application with no ownership setup**: in a repo with a build manifest whose root `AGENTS.md` has no `## Ownership` section, the session's first write is refused once, as a reminder rather than a gate, with the reason sent to the agent rather than to you: it then asks you to set [ownership](../concepts/ownership.md) up now, skip this session, or skip in this repo until you ask. Off per repo with `mode: off`, for you alone in one repo with `Setup: declined <YYYY-MM-DD>` in `.geneseed/ownership.md`, per install with `--no-ownership-gate`.
31
31
  - **The checks you are judged by, and the gates' own switches**: a write to a file listed in `.geneseed/protected-checks.txt`, to the done gate's list, or to a file that can switch a gate off (the hook settings, `excludes.json`, a gate marker in `AGENT.md`, the hook shim). You get a prompt. A shell write counts too, for the common forms: `>`, `>>`, `tee`, `sed -i`, `cp`, `mv`, `rm`. A script or an interpreter's inline code is not seen, so run the checks in CI as well.
32
- - **Ending a turn without the proof**: only in a project whose `.geneseed/done-checks.txt` lists at least one check; a file that lists none turns the gate off for that project. A turn that edited files cannot end until every listed check has passed since the last edit. The agent is stopped once, then the turn may end. Without that file, Geneseed infers the checks from the project's manifest (`package.json` scripts, Maven, Gradle, `pyproject.toml`, `Cargo.toml`, `go.mod`): you get a warning when a turn ends without them, but the turn is not stopped.
32
+ - **Ending a turn without the proof**: only in a project whose `.geneseed/done-checks.txt` lists at least one check; a file that lists none turns the gate off for that project. A turn that edited files cannot end until every listed check has passed since the last edit. The agent is stopped again only after a new edit or a changed background result, at most 3 times between two task notifications and 10 times in the whole turn, then the turn may end. A sub-agent is held to the same proof when it stops. Without that file, Geneseed infers the checks from the project's manifest (`package.json` scripts, Maven, Gradle, `pyproject.toml`, `Cargo.toml`, `go.mod`): you get a warning when a turn ends without them, but the turn is not stopped.
33
33
 
34
34
  If a gate crashes, it asks instead of letting the call through. If it cannot start at all (a deleted or broken shim) or times out, Claude Code blocks the call instead: see [Troubleshoot hooks](../reference/troubleshoot-hooks.md) to recover. Other shell commands go through Claude Code's normal permission flow; an `rm` of files git cannot restore is the real-loss case above.
35
35
 
36
- **Bob** runs one combined gate and has no "ask": it refuses with exit code 2, and only for the rules that admit no judgement call: credentials, destructive git, a scan of a whole filesystem, a write under a project's own protected-checks list, and writes that would switch a gate off. The commit/push and memory checks become a log line, and the call goes through. The ownership gate also refuses with exit 2, but once: the same write passes after you answer. Bob's hook wiring follows its documentation but has not been tested on a live Bob install.
36
+ **Bob** runs one combined gate and has no "ask": it refuses with exit code 2, and only for the rules whose Bob cell says *block* in [Rule enforcement, by host](../concepts/enforcement-table.md). The commit/push check becomes a log line, and the call goes through. The ownership gate also refuses with exit 2, but once: the same write passes after you answer. For what was checked against Bob itself, see [What is verified](../concepts/host-matrix.md#what-is-verified).
37
37
 
38
38
  <!--/harness-->
39
39
  <!--harness:opencode-->
@@ -8,7 +8,7 @@ description: "Where an install lands on IBM Bob or as a plain AGENT.md bundle, a
8
8
  ---
9
9
  Bob and the plain bundle carry the same rules, agents and skills as the other hosts. What differs is where they land and how much of it is enforced. The **Kind** words are explained in [What lands on your machine](on-your-machine.md).
10
10
 
11
- **Bob.** A global install writes to `~/.bob/`, or `BOB_CONFIG_DIR`. Bob does not load a global `AGENTS.md`, so the rules go into `~/.bob/rules/geneseed.md`. A per-repo install writes `AGENTS.md` instead. Hooks live in `~/.bob/settings/settings.json`. Bob runs three of them: context at session start, one combined gate before each tool call, and learn at session end. Bob has no "ask" prompt, so the gate refuses outright, and only for the checks that admit no judgement call: credentials, destructive git, a write under a project's own protected-checks list, and writes that would switch a gate off. The commit/push and memory questions become log lines. One more refusal happens only once: in an application repo whose root `AGENTS.md` has no `## Ownership` section, the session's first write is refused so the agent proposes the [ownership](../concepts/ownership.md) setup, and the same write passes after you answer. Turn it off per repo with `mode: off` in that section, for yourself in one repo with `Setup: declined <YYYY-MM-DD>` in `.geneseed/ownership.md`, or per install with `--no-ownership-gate`.
11
+ **Bob.** A global install writes to `~/.bob/`, or `BOB_CONFIG_DIR`. Bob does not load a global `AGENTS.md`, so the rules go into `~/.bob/rules/geneseed.md`. A per-repo install writes `AGENTS.md` instead. Hooks live in `~/.bob/settings/settings.json`. Geneseed wires four: context at session start, one combined gate before each tool call, the Activity record on each prompt, and learn at the end of a turn (wired, but Bob sends it no transcript, so only the change report runs). Bob has no "ask" prompt, so the gate refuses outright, and only for the rules whose Bob cell says *block* in [Rule enforcement, by host](../concepts/enforcement-table.md). The commit/push question becomes a log line. One more refusal happens only once: in an application repo whose root `AGENTS.md` has no `## Ownership` section, the session's first write is refused so the agent proposes the [ownership](../concepts/ownership.md) setup, and the same write passes after you answer. Turn it off per repo with `mode: off` in that section, for yourself in one repo with `Setup: declined <YYYY-MM-DD>` in `.geneseed/ownership.md`, or per install with `--no-ownership-gate`.
12
12
 
13
13
  **Shared by every host.** A global Bob install reads and writes the same machine-wide folder as the other hosts, `~/.config/geneseed/`: your rules, profile, memory, wiki manifest, exclude paths and notes. See [The shared tier](../concepts/shared-tier.md).
14
14
 
@@ -14,11 +14,11 @@ What a Claude Code or OpenClaude install writes, piece by piece. The **Kind** wo
14
14
  | `CLAUDE.md` (managed block) | The rules, the pointers to agents and skills, and how memory works. Geneseed writes only its own block; your own lines in the file stay | asked | ~7.2k tokens every session | Shrink it with fewer doctrine packs (`--doctrines`); remove it with `geneseed uninstall` |
15
15
  | `user-rules.md` | Your own standing rules, read every session. A global install reads the [shared](../concepts/shared-tier.md) file first, then this one, which can narrow it. Seeded empty | asked | 0 until you write in it | Leave it empty |
16
16
  | `PROFILE.md` | Who you are and how you like answers pitched. Fill it with the `profile` skill. On a global install it lives in the shared tier, and a filled host file replaces the shared one | asked | 0 until you fill it | Leave the seeded text untouched |
17
- | context hook | At session start, and again after a resume or compaction, puts your repo's README, CONTRIBUTING and a listing of `docs/` in front of the agent, with your rules, profile, memory index and wiki | automatic | Your docs, capped at 16 KB a file and 48 KB a session | `geneseed exclude add <folder>` silences every hook in that folder |
17
+ | context hook | At session start, and again after a resume or compaction, puts your repo's README, CONTRIBUTING and a listing of `docs/` in front of the agent, with your rules, profile, memory index and wiki | automatic | Your docs; the whole hook output is capped at 9,000 characters, and what does not fit is listed for the agent to read on demand | `geneseed exclude add <folder>` silences every hook in that folder |
18
18
  | git-gate hook | Before each shell command: asks you before any `git commit` or `git push`, and before a command that would really lose data — a force-push to `main`, a `reset --hard` that abandons unpushed commits, `branch -D` of an unpushed branch, an `rm` git cannot undo | enforced | ~14 ms per shell call | The commit/push question goes away if you build without the **process** pack; the destructive-git question has no switch except `geneseed exclude` |
19
19
  | rule-gate hook | Before each write or edit: asks you when the file would carry a credential-shaped string (outside `.env`), or when the agent writes to `user-rules.md` or memory. In an application repo with no `## Ownership` section in its root `AGENTS.md`, stops the session's first write once so the agent proposes the [ownership](../concepts/ownership.md) setup | enforced | ~14 ms per write | `geneseed exclude add <folder>`; the ownership stop alone: `mode: off` in the repo's `## Ownership`, `Setup: declined <YYYY-MM-DD>` in your personal `.geneseed/ownership.md`, or rebuild with `--no-ownership-gate` |
20
20
  | learn hook | When the agent finishes a reply, and before compaction, distils durable facts from the recent conversation into the memory store. Off until you set `GENESEED_LLM` to a model command such as `claude -p` | automatic | One model call each time it runs, once enabled | Leave `GENESEED_LLM` unset (the default) |
21
- | `skills/` | Written procedures you call by name, such as `brainstorm` or `plan` | on demand | ~4.1k tokens for names and descriptions; a skill's body loads only when called | No per-skill switch; `geneseed uninstall` removes them all |
21
+ | `skills/` | Written procedures you call by name, such as `brainstorm` or `plan` | on demand | ~2.2k tokens for names and descriptions; a skill's body loads only when called | No per-skill switch; `geneseed uninstall` removes them all |
22
22
  | `agents/` | Specialists the agent can delegate to, such as `reviewer` or `tester` | on demand | ~0.5k tokens | `geneseed uninstall` |
23
23
  | `memory/` | Durable facts, one per file, with a `MEMORY.md` index the context hook injects. A global install keeps them in the shared `~/.config/geneseed/memory/`; this folder holds only the convention and a seeded index | automatic | 0 when fresh; grows as facts accumulate | `geneseed memory list`, then `geneseed memory rm <name>` (archives; `--purge` deletes) |
24
24
  | `notebook/` | The agent's own working space: plans, scratch notes, and the gate log `gates.jsonl`. It stays per host; on a global install only the self-improvement notes live in the shared `notes/` | automatic | 0 when fresh; its index grows with use | Delete what you do not want; it is git-ignored and yours |
@@ -13,7 +13,7 @@ An install writes a handful of files into your host's config folder and, where t
13
13
  - **asked**: text the model reads every session. It usually follows it, but nothing makes it.
14
14
  - **on demand**: loads only when you or the agent call it by name.
15
15
 
16
- Token costs are for the default *lean* footprint. Before you type anything, a session carries about 12k tokens of harness. That is roughly 6% of a 200k window. A `--footprint full` build adds about 5k on the rules file. For a live figure on your own install, ask the agent to use the `token-report` skill.
16
+ Token costs are for the default *lean* footprint. Before you type anything, a session carries about 12k tokens of harness. That is roughly 6% of a 200k window. A `--footprint full` build adds about 7k on the rules file. For a live figure on your own install, ask the agent to use the `token-report` skill.
17
17
 
18
18
  ## One folder for the whole machine
19
19
 
package/docs/web-ui.md CHANGED
@@ -75,9 +75,9 @@ Every `/api/*` read takes and checks the pair, with these exceptions:
75
75
  - `/api/ping` and `/api/jobs` ignore it.
76
76
  - The machine-wide reads also ignore it: `/api/update`, `/api/installs`, `/api/fleet`, `/api/migrate/preview`,
77
77
  `/api/kits`, `/api/usage`, `/api/gates`, `/api/excludes`, `/api/mcp`, `/api/loops/active`,
78
- `/api/factories/active`, `/api/activity`, and the Library's skill, agent, memory and notebook lists,
79
- `/api/catalog/skills`, `/api/catalog/agents`, `/api/catalog/memory` and
80
- `/api/catalog/notebook`. Such a read does not check the pair, and its answer does not change
78
+ `/api/factories/active`, `/api/activity`, and the Library's skill, agent, memory, notebook, wiki and config lists,
79
+ `/api/catalog/skills`, `/api/catalog/agents`, `/api/catalog/memory`,
80
+ `/api/catalog/notebook`, `/api/catalog/wiki` and `/api/catalog/config`. Such a read does not check the pair, and its answer does not change
81
81
  with the pair. The Activity detail (`/api/activity/<id>`) and the Activity toggle still take
82
82
  the pair.
83
83
 
@@ -88,7 +88,7 @@ tier hold one memory store: it is listed under the first of them, and `/api/cata
88
88
  them all in `sharedInstalls`. Each row is one id (kind and name), and
89
89
  its `installs` field names the installs that have it, as `host:scope:root` keys (the same keys
90
90
  as `/api/usage`). An id that only some installs have lists only those installs, so an exclusion
91
- stays visible. The other catalog sections stay install-scoped. `/api/item/skill/<name>` and
91
+ stays visible. The laws section stays install-scoped. `/api/item/skill/<name>` and
92
92
  `/api/item/agent/<name>` stay install-scoped too, because each install renders its own copy in
93
93
  its own theme and footprint. With a pair, the item is that install's copy, and an id that
94
94
  install lacks gets a 404. Without a pair, the item is the copy of the first install that has
@@ -191,6 +191,11 @@ budget, measured without project context, for the install whose content was cut,
191
191
  largest. It turns amber at 85% of the budget or whenever content was cut, and Needs you adds one
192
192
  suggestion at the same point.
193
193
 
194
+ A row's details draw the skill list against its own ceiling (`SKILL_LISTING_CEILING`,
195
+ `js/inspect/cost.mjs`) under the cost breakdown, as the row draws the root file against its
196
+ ceiling: a bar, then `part / ceiling · share`, red past 100%. Only a Claude Code install has that
197
+ ceiling, so no other host's details show the bar.
198
+
194
199
  A global **Spotlight** search lives in the topbar — press <kbd>/</kbd> to focus it (or
195
200
  <kbd>Ctrl</kbd>/<kbd>⌘</kbd>+<kbd>K</kbd>, which also works from inside a text field), type
196
201
  to jump to any agent, skill, doc, MCP server, or constitutional rule — the `laws`
@@ -500,7 +505,7 @@ screen the run list stacks above the detail.
500
505
  - "Deploy to folder…" and "Rebuild all" apply to the whole set. An **Excluded folders**
501
506
  card (shown once a global install exists) manages sovereign repos — folders where every
502
507
  global harness goes dormant (hooks stay silent, the global preamble never loads);
503
- add or remove one here, the web mirror of `harness exclude add|remove|list`.
508
+ add or remove one here, the web mirror of `geneseed exclude add|remove|list`.
504
509
  - **Settings** (`#/settings`; `#/about` and `#/installs/server` resolve here) — a rail entry of its
505
510
  own, about the tool and never one install: a sheet with a section index. **Machine**:
506
511
  version + Update (labelled by how this copy updates: git pull, npm install -g, or the command
@@ -2,5 +2,5 @@
2
2
  "_comment": "version is a human-readable release label only; the canonical identity of an installed harness is the source fingerprint stamped in .geneseed-version (see `harness version`), not this string.",
3
3
  "theme": "neutral",
4
4
  "product": "Geneseed",
5
- "version": "5.3.0"
5
+ "version": "5.4.0"
6
6
  }