geneseed 3.6.0 → 3.8.0

package/js/web/actions.mjs

@@ -41,8 +41,8 @@ import { excludeAdd, excludeRemove } from '../inspect/excludes.mjs';
 import { setupBuildArgs } from '../build/generate.mjs';
 import { frontmatter, memoryDropIndex } from '../hosts/hooks.mjs';
 import {
-  HOSTS, bobConfigDir, claudeConfigDir, copilotConfigDir, expanduser, opencodeConfigDir,
-  resolvePath,
+  HOSTS, bobConfigDir, claudeConfigDir, copilotConfigDir, expanduser, openclaudeConfigDir,
+  opencodeConfigDir, resolvePath,
 } from '../hosts/hosts.mjs';
 import {
   EMIT_HOST_SCOPE, doctrinesForBuild, excludedRulesOfDir, footprintOfDir, installState,
@@ -644,7 +644,7 @@ export function apiMcpToggle(state, body) {
     return { ok: false, error: 'config holds comments — edit it by hand to keep them' };
   }
   let cfg;
-  if (['claude', 'bob', 'copilot'].includes(host)) {
+  if (['claude', 'bob', 'copilot', 'openclaude'].includes(host)) {
     if (isFile(p)) {
       let parsed;
       try {
@@ -817,6 +817,7 @@ const EMIT_FOR = 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'],
 ]);
 
 /**
@@ -951,7 +952,8 @@ export function apiDeployCmd(state, body) {
     return { error: `folder not writable: ${root}` };
   }
   const cfgdirs = new Set();
-  for (const fn of [opencodeConfigDir, claudeConfigDir, bobConfigDir, copilotConfigDir]) {
+  for (const fn of [opencodeConfigDir, claudeConfigDir, bobConfigDir, copilotConfigDir,
+    openclaudeConfigDir]) {
     try {
       cfgdirs.add(resolvePath(fn()));
     } catch { /* not every host has a resolvable config dir; skip it */ }
@@ -976,7 +978,7 @@ export function apiDeployCmd(state, body) {
   // and `PreToolUse::Bash` went with them. `doctrinesForBuild` resolves unknown to ALL packs.
   const doctrines = bodyDoctrines(body) ?? doctrinesForBuild(root);
   const excludeRules = bodyExcludeRules(body) ?? excludedRulesOfDir(root);
-  // project-scope emit name == host name (opencode / claude / bob / copilot)
+  // project-scope emit name == host name (opencode / claude / bob / copilot / openclaude)
   const argv = setupBuildArgs(theme || 'neutral', host, root, root, fp, pos, mode, doctrines,
     PACK_ORDER, excludeRules);
   return { cmd: [process.execPath, path.join(ROOT, 'bin', 'build-driver.mjs'), ...argv] };

package/js/web/api.mjs

@@ -724,7 +724,7 @@ export const apiExcludes = () => excludesSnapshot();
  * nested-marker host cannot silently read the bare root.
  */
 export function viewCfg(host, scope, root) {
-  if (scope === 'project' && ['claude', 'bob', 'copilot'].includes(host)) {
+  if (scope === 'project' && ['claude', 'bob', 'copilot', 'openclaude'].includes(host)) {
     return path.join(root, HOSTS.find((h) => h.host === host).projectMarker);
   }
   return root;
@@ -790,7 +790,7 @@ export function apiOverview(state) {
   // can re-emit exactly it. Mirrors `viewCfg`'s rule, spelled out separately here.
   let install = null;
   for (const [host, scope, root] of installTargets()) {
-    const data = (scope === 'project' && ['claude', 'bob', 'copilot'].includes(host))
+    const data = (scope === 'project' && ['claude', 'bob', 'copilot', 'openclaude'].includes(host))
       ? path.join(root, HOSTS.find((h) => h.host === host).projectMarker) : root;
     try {
       if (samePath(data, state.target)) {

package/js/web/docs.mjs

@@ -207,7 +207,7 @@ const HARNESS_HINT_RE = /<!--\s*harness:/;
 export function normHarness(value, state) {
   const v = (value || '').trim().toLowerCase();
   if (HARNESSES.includes(v)) return v;
-  return String(state.emit || '').startsWith('claude') ? 'claude' : 'opencode';
+  return /^(claude|openclaude)/.test(String(state.emit || '')) ? 'claude' : 'opencode';
 }
 
 /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "//": "Every field here is argued and gated in tests/unit/package_manifest.test.mjs. `files`, `bin` and `engines` each have a test that fails when reality drifts from this file; `version` mirrors harness.config.json and is gated too. Read that docblock before editing this one.",
   "name": "geneseed",
-  "version": "3.6.0",
+  "version": "3.8.0",
   "description": "A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.",
   "keywords": [
     "ai",
@@ -9,6 +9,7 @@
     "claude-code",
     "opencode",
     "copilot",
+    "openclaude",
     "agents-md",
     "skills",
     "harness",

package/src/doctrines/README.md

@@ -8,7 +8,7 @@ documentation repo and a production service do not need the same practices.
 The selected packs are inlined into `AGENT.md`'s Doctrines section at build time;
 every pack ships here as a catalogue so you can read the alternatives and switch.
 Change the active set by rebuilding with `--doctrines <list>` (or via the setup
-wizard); the choice is stored in `harness.config.json`. All four are active by
+wizard); the choice is stored in `harness.config.json`. All five are active by
 default.
 
 A pack is **orthogonal to theme and posture**: the theme sets the *voice*, the
@@ -21,9 +21,10 @@ composes.
 | [rigor](rigor.md) | How work is proven — idempotence, honest tests, coverage, gates that can fail. |
 | [ops](ops.md) | How the machine is operated — tool discovery, non-blocking commands, source-layer edits, teardown. |
 | [process](process.md) | How a task is run — planning, context economy, docs-first, consent before push. |
+| [comms](comms.md) | How answers are presented — stable reference codes, a diagram or a table only where it earns its place. |
 
 A rule in one pack may cite a rule in another. That is safe because the **full
-catalogue ships in every bundle** — all four pack files are installed whether or not
+catalogue ships in every bundle** — all five pack files are installed whether or not
 their pack is built into `AGENT.md` — so a cross-pack reference is always readable
 even when the pack it names is not active.
 

package/src/doctrines/comms.md

@@ -0,0 +1,53 @@
+**{{PACK_COMMS}}** — how answers are presented.
+
+### {{DOCTRINE}} comms 1 — {{DOC_COMMS_1}}
+<!-- LEAN:begin -->
+Give every tracked item a short reference code and keep it unchanged for the rest of
+the session — `D` decisions, `O` options, `F` findings, `R` risks, `Q` questions,
+`A` actions. The trigger is countable: any reply naming two or more such items takes
+codes, a {{SKILL}}'s or an {{AGENT}}'s report included, whatever layout its template
+shows; a reply with one item or none takes none. The code opens the item's line —
+`**F1** — the token is logged in plain text`, `**Q2** — keep the v1 route?` — not a
+bare `1.` or a bullet. Number from one within each kind, keep counting across turns
+(the next finding after `F3` is `F4`, even three replies later), invent a new letter
+for a kind the list omits, and never renumber a code once issued — the user will cite
+it back, and a moved code makes their reply mean something you did not say. A code is an address, not an ornament:
+it lets a long exchange be answered by reference, and a decision taken on turn
+three still be named on turn thirty. Where the {{ONTOLOGY}}'s {{ONT_CONDUCT}}
+governs how an answer speaks, this is only the addressing convention — a practice
+a repository adopts or drops like any other rule in these {{DOCTRINES}}.
+<!-- LEAN:else -->
+Give every tracked item a short reference code, unchanged for the session —
+`D` decisions, `O` options, `F` findings, `R` risks, `Q` questions, `A` actions.
+Any reply naming two or more such items takes codes, a {{SKILL}}'s or {{AGENT}}'s
+report included; one item or none takes none. The code opens the line, never a bare
+`1.` or bullet: `**F1** — token logged in plain text`, `**Q2** — keep the v1 route?`
+Number from one within each kind and keep counting across turns (after `F3` comes
+`F4`), invent letters for missing kinds, never renumber a code once issued.
+<!-- LEAN:end -->
+
+### {{DOCTRINE}} comms 2 — {{DOC_COMMS_2}}
+<!-- LEAN:begin -->
+Prose and structure are distinct: beside the prose, pick **either** a diagram **or** a
+table — whichever the matter needs, rarely both — and let the prose keep the context, the
+why, the pitfall and the decision. Draw a boxes-and-arrows diagram only when its arrows
+carry meaning: links to follow (a flow, a sequence, dependencies, a causal chain, a
+topology), a visual or spatial subject, four or more interlinked elements, or when the
+user asks. The test: erase the arrows — if nothing is lost, it was never a diagram.
+Classifications, inventories and attribute comparisons take a table or a list; a chain of
+three steps or fewer stays inline (`A -> B -> C`); a trivial fact stays plain text. A small
+diagram replaces prose only where the prose would run long describing a structure. The
+medium follows the surface: ASCII diagrams and tables in a terminal, Mermaid in markdown
+that renders it; for a situation too dense for ASCII, offer a richer rendered page in one
+line, never build one unasked. This is strictly additive to {{DOCTRINE}} comms 1: tracked
+items keep their codes, one coded line each, and a diagram or table may carry a code as a
+tag but never absorbs, merges or renumbers an item.
+<!-- LEAN:else -->
+Prose and structure are distinct: beside the prose, pick a diagram or a table, rarely
+both; prose keeps the why and the decision. Draw a diagram only when its arrows carry
+meaning — flow, dependencies, topology, a spatial subject, four or more linked elements,
+or on request; if erasing them loses nothing, use a table or list. Three steps or fewer
+stay inline (`A -> B -> C`). ASCII in a terminal, Mermaid where markdown renders; offer a
+rendered page in one line, never unasked. Codes stay ({{DOCTRINE}} comms 1): a diagram
+may tag an item, never absorb or renumber it.
+<!-- LEAN:end -->

package/src/doctrines/process.md

@@ -130,32 +130,6 @@ stalls, halt with a structured summary of what was tried, learned, and remains (
 
 ### {{DOCTRINE}} process 7 — {{DOC_PROCESS_7}}
 <!-- LEAN:begin -->
-Give every tracked item a short reference code and keep it unchanged for the rest of
-the session — `D` decisions, `O` options, `F` findings, `R` risks, `Q` questions,
-`A` actions. The trigger is countable: any reply naming two or more such items takes
-codes, a {{SKILL}}'s or an {{AGENT}}'s report included, whatever layout its template
-shows; a reply with one item or none takes none. The code opens the item's line —
-`**F1** — the token is logged in plain text`, `**Q2** — keep the v1 route?` — not a
-bare `1.` or a bullet. Number from one within each kind, keep counting across turns
-(the next finding after `F3` is `F4`, even three replies later), invent a new letter
-for a kind the list omits, and never renumber a code once issued — the user will cite
-it back, and a moved code makes their reply mean something you did not say. A code is an address, not an ornament:
-it lets a long exchange be answered by reference, and a decision taken on turn
-three still be named on turn thirty. Where the {{ONTOLOGY}}'s {{ONT_CONDUCT}}
-governs how an answer speaks, this is only the addressing convention — a practice
-a repository adopts or drops like any other rule in these {{DOCTRINES}}.
-<!-- LEAN:else -->
-Give every tracked item a short reference code, unchanged for the session —
-`D` decisions, `O` options, `F` findings, `R` risks, `Q` questions, `A` actions.
-Any reply naming two or more such items takes codes, a {{SKILL}}'s or {{AGENT}}'s
-report included; one item or none takes none. The code opens the line, never a bare
-`1.` or bullet: `**F1** — token logged in plain text`, `**Q2** — keep the v1 route?`
-Number from one within each kind and keep counting across turns (after `F3` comes
-`F4`), invent letters for missing kinds, never renumber a code once issued.
-<!-- LEAN:end -->
-
-### {{DOCTRINE}} process 8 — {{DOC_PROCESS_8}}
-<!-- LEAN:begin -->
 When several {{AGENTS}} work on the same code — sub-{{AGENTS}}, a pipeline crew, a
 workflow fan-out, another session or tool in this checkout — each file has one writer at
 a time. Before dispatch, give every unit a **write set** (the files or globs it may

package/src/skills/geneseed.md

@@ -2,17 +2,18 @@
 
 > {{DESC_GENESEED}}
 
-**Trigger:** the user mentions Geneseed, the harness, `AGENT.md`, or asks you to inspect, read from, or refresh the deployed bundle — or you need to know what {{LAWS}}, {{AGENTS}}, or {{SKILLS}} are available in the current install.
+**Trigger:** the user mentions Geneseed, the harness, or `AGENT.md`; asks how the install is set up; asks to change its theme, footprint, posture, mode, doctrine packs or excluded rules — or you need to know what {{LAWS}}, {{AGENTS}}, or {{SKILLS}} this install carries.
 
 ## Procedure
-1. Locate the deployment. Try in order: `command -v geneseed` (use the launcher if found); `$GENESEED_HARNESS`; `$OPENCODE_CONFIG_DIR`; `~/.config/opencode/AGENT.md`; `.opencode/AGENT.md` walking up from `pwd`; any `AGENT.md` at the repo root. Stop and say so if none resolves — do not run `setup`, `build`, or `upgrade` to "fix" this.
-2. For state — install mode, theme, counts, version fingerprint, drift — prefer the CLI: `geneseed status`, `geneseed version`, `geneseed doctor`, `geneseed diff`. All read-only and cheap ({{DOCTRINE}} process 3).
-3. To read a specific piece, read the file directly rather than re-deriving from prose ({{LAW}} III): `<harness>/agents/<name>.md`, `<harness>/skills/<name>/SKILL.md`, `<harness>/memory/<file>.md`, `<harness>/notebook/<file>.md`. The {{ONTOLOGY}}, the {{LAWS}} and the active {{DOCTRINES}} live as their own numbered `## N. …` sections inside `<harness>/AGENT.md`.
-4. Side-effecting verbs need explicit assent ({{DOCTRINE}} process 5): `geneseed learn` (writes to {{MEMORY}}), `geneseed context` (refreshes the project's `context.json`), `geneseed web start|stop` (the local browser UI on `127.0.0.1`). `geneseed web status` is read-only.
-5. Never run `setup`, `build`, `upgrade`, `bootstrap`, `update`, `sync-self`, `link`, `unlink`, or `uninstall` as a side effect — these are scope-changing and only run when the user explicitly asks ({{LAW}} II).
-6. The bundle's directory and section names are theme-independent (plain English everywhere); only voice and prose change per theme. Don't pattern-match on flavour words to find files.
+1. **Locate.** Run `geneseed status --json` first: `installs` lists every install on this machine — host, scope, root, state, theme, footprint, posture, mode, packs, excluded rules — and `rebuild`, the command that reproduces each one exactly. `geneseed` not on PATH → ask the user before using `npx geneseed` (it downloads the package), and prefix every command below the same way. Still nothing → look for a host root file: `~/.config/opencode/AGENT.md` or `.opencode/AGENT.md` (OpenCode), `~/.claude/CLAUDE.md` or `.claude/` (Claude Code), `.openclaude/` (OpenClaude), `AGENTS.md` beside `.bob/` or `.github/` (Bob, Copilot). None → say so; never install to "fix" it.
+2. **Read state** with the read-only verbs, cheapest first ({{DOCTRINE}} process 3): `geneseed status --json`, `geneseed version`, `geneseed catalog` (optionally `agents|skills|laws|ontology|doctrines`), `geneseed doctor`, `geneseed diff`, `geneseed mcp`, `geneseed memory list`, `geneseed exclude list`.
+3. **Read a piece** from disk, not from recall ({{LAW}} III): `<root>/agents/<name>.md`, `<root>/skills/<name>/SKILL.md`, `<root>/memory/`, `<root>/notebook/`. The {{ONTOLOGY}}, the {{LAWS}} and the active {{DOCTRINES}} are numbered `## N. …` sections of the install's root file.
+4. **Change an install only when the user asked for that change** ({{LAW}} II). Take that install's `rebuild` command from step 1, edit only the flag the user named (add it if the command omits it — `--posture` and `--mode` are left out at their defaults) — `--theme`, `--footprint lean|full`, `--posture`, `--mode direct|foreman`, `--doctrines craft,rigor|none`, `--exclude-rules "process 7"|none` — dry-run it first by running the same flags through `geneseed validate`, show the command, and run it once the user agrees. Never rebuild from a bare `geneseed build`: every omitted flag resets that setting to the generator default. Confirm with `geneseed status`.
+5. **Other writes also need the user's word:** `geneseed memory rm <name>`, `geneseed exclude add|remove <path>`, `geneseed web start|stop`, `geneseed uninstall --target <root> --yes`. Personal rules and the profile belong to their own {{SKILLS}}; do not edit `user-rules.md` or `PROFILE.md` from here.
+6. **Never on your own initiative:** `geneseed setup` (interactive only), `geneseed upgrade`, `geneseed update`, `geneseed bootstrap`, `geneseed sync-self`, `geneseed rebuild-all`, `geneseed migrate`, `geneseed link`, `geneseed unlink`. `learn`, `context` and the `*-gate` verbs are `geneseed-hook` verbs the host's hooks run — never run them by hand.
+7. Directory and section names are plain English in every theme; only prose changes. Do not search by flavour words.
 
 ## Done when
-- The user's question about the deployed harness is answered from the live install — file paths or CLI output — not from recall.
+- The answer comes from the live install — CLI output or file paths, not recall — or the requested change was rebuilt with every other setting preserved and `geneseed status` shows it.
 
 <!-- INCLUDE: skills/_self-improvement.md -->

package/src/skills/parallel-agents.md

@@ -5,7 +5,7 @@
 **Trigger:** two or more independent subtasks with no shared state or ordering between them — and a tool that can run subagents.
 
 ## Procedure
-1. Confirm independence: the subtasks must not depend on each other's output or write the same files ({{DOCTRINE}} process 8). Write down each unit's **write set** — the files or globs it may change — and intersect them; an overlap runs in sequence or goes to one owner, and shared append files (registries, index tables, lockfiles, generated bundles) stay with you. If they're sequential or share state, use [plan](plan.md) instead.
+1. Confirm independence: the subtasks must not depend on each other's output or write the same files ({{DOCTRINE}} process 7). Write down each unit's **write set** — the files or globs it may change — and intersect them; an overlap runs in sequence or goes to one owner, and shared append files (registries, index tables, lockfiles, generated bundles) stay with you. If they're sequential or share state, use [plan](plan.md) instead.
 2. Split the work into self-contained units, each with one clear goal and a defined output contract — what it must return.
 3. Dispatch each unit to its own subagent in one batch, each under a handoff envelope: the unit's goal, the inputs it needs, its **write set** (edit nothing outside it; return rows for a shared file instead of writing it), the observable check that proves it done, its output contract — naming every file it changed — and the inherited constraints (no commit/push — {{DOCTRINE}} process 5 stays with you; gaps reported, never invented). Hand each unit only the access its goal needs ({{LAW}} VII). Prefer the read-only [explorer {{AGENT}}](../{{DIR_AGENTS}}/explorer.md) for investigation so the heavy reading stays out of the main context ({{DOCTRINE}} process 3). Where no subagent capability exists, run the units sequentially as personas instead, converging the same way.
 4. Keep the main context lean: collect each subagent's distilled result, not its working transcript.

package/src/skills/pipeline.md

@@ -23,7 +23,7 @@ The minimum roster per task type. The parent may add specialists on top — secu
 
 1. Confirm the task is genuinely substantial — a trivial one-file tweak or a question does not warrant a crew; do it directly instead.
 2. Compose the crew from the floor above, adding specialists only where the task demands them.
-3. Isolate the crew's work in its own git worktree/branch (the SETUP.md worktree add-on). Where worktrees are unavailable, fall back to a single tree, one pipeline at a time, and say so. Give the crew a **write set** and check it against every other pipeline in flight ({{DOCTRINE}} process 8): two crews whose sets overlap do not run at once, and shared append files (registries, index tables, lockfiles, generated bundles) are the parent's to apply, never a crew's.
+3. Isolate the crew's work in its own git worktree/branch (the SETUP.md worktree add-on). Where worktrees are unavailable, fall back to a single tree, one pipeline at a time, and say so. Give the crew a **write set** and check it against every other pipeline in flight ({{DOCTRINE}} process 7): two crews whose sets overlap do not run at once, and shared append files (registries, index tables, lockfiles, generated bundles) are the parent's to apply, never a crew's.
 4. **The dev↔tester loop:** the developer implements, the tester validates — runs the tests and lint, produces raw logs. On failure, the findings go back to the developer. Cap at **5** iterations; on exhaustion, stop, do not merge, and report the failure with the branch left in place for inspection.
 5. **Two execution shapes**, chosen by host capability (same pattern as the [workflow {{SKILL}}](workflow.md)):
    - *Deterministic:* where the host exposes a `workflow` tool, run a saved script encoding analyst → developer → (tester ⇄ developer)×≤5 → proof.

package/src/skills/token-report/SKILL.md

@@ -28,9 +28,10 @@ picking the most recently active source:
 | Claude Code | `~/.claude/projects/<slug>/*.jsonl` | exact usage per request |
 | IBM Bob | `~/.bob/projects/<slug>/*.jsonl` (Claude-shaped, `$BOB_CONFIG_DIR` honoured) | exact usage per request |
 | OpenCode | `~/.local/share/opencode/opencode.db` (SQLite, v1.2+; pre-1.2 falls back to `storage/` JSON files) | exact `tokens` per request; child sessions attributed as subagents |
+| OpenClaude | `~/.openclaude/projects/<slug>/*.jsonl` (Claude-shaped, `$OPENCLAUDE_CONFIG_DIR` honoured) | exact usage per request |
 | GitHub Copilot | `~/.copilot/history-session-state/` | best effort — undocumented schema; token-like fields harvested, else estimates only |
 
-Useful flags: `--host claude|bob|opencode|copilot` to force a host,
+Useful flags: `--host claude|bob|openclaude|opencode|copilot` to force a host,
 `--transcript <path>` / `--session <id>` for a specific session,
 `--limit <tokens>` for the context-window limit used in the % columns
 (default 200000), `--top <n>` for the heaviest-items list.

package/src/skills/token-report/VENDOR.md

@@ -5,7 +5,7 @@ not third-party. It rides the vendored-folder mechanism because it bundles an
 executable (`scripts/token_report.mjs`) and Geneseed's flat-skill pipeline renders
 single `.md` files only. Listing it in the generator's `VENDORED_SKILL_DIRS`
 makes the whole folder ride along verbatim into every host emit — Claude Code,
-IBM Bob, OpenCode, GitHub Copilot — which is exactly what a multi-file skill needs.
+IBM Bob, OpenCode, GitHub Copilot, OpenClaude — which is exactly what a multi-file skill needs.
 
 - **Upstream:** this repository (first-party)
 - **License:** same as Geneseed (see repository LICENSE)
@@ -17,7 +17,7 @@ Consequences of riding this mechanism (deliberate):
   `description` and blockquote purpose line instead;
 - listed in AGENT.md's folder-skills section, not the main skills table.
 
-The script supports all four emitted hosts (exact usage on Claude Code, Bob and
-OpenCode; best-effort on Copilot, whose session-state schema is undocumented).
+The script supports all five emitted hosts (exact usage on Claude Code, Bob,
+OpenClaude and OpenCode; best-effort on Copilot, whose session-state schema is undocumented).
 If a host changes its session storage layout, fix the corresponding finder or
 parser in `scripts/token_report.mjs`.

package/src/skills/token-report/scripts/token_report.mjs

@@ -11,6 +11,8 @@
  *                              (SQLite, v1.2+: session/message/part tables,
  *                              JSON `data` columns; falls back to the pre-1.2
  *                              storage/ JSON files when no DB exists)
+ *   openclaude OpenClaude     ~/.openclaude/projects/<slug>/<session>.jsonl exact usage
+ *                              (Claude Code fork; $OPENCLAUDE_CONFIG_DIR honoured)
  *   copilot   GitHub Copilot   ~/.copilot/history-session-state/           best effort
  *                              (schema undocumented; token fields harvested
  *                              generically, estimates otherwise)
@@ -485,13 +487,14 @@ class SessionData {
 }
 
 // ---------------------------------------------------------------------------
-// Host: Claude Code / IBM Bob (same transcript shape, different config root)
+// Host: Claude Code / IBM Bob / OpenClaude (same transcript shape, different config root)
 // ---------------------------------------------------------------------------
 
 const slugify = (p) => p.replace(/[^A-Za-z0-9]/g, '-');
 
 function claudeShapedRoot(host) {
-  const env = { claude: 'CLAUDE_CONFIG_DIR', bob: 'BOB_CONFIG_DIR' }[host];
+  const env = { claude: 'CLAUDE_CONFIG_DIR', bob: 'BOB_CONFIG_DIR',
+    openclaude: 'OPENCLAUDE_CONFIG_DIR' }[host];
   const root = process.env[env] || path.join(homedir(), `.${host}`);
   return isDir(path.join(root, 'projects')) ? root : null;
 }
@@ -1017,6 +1020,7 @@ async function detect(hostArg, transcript, session) {
   const finders = {
     claude: () => claudeShapedFind('claude', transcript),
     bob: () => claudeShapedFind('bob', transcript),
+    openclaude: () => claudeShapedFind('openclaude', transcript),
     opencode: () => opencodeFind(session),
     copilot: () => copilotFind(transcript),
   };
@@ -1042,13 +1046,13 @@ async function detect(hostArg, transcript, session) {
   }
   if (!best) {
     sysExit('error: no session data found for any supported host '
-      + '(claude, bob, opencode, copilot)');
+      + '(claude, bob, openclaude, opencode, copilot)');
   }
   return [best[0], best[1]];
 }
 
 async function load(host, found) {
-  if (host === 'claude' || host === 'bob') return claudeShapedParse(host, found);
+  if (['claude', 'bob', 'openclaude'].includes(host)) return claudeShapedParse(host, found);
   if (host === 'opencode') {
     const [kind, payload] = found;
     if (kind === 'db') return opencodeDbParse(...payload);
@@ -1058,7 +1062,10 @@ async function load(host, found) {
   return copilotParse(found);
 }
 
-const HOST_NAMES = { claude: 'Claude Code', bob: 'IBM Bob', opencode: 'OpenCode', copilot: 'GitHub Copilot' };
+const HOST_NAMES = {
+  claude: 'Claude Code', bob: 'IBM Bob', openclaude: 'OpenClaude', opencode: 'OpenCode',
+  copilot: 'GitHub Copilot',
+};
 
 function render(d, limit, topN) {
   const out = [`# Token usage report — ${HOST_NAMES[d.host] ?? d.host}`, ''];
@@ -1188,11 +1195,11 @@ function render(d, limit, topN) {
 // ---------------------------------------------------------------------------
 
 const PROG = path.basename(process.argv[1] ?? 'token_report.mjs');
-const HOST_CHOICES = ['claude', 'bob', 'opencode', 'copilot'];
+const HOST_CHOICES = ['claude', 'bob', 'openclaude', 'opencode', 'copilot'];
 const OPTIONS = [
   ['-h, --help', 'show this help message and exit'],
   [`--host {${HOST_CHOICES.join(',')}}`, 'force a host instead of auto-detecting by recency'],
-  ['--transcript TRANSCRIPT', 'explicit transcript path (claude/bob/copilot)'],
+  ['--transcript TRANSCRIPT', 'explicit transcript path (claude/bob/openclaude/copilot)'],
   ['--session SESSION', 'explicit session id (opencode)'],
   ['--limit LIMIT', 'context window limit for % columns (default 200000)'],
   ['--top TOP', 'how many heaviest single items to list (default 5)'],

package/src/skills/workflow.md

@@ -23,7 +23,7 @@ work is worth a crew: a one-file tweak or a question never is.
 |---|---|---|---|
 | OpenCode | `workflow` (the `geneseed-workflow` plugin) | **saved only** — `<name>.js` in `.opencode/workflows/` per repo or `<config>/workflows/` global (`GENESEED_WORKFLOWS_DIR` overrides); nothing inline is eval'd | none — call it when the shape fits |
 | Claude Code | `Workflow` (native) | a saved `.claude/workflows/<name>` by `name`, **or** an inline `script` you author | **required** — the tool refuses unless the user opted in for this task ("use a workflow", "ultracode", a skill that says so) |
-| Bob, Copilot | none | — | fall back to [parallel-agents](parallel-agents.md) / [council](council.md) |
+| Bob, Copilot, OpenClaude | none | — | fall back to [parallel-agents](parallel-agents.md) / [council](council.md) |
 | any, under Orca | Orca orchestration (`orca skills get orchestration`) | tasks, not scripts — each task spec names its target, change, ownership and acceptance | the user asked to supervise or coordinate workers |
 
 Both runtimes speak the same primitives — `agent()`, `parallel()`, `pipeline()`,
@@ -60,7 +60,7 @@ carries the script API — load it before writing one).
    to the primitives, and hold to the host's size guideline unless the user asked for
    more.
 4. **Give every editing agent a write set, and isolate parallel editors** ({{DOCTRINE}}
-   process 8). Name in each editing `agent()` prompt the files it may change and have it
+   process 7). Name in each editing `agent()` prompt the files it may change and have it
    return the files it did change; overlapping sets run in sequence, not in one
    `parallel()`. Pass `isolation: 'worktree'` to each agent that edits in parallel — both
    runtimes take it; read-only agents need none. After the fan-out, compare the changed

package/themes/_TEMPLATE.json

@@ -73,7 +73,7 @@
   "DESC_HERDR": "<one-line description: drive herdr from inside it — split panes, spawn agents, read panes>",
   "DESC_RULE": "<one-line description: ask whether the user wants a standing rule or a durable memory, then write the memory, or pressure-test the rule until it is generic and adopt it in user-rules.md>",
   "DESC_PROFILE": "<one-line description: interview the user and draft or refresh PROFILE.md — who they are, how they work, how they like answers pitched; identity only, rules go to user-rules.md>",
-  "DESC_GENESEED": "<one-line description: interact with the deployed Geneseed harness — read files, status, doctor, diff>",
+  "DESC_GENESEED": "<one-line description: operate the deployed Geneseed harness — find installs and their settings, read files, status, doctor, diff, rebuild one setting on request>",
   "DESC_REVIEW_RESPONSE": "<one-line description: respond to review feedback — verify each point, apply or decline with reasons>",
   "LEX_I": "<themed title for Law I (Sealed Secrets)>",
   "LEX_II": "<themed title for Law II (One Intent, One Act)>",
@@ -90,6 +90,7 @@
   "PACK_RIGOR": "<display name of the rigor doctrine pack — how work is proven>",
   "PACK_OPS": "<display name of the ops doctrine pack — how the machine is driven>",
   "PACK_PROCESS": "<display name of the process doctrine pack — how a session runs>",
+  "PACK_COMMS": "<display name of the comms doctrine pack — how answers are presented>",
   "DOC_CRAFT_1": "<themed title for craft doctrine 1 (Automate Repetition)>",
   "DOC_CRAFT_2": "<themed title for craft doctrine 2 (English Configuration)>",
   "DOC_CRAFT_3": "<themed title for craft doctrine 3 (Documentation in Step)>",
@@ -115,8 +116,9 @@
   "DOC_PROCESS_4": "<themed title for process doctrine 4 (Read the Docs First)>",
   "DOC_PROCESS_5": "<themed title for process doctrine 5 (Consent Before Push)>",
   "DOC_PROCESS_6": "<themed title for process doctrine 6 (Bound the Loop)>",
-  "DOC_PROCESS_7": "<themed title for process doctrine 7 (Codes That Persist)>",
-  "DOC_PROCESS_8": "<themed title for process doctrine 8 (One Writer Per File)>",
+  "DOC_PROCESS_7": "<themed title for process doctrine 7 (One Writer Per File)>",
+  "DOC_COMMS_1": "<themed title for comms doctrine 1 (Codes That Persist)>",
+  "DOC_COMMS_2": "<themed title for comms doctrine 2 (Structure Beside Prose)>",
   "INTRO_DOC": "<themed intro: this file is the entry point an AI agent reads in this repo>",
   "INTRO_AGENTS": "<themed intro to the Agents section — delegate focused work to a specialist>",
   "INTRO_SKILLS": "<themed intro to the Skills section — run the written procedure before improvising>",

package/themes/biker.json

@@ -73,7 +73,7 @@
   "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing rule, or just something to remember? Then log the memory, or lean on the rule till it holds every corner before bolting it into user-rules.md.",
   "DESC_PROFILE": "Stamp the rider's plate into PROFILE.md — who they are, what they ride, how they like the road called; identity only, club rules bolt into user-rules.md.",
-  "DESC_GENESEED": "Interact with the deployed Geneseed harness — locate the install, read its files, run status, doctor, and diff, and drive learn, context, and the local web UI.",
+  "DESC_GENESEED": "Operate the deployed Geneseed harness — find each install and its settings, read its files, run status, doctor and diff, and rebuild it with one setting changed when the user asks.",
   "DESC_REVIEW_RESPONSE": "Take the notes straight — weigh each call, then act on it or push back with reasons.",
   "LEX_I": "Keep It in the Saddlebag · Sealed Secrets",
   "LEX_II": "One Move per Corner · One Intent, One Act",
@@ -90,6 +90,7 @@
   "PACK_RIGOR": "Shakedown",
   "PACK_OPS": "Throttle",
   "PACK_PROCESS": "The Ride",
+  "PACK_COMMS": "Hand Signals",
   "DOC_CRAFT_1": "Let the Cruise Control Do It · Automate Repetition",
   "DOC_CRAFT_2": "Notes in English · English Configuration",
   "DOC_CRAFT_3": "Roadbook in Sync · Documentation in Step",
@@ -115,8 +116,9 @@
   "DOC_PROCESS_4": "Read the Route Notes First · Read the Docs First",
   "DOC_PROCESS_5": "Crew's Nod Before You Push · Consent Before Push",
   "DOC_PROCESS_6": "Set the Turnaround Before You Roll · Bound the Loop",
-  "DOC_PROCESS_7": "Tag Every Part on the Bench · Codes That Persist",
-  "DOC_PROCESS_8": "One Wrench on Each Bolt · One Writer Per File",
+  "DOC_PROCESS_7": "One Wrench on Each Bolt · One Writer Per File",
+  "DOC_COMMS_1": "Tag Every Part on the Bench · Codes That Persist",
+  "DOC_COMMS_2": "Draw the Route Only If It Turns · Structure Beside Prose",
   "INTRO_DOC": "This file is the route briefing a coding rider reads when it joins this repository.",
   "INTRO_AGENTS": "Send the right rider for focused work instead of riding the whole run yourself; each has one job and reports exactly what it did.",
   "INTRO_SKILLS": "A Skill is a move you've drilled for a recurring task. Run the matching move before you wing it.",

package/themes/commentator.json

@@ -73,7 +73,7 @@
   "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing house rule, or just one for the notebook? Then log it, or run the rule through the replay from every angle before it goes on the board in user-rules.md.",
   "DESC_PROFILE": "Build the player profile in PROFILE.md — position, form, how they like the commentary pitched; identity only, the rulebook stays in user-rules.md.",
-  "DESC_GENESEED": "Interact with the deployed Geneseed harness — locate the install, read its files, run status, doctor, and diff, and drive learn, context, and the local web UI.",
+  "DESC_GENESEED": "Operate the deployed Geneseed harness — find each install and its settings, read its files, run status, doctor and diff, and rebuild it with one setting changed when the user asks.",
   "DESC_REVIEW_RESPONSE": "Take the scrutineer's notes straight — weigh each call, then act on it or push back with reasons.",
   "LEX_I": "Sealed Garage · Sealed Secrets",
   "LEX_II": "One Move per Corner · One Intent, One Act",
@@ -90,6 +90,7 @@
   "PACK_RIGOR": "Scrutineering",
   "PACK_OPS": "The Pit Lane",
   "PACK_PROCESS": "Race Control",
+  "PACK_COMMS": "Team Radio",
   "DOC_CRAFT_1": "Automate the Pit Stop · Automate Repetition",
   "DOC_CRAFT_2": "Regs in English · English Configuration",
   "DOC_CRAFT_3": "Notes in Sync · Documentation in Step",
@@ -115,8 +116,9 @@
   "DOC_PROCESS_4": "Read the Briefing First · Read the Docs First",
   "DOC_PROCESS_5": "Team Orders Before You Push · Consent Before Push",
   "DOC_PROCESS_6": "Call the Stint Length Before Lights Out · Bound the Loop",
-  "DOC_PROCESS_7": "Every Car Keeps Its Number · Codes That Persist",
-  "DOC_PROCESS_8": "One Driver Per Car · One Writer Per File",
+  "DOC_PROCESS_7": "One Driver Per Car · One Writer Per File",
+  "DOC_COMMS_1": "Every Car Keeps Its Number · Codes That Persist",
+  "DOC_COMMS_2": "Track Map Only When the Lines Matter · Structure Beside Prose",
   "INTRO_DOC": "This file is the race briefing a coding driver reads when it joins this repository.",
   "INTRO_AGENTS": "Put the right driver in the car for focused work instead of running the whole race yourself; each has one job and reports exactly what it did.",
   "INTRO_SKILLS": "A Skill is a rehearsed manoeuvre for a recurring task. Run the matching manoeuvre before you improvise.",

package/themes/cyberpunk.json

@@ -73,7 +73,7 @@
   "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing rule, or just something to keep on file? Then write the memory, or stress the rule till it holds in every sector before flashing it into user-rules.md.",
   "DESC_PROFILE": "Compile the user's ident into PROFILE.md — who they are, their rig, the bandwidth they want answers at; identity only, hard directives flash to user-rules.md.",
-  "DESC_GENESEED": "Interact with the deployed Geneseed harness — locate the install, read its files, run status, doctor, and diff, and drive learn, context, and the local web UI.",
+  "DESC_GENESEED": "Operate the deployed Geneseed harness — find each install and its settings, read its files, run status, doctor and diff, and rebuild it with one setting changed when the user asks.",
   "DESC_REVIEW_RESPONSE": "Action the review clean — verify each flag, then patch it or push back with reasons.",
   "LEX_I": "Encrypt the Cache · Sealed Secrets",
   "LEX_II": "One Run, One Move · One Intent, One Act",
@@ -90,6 +90,7 @@
   "PACK_RIGOR": "Diagnostics",
   "PACK_OPS": "Runtime",
   "PACK_PROCESS": "Session",
+  "PACK_COMMS": "Uplink",
   "DOC_CRAFT_1": "Script the Grind · Automate Repetition",
   "DOC_CRAFT_2": "Config in English · English Configuration",
   "DOC_CRAFT_3": "Docs in Sync · Documentation in Step",
@@ -115,8 +116,9 @@
   "DOC_PROCESS_4": "Read the Specs First · Read the Docs First",
   "DOC_PROCESS_5": "Authorize the Upload · Consent Before Push",
   "DOC_PROCESS_6": "Set the Kill-Switch Before the Loop · Bound the Loop",
-  "DOC_PROCESS_7": "Every Node Keeps Its Handle · Codes That Persist",
-  "DOC_PROCESS_8": "One Deck Per Node · One Writer Per File",
+  "DOC_PROCESS_7": "One Deck Per Node · One Writer Per File",
+  "DOC_COMMS_1": "Every Node Keeps Its Handle · Codes That Persist",
+  "DOC_COMMS_2": "Trace the Wires, Skip the Chrome · Structure Beside Prose",
   "INTRO_DOC": "This file is the boot sequence a coding daemon reads when it jacks into this repository.",
   "INTRO_AGENTS": "Spin the right daemon for focused work instead of running the whole job on one thread; each has one function and returns a clean log of what it changed.",
   "INTRO_SKILLS": "A Skill is a proven routine for a recurring task. Run the matching routine before you freestyle.",

package/themes/gamer.json

@@ -73,7 +73,7 @@
   "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing house rule, or just something to remember? Then save the memory, or test the rule against its worst case before binding it into user-rules.md.",
   "DESC_PROFILE": "Fill in the player card in PROFILE.md — main role, loadout, preferred difficulty; identity only, house rules go in user-rules.md.",
-  "DESC_GENESEED": "Interact with the deployed Geneseed harness — locate the install, read its files, run status, doctor, and diff, and drive learn, context, and the local web UI.",
+  "DESC_GENESEED": "Operate the deployed Geneseed harness — find each install and its settings, read its files, run status, doctor and diff, and rebuild it with one setting changed when the user asks.",
   "DESC_REVIEW_RESPONSE": "Take the review feedback like a coach's notes — verify each call, then apply it or push back with reasons.",
   "LEX_I": "No-Leak Run · Sealed Secrets",
   "LEX_II": "One Objective per Run · One Intent, One Act",
@@ -90,6 +90,7 @@
   "PACK_RIGOR": "Playtest",
   "PACK_OPS": "Controls",
   "PACK_PROCESS": "The Run",
+  "PACK_COMMS": "Voice Chat",
   "DOC_CRAFT_1": "Macro the Grind · Automate Repetition",
   "DOC_CRAFT_2": "Config in English · English Configuration",
   "DOC_CRAFT_3": "Patch Notes in Sync · Documentation in Step",
@@ -115,8 +116,9 @@
   "DOC_PROCESS_4": "Read the Quest First · Read the Docs First",
   "DOC_PROCESS_5": "Ready-Check Before Push · Consent Before Push",
   "DOC_PROCESS_6": "Set the Retry Cap Before the Grind · Bound the Loop",
-  "DOC_PROCESS_7": "Every Item Keeps Its Tag · Codes That Persist",
-  "DOC_PROCESS_8": "No Double-Looting the Chest · One Writer Per File",
+  "DOC_PROCESS_7": "No Double-Looting the Chest · One Writer Per File",
+  "DOC_COMMS_1": "Every Item Keeps Its Tag · Codes That Persist",
+  "DOC_COMMS_2": "Minimap Only When There Is a Route · Structure Beside Prose",
   "INTRO_DOC": "This file is the loading screen a coding co-op partner reads when it joins this repository.",
   "INTRO_AGENTS": "Pick the right class for focused work instead of soloing the whole raid; each has one role and reports exactly what it did.",
   "INTRO_SKILLS": "A Skill is a practiced combo for a recurring task. Run the matching combo before you freestyle.",

package/themes/imperial.json

@@ -73,7 +73,7 @@
   "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — a standing edict, or a matter merely to be remembered? Then inscribe the memory, or try the edict against the case that would break it before it enters user-rules.md.",
   "DESC_PROFILE": "Inscribe the user's identity into PROFILE.md — grant audience, ask who they are and how they will to be served; identity only, edicts belong in user-rules.md.",
-  "DESC_GENESEED": "Interact with the deployed Geneseed harness — locate the install, read its files, run status, doctor, and diff, and drive learn, context, and the local web UI.",
+  "DESC_GENESEED": "Operate the deployed Geneseed harness — find each install and its settings, read its files, run status, doctor and diff, and rebuild it with one setting changed when the user asks.",
   "DESC_REVIEW_RESPONSE": "Answer the review with discipline — weigh each judgement, then heed it or refute it with cause.",
   "LEX_I": "Arcana Sigillata · Sealed Secrets",
   "LEX_II": "Unus Actus · One Intent, One Act",
@@ -90,6 +90,7 @@
   "PACK_RIGOR": "Ordeal",
   "PACK_OPS": "Enginery",
   "PACK_PROCESS": "Observance",
+  "PACK_COMMS": "Vox",
   "DOC_CRAFT_1": "Machina Pro Labore · Automate Repetition",
   "DOC_CRAFT_2": "Lingua Una · English Configuration",
   "DOC_CRAFT_3": "Scriptura Concurrens · Documentation in Step",
@@ -115,8 +116,9 @@
   "DOC_PROCESS_4": "Lege Prius · Read the Docs First",
   "DOC_PROCESS_5": "Consensus Ante Translationem · Consent Before Push",
   "DOC_PROCESS_6": "Finis Ante Iter · Bound the Loop",
-  "DOC_PROCESS_7": "Sigla Perstantia · Codes That Persist",
-  "DOC_PROCESS_8": "Unus Scriptor Singulis Tabulis · One Writer Per File",
+  "DOC_PROCESS_7": "Unus Scriptor Singulis Tabulis · One Writer Per File",
+  "DOC_COMMS_1": "Sigla Perstantia · Codes That Persist",
+  "DOC_COMMS_2": "Schema Ubi Sagittae Loquuntur · Structure Beside Prose",
   "INTRO_DOC": "This file is the gene-seed's core — the first writ a servant reads on entering this world.",
   "INTRO_AGENTS": "Hand focused work to the specialist whose duty it is rather than carrying every burden in one context; each holds one purpose and returns a clear account of what it changed.",
   "INTRO_SKILLS": "A Skill is a rite proven by repetition. Perform the matching rite before you improvise.",