geneseed 3.6.0 → 3.8.0

package/docs/web/exclusions.md

@@ -14,6 +14,7 @@ Exclusion is all-or-nothing per folder — it doesn't trim which Rules apply or
 ### How it's wired, per host
 
 - **Claude Code** — native suppression via `claudeMdExcludes` in the repo's `.claude/settings.local.json`.
+- **OpenClaude** — the same `claudeMdExcludes`, in the repo's `.openclaude/settings.local.json`.
 - **Bob** — a shadow `rules/geneseed.md` stub that shadows the global one (never overwrites a hand-written stub already there).
 - **OpenCode** — the hook entry's sovereign-bypass guard and its twin in the plugins short-circuit at session start.
 - **Copilot — documented limitation.** GitHub Copilot has no native per-repo suppression hook: the global `copilot-instructions.md` still loads even inside an excluded folder.

package/docs/web/footprint.md

@@ -26,7 +26,7 @@ Neither setting hides text from the agent; they hide it from *every turn*.
 
 ### How to set it
 
-It's set-and-forget — stored in the `.geneseed-footprint` marker, preserved across every rebuild, identical on every host (OpenCode, Claude Code, Bob, Copilot). Changing it re-emits the install.
+It's set-and-forget — stored in the `.geneseed-footprint` marker, preserved across every rebuild, identical on every host (OpenCode, Claude Code, Bob, Copilot, OpenClaude). Changing it re-emits the install.
 
 - **Settings** — the **Footprint** toggle flips the current install (full ⇄ lean) and rebuilds it in place.
 - **Harness tab** — on an active install, a per-harness dropdown sets it for that install independently, then **Apply**. On a host that is not installed yet, it is step 2 of **Install…**.

package/docs/web/harnesses.md

@@ -4,26 +4,26 @@ order: 4
 title: "Supported harnesses"
 kind: "concept"
 ---
-One source, **five emit targets** — each with a per-repo and a global (`-global`) variant, plus a portable `files` bundle any `AGENT.md`-aware tool can read. **OpenCode** runs its own engine (JS plugins, colour themes, LSP); **Claude Code**, **Bob**, and **Copilot** share one Claude-shaped engine that diverges only by host dialect.
+One source, **six emit targets** — each with a per-repo and a global (`-global`) variant, plus a portable `files` bundle any `AGENT.md`-aware tool can read. **OpenCode** runs its own engine (JS plugins, colour themes, LSP); **Claude Code**, **Bob**, **Copilot**, and **OpenClaude** share one Claude-shaped engine that diverges only by host dialect.
 
-The harness *content* — the constitution (Ethos, Rules, Doctrines), Agents, Skills, Memory, and the preamble voice — is **identical on every host**: one build renders the same text for all five targets. What differs is how much of it the host can *automate* (via plugins or hooks) versus carry as preamble discipline.
+The harness *content* — the constitution (Ethos, Rules, Doctrines), Agents, Skills, Memory, and the preamble voice — is **identical on every host**: one build renders the same text for all six targets. What differs is how much of it the host can *automate* (via plugins or hooks) versus carry as preamble discipline.
 
-| Capability | OpenCode | Claude | Bob | Copilot |
-| --- | :---: | :---: | :---: | :---: |
-| Agents · Skills · Memory | ✅ | ✅ | ✅ | ✅ |
-| Context injection | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 📄 preamble |
-| Memory write-back (learn) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 📄 preamble |
-| Git-gate consent (Doctrine process 5) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 📄 preamble |
-| Sovereign-repo excludes | ⚙️ plugin | ✅ | ✅ | ➖ |
-| MCP server wiring | ✅ | ✅ | ✅ | ✅ |
-| Colour themes | ✅ | ➖ | ➖ | ➖ |
-| LSP · workflows · primary-agent · `/`-commands | ✅ | ➖ | ➖ | ➖ |
+| Capability | OpenCode | Claude | Bob | Copilot | OpenClaude |
+| --- | :---: | :---: | :---: | :---: | :---: |
+| Agents · Skills · Memory | ✅ | ✅ | ✅ | ✅ | ✅ |
+| Context injection | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 📄 preamble | 🪝 hook² |
+| Memory write-back (learn) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 📄 preamble | 🪝 hook² |
+| Git-gate consent (Doctrine process 5) | ⚙️ plugin | 🪝 hook | 🪝 hook¹ | 📄 preamble | 🪝 hook² |
+| Sovereign-repo excludes | ⚙️ plugin | ✅ | ✅ | ➖ | ✅ |
+| MCP server wiring | ✅ | ✅ | ✅ | ✅ | ✅ |
+| Colour themes | ✅ | ➖ | ➖ | ➖ | ➖ |
+| LSP · workflows · primary-agent · `/`-commands | ✅ | ➖ | ➖ | ➖ | ➖ |
 
-✅ native · ⚙️ OpenCode plugin · 🪝 `settings.json` hook · 📄 preamble prose only · ➖ no host mechanism (harness discipline still applies). ¹ Bob honours Claude-dialect hooks best-effort — inert if unsupported, harness still holds via the preamble.
+✅ native · ⚙️ OpenCode plugin · 🪝 `settings.json` hook · 📄 preamble prose only · ➖ no host mechanism (harness discipline still applies). ¹ Bob honours Claude-dialect hooks best-effort — inert if unsupported, harness still holds via the preamble. ² OpenClaude is a Claude Code fork: Claude's hooks verbatim, under `~/.openclaude` or a repo's `.openclaude/`.
 
 **The git-gate row is the one capability that is not always present**, on any host. It implements **Doctrine process 5**, so it is wired only on an install that built the **process** [doctrine pack](#/docs/setup-choices) in — drop that pack and the boundary drops with it, because a gate that keeps asking for a rule the install never adopted is a gate arguing with its own harness. One asymmetry: on OpenCode that holds for a *fresh* install, but a pack-off rebuild of an install whose `opencode.json` already carries a `git commit*` entry leaves it in place and reports it — Geneseed cannot tell its own entry from one you typed, so it removes neither ([doctrine packs](#/docs/setup-choices)). The invariant-territory refusals in the same neighbourhood (`rm -rf`, a force-push) are the Rules' territory, not the pack's, and stay in every build.
 
-**No host drops an Agent, Skill, or the memory convention.** The asymmetry is otherwise entirely in *automation mechanism*: OpenCode's plugins and Claude/Bob's hooks enforce a few of these rules for you at the tool boundary, where **Copilot** (no hook mechanism) enforces them through preamble discipline. The OpenCode-only extras (themes, LSP, workflow runner, primary-agent) have no analogue on a Claude-shaped host.
+**No host drops an Agent, Skill, or the memory convention.** The asymmetry is otherwise entirely in *automation mechanism*: OpenCode's plugins and Claude/Bob/OpenClaude's hooks enforce a few of these rules for you at the tool boundary, where **Copilot** (no hook mechanism) enforces them through preamble discipline. The OpenCode-only extras (themes, LSP, workflow runner, primary-agent) have no analogue on a Claude-shaped host.
 
 ---
 

package/docs/web/install-quick.md

@@ -18,7 +18,7 @@ To keep the command around: `npm install -g geneseed`, then plain `geneseed …`
 
 ### 2. Open your agent
 
-Open OpenCode (or Claude Code, Bob, Copilot, or any `AGENT.md`-aware tool) in any repo. The first reply opens with the readiness sigil (`✅` neutral / `🧬` imperial / your theme's equivalent) and your project's docs are already in context.
+Open OpenCode (or Claude Code, Bob, Copilot, OpenClaude, or any `AGENT.md`-aware tool) in any repo. The first reply opens with the readiness sigil (`✅` neutral / `🧬` imperial / your theme's equivalent) and your project's docs are already in context.
 
 ### Prefer a clone?
 

package/docs/web/rules.md

@@ -17,7 +17,7 @@ The agent's standing rules come in **three tiers**, and the tier decides how a r
 
 ### Doctrines — chosen at build time
 
-Practices rather than principles: **craft** (how code is written), **rigor** (how work is proven), **ops** (how the machine is operated), **process** (how a task is run), one file each under `src/doctrines/`. A repository picks its set with `geneseed-build --doctrines <list>` or through the setup wizard — all {N_PACKS} are on by default. This install built in {N_PACKS_ACTIVE}, carrying {N_DOCTRINE_RULES} rules between them. Cited by pack and number — `Doctrine process 5`.
+Practices rather than principles: **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), one file each under `src/doctrines/`. A repository picks its set with `geneseed-build --doctrines <list>` or through the setup wizard — all {N_PACKS} are on by default. This install built in {N_PACKS_ACTIVE}, carrying {N_DOCTRINE_RULES} rules between them. Cited by pack and number — `Doctrine process 5`.
 
 A pack you leave out **still ships in the bundle**: every pack file lands under `doctrines/` beside `AGENT.md` whether or not it was built in. So a rule that cites one in an inactive pack still resolves on disk, and you can read the alternatives before turning one on. What an inactive pack loses is bindingness, not availability.
 

package/docs/web/themes-author.md

@@ -13,7 +13,7 @@ Every rule in the constitution gets its title from a theme key, and a theme that
 
 - `LEX_I`…`LEX_IX` — one title per invariant. `doctor` holds this to an **equality**, not mere presence: a `LEX_*` outside `I`–`IX` is a title for a rule that does not exist and fails the check too.
 - `DOC_*` — one title per doctrine rule, named after its address (`DOC_CRAFT_1`, `DOC_PROCESS_5`, …). `doctor` reads the pack files under `src/doctrines/` and requires exactly the set they name — a missing one is a blank heading, an extra one is a dead key.
-- `PACK_*` — one name per pack (`PACK_CRAFT`, `PACK_RIGOR`, `PACK_OPS`, `PACK_PROCESS`), used for the pack's own sub-heading.
+- `PACK_*` — one name per pack (`PACK_CRAFT`, `PACK_RIGOR`, `PACK_OPS`, `PACK_PROCESS`, `PACK_COMMS`), used for the pack's own sub-heading.
 
 The Ethos section names are **not** theme keys: a citation reads `({{ONTOLOGY}}: {{ONT_TELOS}})`, token on both sides, so heading and reference always move together. They live in the build's fixed structure table and you neither declare nor rename them.
 

package/docs/web-ui.md

@@ -120,7 +120,7 @@ streams the output of background jobs and keeps their history across reloads.
 - **Docs** (`#/docs`) — rendered documentation: markdown pages, concept pages, a CLI
   reference (generated from the harness argument parser), and a glossary, grouped into
   Get started / Core concepts / How-to / MCP servers / Plugins / Reference / Deeper. Filtered
-  for one host family (OpenCode, or Claude Code — which Bob and Copilot share); with no
+  for one host family (OpenCode, or Claude Code — which Bob, Copilot and OpenClaude share); with no
   choice stored it follows the deployed install.
 
 ### 🩺 Care

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": "3.6.0"
+  "version": "3.8.0"
 }

package/js/README.md

@@ -40,12 +40,12 @@ as a per-host install at project or global scope.
 | `source.mjs` | Where the SOURCE is: `ROOT`/`SRC`/`THEMES`/`CONFIG`, `PACK_ORDER`, rule ids, the cfg object |
 | `render.mjs` | The pure text pipeline: theme load, `INCLUDE` inlining, CATALOG blocks, `{{TOKENS}}`, dest paths |
 | `bundle.mjs` | `build` — render a theme into a bundle dir, plus the source-completeness refusal. Sits UNDER both emits |
-| `emit-claude.mjs` | The Claude/Bob/Copilot emit — the render half plus the settings + CLAUDE.md managed-block wire |
+| `emit-claude.mjs` | The Claude/Bob/Copilot/OpenClaude emit — the render half plus the settings + CLAUDE.md managed-block wire |
 | `emit-opencode.mjs` | The OpenCode emits — a project's `.opencode/` and the global config dir. Deliberate twin of the above |
 | `emit-common.mjs` | Constants, tree walkers, and the three writers BOTH global emits share. Decides no host |
 | `stubs.mjs` | Write-once seed files: context, wiki, rules, excludes, profile, `.gitignore`, memory/notebook indexes |
 | `version.mjs` | The release marker: fingerprint the sources, read/compare/write an install's version, warn on downgrade |
-| `driver.mjs` | The generator driver: `--emit`/`--theme`/`--footprint` flag parsing, the nine emit targets, per-host emit orchestration, the prune and the manifest. `bin/build-driver.mjs` is only its entry |
+| `driver.mjs` | The generator driver: `--emit`/`--theme`/`--footprint` flag parsing, the eleven emit targets, per-host emit orchestration, the prune and the manifest. `bin/build-driver.mjs` is only its entry |
 | `generate.mjs` | CLI verbs `build`, `prompt`, `theme`, `rebuild-all` — the thin face over `driver.mjs` |
 | `catalog.mjs` | `geneseed catalog` — prints the shipped roster. Classifies nothing itself |
 | `themes.mjs` | Maintainer-only `--sync-themes`: inserts `_TEMPLATE.json`'s missing keys into the committed themes |
@@ -66,7 +66,7 @@ user co-owns, and the hook verbs those emitted configs then run.
 
 | module | owns |
 |---|---|
-| `hosts.mjs` | The four host config dirs (opencode/claude/bob/copilot), plus `resolvePath`/`expanduser` |
+| `hosts.mjs` | The five host config dirs (opencode/claude/bob/copilot/openclaude), plus `resolvePath`/`expanduser` |
 | `hooks.mjs` | The verbs the emitted hooks run every session: `context`, `git-gate`, `rule-gate`, `tool-gate` (the two gates fused, for Copilot), `learn`. `--host` picks the verdict dialect |
 | `settings.mjs` | Merges into user-owned `settings.json`/`opencode.json`; owns the hook shim and the managed blocks |
 | `native.mjs` | Capability specs → host-native subagents and skills. The impure half of the emit |

package/js/build/driver.mjs

@@ -1,5 +1,5 @@
 /**
- * The generator driver — flag parsing, the nine emit targets, and the per-host emit orchestration.
+ * The generator driver — flag parsing, the eleven emit targets, and the per-host emit orchestration.
  * `bin/build-driver.mjs` (`geneseed-build`) is only its entry; this module is what the CLI verbs
  * (`build`, `setup`, `migrate`, `doctor`, `diff`, `validate`, the web console) import. It lived in
  * `bin/` until 2026-09, which made nine `js/` modules import upward from a binary.
@@ -51,7 +51,7 @@ import { parseJson, jsonDumpsIndent } from '../lib/json.mjs';
 // that should exist twice. golden.py's 259 cells are what made the move safe to attempt.
 import {
   GLOBAL_MANIFEST, resolvePath, opencodeConfigDir, claudeConfigDir, bobConfigDir,
-  copilotConfigDir, hostCatalogsNatively,
+  copilotConfigDir, openclaudeConfigDir, hostCatalogsNatively,
 } from '../hosts/hosts.mjs';
 
 // P5d moved these out of this file for the reason P5c moved the host resolvers: `harness
@@ -71,9 +71,9 @@ import { registryRecord, registryRoots } from '../inspect/registry.mjs';
 // maintainer pair that needs nothing this driver is banned from having.
 import { syncThemes } from './themes.mjs';
 
-/** The nine `--emit` choices, in build.py:337-338's order. */
+/** The eleven `--emit` choices: build.py:337-338's nine, then OpenClaude's pair. */
 const EMITS = ['files', 'opencode', 'opencode-global', 'claude', 'claude-global',
-  'bob', 'bob-global', 'copilot', 'copilot-global'];
+  'bob', 'bob-global', 'copilot', 'copilot-global', 'openclaude', 'openclaude-global'];
 
 /** `_build_emit.PRIMARY_AGENT_SRC`. */
 const PRIMARY_AGENT_SRC = path.join(ROOT, 'adapters', 'opencode', 'agents', 'orchestrator.md');
@@ -166,7 +166,7 @@ const VALUED = {
   '--theme': 'theme', '--posture': 'posture', '--mode': 'mode',
   '--doctrines': 'doctrines', '--exclude-rules': 'excludeRules',
   '--out': 'out', '--target': 'out', '--emit': 'emit',
-  '--footprint': 'footprint', '--root': 'root',
+  '--footprint': 'footprint', '--root': 'root', '--config-dir': 'cfgDir',
 };
 const FLAGS = {
   '--sync-themes': 'syncThemes', '--validate-only': 'validateOnly',
@@ -509,9 +509,11 @@ export function hookRunnerEntry() {
  * POSIX spelling, per the original: `claudeMdExcludes` entries are glob patterns, where a
  * backslash is an escape, so the Windows-native form risks never matching.
  */
-function preambleExclude(claudeMd) {
+function preambleExclude(claudeMd, host) {
   if (path.basename(claudeMd) !== 'CLAUDE.md') return null;
-  return resolvePath(path.join(claudeConfigDir(), 'CLAUDE.md')).split(path.sep).join('/');
+  // OpenClaude inherited `claudeMdExcludes` from Claude Code; its global preamble is its own.
+  const globalDir = host === 'openclaude' ? openclaudeConfigDir() : claudeConfigDir();
+  return resolvePath(path.join(globalDir, 'CLAUDE.md')).split(path.sep).join('/');
 }
 
 /**
@@ -808,7 +810,7 @@ function emitClaudeCore(cfg, args, { cfgDir, claudeMd, scope, host, out, hookOpt
     theme: args.theme, cfgDir, claudeMd, scope, host,
     out: out === null ? null : out,
     footprint: args.footprint, nativeCatalog: hostCatalogsNatively(host),
-    oldOwned, oldManaged, preambleExclude: preambleExclude(claudeMd),
+    oldOwned, oldManaged, preambleExclude: preambleExclude(claudeMd, host),
     ...(hookOpts ? { hookOpts } : {}),
   });
   const { owned, stats, memStatus, nbStatus, managed } = rendered;
@@ -930,6 +932,42 @@ function emitClaude(cfg, args, out) {
     + `settings.json), ${r.memStatus}, ${r.nbStatus}.\n`);
 }
 
+/**
+ * OpenClaude global — `~/.openclaude` (or `$OPENCLAUDE_CONFIG_DIR`). The Claude emit with
+ * another config dir: OpenClaude is a Claude Code fork that reads neither `~/.claude` nor
+ * `CLAUDE_CONFIG_DIR`, so a Claude install is invisible to it and it needs its own.
+ */
+function emitOpenclaudeGlobal(cfg, args, out) {
+  const cfgDir = args.cfgDir ?? openclaudeConfigDir();
+  const hookOpts = hookRunnerEntry();
+  const r = emitClaudeCore(cfg, args, {
+    cfgDir, claudeMd: path.join(cfgDir, 'CLAUDE.md'), scope: 'global', host: 'openclaude', out,
+    hookOpts,
+  });
+  process.stdout.write(`[geneseed] openclaude-global -> ${cfgDir}: ${r.nAgents} subagents, `
+    + `${r.nSkills} skills, CLAUDE.md, ${r.nHooks} hook group(s), settings.json, `
+    + `${r.memStatus}, ${r.nbStatus}. MCP servers go in .openclaude.json.\n`);
+  return cfgDir;
+}
+
+/**
+ * OpenClaude per-repo — everything under `.openclaude/`, the preamble included. OpenClaude
+ * reads the root CLAUDE.md only when the repo has no AGENTS.md, but `.openclaude/CLAUDE.md`
+ * always; keeping the root untouched also lets a Claude Code install share the repo.
+ */
+function emitOpenclaude(cfg, args, out) {
+  const root = args.root ? resolveOut(args.root) : out;
+  const cfgDir = path.join(root, '.openclaude');
+  const hookOpts = hookRunnerEntry();
+  const r = emitClaudeCore(cfg, args, {
+    cfgDir, claudeMd: path.join(cfgDir, 'CLAUDE.md'), scope: 'project', host: 'openclaude', out,
+    hookOpts,
+  });
+  process.stdout.write(`[geneseed] openclaude (folder) -> ${root}: .openclaude/ `
+    + `(CLAUDE.md, ${r.nAgents} subagents, ${r.nSkills} skills, ${r.nHooks} hook group(s), `
+    + `settings.local.json), ${r.memStatus}, ${r.nbStatus}.\n`);
+}
+
 /**
  * `_build_global.emit_bob_global` — into Bob's global config dir (~/.bob).
  *
@@ -994,10 +1032,10 @@ function writeMarkers(markerDir, emit, footprint) {
  * compares it file by file. The Python spells that `HOSTS[host]["emit_global"](theme,
  * out=..., cfg=<tmp>, footprint=...)`, where `cfg` overrides the target the emit would
  * otherwise resolve. This is that call, and the override is threaded as `args.cfgDir` through
- * the four `emit*Global` bodies rather than added to `parseArgs`: `build.py` has no
- * `--cfg-dir` flag, and a flag on one driver and not the other is a divergence
- * `tests/golden.py` compares 259 times and could never see, because it drives both from the
- * same argv.
+ * the `emit*Global` bodies. The same key is also `--config-dir` on the command line: a global
+ * emit never writes to `--out` (there `out` is the legacy bundle a memory store migrates FROM,
+ * and `update` passes it for exactly that), so without the flag there was no way to preview a
+ * global install anywhere but over the live one.
  *
  * WHICH SIDE OF THE BOUNDARY THIS SITS ON. P3c's rule was that a render CHILD must never
  * resolve a config dir, because a child that did would write 135 files into the developer's
@@ -1012,6 +1050,7 @@ const GLOBAL_EMITS = {
   claude: emitClaudeGlobal,
   bob: emitBobGlobal,
   copilot: emitCopilotGlobal,
+  openclaude: emitOpenclaudeGlobal,
 };
 
 /**
@@ -1033,7 +1072,7 @@ const GLOBAL_EMITS = {
  * three-positional call leaves in place, inherited here rather than re-decided.
  */
 const PROJECT_EMITS = {
-  claude: emitClaude, bob: emitBob, copilot: emitCopilot,
+  claude: emitClaude, bob: emitBob, copilot: emitCopilot, openclaude: emitOpenclaude,
   // P2. `opencode` joins the three for `cmdValidate`, which has to be able to render EVERY
   // `--emit` choice into its sandbox and not only the three doctor already scans. Its call
   // shape is `emitClaude`'s exactly — `(cfg, args, out)` — so the row is the whole change.
@@ -1148,6 +1187,15 @@ function run(argv) {
   }
 
   const out = resolveOut(args.out);
+  // Refused rather than ignored on a per-repo emit: an ignored target flag is how a preview
+  // lands on a live install, which is the bug this flag exists to close.
+  if (args.cfgDir !== undefined) {
+    if (!args.emit.endsWith('-global')) {
+      die(2, `argument --config-dir: only applies to a -global emit (got --emit ${args.emit}); `
+        + 'a per-repo emit writes under --out/--root');
+    }
+    args.cfgDir = resolveOut(args.cfgDir);
+  }
   const cfg = makeCfg(args);
 
   // The marker directory is the emit's TARGET, which for a global emit is the config dir it
@@ -1186,6 +1234,8 @@ function run(argv) {
   // An ALLOW-LIST, not "everything that is not global": a plain `--emit files` dev build —
   // the default — must never pollute the registry, and only the four per-repo host emits
   // are ones `_EMIT_HOST_SCOPE` can map back to a row. Records `out`, where the marker is.
-  if (['opencode', 'claude', 'bob', 'copilot'].includes(args.emit)) registryRecord(markerDir);
+  if (['opencode', 'claude', 'bob', 'copilot', 'openclaude'].includes(args.emit)) {
+    registryRecord(markerDir);
+  }
   return 0;
 }

package/js/build/emit-claude.mjs

@@ -126,7 +126,7 @@ export function emitClaudeRender(cfg, job) {
   // settings.local.json; Bob documents no local variant, so its settings.json is ignored.
   if (scope === 'project') {
     const gi = path.join(cfgDir, '.gitignore');
-    const giLines = (host === 'claude' ? ['settings.local.json']
+    const giLines = (host === 'claude' || host === 'openclaude' ? ['settings.local.json']
       : host === 'bob' ? ['settings.json'] : [])
       .concat(['wiki.jsonc', 'agent-overrides.json']);
     if (!existsSync(gi)) {

package/js/build/generate.mjs

@@ -80,12 +80,28 @@ function sysExit(msg) {
  * Calling the driver in-process keeps that: `resolveOut` resolves against `process.cwd()`
  * the same way. `build/the-bundle-follows-cwd-not-the-checkout` is the cell.
  *
- * Every other flag is the generator's own default, read from `harness.config.json` by the
- * driver — `harness build` forwards `--theme` and nothing else, and its own `--theme`
- * carries no `choices`, so an unknown one is refused by the generator rather than here.
+ * `geneseed build` used to forward `--theme` alone, which made `setup`'s own off-TTY hint
+ * (`geneseed build --emit … --theme …`) a usage error and left every other axis reachable
+ * only through the undocumented `geneseed-build`. Values are forwarded unchecked: the driver
+ * owns the choices, so the table does not repeat them.
+ *
+ * `--validate-only` is NOT one of these: it lives on `geneseed validate` only — that verb's
+ * source-tree half is the doctor, which starts a process, and this command's whole closure
+ * (`bin/geneseed-cli.mjs` → here → `driverMain`) is under the same transitive `child_process`
+ * ban as `bin/build-driver.mjs` itself. `driver.mjs`'s `run()` refuses the flag unconditionally
+ * for exactly that reason.
  */
+const BUILD_FORWARD = [
+  ['theme', '--theme'], ['emit', '--emit'], ['footprint', '--footprint'],
+  ['posture', '--posture'], ['mode', '--mode'], ['doctrines', '--doctrines'],
+  ['excludeRules', '--exclude-rules'], ['out', '--out'], ['root', '--root'],
+  ['configDir', '--config-dir'],
+];
+
 export function cmdBuild(args) {
-  return driverMain(args.theme ? ['--theme', args.theme] : []);
+  const argv = [];
+  for (const [key, flag] of BUILD_FORWARD) if (args[key] != null) argv.push(flag, args[key]);
+  return driverMain(argv);
 }
 
 // --------------------------------------------------------------------------------------
@@ -123,7 +139,7 @@ export function setupBuildArgs(theme, emit, out = null, root = null, footprint =
   posture = 'peer', mode = 'direct', doctrines = null, allPacks = PACK_ORDER,
   excludeRules = null) {
   const argv = ['--theme', theme, '--emit', emit];
-  if (!['opencode-global', 'claude-global', 'bob-global', 'copilot-global'].includes(emit)) {
+  if (!emit.endsWith('-global')) {
     if (out) argv.push('--out', out);
     if (root) argv.push('--root', root);
   }
@@ -158,8 +174,69 @@ export const DEFAULT_EMIT = new Map([
   ['claude global', 'claude-global'], ['claude project', 'claude'],
   ['bob global', 'bob-global'], ['bob project', 'bob'],
   ['copilot global', 'copilot-global'], ['copilot project', 'copilot'],
+  ['openclaude global', 'openclaude-global'], ['openclaude project', 'openclaude'],
 ]);
 
+/**
+ * Everything `rebuild-all` reads back off one install, and the argv that re-emits it unchanged.
+ *
+ * EXTRACTED SO `status` SHOWS WHAT A REBUILD WOULD USE, not a second reading of the same
+ * markers that could drift from this one. An agent changing one setting takes `argv`, edits one
+ * flag and runs it; every flag it did not touch has to be the install's own, or the "one
+ * change" silently resets the rest — which is exactly the failure the seven read-backs below
+ * exist to prevent.
+ *
+ * THE MARKER IS TRUSTED ONLY FOR ITS OWN HOST. There is one `.geneseed-emit` per root and the
+ * last deploy wins, so in a dual-host repo (`.opencode/` and `.claude/` in one cwd) the other
+ * host's row would otherwise rebuild with the WRONG emit — turning a Claude install into an
+ * OpenCode one. `rebuild-all/a-dual-host-repo-rebuilds-each-row-in-its-own-emit` is the cell.
+ */
+export function installProfile(host, scope, root) {
+  const raw = readMaybe(path.join(root, '.geneseed-emit'));
+  let marker = raw === null ? '' : raw.trim();
+  if (marker && (EMIT_HOST_SCOPE.get(marker) ?? ['', ''])[0] !== host) marker = '';
+  const emit = marker || DEFAULT_EMIT.get(`${host} ${scope}`) || 'opencode-global';
+  const theme = themeOfDir(root) || defaultTheme();
+  const footprint = footprintOfDir(root);
+  const posture = postureOfDir(root) || defaultPosture();
+  const mode = modeOfDir(root) || defaultMode();
+  // A rebuild that defaulted the pack selection would re-emit an install into a constitution
+  // its owner did not choose — and in one direction that is not merely surprising: dropping
+  // the process pack takes the commit/push consent RULES out of AGENT.md while
+  // `claudeHookGroups` keeps the gate wired, or the reverse. ⚠ AND THE FALLBACK IS NOT
+  // `harness.config.json`: a pre-migration carrier has no marker, and resolving that silence
+  // out of a machine-wide config narrows every such install on its first upgrade.
+  // `doctrinesForBuild` resolves unknown to ALL packs — see its docblock.
+  const doctrines = doctrinesForBuild(root);
+  // The per-rule axis is preserved for the same reason and with sharper teeth: an upgrade that
+  // dropped it would quietly hand back every rule its owner switched off, and `process 5` is
+  // one of them. `null` (no marker) stays `null` so the argv omits the flag, as it always did.
+  const excludeRules = excludedRulesOfDir(root);
+  const out = scope === 'global' ? null : root;
+  const argv = setupBuildArgs(theme, emit, out, out, footprint, posture, mode, doctrines,
+    PACK_ORDER, excludeRules);
+  // A GLOBAL ROW NAMES ITS OWN DIR. `root` came from the host's config-dir resolver, which
+  // honours env overrides (`OPENCODE_CONFIG_DIR`, `CLAUDE_CONFIG_DIR`…); without the flag the
+  // same argv run from a shell lacking that variable re-emits into the DEFAULT dir — a second
+  // install beside the one it was meant to rebuild. Appended, so the argv's head is unchanged.
+  if (scope === 'global') argv.push('--config-dir', root);
+  return {
+    host, scope, root, state: installState(root, host, scope),
+    emit, theme, footprint, posture, mode, doctrines, excludeRules, argv,
+  };
+}
+
+/**
+ * `argv` as one pasteable command, using the `geneseed build` launcher rather than the raw
+ * generator: `geneseed-build` is only on PATH for an npm global install, while a git-clone
+ * install has only the `geneseed` launcher, and `geneseed build` now forwards every flag
+ * `setupBuildArgs` produces. Only whitespace is quoted — a path holding shell metacharacters
+ * (`$`, `&`) would need quoting by hand.
+ */
+export function rebuildCommand(argv) {
+  return ['geneseed', 'build', ...argv.map((a) => (/\s/.test(a) ? `"${a}"` : a))].join(' ');
+}
+
 /**
  * `_harness_build.cmd_rebuild_all` — re-emit every ACTIVE install in place, best-effort.
  *
@@ -171,16 +248,12 @@ export const DEFAULT_EMIT = new Map([
  * `main` converts, and `rebuild-all/one-broken-install-does-not-stop-the-rest` is the cell
  * that fails if either half is undone.
  *
- * FIVE VALUES ARE READ BACK OFF EACH INSTALL, not defaulted. Theme and emit and footprint
- * come from markers; posture and mode are detected from the `**<Name>**` lead in the
- * deployed carrier's prose, because they were never markered. A rebuild that defaulted any
- * of them would silently re-emit an install into something its owner did not choose — which
- * is the same failure mode `_footprint_of_dir`'s WARN exists to prevent, at a larger scale.
- *
- * THE MARKER IS TRUSTED ONLY FOR ITS OWN HOST. There is one `.geneseed-emit` per root and the
- * last deploy wins, so in a dual-host repo (`.opencode/` and `.claude/` in one cwd) the other
- * host's row would otherwise rebuild with the WRONG emit — turning a Claude install into an
- * OpenCode one. `rebuild-all/a-dual-host-repo-rebuilds-each-row-in-its-own-emit` is the cell.
+ * SEVEN VALUES ARE READ BACK OFF EACH INSTALL, not defaulted — see `installProfile`. Theme and
+ * emit and footprint come from markers; posture and mode are detected from the `**<Name>**`
+ * lead in the deployed carrier's prose, because they were never markered. A rebuild that
+ * defaulted any of them would silently re-emit an install into something its owner did not
+ * choose — which is the same failure mode `_footprint_of_dir`'s WARN exists to prevent, at a
+ * larger scale.
  */
 export function cmdRebuildAll() {
   const targets = installTargets().filter(([h, s, r]) => installState(r, h, s) === 'active');
@@ -190,34 +263,11 @@ export function cmdRebuildAll() {
   }
   const failures = [];
   for (const [host, scope, root] of targets) {
-    const raw = readMaybe(path.join(root, '.geneseed-emit'));
-    let marker = raw === null ? '' : raw.trim();
-    if (marker && (EMIT_HOST_SCOPE.get(marker) ?? ['', ''])[0] !== host) marker = '';
-    const emit = marker || DEFAULT_EMIT.get(`${host} ${scope}`) || 'opencode-global';
-    const theme = themeOfDir(root) || defaultTheme();
-    const footprint = footprintOfDir(root);
-    const posture = postureOfDir(root) || defaultPosture();
-    const mode = modeOfDir(root) || defaultMode();
-    const out = scope === 'global' ? null : root;
-    // SIX values now, not five. A rebuild that defaulted the pack selection would re-emit an
-    // install into a constitution its owner did not choose — and in one direction that is not
-    // merely surprising: dropping the process pack takes the commit/push consent RULES out of
-    // AGENT.md while `claudeHookGroups` keeps the gate wired, or the reverse. ⚠ AND THE
-    // FALLBACK IS NOT `harness.config.json`: a pre-migration carrier has no marker, and
-    // resolving that silence out of a machine-wide config narrows every such install on its
-    // first upgrade. `doctrinesForBuild` resolves unknown to ALL packs — see its docblock.
-    const doctrines = doctrinesForBuild(root);
-    // SEVEN. The per-rule axis is preserved for the same reason and with sharper teeth: an
-    // upgrade that dropped it would quietly hand back every rule its owner switched off, and
-    // `process 5` is one of them — the consent gate would return to a harness that had been
-    // built without it. No `doctrinesForBuild` rescue is needed here; see `apiInstallCmd`.
-    const excludeRules = excludedRulesOfDir(root);
-    const argv = setupBuildArgs(theme, emit, out, out, footprint, posture, mode, doctrines,
-      PACK_ORDER, excludeRules);
+    const p = installProfile(host, scope, root);
     const label = `${host}:${scope} (${root})`;
-    printOut(`[rebuild-all] ${label}: theme=${theme} emit=${emit} footprint=${footprint} `
-      + `posture=${posture} mode=${mode}\n`);
-    const rc = driverMain(argv);
+    printOut(`[rebuild-all] ${label}: theme=${p.theme} emit=${p.emit} footprint=${p.footprint} `
+      + `posture=${p.posture} mode=${p.mode}\n`);
+    const rc = driverMain(p.argv);
     if (rc !== 0) {
       failures.push(label);
       printErr(`[rebuild-all] FAILED ${label} (exit ${rc})\n`);

package/js/build/source.mjs

@@ -92,17 +92,18 @@ export function discoverNames(dir, first) {
  *
  * DELIBERATELY NOT `discoverNames('doctrines', 'craft')`. That helper `.sort()`s, so it
  * answers `craft, ops, process, rigor`; the constitution's order is a reading order —
- * write it (craft), prove it (rigor), run it (ops), ship it (process) — and no sort
- * produces it. Discovery still runs, but as a GATE rather than as the order: `js/build/render.mjs`
+ * write it (craft), prove it (rigor), run it (ops), ship it (process), then say it
+ * (comms) — and no sort produces it. comms is LAST because presenting the answer is the last
+ * act of any task, and because appending left every earlier pack's position untouched. Discovery still runs, but as a GATE rather than as the order: `js/build/render.mjs`
  * refuses to build when a pack file exists under `src/doctrines/` that is missing from this
- * array, so a fifth pack cannot be silently dropped from every install.
+ * array, so a sixth pack cannot be silently dropped from every install.
  *
  * It lives here, beside `makeCfg` and `discoverNames`, because every consumer (the cfg
  * default, the render loop, the `Active packs:` marker, the CLI flag, the wizard, the
  * doctor) already imports this module and this module imports nothing of theirs — the one
  * placement that cannot introduce a cycle.
  */
-export const PACK_ORDER = ['craft', 'rigor', 'ops', 'process'];
+export const PACK_ORDER = ['craft', 'rigor', 'ops', 'process', 'comms'];
 
 /**
  * Every doctrine rule address this checkout ships — `pack.n`, in render order.