geneseed 4.10.0 → 4.15.1

package/CHANGELOG.md

@@ -8,6 +8,112 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
 
 ## [Unreleased]
 
+## [4.15.1] — 2026-10-23
+
+Patch: two host fixes. The first npm release since 4.14.0, so it also carries 4.15.0's comms 4 doctrine.
+
+### Upgrade notes
+- Run `geneseed rebuild-all`; nothing changes on a machine until something re-emits.
+
+### Fixed
+- OpenCode 1.x: the guard and learn plugins no longer write `[geneseed-guard] …` / `[geneseed-learn] …` lines in red over the TUI input box. Their messages now go to OpenCode's own log (`client.app.log`, service `geneseed-guard` / `geneseed-learn`). OpenCode 2 and a refused log call still use stderr. The workflow plugin's one-line load banner stays on stderr.
+- IBM Bob: the first reply now starts with the theme's readiness line. Both Bob carriers (global `rules/geneseed.md`, the project's `AGENTS.md` block) open with a short first-reply override; without it, Bob's own greeting won. A bare "hi" still gets Bob's fixed welcome. Run `geneseed rebuild-all` to pick it up.
+
+## [4.15.0] — 2026-10-22
+
+Minor: a new comms doctrine rule makes every generated agent write its prose in ASD-STE100 Simplified Technical English.
+
+### Upgrade notes
+- Run `geneseed rebuild-all` to get the new rule; nothing changes on a machine until something re-emits. To keep the old behaviour on one install, rebuild it with `--exclude-rules "comms 4"`.
+
+### Added
+- **Doctrine comms 4, Simplified Technical English.** Every generated agent writes the prose of its replies and reports in ASD-STE100: one topic per sentence (at most 20 words in an instruction, 25 in a description), imperative steps with one action each and the condition first, the active voice, no -ing forms, no dropped articles, and one word per meaning. Code, commands, paths, identifiers and quoted output stay as they are. STE is an English standard and the ontology imposes no language, so an answer in another language keeps that language and the same sentence rules; the theme keeps its voice. It is in the toggleable comms pack, not a law, per DESIGN.md Decision 7: `--exclude-rules "comms 4"` turns it off. The carrier ceilings rise by 1 003 characters (full) and 472 (lean). Run `geneseed rebuild-all` to get it.
+
+## [4.14.0] — 2026-10-22
+
+Minor: the React kit supports webpack projects as well as Vite.
+
+### Upgrade notes
+- Run `geneseed rebuild-all` to get the new kit text; nothing changes on a machine until something re-emits.
+
+### Changed
+- **The `react` kit supports webpack as well as Vite** (#368). The `react` skill reads the bundler from `package.json` and loads its side file: the new `react/webpack.md` (config, client-side routing with `historyApiFallback` and `publicPath`, `DefinePlugin` env values, a webpack build-failure table) or `react/vite.md`. The kit rules, both agents, the Jest configuration table in `react-testing` and every theme's descriptions now name both bundlers.
+
+## [4.13.0] — 2026-10-21
+
+Minor: sharper ported skills, a wiki that keeps its history, and self-improvement notes that carry their evidence.
+
+### Upgrade notes
+- Run `geneseed rebuild-all` to get the new skill and agent text; nothing changes on a machine until something re-emits. Notes already in `notebook/skill-notes/` and `notebook/agent-notes/` keep working as written; only new lines take the new format.
+
+### Changed
+- **Self-improvement notes carry their evidence and their scope** (#366). A note is now one line, `- [skill|general] <correction> — seen: <what happened, against what was expected> (<date>)`, and an agent's `spec-feedback:` line takes the same shape. `seen:` is what a correction is judged by when `geneseed diff` hands it back for folding into `src/`, and pruning drops the lines without one first. `general` marks a correction that would fix other skills or agents too, so it belongs in a law, doctrine or memory rather than one file. The `geneseed diff` report explains both markers. Agents now share one self-improvement footer (`src/agents/_self-improvement.md`) instead of 29 copies; rendered agents differ only by the new wording.
+- **The wiki writes history, not the present** (#365). Wiki claims are dated, code claims cite `owner/repo@commit`, and a correction supersedes a claim rather than rewriting it. A new report-only lint pass lists contradictions, orphans and overtaken claims without restructuring the wiki. Adapted from mattpocock/skills' chief-of-staff.
+- **The mattpocock ports are sharpened against upstream `5beb35b`** (#365):
+  - `parallel-agents`: each slice branches off the integration tip when it is dispatched and merges the tip back before returning, so a later slice no longer misses its blocker's merged work. A whole-branch review follows.
+  - `codebase-design`: an interface is designed twice, and an ADR is not silently reopened.
+  - `research` and the `researcher` agent: one read in the source that owns a claim stands on its own; any other claim still needs two sources.
+  - `ship`: the docs check moves before the push it gates.
+  - `plan`, `wayfinder`, `prototype`, `develop`, `debug`, `rule`, `brainstorm`, `handoff` and `skill-forge` get smaller fixes: slice sizing, ticket graduation, mocking only at boundaries, checking for an existing guardrail before proposing one, and trigger pruning.
+  - New credits on `parallel-agents`, `skill-forge`, `brainstorm` and `wiki`.
+
+## [4.12.0] — 2026-10-21
+
+Minor: a second opt-in kit, `react`, and the setup wizard asks about each kit on its own.
+
+### Upgrade notes
+- Nothing to rebuild unless you want the new kit. Default installs are unchanged: no kit is on. To turn it on, run `geneseed build --emit <target> --kits react` (or `--kits react,spring-boot` for both), or use **Installs → Kits** in the web console.
+
+### Added
+- **The `react` kit** (#362), for React 18 or 19 apps built with Vite, in TypeScript or JavaScript, tested with Jest and React Testing Library. Skills `react` (with side files for Vite and accessibility) and `react-testing`; agents `react-engineer` and `react-reviewer` (read-only); kit rules, and a banned-API gate that keeps `ReactDOM.render(`, `findDOMNode`, Enzyme, `react-test-renderer` and `@testing-library/react-hooks` out of kit files. Adapted from affaan-m/everything-claude-code (MIT), rewritten and condensed for Vite and Jest, with no Server Components material.
+
+### Changed
+- **The setup wizard asks one yes/no per kit** (#362). A single pick could not turn on two kits at once.
+
+### Repository
+Not in the package; how Geneseed itself is built and checked.
+- CI's golden cells run as two parallel jobs per platform, emit and CLI (#361). On Windows that leg drops from about 7 minutes in sequence to about 4. The unit suite runs at `--test-concurrency=8` on Linux and in the publish job; Windows keeps the default, where the flag bought nothing. If branch protection names the old `node-cells (<os>)` checks, they now report as `node-cells (<os>, emit)` and `node-cells (<os>, cli)`.
+- The unit suite drops three repeated full-cost runs (#363): two update-flow arms use a doctor stand-in (the real rejection and exact rollback stay in `update_git`), the packaging test counts themes in process instead of a second `doctor --all`, and `--no-deletion-gate` replays only the 67 real-loss rows. 151 s to 139 s locally, same 2012 tests.
+
+## [4.11.2] — 2026-10-21
+
+Patch: a clone install on macOS or Linux puts the `geneseed` command on your PATH.
+
+### Upgrade notes
+- Nothing to rebuild. If `geneseed` is not found in a new terminal, run `./geneseed link` from your clone and accept the offer to add `~/.local/bin` to your shell's startup file.
+
+### Fixed
+- **A clone install puts `geneseed` on your PATH on macOS and Linux** (#359). `./install` never linked the command, and `geneseed link` wrote it to `~/.local/bin`, which macOS zsh does not search, so `geneseed` was not found (reported 2026-10). `./install` now runs `link` when `geneseed` is not found yet, and `link` offers, in a terminal, to add the folder to your shell's startup file (`~/.zshrc`, or `~/.bashrc` / `~/.bash_profile` for bash). It appends one marked block, never twice; `geneseed unlink` removes it. Outside a terminal it prints the line to add, as before.
+
+## [4.11.1] — 2026-10-21
+
+Patch: the web console on a machine with only IBM Bob (or any host but OpenCode): it opens on the install you have, the first-deploy form asks a per-repo mode for its folder, and the doctor stops reading a misplaced project install as a broken bundle.
+
+### Upgrade notes
+- Restart the console after updating (`geneseed web restart`) so it serves the rebuilt UI. If a per-repo install landed in `Harness/` inside your Geneseed clone, remove it with `./geneseed uninstall --target Harness --yes`, then delete `Harness/`.
+
+### Fixed
+- **The web console works on a machine without OpenCode** (#357). It always opened on the OpenCode global dir, so with only IBM Bob installed the Overview showed the first-deploy form over a working `~/.bob`, and nothing could re-point it (the harness selector hides itself below two installs). When nothing is deployed where it looks, the console now shows the first active install it finds, a global before a project, and follows a first deploy to where it landed.
+- **The first-deploy form asks a project mode for its folder** (#357). Picking a per-repo mode (`bob`, `claude`, `opencode`, `openclaude`) sent a Build with no folder, so the files landed in `Harness/` inside the Geneseed clone, where the host never looks. The form now asks for the folder (typed or Browse…) and deploys there; Build refuses a per-repo mode it has no folder for; the portable `files` bundle is left to the CLI. To remove an install misplaced this way, run `./geneseed uninstall --target Harness --yes` in the clone, then delete `Harness/`.
+- **The doctor's committed-bundle check no longer reads a Claude, Bob or OpenClaude project install as a broken bundle** (#357). Such a tree has a `.bob/`-style data dir, not the bundle layout, so every file read "missing" (178 lines on the reported machine) and no rebuild could clear them.
+
+## [4.11.0] — 2026-10-21
+
+Minor: the self-improvement loops write to notebook notes instead of the installed skill or agent file, the web console gains a Kits section, and `./install` waits for your answers and finds tools installed for one user.
+
+### Upgrade notes
+- Run `geneseed rebuild-all` once after updating so installed skills, agents and AGENT.md carry the new self-improvement footer. Lessons the loops wrote into installed files before this release are still exported by `upgrade` into `improvements/`, as before.
+
+### Added
+- **Web console: Kits section** (#353). A top-level Kits page between Library and Loops: a list and a detail page per kit (rules, banned APIs, members linked to the Library, upstream pin and compare link, a switch per install that rebuilds through the install job). Installs → Kits shares its staging and Apply control. `GET /api/kits` now carries rules, word budget, banned APIs and credits, and the Library shows a `kit:` badge on kit members.
+
+### Changed
+- **Self-improvement writes to a sidecar, not the skill** (#354). The skill and agent loops used to edit the rendered file in place, which the doctor reported as stale and the next rebuild erased. They now write corrections to `notebook/skill-notes/<name>.md` and `notebook/agent-notes/<name>.md` (seed-once, agent-owned, never overwritten), and read them back before the skill runs or the agent is dispatched. `geneseed diff` lists the notes and `--out` exports them for back-porting into `src/`. AGENT.md names the notes paths, so the carrier ceilings rise by exactly that text (full 62_263, lean 39_156).
+
+### Fixed
+- **Setup's prompts no longer answer themselves in a real terminal** (#356). Reading `process.stdin` puts a terminal's input in non-blocking mode, and the line reader took the resulting `EAGAIN` for end of input: "Continue without one? (y/N)" printed and answered N at once, so `./install` stopped before anyone could type, and every other wizard question silently took its default. The reader now waits for the keypress.
+- **A tool installed for one user is found** (#356). Setup looked only on PATH, so an IBM Bob installed under the user's profile read as missing. It now also checks `~/.local/bin`, `~/bin`, each tool's own installer dir (`~/.opencode/bin`, `~/.claude/local`), the per-user npm prefix on Windows, and Bob's desktop app folder (`%LOCALAPPDATA%\Programs` on Windows, `/Applications` and `~/Applications` on macOS); a tool found there is listed with its path. When nothing is found, setup asks for the tool's path before offering to stop. The double-clickable `install.command` now waits for Enter before its window can close, as `install.cmd` already did.
+
 ## [4.10.0] — 2026-10-20
 
 Minor: opt-in kits (and a first one, `spring-boot`), credits for adapted content, a weekly upstream-drift check, and a web Kits tab.

package/README.md

@@ -13,7 +13,7 @@
 [![Themes](https://img.shields.io/badge/themes-14-9cf)](themes/)
 [![Skills](https://img.shields.io/badge/skills-47-blueviolet)](src/skills/)
 [![Agents](https://img.shields.io/badge/agents-20-orange)](src/agents/)
-[![Laws and doctrines](https://img.shields.io/badge/laws-9%20%2B%2029%20doctrines-critical)](src/doctrines/)
+[![Laws and doctrines](https://img.shields.io/badge/laws-9%20%2B%2030%20doctrines-critical)](src/doctrines/)
 [![Plugins](https://img.shields.io/badge/plugins-7-teal)](adapters/opencode/plugins/)
 [![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)
 
@@ -157,7 +157,7 @@ geneseed web stop            # stop the daemon
 geneseed web status          # is it running, and where
 ```
 
-The sidebar has six pages: **Overview** (what's deployed, health, recent jobs), **Constitution** (the rules and doctrine switches), **Library** (skills, agents, the wiki), **Personal** (your rules, profile, memory, notebook), **Installs** (hosts, local edits, doctor, server) and **Docs** — this documentation, opening on the Understand track, with a map of what Geneseed put on your machine.
+The sidebar has eight pages: **Overview** (what's deployed, health, recent jobs), **Constitution** (the rules and doctrine switches), **Library** (skills, agents, the wiki), **Kits** (opt-in stack bundles), **Loops** (the loop catalogue), **Personal** (your rules, profile, memory, notebook), **Installs** (hosts, local edits, doctor, server) and **Docs** — this documentation, opening on the Understand track, with a map of what Geneseed put on your machine.
 
 It binds to `127.0.0.1` only and runs entirely offline — no npm needed at runtime; the UI build ships in `web/dist/`. Mutating actions run in the background and report back as toasts (fire-and-notify), guarded by a per-session token so other sites can't trigger them. A global **Spotlight** search in the topbar jumps to any agent, skill, rule, doc, or MCP server. Rebuild the UI after changing anything under `web/src/` with `cd web && npm install && npm run build`. If `web/dist/` is missing (fresh clone, never built), `geneseed web` offers to run that build for you — answer `Y` and it installs, builds, and starts the server; in non-interactive shells it prints the manual recipe instead.
 
@@ -334,7 +334,7 @@ geneseed rebuild-all   # re-render every registered install in its own theme + m
 ./geneseed upgrade     # just the content refresh (remembers theme + emit mode)
 ```
 
-**Local edits survive.** If the agent refined its deployed agent/skill files in place, an upgrade exports that drift to an `improvements/` file inside the install before overwriting. Details: [Upgrade](docs/guides/upgrade.md).
+**Local edits survive.** The self-improvement loops write to notes under `notebook/`, which no rebuild touches. If you or the agent edited deployed agent/skill files in place anyway, an upgrade exports that drift to an `improvements/` file inside the install before overwriting. Details: [Upgrade](docs/guides/upgrade.md).
 
 ## 📚 Documentation
 
@@ -373,12 +373,13 @@ Some skills and agents are adapted from other open-source skill collections, und
 
 - `daydream` — [glebis/claude-skills](https://github.com/glebis/claude-skills) by Gleb Kalinin (MIT): the vendored `daydream` skill.
 - `react-view-transitions` — [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) by Vercel Engineering (MIT): the vendored `react-view-transitions` skill.
-- `mattpocock-skills` — [mattpocock/skills](https://github.com/mattpocock/skills) by Matt Pocock (MIT): the vocabulary and procedures behind codebase-design, wayfinder, prototype, develop, handoff and research, the spec pass of geneseed-code-review, the question rounds of brainstorm, the slicing of plan, and the reproduction step of debug.
+- `mattpocock-skills` — [mattpocock/skills](https://github.com/mattpocock/skills) by Matt Pocock (MIT): the vocabulary and procedures behind codebase-design, wayfinder, prototype, develop, handoff and research, the spec pass of geneseed-code-review, the question rounds and questionnaire of brainstorm, the slicing of plan, the reproduction step of debug, the integration-branch rules of parallel-agents, the trigger-pruning of skill-forge, and the dated-history rule of wiki.
 - `mattpocock-skills-frozen` — [mattpocock/skills](https://github.com/mattpocock/skills) by Matt Pocock (MIT), pinned at 391a2701, the last commit carrying `resolving-merge-conflicts` (deleted upstream since): the merge-conflict step of git-history, from a skill upstream has since deleted, so the weekly drift check skips it.
 - `mattpocock-skills-2509` — [mattpocock/skills](https://github.com/mattpocock/skills) by Matt Pocock (MIT), a second key for the same repo, at the same pin as `mattpocock-skills` today (5beb35b0): the PR body of ship and the guardrail clause of rule.
 - `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.
 - `vibe-wise` — [nykooi1/vibe-wise](https://github.com/nykooi1/vibe-wise) by Noah Kim (MIT): the state file, levels and checkpoints of learn-mode.
 - `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.
+- `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.
 
 ## 📄 License
 

package/SHIPPED.md

@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
 > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
 > human-readable label only. The canonical identity of an installed harness is the
 > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
-> string. Current label: **4.10.0**.
+> string. Current label: **4.15.1**.
 
 ## Capabilities
 

package/adapters/opencode/plugins/geneseed-guard.js

@@ -153,7 +153,21 @@ const gateOff = (marker) => new RegExp(`^${marker}:[ \\t]*off[ \\t]*\\r?$`, "m")
 const DELETION_GATE_OFF = gateOff("Deletion gate")
 const SECRETS_GATE_OFF = gateOff("Secrets gate")
 
-function log(msg) { console.error(`[geneseed-guard] ${msg}`) }
+// OpenCode 1.x paints a plugin's stderr over its TUI input box (in red); its own log API
+// writes to the log file instead. The V1 entry sets LOG_CLIENT; V2 and tests have no
+// client and keep stderr, as does a refused log call, so no line is lost. Never throws:
+// a log line must not break a tool call.
+let LOG_CLIENT = null
+function say(msg, level = "warn") {
+  try {
+    if (LOG_CLIENT?.app?.log) {
+      Promise.resolve(LOG_CLIENT.app.log({ body: { service: "geneseed-guard", level, message: msg } })).catch(() => console.error(`[geneseed-guard] ${msg}`))
+      return
+    }
+  } catch { /* fall through to stderr */ }
+  console.error(`[geneseed-guard] ${msg}`)
+}
+const log = (msg) => say(msg)
 
 // ---- the gate ledger ------------------------------------------------------------
 // The twin of `ledger()` in js/hosts/hooks.mjs: one JSON line per BLOCK into
@@ -1369,6 +1383,7 @@ async function recordUse(tool, args) {
 }
 
 export const GeneseedGuard = async (ctx) => {
+  if (ctx?.client) LOG_CLIENT = ctx.client
   // The session's working directory, the same resolution the context plugin uses.
   const root = () => ctx?.worktree || ctx?.directory || process.cwd()
   return {

package/adapters/opencode/plugins/geneseed-learn.js

@@ -38,6 +38,21 @@ import * as path from "node:path"
 import { fileURLToPath } from "node:url"
 import { homedir } from "node:os"
 
+// OpenCode 1.x paints a plugin's stderr over its TUI input box (in red); its own log API
+// writes to the log file instead. The V1 entry sets LOG_CLIENT; V2 and tests have no
+// client and keep stderr, as does a refused log call, so no line is lost. Never throws:
+// a log line must not break a tool call.
+let LOG_CLIENT = null
+function say(msg, level = "warn") {
+  try {
+    if (LOG_CLIENT?.app?.log) {
+      Promise.resolve(LOG_CLIENT.app.log({ body: { service: "geneseed-learn", level, message: msg } })).catch(() => console.error(`[geneseed-learn] ${msg}`))
+      return
+    }
+  } catch { /* fall through to stderr */ }
+  console.error(`[geneseed-learn] ${msg}`)
+}
+
 // The plugin's own directory. In the global install the layout is
 // <cfg>/plugins/geneseed-learn.js beside <cfg>/memory, so the store can be found
 // relative to this file — no manual `export GENESEED_HARNESS` needed.
@@ -471,17 +486,18 @@ async function storeDistil(output, { isChild, memDir, agentName, existing }) {
     const lesson = output.trim().split("\n")[0].replace(/^[-*]\s*/, "").trim()
     if (lesson.length < 10 || lesson.length > 300) return // junk / truncation guard
     const f = await appendAgentLesson(memDir, agentName, lesson)
-    console.error(`[geneseed-learn] agent lesson -> ${f}`)
+    say(`agent lesson -> ${f}`, "info")
     return
   }
   const res = await writeMemories(output, memDir, existing)
   for (const [verb, slugs] of [["wrote", res.created], ["updated", res.updated], ["archived", res.archived]]) {
-    if (slugs.length) console.error(`[geneseed-learn] ${verb} ${slugs.length} memory file(s): ${slugs.join(", ")}`)
+    if (slugs.length) say(`${verb} ${slugs.length} memory file(s): ${slugs.join(", ")}`, "info")
   }
 }
 
 export const GeneseedLearn = async (ctx) => {
   const { client } = ctx ?? {}
+  if (client) LOG_CLIENT = client
   const ours = new Set()       // throwaway distil sessions — never mine our own output
   const timers = new Map()     // sid -> debounce timer, re-armed on each idle
   const inFlight = new Set()   // sid currently being distilled (guards against overlap)
@@ -510,8 +526,8 @@ export const GeneseedLearn = async (ctx) => {
       if (!memDir) {
         if (!warnedNoDir) {
           warnedNoDir = true
-          console.error(
-            "[geneseed-learn] no memory dir — set $GENESEED_HARNESS or $GENESEED_MEMORY."
+          say(
+            "no memory dir — set $GENESEED_HARNESS or $GENESEED_MEMORY."
           )
         }
         return
@@ -524,8 +540,8 @@ export const GeneseedLearn = async (ctx) => {
       notes = notes.slice(-MAX_NOTES_CHARS)
       model = model ?? envModel()
       if (!model) {
-        console.error(
-          "[geneseed-learn] could not determine a model — set $GENESEED_MODEL=provider/model."
+        say(
+          "could not determine a model — set $GENESEED_MODEL=provider/model."
         )
         return
       }
@@ -540,7 +556,7 @@ export const GeneseedLearn = async (ctx) => {
       const newId = session?.id ?? session?.data?.id
       if (!newId) {
         // Prompting with {id: undefined} would 404 silently on every idle.
-        console.error("[geneseed-learn] session.create returned no id — skipping this distil.")
+        say("session.create returned no id — skipping this distil.")
         return
       }
       ours.add(newId)
@@ -558,7 +574,7 @@ export const GeneseedLearn = async (ctx) => {
       await storeDistil(output, { isChild, memDir, agentName, existing })
     } catch (err) {
       // Never break the session over a memory write.
-      console.error(`[geneseed-learn] skipped: ${err?.message ?? err}`)
+      say(`skipped: ${err?.message ?? err}`)
     } finally {
       inFlight.delete(sid)
     }
@@ -647,7 +663,7 @@ async function setupV2(ctx) {
       if (!memDir) {
         if (!warnedNoDir) {
           warnedNoDir = true
-          console.error("[geneseed-learn] no memory dir — set $GENESEED_HARNESS or $GENESEED_MEMORY.")
+          say("no memory dir — set $GENESEED_HARNESS or $GENESEED_MEMORY.")
         }
         return
       }
@@ -660,7 +676,7 @@ async function setupV2(ctx) {
         model = env ? { providerID: env.providerID, id: env.modelID } : null
       }
       if (!model) {
-        console.error("[geneseed-learn] could not determine a model — set $GENESEED_MODEL=provider/model.")
+        say("could not determine a model — set $GENESEED_MODEL=provider/model.")
         return
       }
 
@@ -673,7 +689,7 @@ async function setupV2(ctx) {
       })
       await storeDistil(String(reply?.text ?? ""), { isChild, memDir, agentName, existing })
     } catch (err) {
-      console.error(`[geneseed-learn] skipped: ${err?.message ?? err}`)
+      say(`skipped: ${err?.message ?? err}`)
     } finally {
       inFlight.delete(sid)
     }
@@ -695,7 +711,7 @@ async function setupV2(ctx) {
       if (prev) clearTimeout(prev)
       timers.set(sid, setTimeout(() => { timers.delete(sid); runDistill(sid) }, DEBOUNCE_MS))
     }
-  })().catch((err) => console.error(`[geneseed-learn] event stream ended: ${err?.message ?? err}`))
+  })().catch((err) => say(`event stream ended: ${err?.message ?? err}`))
   return () => {
     controller.abort()
     for (const t of timers.values()) clearTimeout(t)

package/adapters/opencode/plugins/geneseed-workflow.js

@@ -25,7 +25,21 @@ import * as path from "node:path"
 import { fileURLToPath, pathToFileURL } from "node:url"
 
 const DEBUG = !!process.env.GENESEED_DEBUG
-function dlog(m) { if (DEBUG) console.error(`[geneseed-workflow] ${m}`) }
+function dlog(m) { if (DEBUG) say(m, "debug") }
+// OpenCode 1.x paints a plugin's stderr over its TUI input box (in red); its own log API
+// writes to the log file instead. The V1 entry sets LOG_CLIENT; V2 and tests have no
+// client and keep stderr, as does a refused log call, so no line is lost. Never throws:
+// a log line must not break a tool call.
+let LOG_CLIENT = null
+function say(msg, level = "warn") {
+  try {
+    if (LOG_CLIENT?.app?.log) {
+      Promise.resolve(LOG_CLIENT.app.log({ body: { service: "geneseed-workflow", level, message: msg } })).catch(() => console.error(`[geneseed-workflow] ${msg}`))
+      return
+    }
+  } catch { /* fall through to stderr */ }
+  console.error(`[geneseed-workflow] ${msg}`)
+}
 
 const __dir = path.dirname(fileURLToPath(import.meta.url))
 const WORKFLOWS_DIR = process.env.GENESEED_WORKFLOWS_DIR
@@ -184,7 +198,9 @@ const NAME_DESCRIPTION = "saved workflow name; omit to list available"
 const ARGS_DESCRIPTION = "inputs passed to the workflow script as `args` (object, or a JSON object string)"
 
 // One-line load banner (always on) so a restart visibly confirms the plugin loaded and the
-// `workflow` tool is registered. tests/host_canary.mjs reads it as V1's proof of load.
+// `workflow` tool is registered. tests/host_canary.mjs reads it as V1's proof of load, so it
+// stays on stderr, not `say`: `opencode debug config` never prints a `client.app.log` line. It
+// runs once, before the TUI draws, so it does not land in the input box as `say`'s lines did.
 async function loadBanner(warn = "") {
   try {
     const names = await listWorkflows()
@@ -194,6 +210,7 @@ async function loadBanner(warn = "") {
 
 export const GeneseedWorkflow = async (ctx) => {
   const { client, directory, worktree } = ctx
+  if (client) LOG_CLIENT = client
   let toolHelper
   try { ({ tool: toolHelper } = await import("@opencode-ai/plugin")) }
   catch { dlog("@opencode-ai/plugin tool helper unavailable — registering a raw tool def") }

package/docs/concepts/kits.md

@@ -26,10 +26,22 @@ The first kit is `spring-boot`, for Spring Boot 4 (Spring Framework 7, Java 21+)
 
 The kit is adapted from [piomin/claude-ai-spring-boot](https://github.com/piomin/claude-ai-spring-boot) by Piotr Mińkowski (Apache-2.0), rewritten and condensed for Boot 4. Each of its skill folders ships `LICENSE-piomin-spring-boot.txt`, and each agent carries a credit line.
 
+The second kit is `react`, for React 18 or 19 apps built with Vite or webpack, in TypeScript or JavaScript, tested with Jest and React Testing Library. It adds four members:
+
+| Member | Kind | What it is for |
+|---|---|---|
+| `react` | skill | Components, hooks, state placement, data fetching, TypeScript or JavaScript, React security; side files for Vite and for webpack (config, client-side routing, env variables, build failures), read by whichever the project uses, and accessibility |
+| `react-testing` | skill | Jest and Testing Library: role queries, `userEvent`, MSW network mocks, `jest-axe`, and the Jest configuration a Vite or webpack project needs |
+| `react-engineer` | agent | Implements a React feature, or makes a broken Vite or webpack build or Jest run green |
+| `react-reviewer` | agent | Framework-aware review: hooks, state, data fetching, accessibility, React security, tests |
+
+It is adapted from [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) by Affaan Mustafa (MIT), rewritten and condensed for Vite and Jest; the webpack side file is first-party. It has no Server Components material: a client-rendered app has no server render.
+
 ### Switching kits on and off
 
 ```bash
 geneseed build --emit claude-global --kits spring-boot
+geneseed build --emit claude-global --kits react,spring-boot
 geneseed build --emit claude-global --kits none
 ```
 
@@ -37,7 +49,7 @@ geneseed build --emit claude-global --kits none
 
 A build does exactly what its flags say. A plain `build` without `--kits` therefore turns off a kit the install has on. Before it does, it warns: `this install has kit <k>; this build turns it off — pass --kits <k> to keep it`.
 
-The setup wizard asks one question listing the kits, with the install's current kits as the default. It asks it only when at least one kit exists.
+The setup wizard asks one yes/no question per kit, each defaulting to whether the install has that kit on. It asks them only when at least one kit exists.
 
 ### What an install records
 
@@ -47,7 +59,7 @@ An install with a kit on records it in its instructions file, under the skill se
 
 `geneseed status` shows `kits: spring-boot` on the install's row, and `status --json` carries the same list.
 
-In the web console, **Installs → Kits** (`#/installs/kits`) lists every install (disabled ones read-only) with one switch per kit. Toggling stages the set; **Apply** asks for confirmation, then rebuilds that one install with exactly that set as a console job (replace, not replay). Files you edited in a kit that is now off are kept, and the row names them so you can delete them by hand.
+In the web console, **Installs → Kits** (`#/installs/kits`) lists every install (disabled ones read-only) with one switch per kit. Toggling stages the set; **Apply** asks for confirmation, then rebuilds that one install with exactly that set as a console job (replace, not replay). Files you edited in a kit that is now off are kept, and the row names them so you can delete them by hand. The top-level **Kits** page (`#/kits`) lists the kits; a kit's page (`#/kits/<kit>`) shows its rules, banned APIs and upstream credits with the same per-install switch, and the Library tags each member skill or agent with a `kit:` badge.
 
 ### What a kit adds to an install
 

package/docs/concepts/skills.md

@@ -41,7 +41,7 @@ The full list, with each description, is in the catalog.
 
 ### Skills improve themselves
 
-Every skill ends with one beat of reflection: if a step misled or a step was missing, the agent proposes the exact edit to that skill and applies it only with your assent. Most runs end with nothing to change.
+Every skill ends with one beat of reflection: if a step misled or a step was missing, the agent writes the exact correction, with your assent, into that skill's notes file, `notebook/skill-notes/<name>.md`, and reads those notes the next time the skill runs. It never edits the installed skill itself: that file is rendered from `src/`, a rebuild would overwrite the edit, and `doctor` would report it as drift. Agents work the same way through `notebook/agent-notes/`. Each note is one line that carries its evidence, `- [skill|general] <correction> — seen: <what happened, against what was expected> (<date>)`: `seen:` is what you judge the correction by before folding it in, and `general` marks one that belongs in a law, doctrine or memory rather than in that one skill. `geneseed diff` lists the notes so you can fold them back into `src/`. Most runs end with nothing to change.
 
 ### Old names keep working
 

package/docs/extending.md

@@ -513,10 +513,9 @@ enumerates skills would miss it. `src/kits/<kit>/` holds only `rules.md`.
    to a kit member (it would dangle in an install without the kit), and a kit file that links to
    another kit's member. Links run kit → core only. A kit's links to its own members do not
    protect them from `--exclude-skills`; its link to a core skill still protects that skill.
-5. **The setup wizard.** It asks its kits question only when at least one kit exists. The shipped
-   `spring-boot` kit therefore added one answer line to the stdin strings in
-   `tests/unit/wizard.test.mjs`, and the `wizard-no-kit` job holds that the question is skipped on a
-   tree with no kit.
+5. **The setup wizard.** It asks one yes/no per kit, and only when at least one kit exists. Each
+   shipped kit therefore adds one answer line to the stdin strings in `tests/unit/wizard.test.mjs`,
+   and the `wizard-no-kit` job holds that the questions are skipped on a tree with no kit.
 6. **Golden cells**: the matrix (`tests/helpers/matrix/emit.*.json`) carries kit on for `claude` and
    `opencode`, the kit-off baseline (`kits: []`, spelled `--kits none`), and three deletion cells
    (kit on to off). One deletion cell sets `edit` (a map of sandbox path to appended text) so a member

package/docs/guides/install-bob.md

@@ -13,7 +13,9 @@ geneseed build --emit bob-global                                   # ~/.bob
 geneseed build --emit bob --out /path/to/repo --root /path/to/repo # one repo
 ```
 
-Bob is shaped like Claude Code, so it gets the same agents and skills. Per repo, the preamble goes into a root `AGENTS.md` and the rest into `.bob/`. Globally, everything goes under `~/.bob` (`$BOB_CONFIG_DIR` moves it), and the preamble rides `rules/geneseed.md`, because Bob does not auto-load a global `AGENTS.md`. Bob's hooks refuse an action with exit code 2, and Bob has no `SubagentStop` or `PreCompact` events. Bob support has not yet been verified against a live install.
+Bob is shaped like Claude Code, so it gets the same agents and skills. Per repo, the preamble goes into a root `AGENTS.md` and the rest into `.bob/`. Globally, everything goes under `~/.bob` (`$BOB_CONFIG_DIR` moves it), and the preamble rides `rules/geneseed.md`, because Bob does not auto-load a global `AGENTS.md`. Bob's hooks refuse an action with exit code 2, and Bob has no `SubagentStop` or `PreCompact` events.
+
+Both scopes open Bob's carrier with a short first-reply override, so the theme's readiness line (for example "🧬 Gene-seed implanted…") starts the first reply. Without it, Bob's own greeting outranked the instruction lower in the file. A bare greeting such as "hi" still gets Bob's fixed welcome; the line appears on the first real request. That much was checked by hand in the Bob IDE (2026-10); the rest of the Bob support has not been verified against a live install.
 
 ---
 

package/docs/guides/run-anywhere.md

@@ -8,7 +8,7 @@ description: "Put the geneseed command on your PATH from a clone."
 ---
 **Installed from npm? You have nothing to do.** `npm install -g geneseed` already puts `geneseed`, `geneseed-build` and `geneseed-hook` on your `PATH`.
 
-From a clone, you call the launcher inside the clone: `./geneseed` (Windows: `.\geneseed.cmd`). To type plain `geneseed` from any folder, link it.
+From a clone, you call the launcher inside the clone: `./geneseed` (Windows: `.\geneseed.cmd`). To type plain `geneseed` from any folder, link it. On macOS and Linux, `./install` does this for you when `geneseed` is not found yet.
 
 ## macOS and Linux
 
@@ -17,7 +17,7 @@ From a clone, you call the launcher inside the clone: `./geneseed` (Windows: `.\
 ./geneseed link /usr/local/bin     # or another bin folder (may ask for sudo)
 ```
 
-`link` writes a small shell launcher that runs this clone by its absolute path. It also tells you whether the target folder is on your `PATH`, and if it is not, the one line to add to your shell profile. Then:
+`link` writes a small shell launcher that runs this clone by its absolute path. If the target folder is not on your `PATH` (macOS zsh does not search `~/.local/bin`), it offers to add it to your shell's startup file: `~/.zshrc` for zsh, `~/.bashrc` for bash on Linux, `~/.bash_profile` for bash on macOS. It appends one marked block, never twice, and `geneseed unlink` removes it. Outside a terminal, or for another shell, it prints the line to add instead. Open a new terminal, then:
 
 ```
 geneseed            # the web console (or the command list), from any folder

package/docs/guides/upgrade.md

@@ -46,7 +46,7 @@ A rebuild only replaces files the install's manifest says Geneseed owns. It leav
 
 ## Local edits, and the improvements file
 
-The agent can refine its own deployed agent and skill files as it works, and so can you. A rebuild would overwrite those edits, so **setup, re-theme and upgrade export them first**. When the files they are about to overwrite differ from a fresh render, the differences are written to a markdown **improvements file** in `improvements/`, inside the install's own folder (for the OpenCode global install, `~/.config/opencode/improvements/`). The manifest does not list that folder, so rebuilds never overwrite it and uninstall never removes it.
+The agent records what it learns about a skill or agent in notes under `notebook/skill-notes/` and `notebook/agent-notes/`, which rebuilds never touch. Edits made to the deployed agent and skill files themselves, by you or by an older harness, are another matter: a rebuild would overwrite those, so **setup, re-theme and upgrade export them first**. When the files they are about to overwrite differ from a fresh render, the differences are written to a markdown **improvements file** in `improvements/`, inside the install's own folder (for the OpenCode global install, `~/.config/opencode/improvements/`). The manifest does not list that folder, so rebuilds never overwrite it and uninstall never removes it.
 
 A rebuild also refuses to overwrite a file you edited. The manifest records a fingerprint of every file Geneseed wrote; when a file no longer matches it, the rebuild leaves it alone and prints `kept your edited <file> — delete it to get Geneseed's copy back`. From then on the file is yours and later rebuilds skip it. A file the new version no longer ships is kept the same way, with `(no longer shipped)`. Line-ending changes from a git checkout do not count as edits. Installs made before fingerprints existed are overwritten as before.
 
@@ -58,7 +58,7 @@ geneseed diff --full                   # with line-level diffs
 geneseed diff --out improvements.md    # write the improvements file
 ```
 
-`diff` compares the global OpenCode install by default. Pass `--target <config dir>` to compare another install. A file you replaced with a link to your own copy (a skill folder junctioned or symlinked elsewhere, say) is listed as `linked`: Geneseed never writes through a link, so it is yours and not drift, and it stays out of the improvements file. The improvements file is self-contained. To make the changes permanent, hand it to an agent in a Geneseed clone and ask it to fold them back into `src/`. Then they survive every future build. The web console's **Changes** page exports the same file.
+`diff` compares the global OpenCode install by default. Pass `--target <config dir>` to compare another install. A file you replaced with a link to your own copy (a skill folder junctioned or symlinked elsewhere, say) is listed as `linked`: Geneseed never writes through a link, so it is yours and not drift, and it stays out of the improvements file. `diff` also lists every non-empty self-improvement note, and `--out` copies them into the improvements file; the upgrade export does not fire on notes alone, since a rebuild cannot lose them. The improvements file is self-contained. To make the changes permanent, hand it to an agent in a Geneseed clone and ask it to fold them back into `src/`. Then they survive every future build. The web console's **Changes** page exports the same file.
 
 ## Moving from a clone to npm
 

package/docs/reference/troubleshoot-install.md

@@ -97,7 +97,7 @@ reports `version "21` or higher.
 .\geneseed.cmd link
 ```
 
-On Windows, `link` writes to `%LOCALAPPDATA%\Geneseed\bin` and adds it to your user PATH — only **new** terminals see it, so close and reopen yours.
+On macOS and Linux, `link` offers to add `~/.local/bin` to your shell's startup file when it is not on your PATH; accept, then open a **new** terminal. On Windows, `link` writes to `%LOCALAPPDATA%\Geneseed\bin` and adds it to your user PATH — only **new** terminals see it, so close and reopen yours.
 
 **Confirm.**
 

package/docs/web-ui.md

@@ -114,6 +114,11 @@ streams the output of background jobs and keeps their history across reloads.
   **Promote to rule** control turns a recurring lesson into a trial rule in
   `user-rules.md` — provenance recorded, the source fact deleted so it isn't loaded
   twice — landing you on the Rules page.
+- **Kits** (`#/kits`, `#/kits/<kit>`) — the list of shipped kits and, per kit, a detail page
+  with its rules, word budget, banned APIs, upstream credits and one switch per install.
+  `GET /api/kits` carries `rules`, `rulesWordBudget`, `banned` and `credits` per kit; the
+  catalog and item endpoints for skills and agents carry `kit` (the owning kit or `null`),
+  which the Library shows as a `kit:` badge.
 - **Loops** (`#/loops`) — the loop catalogue `geneseed loop` runs from, read-only, laid out
   like the Library: a rail of sections (**Templates**, **Bricks**, **Active**, each with its
   count; `#/loops/<section>/<item>` opens an entry), with the selected section's groups
@@ -194,7 +199,7 @@ streams the output of background jobs and keeps their history across reloads.
     card (shown once a global install exists) manages sovereign repos — folders where every
     global harness goes dormant (hooks stay silent, the global preamble never loads);
     add or remove one here, the web mirror of `harness exclude add|remove|list`.
-- **Kits** (`#/installs/kits`) — every install (disabled ones read-only) as a card with one switch per kit.
+- **Kits** (`#/installs/kits`) — every install (disabled ones read-only) as a panel with one switch per kit.
   Toggling only stages the set; **Apply** asks first, then rebuilds that install with
   exactly that set as a console job. Files you edited in a kit that is now off are kept,
   and the row lists them.

package/harness.config.json

@@ -2,5 +2,5 @@
   "_comment": "version is a human-readable release label only; the canonical identity of an installed harness is the source fingerprint stamped in .geneseed-version (see `harness version`), not this string.",
   "theme": "neutral",
   "product": "Geneseed",
-  "version": "4.10.0"
+  "version": "4.15.1"
 }

package/js/build/emit-claude.mjs

@@ -21,7 +21,7 @@ import {
 } from './emit-common.mjs';
 import { kitsBody, renderAll, renderFile } from './render.mjs';
 import {
-  BOB_RULES_STUB, ensureContextStub, ensureExcludesStub, ensureNotebookIndex,
+  BOB_RULES_STUB, bobFirstReply, ensureContextStub, ensureExcludesStub, ensureNotebookIndex,
   ensureProfileStub,
   ensureRulesStub, ensureWikiStub, WIKI_FILE,
 } from './stubs.mjs';
@@ -100,7 +100,7 @@ export function emitClaudeRender(cfg, job) {
   if (isBob && agentText !== null) {
     const rulesMd = path.join(cfgDir, 'rules', 'geneseed.md');
     claimAndWrite(cfgDir, rulesMd, 'rules/geneseed.md', scope === 'project' ? BOB_RULES_STUB
-      : stripCapabilityLinks(prefixedAgentText('../') || agentText), owned);
+      : bobFirstReply(theme.LOADED_SIGIL) + stripCapabilityLinks(prefixedAgentText('../') || agentText), owned);
   }
 
   ensureAgentOverridesStub(cfg, cfgDir);
@@ -179,6 +179,8 @@ export function emitClaudeRender(cfg, job) {
   let claudeMdText = null;
   if (agentText !== null && !(isBob && scope === 'global')) {
     claudeMdText = stripCapabilityLinks(prefixedAgentText(lawsPrefix) || agentText);
+    // Bob only: its greeting persona outranks the template's sigil paragraph — see `bobFirstReply`.
+    if (isBob) claudeMdText = bobFirstReply(theme.LOADED_SIGIL) + claudeMdText;
   }
 
   // WIRE — see `claudeWire` below. One child per emit, so the two halves are two

package/js/build/stubs.mjs

@@ -139,6 +139,19 @@ file (\`~/.bob/rules/geneseed.md\`) so the global preamble does not stack on top
 the project's own. Follow the root \`AGENTS.md\`.
 `;
 
+/**
+ * The paragraph a Bob emit puts FIRST in what Bob auto-loads (global `rules/geneseed.md`,
+ * the project's `AGENTS.md` block). Tried live in the Bob IDE (2026-10-23): with only the
+ * template's sigil paragraph — below the banner — the first reply to a real request carried
+ * no sigil; with this paragraph on top it did. Bob's own greeting persona outranks a rule
+ * that does not say it overrides it. A bare "hi" still gets Bob's fixed welcome either way.
+ */
+export function bobFirstReply(sigil) {
+  return '**First-reply override — highest priority.** Your very first reply in every '
+    + 'conversation MUST begin with this exact line, before anything else and instead of any '
+    + `default greeting or self-introduction:\n\n> ${sigil}\n\n`;
+}
+
 /** `_build_render.PROFILE_FILE`. */
 const PROFILE_FILE = 'PROFILE.md';