geneseed 5.0.1 โ†’ 5.0.4

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 (185) hide show
  1. package/CHANGELOG.md +92 -0
  2. package/README.md +4 -4
  3. package/SHIPPED.md +2 -2
  4. package/adapters/claude-code/README.md +11 -5
  5. package/adapters/openclaude/README.md +3 -1
  6. package/adapters/opencode/HOW-OPENCODE-LOADS.md +3 -0
  7. package/adapters/opencode/plugins/geneseed-context.js +12 -1
  8. package/adapters/opencode/plugins/geneseed-guard.js +594 -73
  9. package/adapters/opencode/plugins/geneseed-learn.js +1 -1
  10. package/adapters/opencode/plugins/geneseed-workflow.js +1 -1
  11. package/adapters/opencode/workflows/_runtime.js +1 -1
  12. package/bin/geneseed-cli.mjs +3 -0
  13. package/bin/geneseed-hook.mjs +31 -9
  14. package/docs/PRD.md +1 -1
  15. package/docs/README.md +4 -1
  16. package/docs/concepts/enforcement-table.md +23 -4
  17. package/docs/concepts/exclusions.md +48 -2
  18. package/docs/concepts/factories.md +151 -0
  19. package/docs/concepts/foreman-mode.md +19 -4
  20. package/docs/concepts/hook-gates.md +1 -1
  21. package/docs/concepts/hooks.md +53 -12
  22. package/docs/concepts/host-matrix.md +5 -3
  23. package/docs/concepts/hosts.md +1 -1
  24. package/docs/concepts/kits.md +18 -0
  25. package/docs/concepts/loop-gates.md +3 -0
  26. package/docs/concepts/loops.md +1 -0
  27. package/docs/concepts/rules.md +1 -1
  28. package/docs/concepts/shared-tier.md +1 -1
  29. package/docs/concepts/skills.md +1 -1
  30. package/docs/extending.md +8 -2
  31. package/docs/guides/autostart.md +29 -3
  32. package/docs/guides/choose-your-setup.md +1 -1
  33. package/docs/guides/migrate.md +1 -1
  34. package/docs/guides/run-a-factory.md +88 -0
  35. package/docs/guides/set-up-ownership.md +1 -0
  36. package/docs/guides/uninstall.md +1 -1
  37. package/docs/reference/factory-actions.md +22 -0
  38. package/docs/reference/loop-actions.md +1 -1
  39. package/docs/reference/plugin-activity.md +1 -1
  40. package/docs/reference/plugin-context.md +1 -1
  41. package/docs/reference/plugin-guard.md +24 -5
  42. package/docs/reference/troubleshoot-doctor.md +2 -2
  43. package/docs/understand/a-day.md +9 -5
  44. package/docs/web-ui.md +101 -17
  45. package/harness.config.json +1 -1
  46. package/js/README.md +21 -3
  47. package/js/build/args.mjs +14 -2
  48. package/js/build/emit-claude.mjs +9 -1
  49. package/js/build/emit-opencode.mjs +2 -1
  50. package/js/build/source.mjs +28 -3
  51. package/js/cli-table.json +287 -3
  52. package/js/factory/cli.mjs +153 -0
  53. package/js/factory/graph.mjs +245 -0
  54. package/js/factory/registry.mjs +71 -0
  55. package/js/factory/state.mjs +429 -0
  56. package/js/hosts/activity.mjs +3 -3
  57. package/js/hosts/geneseed-dir.mjs +2 -2
  58. package/js/hosts/gitref.mjs +21 -0
  59. package/js/hosts/hooks-context.mjs +71 -15
  60. package/js/hosts/hooks-done.mjs +3 -1
  61. package/js/hosts/hooks-learn.mjs +1 -1
  62. package/js/hosts/hooks-prims.mjs +271 -1
  63. package/js/hosts/hooks.mjs +409 -151
  64. package/js/hosts/hosts.mjs +22 -0
  65. package/js/hosts/installs.mjs +9 -5
  66. package/js/hosts/settings.mjs +128 -27
  67. package/js/hosts/shim.mjs +155 -7
  68. package/js/hosts/store-watch.mjs +36 -11
  69. package/js/inspect/checks-authoring.mjs +11 -1
  70. package/js/inspect/cost.mjs +91 -5
  71. package/js/inspect/diff.mjs +2 -1
  72. package/js/inspect/doctor.mjs +2 -1
  73. package/js/inspect/inventory.mjs +2 -1
  74. package/js/inspect/validate.mjs +1 -1
  75. package/js/loop/catalog.mjs +24 -12
  76. package/js/loop/cli.mjs +21 -15
  77. package/js/loop/graph.mjs +13 -4
  78. package/js/loop/registry.mjs +65 -28
  79. package/js/loop/state.mjs +18 -8
  80. package/js/maintain/migrate.mjs +2 -2
  81. package/js/maintain/uninstall.mjs +5 -1
  82. package/js/web/actions.mjs +17 -1
  83. package/js/web/api.mjs +52 -11
  84. package/js/web/catalog.mjs +38 -2
  85. package/js/web/daemon.mjs +136 -6
  86. package/js/web/handler.mjs +14 -5
  87. package/js/web/routes.mjs +12 -4
  88. package/js/web/server.mjs +4 -1
  89. package/package.json +1 -1
  90. package/registry.json +35 -0
  91. package/src/AGENT.md.tmpl +18 -24
  92. package/src/agents/_self-improvement.md +7 -6
  93. package/src/agents/developer.md +3 -2
  94. package/src/agents/docker-expert.md +1 -0
  95. package/src/agents/memory-curator.md +3 -2
  96. package/src/bricks/docs-update.md +5 -0
  97. package/src/bricks/holdout-write.md +23 -0
  98. package/src/bricks/holdout.md +25 -0
  99. package/src/bricks/intake.md +18 -0
  100. package/src/bricks/merge-gate.md +22 -0
  101. package/src/bricks/pr-open.md +21 -0
  102. package/src/bricks/retro.md +17 -0
  103. package/src/bricks/test.md +4 -1
  104. package/src/bricks/triage.md +19 -0
  105. package/src/doctrines/comms.md +29 -41
  106. package/src/doctrines/craft.md +3 -10
  107. package/src/doctrines/ops.md +4 -15
  108. package/src/doctrines/process.md +24 -19
  109. package/src/doctrines/rigor.md +1 -5
  110. package/src/factories/analysis-to-build.json +34 -0
  111. package/src/factories/bug-report-to-fix.json +32 -0
  112. package/src/factories/issue-to-pr.json +49 -0
  113. package/src/kits/ci-pipelines/rules.md +10 -0
  114. package/src/kits/ci-pipelines.json +14 -0
  115. package/src/kits/docker/rules.md +11 -0
  116. package/src/kits/docker.json +12 -0
  117. package/src/memory/README.md +5 -4
  118. package/src/modes/foreman.md +23 -10
  119. package/src/notebook/README.md +1 -1
  120. package/src/skills/_checkpoints.md +1 -0
  121. package/src/skills/_self-improvement.md +12 -9
  122. package/src/skills/adhd.md +1 -1
  123. package/src/skills/compose-ops.md +58 -0
  124. package/src/skills/factory-forge.md +97 -0
  125. package/src/skills/factory.md +126 -0
  126. package/src/skills/gitlab-ci.md +51 -0
  127. package/src/skills/jenkins-pipeline.md +56 -0
  128. package/src/skills/parallel-agents.md +1 -1
  129. package/src/skills/pipeline.md +2 -2
  130. package/src/skills/rule.md +24 -18
  131. package/src/skills/skill-forge.md +24 -6
  132. package/src/skills/workflow.md +2 -1
  133. package/themes/_TEMPLATE.json +9 -4
  134. package/themes/biker.json +9 -4
  135. package/themes/commentator.json +9 -4
  136. package/themes/cyberpunk.json +9 -4
  137. package/themes/gamer.json +9 -4
  138. package/themes/imperial.json +9 -4
  139. package/themes/joker.json +9 -4
  140. package/themes/marvin.json +9 -4
  141. package/themes/mean.json +9 -4
  142. package/themes/military.json +9 -4
  143. package/themes/neutral.json +9 -4
  144. package/themes/pirate.json +9 -4
  145. package/themes/sports.json +9 -4
  146. package/themes/verstappen.json +9 -4
  147. package/themes/wizard.json +9 -4
  148. package/web/dist/assets/ActiveLoops-BTHIaRhn.js +1 -0
  149. package/web/dist/assets/Activity-BaoxwVFH.js +1 -0
  150. package/web/dist/assets/ActivityDetail-C_bFD0rW.js +1 -0
  151. package/web/dist/assets/{Bonsai-C1iBAt4v.js โ†’ Bonsai-B01lLf0m.js} +1 -1
  152. package/web/dist/assets/{CopyButton-DJ3a4N88.js โ†’ CopyButton-Bc66KPyA.js} +1 -1
  153. package/web/dist/assets/Dashboard-X7GZzGJp.js +2 -0
  154. package/web/dist/assets/{Docs-Kffdg5uV.js โ†’ Docs-LRYVnGLG.js} +3 -3
  155. package/web/dist/assets/Factories-ARenKBiP.js +1 -0
  156. package/web/dist/assets/{GreenhouseView-k56_cBSF.js โ†’ GreenhouseView-CfWR2-sX.js} +1 -1
  157. package/web/dist/assets/{Installs-DtEKLC9h.js โ†’ Installs-nfFHnovH.js} +3 -3
  158. package/web/dist/assets/{JournalView-RQnk5l7I.js โ†’ JournalView-lpOHcHKK.js} +1 -1
  159. package/web/dist/assets/Kits-Bw5EQl_i.js +1 -0
  160. package/web/dist/assets/Laws-CnZJ0wjZ.js +4 -0
  161. package/web/dist/assets/LibRows-Hqvf1beK.js +1 -0
  162. package/web/dist/assets/Library-JaSsp6Yr.js +3 -0
  163. package/web/dist/assets/Loops-ZaHC5MVl.js +2 -0
  164. package/web/dist/assets/{OperatorHudView-CM5jNPwL.js โ†’ OperatorHudView-CggG0_sK.js} +1 -1
  165. package/web/dist/assets/Personal-BObvlb70.js +2 -0
  166. package/web/dist/assets/Settings-BFfPMPc9.js +1 -0
  167. package/web/dist/assets/Tabs-B594Pad_.js +1 -0
  168. package/web/dist/assets/api-DLDVY3K-.js +1 -0
  169. package/web/dist/assets/index-DsLmKHw0.js +6 -0
  170. package/web/dist/assets/index-DvPjphz0.css +1 -0
  171. package/web/dist/index.html +3 -3
  172. package/web/dist/assets/Activity-Ci4PZco3.js +0 -1
  173. package/web/dist/assets/ActivityDetail-C8hroCND.js +0 -1
  174. package/web/dist/assets/Dashboard-C_On4KXw.js +0 -2
  175. package/web/dist/assets/Kits-CXkEBpnf.js +0 -1
  176. package/web/dist/assets/Laws-DhhIVqmh.js +0 -3
  177. package/web/dist/assets/Library-CAUiEoJo.js +0 -3
  178. package/web/dist/assets/Loops-LKD8mF4E.js +0 -2
  179. package/web/dist/assets/Personal-B6Uoly3C.js +0 -2
  180. package/web/dist/assets/RailCats-DQxxYBEP.js +0 -1
  181. package/web/dist/assets/Settings-BTe6-wda.js +0 -1
  182. package/web/dist/assets/Tabs-CbdDWTp_.js +0 -1
  183. package/web/dist/assets/api-D_r0Jtla.js +0 -1
  184. package/web/dist/assets/index-HfGmYXab.js +0 -3
  185. package/web/dist/assets/index-ao3M-Fhm.css +0 -1
package/CHANGELOG.md CHANGED
@@ -8,6 +8,98 @@ label. For the capability โ†” spec map, see [SHIPPED.md](SHIPPED.md).
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [5.0.4] โ€” 2026-11-09
12
+
13
+ ### Added
14
+ - **The Factories page draws a factory vertically, with its forks.** Stages run top to bottom; the lanes of a fork sit side by side, each labelled with its outcome, and join again at the first stage they all reach. Routes back are rails on the left (`โ†บ <cycle> ยท max N`), stop edges one rail on the right; a live run lights the lane it took and the stage it stands on. A loop stage's ring is about twice its old size. The graph never scrolls sideways: in a narrower pane its rails become tags and its lanes shrink to compact boxes, and only below about 524 px do the lanes stack.
15
+ - **The factory engine and `geneseed factory`.** A factory carries one work item through a graph of stages, each a brick or a whole loop (`loop:<name>`). A failure may route back to an earlier stage, but only through a declared cycle with its `max` (5 at most). The state lives in `FACTORY.md` beside the child loop's `LOOP.md`. Every run ends by construction: 30 stage transitions per task, and a run-wide ceiling fixed at the first spec record (20 tasks at most). The CLI has the actions `check`, `list`, `init`, `next`, `record` and `decide`. It refuses an outcome that contradicts the child loop's `LOOP.md`, a dirty tree after a stage outside a loop, and a hand-edited `FACTORY.md` past the engine's bounds. See `docs/reference/factory-actions.md`.
16
+ - **The first shipped factory, `bug-report-to-fix`, and the `factory` skill.** The factory runs `intake` โ†’ `loop:bugfix` โ†’ `pr-open` โ†’ `merge-gate` โ†’ `retro`, and red CI at `merge-gate` sends the fix back to the loop, twice at most. The run ends at an open PR with green CI; the merge stays yours. The `factory` skill creates the run's worktree on `loop/factory-<slug>`, steps the engine, and runs each loop stage through the `loop` skill in that same worktree. Four new bricks: `intake` (reads a request, a document, or a GitHub or GitLab issue), `pr-open` (pushes, which asks, and opens or updates the PR), `merge-gate` (waits for CI, 30 minutes at most, and asks you when the repo has no CI) and `retro` (writes the run report to `.geneseed/factory-runs/<slug>.md`). Each run is registered in `factories.json` beside the loop registry. See `docs/concepts/factories.md` and `docs/guides/run-a-factory.md`. Run `geneseed rebuild-all` to get the skill.
17
+ - **A Factories page in the console**, in the rail's Build group after Loops. **Templates** lists the factories an install resolves and draws the selected one as a graph: its stages as blocks left to right, joined by lines labelled with their outcomes; each `loop:` stage as a block holding its loop's ring; each route back as an arc above the row with its cycle and `max`; `close` and `stop` as end caps. **Active** lists every registered run, polled, and draws it with its current stage lit, its cycle laps, its task number, and the child loop's current node. It reads `GET /api/factories/catalog` and `GET /api/factories/active`. It changes nothing in a run; the Active poll only drops finished runs older than 7 days from `factories.json`, as Loops โ€บ Active does for `loops.json`.
18
+ - **A second shipped factory, `issue-to-pr`, and the `triage` brick.** The factory runs `intake` โ†’ `holdout-write` โ†’ `triage` โ†’ one lane โ†’ `holdout` โ†’ `pr-open` โ†’ `merge-gate` โ†’ `retro`. `triage` is a fork: it reads the work item and reports the outcome that names its lane (`bug`, `feature`, `deps`, `refactor` for the matching loop, `docs` for the `docs-update` brick). A failed scenario or red CI sends the work back to that same lane, twice at most each. The merge stays yours.
19
+ - **Factory forks, named outcomes and `$lane`.** A brick that declares an outcome other than `pass`, `fail`, `error` or `none` is a fork: each outcome has its own edge to its own lane, a loop or a brick. `geneseed factory next` hands a fork its `lanes`, and the outcome recorded names the lane taken, kept in `FACTORY.md` as `lane`. An edge target or a cycle node may be `$lane`, the stage the run's most recent fork chose, so a route back returns to the lane the run took. `geneseed factory check` refuses `$lane` with no fork, or before any fork on some path; cycles, their `max` and the transition ceilings are unchanged. The `loop:$triaged` stage, the factory's `loops` list and `record --loop` are retired: `check` (and so the doctor) names each with its replacement, and never rewrites a user's file.
20
+ - **The `factory-forge` skill.** It composes bricks and loops into a factory of your own. It interviews you for the input, the stages, the human gates, the failures that route back and their `max` (5 at most), then writes `.geneseed/factories/<name>.json` (project) or `~/.config/geneseed/factories/<name>.json` (global). It runs `geneseed factory check` until the file passes and explains each rule a problem names. When a stage needs a brick that does not exist, it offers the `brick-forge` skill or runs it: `brick-forge` stays the only skill that writes bricks. Then it hands the factory to the `factory` skill. Run `geneseed rebuild-all` to get the skill.
21
+ - **A third shipped factory, `analysis-to-build`.** The factory runs `intake` โ†’ `spec` โ†’ `loop:feature` โ†’ `pr-open` โ†’ `merge-gate` โ†’ `retro`. The `spec` stage writes `specs/<slug>/spec.md` with an ordered task list, and you approve it at its gate; the spec is then committed, and `loop:feature` runs once per task, in order, in one worktree, with one PR at the end. Red CI after the last task sends the work back to the loop as one extra task: `geneseed factory next` hands out the last task's index with `extra` set to the stage that sent it back (`"merge-gate reported fail"`). That lap spends cycle `ci` (twice at most) and the transition ceilings, and gives no fresh budget.
22
+ - **Holdout scenarios in every shipped factory, and the `holdout-write` and `holdout` bricks.** After `intake` (or `spec`), `holdout-write` writes 3 to 8 prose scenarios (given / when / then) to `~/.config/geneseed/holdout/<slug>/`, outside the worktree. After the loop, `holdout` plays them against the built change, before `pr-open`. A failed scenario sends the work back to the loop with one sentence per failure (observed against expected, never the scenario's text), twice at most (cycle `holdout`). `error` stops the run, for example when the diff touches the holdout folder. Both stages run as `tester`, and the `factory` skill never hands holdout content to the developer. No hook refuses a read of the folder on any host: it is protected by its place outside the worktree, by `holdout`'s `error` and by the skill's rule.
23
+ - **`geneseed loop init --factory <slug>`** stores on the loop's registry row the factory run the loop is a stage of.
24
+ - **`geneseed loop init --note <text>`** starts the new loop's notes with that text, so a factory can hand on the reason a stage failed.
25
+
26
+ ### Changed
27
+ - **The console's Library, Loops and Factories pages stack their panes when the page is narrow.** When the page has less than 1174 px for these panes (for example half a window), the reader could not keep 560 px beside the rail and the list. The panes now go one under the other, each block only as tall as its content. Under the page header comes a toolbar card: the sections as one row of buttons with their counts (the open one filled with the accent), the filter with the usage filter beside it, and the categories as chips (only for a section with categories). Next comes a picker card: its header shows how many entries the filter leaves and which one is open; under it, about five rows scroll on their own. Picking a row keeps the picker open, so the next entry is one click away. A link to an entry from outside the list opens with the picker closed, and a section opens with it open. The entry comes last, as a plain card. A locked Library (Personal โ€บ Memory, Notebook) stacks only under 942 px. The reader no longer scrolls sideways: the start command and code blocks wrap, a source path breaks after a slash, and a loop ring scales up to its own drawn width (it was capped at 680 px, which drew the widest shipped ring at 82%). The ring takes the width that keeps its labels at 11 px or more before "How it runs" sits beside it; a reader narrower than that still shrinks them. The Constitution's packs column and the Docs map's piece panel go under their content when it runs out of room, not at a fixed 1180 px window width.
28
+ - **The Library's Loadout panel, redrawn.** The total in tokens comes first, with the install it was read from and the delta against the primary as pills. The bar shows three groups (Constitution, Catalogues, This agent) instead of one slice per block, each with its own card; the Constitution card is folded for an Adept. The rules start with the ones the agent's spec cites, then one pill per pack, and the full list sits behind "Show all". What is not counted moves to a footnote.
29
+ - **The Constitution table's last columns read Status, Rule text, Enforced by, Hook gate**, so each switch sits beside what it acts on. When the table is narrower than 760 px, Status and Enforced by still fold into chips under the rule name.
30
+ - **The loop engine ignores `FACTORY.md`** in its scoring and porcelain checks, as it ignores `LOOP.md`. Loop behaviour is otherwise unchanged.
31
+ - **Doctrine comms 5, *Mark the Ask*, merged into comms 1, now *Codes and Markers*.** Both rules set the reply format and shared one example, so one rule now holds the reference codes and the ask markers. The id `mark-the-ask` is retired and never reused; the doctrines now hold 30 rules. An install that excluded `comms 5` gets a warning ("comms 5 was retired") and excludes nothing; the rebuild does not fail. *Automate Repetition* (craft 1) and *Search Before Creating* (craft 4) lose the sentences that repeated each other, and the Memory section points to *Persist Insight* instead of restating it. The lean root is about 900 characters shorter. Run `geneseed rebuild-all` to get it.
32
+ - **Five situational rules keep one line in the lean root.** *Edit the Source, Not the Surface*, *Record the Probe, Not the Snapshot*, *Restart Is Not Reload*, *Serialize Against a Rationed Resource* (ops 3, 5, 6, 7) and *External Gate* (rigor 5) now carry one trigger sentence in a lean install; the full text stays in the pack file, which the root already points to. The full footprint does not change. The `parallel-agents` and `workflow` skills cite *Serialize Against a Rationed Resource* at their fan-out step. The lean root is about 1 200 characters shorter, and the lean size ceiling drops from 41 612 to 40 312. Run `geneseed rebuild-all` to get it.
33
+
34
+ ### Fixed
35
+ - **A loop can pass in a project with no linter.** The `test` brick listed a check the project does not have as `SKIPPED`, which the engine rightly refuses for a `pass`, so `bugfix` and `feature` could never close on such a repo (found by the factory end-to-end run). The brick now lists it as `<check>: N/A (not configured)`; a check that exists but did not run is still `SKIPPED` and still blocks.
36
+ - **`pr-open` builds the PR body from what it is given.** It asked for the loop's notes, which leave with `LOOP.md` when the loop closes; it now uses the run's `requirement` and `input` and the branch's commit subjects.
37
+ - **The Loadout panel no longer counts user rules a sub-agent never receives.** On a host with no SubagentStart wiring (Bob, OpenCode), or an install emitted before it, the user rules render muted with the reason and are left out of "Rules it follows".
38
+ - **`geneseed factory record` no longer accepts `pass` from a loop stage on a HEAD move alone.** With no `LOOP.md` left, `pass` now also needs the loop registry to show a `geneseed loop init` in the worktree after `factory next`. `next` stores the launch time, and each `loop init` stamps the registry row with a new `initAt`. Without that evidence only `fail` is accepted.
39
+ - **`geneseed loop init --note-file <path>`** now reads the starting note from the file, as `record` does. Before, `init` ignored the flag.
40
+ - **`FACTORY.md` is checked more strictly.** A gate amend count above 3, a chosen loop outside the factory's `loops`, an unknown status, or a `history` or `cycles` that is not a list is refused as unreadable. A `cycles: {}` no longer makes `record` crash. The fourth gate amend still stops the run, but now stores 3, so the stopped `FACTORY.md` stays readable.
41
+ - **Project factories at `.geneseed/factories/` are no longer git-ignored.** The `.geneseed/.gitignore` Geneseed seeds now lets `factories/` back in, as it does `bricks/` and `loops/`. A repo seeded before keeps its file: add the line `!/factories/` to it by hand.
42
+ - **The factory's close commit no longer leaves the CI state unread.** Its push re-runs CI after `merge-gate` saw it green; the `factory` skill now reads the checks once more, with the same 30-minute bound, and the run report and the final report give that state.
43
+ - **`merge-gate` waits with a command that returns by itself.** It polled once a minute, but hosts refuse a foreground `sleep`. It now runs `gh pr checks <pr> --watch --interval 30` or `glab ci status --wait`, each call bounded under 10 minutes, repeated up to 30 minutes, then reads the verdict once.
44
+ - **The docs list Factory actions after Loop actions.** The two pages had the same `order:`.
45
+ - **`geneseed web restart` no longer leaves the old console running on the preferred port.** When port 4747 is taken, `web start` and `web restart` now identify the holder through `/api/ping`, which carries a hash of the install root. A console of the same install is asked to shut down with an install secret (an owner-only file next to the daemon record, never sent as such) and the port taken; no process is ever signalled by pid. Another program, a console of another install, or a console too old to carry the root are never touched: the command prints a line naming the port and the holder, then says which port it served on instead. A foreground `geneseed web` that loses the bind says so too. The Restart button of a console that is no longer the recorded daemon says that, with the recorded address, instead of "foreground server". `web status` also lists a console on 4747 that is not the recorded one.
46
+
47
+ ## [5.0.3] โ€” 2026-11-08
48
+
49
+ ### Added
50
+
51
+ - **Sub-agents now receive your `user-rules.md`.** No sub-agent ever got the SessionStart output, so rules written for sub-agents reached none. On Claude Code and OpenClaude, `SubagentStart` now runs `geneseed-hook context` (it ran `activity` before; the Activity record still runs), which reads the event name and injects every `user-rules.md` layer (shared tier, install, project root) as one JSON `hookSpecificOutput.additionalContext`, under the same 9 000-character budget and cut as SessionStart. The profile and project context are not injected: the root file already reaches a sub-agent. The budget holds for the JSON line itself, after escaping. The project-root layer is the `user-rules.md` at the root SessionStart discovers from (`$GENESEED_ROOT`, else `$CLAUDE_PROJECT_DIR`, else the hook's working dir), not the git root of the payload's `cwd`. OpenCode follows in a later release; Bob has no `SubagentStart` event. Re-emit an install to wire it. A global install emitted with this change stands down on `SubagentStart` in a project whose earlier-emitted project install already runs `context` (on SessionStart), so that project's sub-agents get no rules, and the Loadout panel shows it as not wired, until the project install is re-emitted too.
52
+ - **The Library shows what each agent loads.** Agents gets a pinned first row for the main agent (neutral **Primary agent**, imperial **Servant**, a new `PRIMARY_AGENT` theme noun) with a **base** pill, and every agent's detail gets a **Loadout** panel: a stacked bar of what it loads (the root file by section, the session files or the user rules, both catalogues, an Adept's spec), the delta against the primary, and the rules it follows, grouped by kind, each linking to its Laws row and marked when the Adept's spec cites it. The figures come from `agentLoadout` (`js/inspect/cost.mjs`), which shares its measurements with the Overview's always-on cost; `GET /api/loadout` and `/api/loadout/<agent>` serve them. An install emitted before this release shows its user rules as not wired until it is re-emitted.
53
+ - **Two new opt-in kits, `ci-pipelines` and `docker`.** `ci-pipelines` adds the `jenkins-pipeline` skill (declarative `Jenkinsfile`, shared libraries, CPS and `@NonCPS`, sandbox approval, credentials, `parallel` and `when`, JenkinsPipelineUnit) and the `gitlab-ci` skill (`rules:`, `needs:`, `include:` and `extends:`, caching and artifacts, protected and masked variables, environments, CI lint), with rules and a banned list for GitLab's older job-condition keywords, which GitLab no longer actively develops. `docker` adds the `compose-ops` skill for running any Compose stack: health-ordered startup, volumes, pinned images, secrets, restart, limits, logging, networks, lean non-root images, and safe updates with rollback. The spring-boot kit's `docker-expert` now says it covers the image and its dev Compose file only. Both kits are off by default, so installs without them are unchanged. To turn one on, run `geneseed build --emit <target> --kits ci-pipelines` (or `docker`), or use **Installs โ†’ Kits** in the web console.
54
+ - **The Constitution page repeats its column header under every open band.** Ethos, Dictates and each doctrine pack get their own compact header row (No., Rule, Latin name, Status, Enforced by, plus the two switch columns where they exist); a folded pack has none. The single header above the Dictates is gone.
55
+ - **`--no-external-gate` stops the protected-check and gate-configuration asks** on every host: `rule-gate`, the shell path in `git-gate`, Bob's `tool-gate`, the OpenCode guard and OpenCode 2's `evaluate` ask. Other gates keep running, and OpenCode's own `permission.edit` keys stay. With it off the agent can edit the other gates' wiring unasked.
56
+ - **`--no-test-note` stops the weakened-test note,** at edit time, at turn end and in the OpenCode context plugin. The done checks do not change, and `--no-done-gate` still silences the turn-end line.
57
+ - **Settings can start the web console at login.** The **Start at login** row writes the login item when there is none, updates it when it names another copy or Node, and removes it. Each action asks first and names the file: `geneseed-web.vbs` in the Windows Startup folder, or `~/Library/LaunchAgents/dev.geneseed.web.plist` on macOS, which loads at the next login. The file carries a `GENESEED_AUTOSTART` line in a fixed place, and Geneseed changes or deletes only a file with that line there. The write goes through a temp file renamed over the target. The confirm names the copy the file runs and warns when that copy is an agent worktree or an npx cache. On Windows a path with `%` or non-ASCII is refused, and any path with a control character is refused. A login item you wrote yourself is never touched: the row links to the guide. A failed write shows the system's error. The request carries only the action, never a path.
58
+ - **The Constitution page has both switches.** Rule VIII carries the test note and now reads *Hook gate* or *Gate off*. Doctrine rigor 5 keeps its rule switch on the row and gets a gate line inside the opened row. Excluding the rule and switching off the gate are independent.
59
+ - **Constitution rows have two toggles: Rule text and Hook gate.** Each column is headed, and each switch's name says its rule and what it controls. A Dictate's text cell is locked. Rigor 5's gate switch moved from the opened row onto the row. A hook with no switch shows a locked cell: process 5, process 1 and ops 2 go with their text. Excluding rigor 5 also switches its gate off in the same rebuild, and including it again offers to re-arm the gate, checked by default. A row whose text is excluded while its hook still asks says so. The confirm dialog gained an optional checkbox.
60
+ - **Each hooked rule on the Constitution page says what its hook does.** The opened row folds four short lines after the rule text: what triggers the hook, what each host does (ask, refuse or warn), what it does not see, and what still holds with the gate off. Rules I, III, IV and VIII, doctrines process 1, process 5, rigor 5 and ops 2, and the Ownership section carry one; a text-only rule shows nothing new.
61
+ - **The web console's Terminal drawer shows each run as a phase timeline.** The runs are listed on the left with a status dot, a short detail and the duration. The picked run shows numbered phases (*Update the source*, one *Rebuild* per install) with their state, warnings in an amber box, refused links as grey notices and a failure's error line in red. **Full log** still shows the raw output, and a line the reader does not know stays visible in its phase.
62
+
63
+ ### Changed
64
+
65
+ - **A gate prompt now says what will change, the safe choice, why it asks and what happens if allowed.** The text is fixed per gate and file class, in plain English, with a repo-relative path and a line count. An agent-supplied name is cleaned, clipped and quoted, and the agent's own description is quoted only on the deletion, root-scan and commit asks, labelled as not checked. No gate decision changed: `tests/unit/gate_verdicts.test.mjs` pins them.
66
+ - **A refusal on Bob or OpenCode asks the model to relay the text word for word,** and a Bob warning says the call ran without a prompt.
67
+ - **OpenCode shows the explanation before the dialog,** on the two asks it has: a note on V2, a toast on V1.
68
+ - **The commit and push ask is one line,** because it is routine.
69
+ - **The web console's Gate asks panel shows a dot and a legend** in place of the long install badge, in the Library's colour.
70
+ - **Excluding *Persist Insight* or *Commands Must Return* drops its hook too,** as excluding *Consent Before Push* already did. Building without the rule's pack does the same. Process 1 off (`--no-rule-store`): a write to `user-rules.md` or `user-rules.draft.md`, by a write tool or a parsed shell write, the hard-link check included, is ordinary work on every host: `rule-gate`, `git-gate`, Bob's `tool-gate` and the OpenCode guard stand down, and OpenCode's `permission.edit` keys on those files are swept at the next rebuild. Ops 2 off (`--no-root-scan`): the root-scan check stands down in `git-gate`, Bob's `tool-gate` and the guard. The OpenCode guard reads the state from the install's `Active packs:` and `Excluded rules:` lines. Every other check stays, and the change report still lists a rule-file change, since no prompt approved it. With process 1 off that report is the only signal, and an agent that writes `memory/.own-writes.json` can hide a change from it. Including the rule again re-arms the hook at the next rebuild. A build that keeps both rules is unchanged. The Constitution page reads *with text* for both, drops the *the hook still asks* note for them, and the exclude confirm says the hook goes too.
71
+ - **Memory is written freely, with no prompt.** *Persist Insight* now gates only standing rules: a write to `user-rules.md` or the rule draft `user-rules.draft.md` still asks on Claude Code and OpenClaude, blocks on Bob, and gets OpenCode's own prompt or a refusal. `MEMORY.md` and the fact files in a memory store pass on every host, by a write tool and by a shell command. You see each memory afterwards in the web console, and a shell write to one still shows in the change report. The doctrine text, `AGENT.md` ยง5, the `rule` skill (the agent sorts a fact from a rule itself and writes a fact at once) and the memory-curator say the same. OpenCode drops the `permission.edit` asks on `MEMORY.md` and `memory/*.md`: a rebuild sweeps the ones an install recorded, so an install keeps prompting until it re-emits.
72
+ - **Self-improvement notes are written freely, too.** A skill writes its correction into `skill-notes/` with no prompt, and a caller writes an agent's `spec-feedback:` into `agent-notes/` without asking. Folding a note into `src/` is still the user's call. A note line gains an optional `situation:` field, `- [skill|general] <correction> [โ€” situation: <when it applies>] โ€” seen: <what happened> (<date>)`, and old lines without it keep working. The `skill-forge` skill probes a skill or agent note before it folds it. One past task whose original ask still exists runs as two dispatched agents from the pre-fix revision: one is told to read no notes file, the other gets the note inlined. The `fresh-eyes` skill freezes one rubric from the ask and rules both results blind against it. The note is folded only when it wins, on the result or on a stated process gain; on a tie or a loss the user keeps or deletes it. That costs two runs and a validator per note, and a trivial wording fix skips the probe. The `geneseed diff` report now points at that probe instead of "fold each one". No gate asked on a notes write before this change, so only the skill and agent text and that report change, after a rebuild.
73
+ - **A second name of a rule file asks like the rule file.** A hard link has no target to follow, so the gates compare a hard-linked target's device and inode with the known rule files (the install's, the shared tier's, the project's, and those beside `$GENESEED_HARNESS` and `$GENESEED_MEMORY`) on every host: a memory file hard-linked to `user-rules.md` no longer passes. Any other hard-linked file, a pnpm store's for example, still passes.
74
+ - **A memory phrased as an instruction to later sessions is a standing rule.** The doctrine and the `rule` skill say so: "alwaysโ€ฆ", "neverโ€ฆ" or `force: constraint` goes through the rule branch, with consent.
75
+ - **The change report watches the rule draft and the project layer's rule files,** at the session's git root, on every host.
76
+ - **The Activity Garden stands each repository's trees on a wooden shelf.** A brass plate on the plank names the repository and its session count, replacing the shelf heading. Under each pot a caption shows the session title on two lines at most, the install and status pills (working green, your move amber, blocked red, idle grey) and the turns and context; the floating label above the tree is gone. On a narrow screen a shelf's trees stack onto several planks. The plank and plate have light-mode colours. The plate asks for Fraunces and falls back to the system serif, since no font package is added.
77
+ - **The Activity Garden no longer shows Recently ended sessions.** The list view keeps the section, its fold and the hosts and projects it adds to the filters; in the Garden view only live sessions show and the filters offer only their hosts and projects.
78
+ - **The web console's left rail no longer ends in a status card.** The install, doctor, local edits, build age and Voice button live on Installs, Doctor, Diff and Overview. The voice switch leaves the rail with it: a voice is set per install on Installs, which already rebuilds in place.
79
+ - **The web console's rail is regrouped.** Pages sit under Govern, Build, Run and Help headers, each icon in a chip tinted by its group (light mode has its own pastel pair), and a header button collapses the rail to a 64 px strip of chips. The choice is kept per browser.
80
+ - **A Foreman worker can lead its own team.** It can start read-only helpers at any time, and writing sub-workers in worktrees branched from its own. It commits and merges their branches into its own branch, locally, and never pushes or merges beyond it. Nesting stops at session โ†’ worker โ†’ sub-worker. The git gate lets a sub-agent's commit or merge through without a prompt in a linked worktree on a branch that is not shared; a push, a command with one, or a session that only runs in a worktree still asks. *Consent Before Push* names this batch beside the loop one. Each worker reports a one-line status: by `SendMessage` on Claude Code, in `notebook/foreman/<task>.status` on OpenCode and Bob.
81
+ - **The subagent depth is capped at two where the host allows it.** Claude Code installs write `env.CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH = "2"`, and OpenCode installs write `"subagent_depth": 2`, each only when the key is absent. Uninstall removes the Claude key while it still reads `"2"`; the OpenCode key stays, as `lsp` does. OpenClaude and Bob get no key.
82
+
83
+ ### Fixed
84
+
85
+ - **An `Active packs:` or `Excluded rules:` line outside Geneseed's block no longer counts.** In a shared `CLAUDE.md` or `AGENTS.md` both are read from the managed block only, as the gate switches already were. A line appended to the user's part of the file used to drop packs or rules at the next rebuild, and their hooks with them (process 5's consent ask included). A generated `AGENT.md` is still read whole.
86
+ - **An OpenCode project install asks before an edit tool writes `.opencode/AGENT.md`.** The guard reads that file before the project's own carrier, so a file planted there could set its gate markers and rule exclusions. Its `permission.edit` key was written for a global install only; the guard already refused a shell write to it.
87
+ - **The Constitution table no longer crushes its Rule column.** It folds by the width it has (a container query), not the window: Latin name first, under the rule name; then Status and Enforced by, as chips under it; at phone width No. moves above the name. Rule keeps 220 px, the two switch columns stay at 44 px or more, and every band's header drops the same columns as its rows. At a 1274 px window, beside the side panels, rule names and "10 asks" no longer wrap word by word and the Latin name no longer overlaps the Status pill.
88
+ - **A gate marker outside the managed block no longer disarms a gate.** In a `CLAUDE.md` or `AGENTS.md`, every gate marker now counts only inside the `<!-- BEGIN GENESEED -->` block. Before, an appended line passed unasked and the next rebuild emitted the flag. A write tool that changes that block asks under External Gate, and an edit outside it stays silent. Bob global's `rules/geneseed.md` is now protected. A shell edit inside the block, or one that puts a fake block before it, stays a limit.
89
+ Run `geneseed rebuild-all` before you switch either one off: an older hook shim refuses the new flag, and the gate verb then lets every call through.
90
+
91
+ ## [5.0.2] โ€” 2026-11-07
92
+
93
+ PowerShell write cmdlets are parsed like their Unix forms, and a suite can no longer write the real tier unseen.
94
+
95
+ ### Added
96
+ - **PowerShell writes are parsed forms on every host.** On Windows PowerShell is the normal shell, and a live `Add-Content -Path "$HOME\.config\geneseed\user-rules.md" -Value "..."` on OpenCode 2.2.5 reached the store with no prompt. `shellWriteTargets` and its guard twin now read `Add-Content`, `Set-Content`, `Out-File`, `Clear-Content`, `Remove-Item`, `Copy-Item`, `Move-Item`, `New-Item` and `Rename-Item`, the aliases `ac`, `sc`, `del`, `copy`, `move`, `ni` and `ren`, and `rm`, `cp` and `mv` with a named parameter, in any case. A pipe into one counts. The outcomes are those of the other parsed forms: ask where the host can ask, refuse on OpenCode 1, warn on Bob. The protected-check and gate-configuration checks see these forms too. It is a parser, not a text scan: `Get-Content MEMORY.md` and a commit message naming the file stay free, and what it cannot read it leaves out. `pwsh -c` stays unread, as `bash -c` does. Shell is still not a boundary.
97
+ - **A path that opens with the home is read, in every parsed form:** `~`, `$HOME`, `${HOME}`, `$env:HOME` and `$env:USERPROFILE`, so `echo x >> "$HOME/user-rules.md"` is seen as well.
98
+
99
+ ### Fixed
100
+ - **A PowerShell here-string is data to the shell-write reader.** An apostrophe in a commit message could unpair the quotes and read a following line as a command. This holds only with a PowerShell cue, the tool's name or a `Verb-Noun` word outside the here-string: to bash `@'` is a plain quote, and what follows it is read.
101
+ - **The test suite no longer writes the real machine tier.** The OpenCode 2 change-report test ran with the real home, so its fixture's path landed in `~/.config/geneseed/.store-report.json`. The test now has its own home. `tests/shim_intact.mjs` fails if the report names a path in the checkout's `adapters/` or `tests/` or in the temp root, and CI runs the suite against a fenced, empty tier that must stay empty.
102
+
11
103
  ## [5.0.1] โ€” 2026-11-06
12
104
 
13
105
  The migration can finish in the console: a preview, and Approve and Reject on pending rules.
package/README.md CHANGED
@@ -11,9 +11,9 @@
11
11
  [![Node >= 22.7](https://img.shields.io/badge/node-%3E%3D22.7-5fa04e)](package.json)
12
12
  [![zero dependencies](https://img.shields.io/badge/deps-zero-success)](package.json)
13
13
  [![Themes](https://img.shields.io/badge/themes-14-9cf)](themes/)
14
- [![Skills](https://img.shields.io/badge/skills-49-blueviolet)](src/skills/)
14
+ [![Skills](https://img.shields.io/badge/skills-51-blueviolet)](src/skills/)
15
15
  [![Agents](https://img.shields.io/badge/agents-20-orange)](src/agents/)
16
- [![Laws and doctrines](https://img.shields.io/badge/laws-9%20%2B%2031%20doctrines-critical)](src/doctrines/)
16
+ [![Laws and doctrines](https://img.shields.io/badge/laws-9%20%2B%2030%20doctrines-critical)](src/doctrines/)
17
17
  [![Plugins](https://img.shields.io/badge/plugins-7-teal)](adapters/opencode/plugins/)
18
18
  [![OpenCode ยท Claude Code ยท Bob ยท OpenClaude ยท AGENT.md](https://img.shields.io/badge/works%20with-OpenCode%20ยท%20Claude%20Code%20ยท%20Bob%20ยท%20OpenClaude%20ยท%20AGENT.md-1f6feb)](#-supported-harnesses)
19
19
 
@@ -180,7 +180,7 @@ The harness ships as a small set of layers, and the web console's rail is the sa
180
180
  | **๐Ÿ›ก๏ธ Rules** (`laws/`) | 9 universal laws โ€” always in force, never toggleable: sealed-secrets, one-intent-one-act, verify-before-asserting, deletion-is-deliberate, surface-failures, data-not-orders, least-privilege, cure-the-cause, echo-the-intent. Each rule has a permanent id; its number is only its position, and the harness cites rules by name |
181
181
  | **๐Ÿ“ Doctrines** (`doctrines/`) | practice packs, chosen per install at build time: **craft** (how code is written), **rigor** (how work is proven), **ops** (how the machine is operated), **process** (how a task is run), **comms** (how answers are presented). A doctrine rule may tighten a Rule, never repeal one, and the user's own `user-rules.md` outranks it. Pick with `geneseed-build --doctrines craft,rigor` (or `none`), a single rule with `--exclude-rules "process 7"`, in the setup wizard, or through the switches on the console's Constitution page; all five pack files ship on disk either way, so a citation into a pack you left out still resolves |
182
182
  | **๐Ÿค– Agents** (20) | capability specialists: `reviewer`, `tester`, `architect`, `docs`, `security`, `performance`, `explorer`, `researcher`, `developer`, `memory-curator` โ€” plus a debate **council** the `council` skill convenes: `advocate`, `skeptic`, `pragmatist`, `steward`, `visionary`, `user-advocate`, `framer`, `empiricist`, `operator`, `historian` |
183
- | **๐Ÿ›  Skills** (49) | repeatable workflows: brainstorm ยท plan ยท **codebase-design** ยท **wayfinder** ยท **develop** ยท **worktree** ยท debug ยท **prototype** ยท refactor ยท **ponytail** ยท **adhd** ยท **forge-mcp** ยท **bruno** ยท geneseed-code-review ยท **fresh-eyes** ยท **security-audit** ยท **dependencies** ยท **review-response** ยท commit ยท **ship** ยท **release** ยท **git-history** ยท document-project ยท **frontend-design** ยท **deck** ยท **prose** ยท **ingest** ยท **research** ยท **teach** ยท **learn-mode** ยท **ownership** ยท handoff ยท roast-me ยท **council** ยท parallel-agents ยท **workflow** ยท **wiki** ยท **geneseed** ยท **rule** ยท **profile** ยท **skill-forge** ยท **pipeline** ยท **loop** ยท **brick-forge** ยท **daydream** ยท **react-view-transitions** ยท **token-report** ยท **explain-changes** ยท **diagram-design** |
183
+ | **๐Ÿ›  Skills** (51) | repeatable workflows: brainstorm ยท plan ยท **codebase-design** ยท **wayfinder** ยท **develop** ยท **worktree** ยท debug ยท **prototype** ยท refactor ยท **ponytail** ยท **adhd** ยท **forge-mcp** ยท **bruno** ยท geneseed-code-review ยท **fresh-eyes** ยท **security-audit** ยท **dependencies** ยท **review-response** ยท commit ยท **ship** ยท **release** ยท **git-history** ยท document-project ยท **frontend-design** ยท **deck** ยท **prose** ยท **ingest** ยท **research** ยท **teach** ยท **learn-mode** ยท **ownership** ยท handoff ยท roast-me ยท **council** ยท parallel-agents ยท **workflow** ยท **wiki** ยท **geneseed** ยท **rule** ยท **profile** ยท **skill-forge** ยท **pipeline** ยท **loop** ยท **factory** ยท **factory-forge** ยท **brick-forge** ยท **daydream** ยท **react-view-transitions** ยท **token-report** ยท **explain-changes** ยท **diagram-design** |
184
184
  | **๐Ÿ”Œ Plugins** (OpenCode) | `geneseed-context` injects project docs *and your machine wiki* every session (and across compaction); `geneseed-learn` distils memory at session end; `geneseed-guard` enforces the safety Laws and protected wiki folders at the tool boundary; `geneseed-workflow` registers the `workflow` tool that runs saved orchestration scripts; `geneseed-notify` sends a native OS notification when a long run finishes; `geneseed-ponytail` holds a minimal-code mode (`/ponytail lite\|full\|ultra\|off`), opt-in, injecting the laziest-that-works ruleset every turn so it doesn't drift; `geneseed-activity` streams what each session is doing to the web console's Activity view |
185
185
  | **๐Ÿง  Memory** (`memory/`) | one-fact-per-file durable knowledge, indexed by `MEMORY.md` (git-ignored, personal) |
186
186
  | **๐Ÿ”— Shared tier** (`~/.config/geneseed`) | one machine-wide home for memory, your rules, profile, wiki manifest, exclude paths and notes, read by every global install on every host; existing stores [fold into it](docs/guides/upgrade-to-5.md) on the next global rebuild, and a project install opts in with `--shared-tier on` |
@@ -386,7 +386,7 @@ Some skills and agents are adapted from other open-source skill collections, und
386
386
  - `superpowers` โ€” [obra/superpowers](https://github.com/obra/superpowers) by Jesse Vincent (MIT): the core of debug, the size step and builder check of brainstorm, the plan rules of plan, the reviewer brief behind geneseed-code-review and the reviewer agent, the review-handling steps of review-response, and the ruling format of pipeline and parallel-agents.
387
387
  - `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
388
  - `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
- - `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.
389
+ - `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.
390
390
  - `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
391
 
392
392
  ## ๐Ÿ“„ 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.0.1**.
23
+ > string. Current label: **5.0.4**.
24
24
 
25
25
  ## Capabilities
26
26
 
@@ -29,7 +29,7 @@ Every row below is present in the tree today; "Spec" names the design record.
29
29
  | Capability | What it is | Spec |
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
- | **Laws / Agents / Skills / Memory / Notebook** | 9 laws, 20 agents, 49 skills, the memory convention, and the agent's sovereign notebook | `2026-06-11-notebook-sovereign-space` ยท `2026-06-10-notebook-agent-own-space` |
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
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` |
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
35
  | **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements.md` back-port | `2026-06-12-improvements-export` |
@@ -17,7 +17,8 @@ absolute-path hooks instead โ€” `geneseed setup` does that for you.) It:
17
17
  - on **PreToolUse** (matcher `Bash|PowerShell`), runs `geneseed-hook git-gate` โ€” the tool-boundary
18
18
  half of Doctrine process 5 (*consent before every commit and push*) and of the
19
19
  destructive-git Rule. Drop the `process` pack (or exclude process 5) and the hook stays,
20
- wired with `--no-consent`: commits and pushes pass without asking, while the
20
+ wired with `--no-consent`: commits and pushes pass without asking (excluding process 1 or ops 2,
21
+ or their pack, adds `--no-rule-store` / `--no-root-scan` the same way), while the
21
22
  Law IV refusals (asked only on real data loss: a force-push to `main`, a `reset --hard`
22
23
  that abandons unpushed commits, an `rm` git cannot undo) stay in every build unless the install is
23
24
  built `--no-deletion-gate`, which appends that flag and stands the real-loss check down
@@ -39,14 +40,15 @@ absolute-path hooks instead โ€” `geneseed setup` does that for you.) It:
39
40
  over-matching the tool surface is harmless.
40
41
  - on **PreToolUse** (matcher `Write|Edit|NotebookEdit`), runs
41
42
  `geneseed-hook rule-gate` โ€” refuses a write that would put a credential into a tracked
42
- file, and asks first on the first write to `user-rules.md` or a memory file (whether
43
- something you want kept is a rule or a fact is your call). In an application repo (a git
43
+ file, and asks first on a write to `user-rules.md` or the rule draft (a standing rule is
44
+ your call; memory is written freely, and you see it afterwards in the web console). In an application repo (a git
44
45
  root holding a build manifest) whose root `AGENTS.md` has no `## Ownership` section, it also
45
46
  denies the session's first write once, with a reason addressed to the agent: propose the
46
47
  ownership setup now, skip this session, or skip in this repo until asked; the next write
47
48
  passes, and sub-agents defer. Off per repo with `mode: off` in that section, for one developer
48
49
  in one repo with `Setup: declined <YYYY-MM-DD>` in their personal `.geneseed/ownership.md`,
49
- per install with `--no-ownership-gate`. Ordinary edits pass.
50
+ per install with `--no-ownership-gate`. `--no-external-gate` and `--no-test-note` stop the protected-check and
51
+ gate-configuration asks and the weakened-test note. Ordinary edits pass.
50
52
  (`MultiEdit` is not a Claude Code tool and is not in the matcher; the gate reads
51
53
  `edits[].new_string` as a cheap guard regardless.)
52
54
  - on **SessionStart**, every source (`startup`, `resume`, `clear`, `compact`, `fork`), runs
@@ -76,7 +78,11 @@ absolute-path hooks instead โ€” `geneseed setup` does that for you.) It:
76
78
  and auto-compaction is the moment that window is about to be summarised away.
77
79
  This captures memory *before* the summary; the SessionStart `context` hook (which
78
80
  also fires on the `compact` source) re-seeds context *after* it.
79
- - on **UserPromptSubmit**, **SessionEnd** and **SubagentStart**, runs `geneseed-hook activity`, which decides
81
+ - on **SubagentStart**, runs `geneseed-hook context`, which reads the event name and hands the
82
+ sub-agent your `user-rules.md` layers (tier, install, project root) as one JSON
83
+ `hookSpecificOutput.additionalContext`. No sub-agent receives the SessionStart output, so this
84
+ is the only way your rules reach one.
85
+ - on **UserPromptSubmit** and **SessionEnd**, runs `geneseed-hook activity`, which decides
80
86
  nothing and prints nothing: it records the session for the web console's Activity view.
81
87
  Every other hook above feeds that view too, after it has decided. `GENESEED_ACTIVITY=off`
82
88
  (or the console's toggle) turns it off; see `docs/reference/plugin-activity.md`.
@@ -58,7 +58,9 @@ global config file.
58
58
  The Claude group set, unchanged: `PreToolUse` (git gate on `Bash|PowerShell`, rule gate on
59
59
  writes), `SessionStart` (context on every source โ€” one matcher-less group covers
60
60
  `startup`, `resume`, `clear`, `compact` and `fork` alike), `Stop`,
61
- `SubagentStop` and `PreCompact` (learn), and `UserPromptSubmit` and `SessionEnd`
61
+ `SubagentStop` and `PreCompact` (learn), `SubagentStart` (`context`, which hands a sub-agent
62
+ your `user-rules.md` layers as `hookSpecificOutput.additionalContext`; OpenClaude 0.32.0's
63
+ bundle reads that field for this event), and `UserPromptSubmit` and `SessionEnd`
62
64
  (`activity`, which feeds the web console's Activity view). OpenClaude reads Claude's
63
65
  `hookSpecificOutput.permissionDecision`, so the gates **ask** where Claude asks.
64
66
  The context hook carries `--host openclaude` for one reason. It tells the hook
@@ -92,6 +92,7 @@ changed for each plugin:
92
92
  | throwaway session + `prompt` to distil | `ctx.generate.text({ prompt, model })`: one stateless call |
93
93
  | a hook throws to block a tool | a throw is a **defect that fails the whole step**. The guard renames the call instead (see `geneseed-guard.js`) |
94
94
  | `permission.ask` is declared and never called; only a static `permission.edit` rule asks | `permission.hook("evaluate")` runs for every `permission.assert`, after the rules, and may raise the effect to `ask`: `edit` per file, and `shell` per parsed command with `source.id` naming the call. The guard uses both for rule-store writes |
95
+ | `Permission.ask` calls no plugin hook, so the guard's note before a prompt is `client.tui.showToast` from `tool.execute.before` (`duration: 120000`, `query: { directory }`). It shows with the dialog, keeps newlines and expires under it. `data: true` does not prove a TUI saw it | `ctx.session.synthetic` from `evaluate`, which carries `sessionID`, with `resume: false`. The TUI renders `description` and the model gets `text`, so the block goes in the first and one short line in the second. `opencode run` and `mini` drop it. An unattended session posts it, then denies |
95
96
  | `@opencode-ai/plugin` `tool()` helper | `@opencode/plugin`; a plain JSON-schema `input` needs no helper |
96
97
  | `todo.updated` | no V2 event. The activity cards show no todos on V2 |
97
98
  | user-message `summary.diffs` (files touched) | `session.step.ended` / `step.failed` `files`: paths only, so the activity cards show files with no line counts, and a revert never removes one |
@@ -99,6 +100,8 @@ changed for each plugin:
99
100
  | tool part carries its name | `session.tool.called` has no name; it rides on `session.tool.input.started` |
100
101
  | tools `bash`, `apply_patch`, `task` | renamed `shell`, `patch`, `subagent` (the old ids are aliases). The guard's substring classes cover both spellings; its usage counter takes `subagent` (type under `agent`) beside `task`, since the hook sees the name before alias resolution |
101
102
 
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
+
102
105
  None of this is checked by a mock alone: `node tests/host_canary.mjs` starts the real V1 and V2
103
106
  and fails on the host's own `failed to load plugin` log line.
104
107
 
@@ -1026,7 +1026,7 @@ function testEditPairs(tool, args, before) {
1026
1026
  }
1027
1027
  async function noteWeakened(root, sid, tool, args) {
1028
1028
  try {
1029
- if (!sid || !args) return
1029
+ if (!sid || !args || await testNoteOff()) return
1030
1030
  const file = typeof args.filePath === "string" ? path.resolve(root, args.filePath) : null
1031
1031
  let before = ""
1032
1032
  if (file && String(tool).toLowerCase() === "write" && isTestPath(path.relative(root, file))) {
@@ -1077,6 +1077,17 @@ function doneGateOff() {
1077
1077
  })().catch(() => false)
1078
1078
  return doneGateOffOnce
1079
1079
  }
1080
+ // `--no-test-note`, the same contract: `Test note: off` stops the weakened-test reminder and only it.
1081
+ let testNoteOffOnce = null
1082
+ function testNoteOff() {
1083
+ testNoteOffOnce ??= (async () => {
1084
+ const dir = await harnessDir()
1085
+ if (!dir) return false
1086
+ const text = await fs.readFile(path.join(dir, "AGENT.md"), "utf8")
1087
+ return /^Test note:[ \t]*off[ \t]*\r?$/m.test(text)
1088
+ })().catch(() => false)
1089
+ return testNoteOffOnce
1090
+ }
1080
1091
 
1081
1092
  // null when the project has no list (or it is unreadable): then the checks are inferred.
1082
1093
  async function readDoneChecks(root) {