geneseed 5.0.0 → 5.0.3

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 (138) hide show
  1. package/CHANGELOG.md +70 -0
  2. package/README.md +1 -1
  3. package/SHIPPED.md +1 -1
  4. package/adapters/claude-code/README.md +6 -4
  5. package/adapters/opencode/HOW-OPENCODE-LOADS.md +3 -0
  6. package/adapters/opencode/plugins/geneseed-context.js +13 -2
  7. package/adapters/opencode/plugins/geneseed-guard.js +595 -74
  8. package/adapters/opencode/plugins/geneseed-learn.js +1 -1
  9. package/bin/geneseed-hook.mjs +21 -7
  10. package/docs/PRD.md +1 -1
  11. package/docs/concepts/enforcement-table.md +22 -3
  12. package/docs/concepts/exclusions.md +48 -2
  13. package/docs/concepts/foreman-mode.md +19 -4
  14. package/docs/concepts/hook-gates.md +1 -1
  15. package/docs/concepts/hooks.md +53 -12
  16. package/docs/concepts/host-matrix.md +4 -3
  17. package/docs/concepts/hosts.md +1 -1
  18. package/docs/concepts/kits.md +18 -0
  19. package/docs/concepts/shared-tier.md +5 -5
  20. package/docs/concepts/skills.md +1 -1
  21. package/docs/extending.md +3 -1
  22. package/docs/guides/autostart.md +27 -3
  23. package/docs/guides/choose-your-setup.md +1 -1
  24. package/docs/guides/migrate.md +5 -3
  25. package/docs/guides/uninstall.md +1 -1
  26. package/docs/guides/upgrade-to-5.md +6 -4
  27. package/docs/reference/plugin-context.md +1 -1
  28. package/docs/reference/plugin-guard.md +24 -5
  29. package/docs/reference/troubleshoot-doctor.md +2 -2
  30. package/docs/understand/a-day.md +9 -5
  31. package/docs/web-ui.md +78 -20
  32. package/harness.config.json +1 -1
  33. package/js/README.md +3 -2
  34. package/js/build/emit-claude.mjs +9 -1
  35. package/js/build/emit-opencode.mjs +2 -1
  36. package/js/build/fold.mjs +7 -7
  37. package/js/build/rule-decide.mjs +273 -0
  38. package/js/build/source.mjs +9 -3
  39. package/js/cli-table.json +122 -2
  40. package/js/hosts/geneseed-dir.mjs +1 -1
  41. package/js/hosts/hooks-context.mjs +9 -7
  42. package/js/hosts/hooks-done.mjs +3 -1
  43. package/js/hosts/hooks-learn.mjs +1 -1
  44. package/js/hosts/hooks-prims.mjs +270 -0
  45. package/js/hosts/hooks.mjs +409 -151
  46. package/js/hosts/hosts.mjs +22 -0
  47. package/js/hosts/installs.mjs +13 -9
  48. package/js/hosts/memory-files.mjs +2 -2
  49. package/js/hosts/settings.mjs +123 -23
  50. package/js/hosts/shim.mjs +155 -7
  51. package/js/hosts/store-watch.mjs +41 -14
  52. package/js/inspect/diff.mjs +2 -1
  53. package/js/inspect/inventory.mjs +1 -0
  54. package/js/inspect/registry.mjs +4 -2
  55. package/js/inspect/validate.mjs +1 -1
  56. package/js/lib/paths.mjs +13 -0
  57. package/js/maintain/migrate.mjs +60 -22
  58. package/js/maintain/uninstall.mjs +5 -1
  59. package/js/web/actions.mjs +17 -1
  60. package/js/web/api.mjs +22 -16
  61. package/js/web/handler.mjs +2 -0
  62. package/js/web/routes.mjs +9 -4
  63. package/js/web/update-check.mjs +2 -2
  64. package/js/web/user-files.mjs +38 -11
  65. package/package.json +1 -1
  66. package/registry.json +21 -0
  67. package/src/AGENT.md.tmpl +17 -21
  68. package/src/agents/_self-improvement.md +7 -6
  69. package/src/agents/developer.md +3 -2
  70. package/src/agents/docker-expert.md +1 -0
  71. package/src/agents/memory-curator.md +3 -2
  72. package/src/doctrines/process.md +24 -19
  73. package/src/kits/ci-pipelines/rules.md +10 -0
  74. package/src/kits/ci-pipelines.json +14 -0
  75. package/src/kits/docker/rules.md +11 -0
  76. package/src/kits/docker.json +12 -0
  77. package/src/memory/README.md +5 -4
  78. package/src/modes/foreman.md +23 -10
  79. package/src/notebook/README.md +1 -1
  80. package/src/skills/_self-improvement.md +12 -9
  81. package/src/skills/compose-ops.md +58 -0
  82. package/src/skills/gitlab-ci.md +51 -0
  83. package/src/skills/jenkins-pipeline.md +56 -0
  84. package/src/skills/pipeline.md +2 -2
  85. package/src/skills/rule/approve.md +11 -5
  86. package/src/skills/rule.md +26 -19
  87. package/src/skills/skill-forge.md +24 -6
  88. package/themes/_TEMPLATE.json +5 -2
  89. package/themes/biker.json +5 -2
  90. package/themes/commentator.json +5 -2
  91. package/themes/cyberpunk.json +5 -2
  92. package/themes/gamer.json +5 -2
  93. package/themes/imperial.json +5 -2
  94. package/themes/joker.json +5 -2
  95. package/themes/marvin.json +5 -2
  96. package/themes/mean.json +5 -2
  97. package/themes/military.json +5 -2
  98. package/themes/neutral.json +5 -2
  99. package/themes/pirate.json +5 -2
  100. package/themes/sports.json +5 -2
  101. package/themes/verstappen.json +5 -2
  102. package/themes/wizard.json +5 -2
  103. package/web/dist/assets/Activity-Ck_Xffpo.js +1 -0
  104. package/web/dist/assets/ActivityDetail-CBxVS4mU.js +1 -0
  105. package/web/dist/assets/{Bonsai-B_y20b3i.js → Bonsai-BlOwsvW6.js} +1 -1
  106. package/web/dist/assets/{CopyButton-CHQte7Ap.js → CopyButton-DFMOIGbe.js} +1 -1
  107. package/web/dist/assets/Dashboard-BUdUTjbB.js +2 -0
  108. package/web/dist/assets/{Docs-Dgv_MWfT.js → Docs-D_2Jt6gU.js} +3 -3
  109. package/web/dist/assets/{GreenhouseView-CSzTMSl_.js → GreenhouseView-WalcX5bp.js} +1 -1
  110. package/web/dist/assets/Installs-UGiPDMDt.js +3 -0
  111. package/web/dist/assets/{JournalView-CvRk1-m5.js → JournalView-CZtXQz-v.js} +1 -1
  112. package/web/dist/assets/Kits-XQHsazCN.js +1 -0
  113. package/web/dist/assets/Laws-B6A55S-2.js +4 -0
  114. package/web/dist/assets/Library-D7L0Wdbh.js +3 -0
  115. package/web/dist/assets/Loops-C0loS73u.js +2 -0
  116. package/web/dist/assets/{OperatorHudView-DuGz_sTk.js → OperatorHudView-CeDw5qMB.js} +1 -1
  117. package/web/dist/assets/Personal-PVmGA2-M.js +2 -0
  118. package/web/dist/assets/{RailCats-AW92uhsX.js → RailCats-BGZnJ6fa.js} +1 -1
  119. package/web/dist/assets/Settings-DWuxwh4i.js +1 -0
  120. package/web/dist/assets/Tabs-d2RIRAKT.js +1 -0
  121. package/web/dist/assets/api-BMFDSXoB.js +1 -0
  122. package/web/dist/assets/index-BEI5ugYQ.css +1 -0
  123. package/web/dist/assets/index-BNttaGQb.js +6 -0
  124. package/web/dist/index.html +3 -3
  125. package/web/dist/assets/Activity-D8G4eClY.js +0 -1
  126. package/web/dist/assets/ActivityDetail-BtOBYk3M.js +0 -1
  127. package/web/dist/assets/Dashboard-B8uXeJZ_.js +0 -2
  128. package/web/dist/assets/Installs-BDk9lqBI.js +0 -3
  129. package/web/dist/assets/Kits-CoITzxWM.js +0 -1
  130. package/web/dist/assets/Laws-Ctf5r9rE.js +0 -3
  131. package/web/dist/assets/Library-DNwHYVXt.js +0 -3
  132. package/web/dist/assets/Loops-S85PMQ8m.js +0 -2
  133. package/web/dist/assets/Personal-afJNwvRS.js +0 -2
  134. package/web/dist/assets/Settings-CGDFz-6j.js +0 -1
  135. package/web/dist/assets/Tabs-1qLrnqmn.js +0 -1
  136. package/web/dist/assets/api-C46vAuqp.js +0 -1
  137. package/web/dist/assets/index-COTd4TRZ.js +0 -3
  138. package/web/dist/assets/index-CtorA7uK.css +0 -1
package/CHANGELOG.md CHANGED
@@ -8,6 +8,76 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [5.0.3] — 2026-11-08
12
+
13
+ ### Added
14
+
15
+ - **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.
16
+ - **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.
17
+ - **`--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.
18
+ - **`--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.
19
+ - **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.
20
+ - **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.
21
+ - **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.
22
+ - **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.
23
+ - **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.
24
+
25
+ ### Changed
26
+
27
+ - **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.
28
+ - **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.
29
+ - **OpenCode shows the explanation before the dialog,** on the two asks it has: a note on V2, a toast on V1.
30
+ - **The commit and push ask is one line,** because it is routine.
31
+ - **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.
32
+ - **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.
33
+ - **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.
34
+ - **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.
35
+ - **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.
36
+ - **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.
37
+ - **The change report watches the rule draft and the project layer's rule files,** at the session's git root, on every host.
38
+ - **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.
39
+ - **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.
40
+ - **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.
41
+ - **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.
42
+ - **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.
43
+ - **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.
44
+
45
+ ### Fixed
46
+
47
+ - **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.
48
+ - **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.
49
+ - **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.
50
+ - **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.
51
+ 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.
52
+
53
+ ## [5.0.2] — 2026-11-07
54
+
55
+ PowerShell write cmdlets are parsed like their Unix forms, and a suite can no longer write the real tier unseen.
56
+
57
+ ### Added
58
+ - **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.
59
+ - **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.
60
+
61
+ ### Fixed
62
+ - **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.
63
+ - **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.
64
+
65
+ ## [5.0.1] — 2026-11-06
66
+
67
+ The migration can finish in the console: a preview, and Approve and Reject on pending rules.
68
+
69
+ ### Added
70
+ - **The console finishes the 5.0 migration with no terminal.** *Preview next rebuild* on the Installs page shows what each global install would fold, and any orphans, and writes nothing. It is the fold and orphan half of `geneseed migrate --dry-run`, through one new function (`migratePreview`) and one read-only route.
71
+ - **Approve and Reject on the Rules page.** The *Pending* section now decides what the fold drafted: *Approve* and *Reject* on a rule, and for a profile or wiki pointer the two files with *Use the host file*, *Use the shared file* and *Keep both*. The steps are the rule skill's own, in one module (`js/build/rule-decide.mjs`): target file, ledger row, draft, so a failed step leaves the rule in force. A stale page reloads and applies nothing. A decision that moves a file offers *Rebuild all*, and none applies while a job runs. Only what the fold drafted is decidable. The change report lists a decision like any other console write, and its line now says one may be yours: the console's token is readable by anything on the machine, so the console is no boundary against an agent with a shell.
72
+
73
+ ### Changed
74
+ - **A real `geneseed migrate` runs only from the npm package.** From a git clone or a bundle it refuses with exit 3 before any write, and says to use `geneseed update`: the rebuild there would point the hook shim back at the same copy. An npx cache counts as outside the package. `--dry-run` works from anywhere, and there it says a real run would refuse instead of listing re-emits. A run from the npm package does not change. The guides and `migrate --help` now say that the rebuild, not `migrate`, rewrites the shim, and that it names whichever Geneseed ran it.
75
+ - **The rule skill's approval flow names the console as a second decider**, and reads the retired files of each host's config directory: `installs.json` holds project roots only, so the old wording found none.
76
+
77
+ ### Fixed
78
+ - **The sidebar no longer says `built never` on a live Claude-family install.** The Overview read the mtime of `AGENT.md`, which such an install lacks. It now reads the version marker, as the fleet does.
79
+ - **`geneseed migrate --dry-run` writes nothing, as it says.** It used to prune dead rows from `installs.json` while it listed the installs.
80
+
11
81
  ## [5.0.0] — 2026-11-06
12
82
 
13
83
  Memory, rules, profile and the wiki move to one machine-wide shared tier at `~/.config/geneseed`, and existing stores fold into it on the next global emit. Breaking: see Removed.
package/README.md CHANGED
@@ -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.0**.
23
+ > string. Current label: **5.0.3**.
24
24
 
25
25
  ## Capabilities
26
26
 
@@ -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
@@ -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
 
@@ -280,7 +280,7 @@ async function draftLine() {
280
280
  try {
281
281
  const { items } = JSON.parse(await fs.readFile(path.join(machineDir(), ".fold-state.json"), "utf8"))
282
282
  const n = Object.values(items ?? {}).filter((i) => i?.state === "pending").length
283
- return n ? `[drafts] ${n} drafted item${n === 1 ? "" : "s"} in user-rules.draft.md wait${n === 1 ? "s" : ""} for the user's decision (the rule skill).` : null
283
+ return n ? `[drafts] ${n} drafted item${n === 1 ? "" : "s"} in user-rules.draft.md wait${n === 1 ? "s" : ""} for the user's decision (the rule skill or the web console).` : null
284
284
  } catch { return null }
285
285
  }
286
286
 
@@ -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) {