geneseed 5.6.0 → 6.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (84) hide show
  1. package/CHANGELOG.md +20 -0
  2. package/README.md +2 -2
  3. package/SHIPPED.md +2 -2
  4. package/adapters/opencode/README.md +7 -4
  5. package/docs/concepts/agents.md +8 -0
  6. package/docs/concepts/exclusions.md +1 -1
  7. package/docs/concepts/foreman-mode.md +4 -2
  8. package/docs/concepts/kits.md +20 -2
  9. package/docs/concepts/loops.md +5 -0
  10. package/docs/concepts/skills.md +1 -1
  11. package/docs/concepts/superpowers-kit.md +79 -0
  12. package/docs/extending.md +11 -4
  13. package/docs/guides/install-scripted.md +1 -1
  14. package/docs/reference/cli.md +2 -0
  15. package/docs/reference/profiles.md +10 -5
  16. package/harness.config.json +1 -1
  17. package/js/README.md +2 -0
  18. package/js/build/args.mjs +4 -2
  19. package/js/build/driver.mjs +8 -8
  20. package/js/build/emit-claude.mjs +5 -3
  21. package/js/build/emit-opencode.mjs +2 -2
  22. package/js/build/generate.mjs +1 -1
  23. package/js/build/profile.mjs +15 -7
  24. package/js/build/render.mjs +81 -10
  25. package/js/build/source.mjs +75 -1
  26. package/js/cli-table.json +17 -2
  27. package/js/hosts/installs.mjs +50 -4
  28. package/js/hosts/native.mjs +104 -3
  29. package/js/hosts/opencode.mjs +13 -15
  30. package/js/inspect/checks-authoring.mjs +24 -1
  31. package/js/inspect/checks-build.mjs +43 -2
  32. package/js/inspect/checks-counts.mjs +72 -1
  33. package/js/inspect/diff.mjs +17 -3
  34. package/js/inspect/doctor.mjs +23 -2
  35. package/js/inspect/status.mjs +5 -1
  36. package/js/inspect/validate.mjs +1 -1
  37. package/js/loop/catalog.mjs +10 -0
  38. package/js/maintain/kit-migration.mjs +109 -0
  39. package/js/maintain/plugin-detect.mjs +150 -0
  40. package/js/maintain/profiles.mjs +46 -5
  41. package/js/maintain/setup.mjs +45 -11
  42. package/js/maintain/update.mjs +1 -1
  43. package/js/web/actions.mjs +28 -7
  44. package/js/web/api.mjs +3 -1
  45. package/js/web/profiles-api.mjs +11 -7
  46. package/package.json +1 -1
  47. package/profiles/autonomous.json +1 -0
  48. package/profiles/corporate.json +1 -1
  49. package/profiles/mentor.json +1 -0
  50. package/profiles/minimal.json +2 -1
  51. package/profiles/starter.json +1 -1
  52. package/src/AGENT.md.tmpl +1 -6
  53. package/src/agents/_template.md +4 -0
  54. package/src/agents/advocate.md +1 -0
  55. package/src/agents/architect.md +1 -0
  56. package/src/agents/developer.md +12 -4
  57. package/src/agents/empiricist.md +1 -0
  58. package/src/agents/explorer.md +1 -0
  59. package/src/agents/framer.md +1 -0
  60. package/src/agents/historian.md +1 -0
  61. package/src/agents/operator.md +1 -0
  62. package/src/agents/performance.md +2 -1
  63. package/src/agents/pragmatist.md +1 -0
  64. package/src/agents/react-reviewer.md +1 -0
  65. package/src/agents/researcher.md +1 -0
  66. package/src/agents/reviewer.md +1 -0
  67. package/src/agents/security.md +1 -0
  68. package/src/agents/skeptic.md +1 -0
  69. package/src/agents/spring-reviewer.md +1 -0
  70. package/src/agents/spring-security.md +1 -0
  71. package/src/agents/steward.md +1 -0
  72. package/src/agents/user-advocate.md +1 -0
  73. package/src/agents/visionary.md +1 -0
  74. package/src/bricks/ci-fix.md +12 -2
  75. package/src/kits/superpowers/missing.md +3 -0
  76. package/src/kits/superpowers/provider.md +7 -0
  77. package/src/kits/superpowers/rules.md +6 -0
  78. package/src/kits/superpowers.json +45 -0
  79. package/src/modes/foreman.md +18 -12
  80. package/src/skills/parallel-agents.md +2 -2
  81. package/src/skills/spring-boot/cloud.md +8 -2
  82. package/src/skills/spring-boot.md +3 -1
  83. package/src/skills/spring-testing.md +3 -3
  84. package/src/upstreams.json +1 -1
package/CHANGELOG.md CHANGED
@@ -8,6 +8,26 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [6.0.0] — 2026-11-17
12
+
13
+ ### Added
14
+
15
+ - **Sub-agent model tiers on Claude Code, opt-in with `--tiers auto`.** Each agent carries a tier: *strong* (review, security, architecture, performance) runs on the session's own model, *standard* (the default) on `sonnet`, *light* (explorer, researcher, the council seats) on `haiku`. A `tiers` map in `agent-overrides.json` names other models, and a per-agent pin still wins. The setting is recorded with the install and kept by every rebuild: rebuild-all, upgrade, profile apply, the wizard, console deploy and restore. Off by default, and with it off every agent file is unchanged. OpenCode, OpenClaude and Bob still inherit for now. On Bedrock or Vertex, the doctor says to pin `ANTHROPIC_DEFAULT_SONNET_MODEL` / `ANTHROPIC_DEFAULT_HAIKU_MODEL`.
16
+
17
+ ### Changed
18
+
19
+ - **BREAKING (6.0.0): five Rites are now the `superpowers` kit.** `brainstorm`, `debug`, `plan`, `geneseed-code-review` and `review-response` are Geneseed's vendored, modified copies of obra/superpowers (Jesse Vincent, MIT). They are off unless a build names the kit (`--kits superpowers`). With the kit off, core links to them point at the official plugin's skills (`superpowers:systematic-debugging` on Claude Code, the bare name on OpenCode), and the instructions file gains a Workflow provider block. `parallel-agents`, `pipeline` and the `reviewer` agent stay core. See [the superpowers kit](docs/concepts/superpowers-kit.md).
20
+ - **Existing installs keep the five Rites.** `rebuild-all`, `update` and `migrate` turn the kit on for an install built before it existed, unless the plugin is seen, and print one line per install saying which.
21
+ - The Shipped profiles `starter` and `corporate` set the kit on; `mentor`, `minimal` and `autonomous` choose it by detection (`kitsByDetection`, a new optional profile key). The setup wizard asks the kit question after the install mode and defaults it by detection (Bob and OpenClaude default to yes).
22
+ - `doctor` and `status` warn when the kit and the official plugin are both on, or both off. Detection reads files only: the Claude Code and OpenCode settings, then the desktop app's own plugin state, labelled as app state; each line names the file it read.
23
+ - The `ci-fix` brick carries its CI-specific steps in its own body, so it works with the kit off.
24
+ - **Foreman workers spend fewer tokens.** A task worker runs the targeted test file while it iterates, sends the output to a file and reads only the count line and the failing test names, and waits for a background run's notice instead of polling it. Its loop bound is now countable: after the 3rd run in a row that leaves the same test red, it returns `STATUS: ERROR`. At about 150k tokens of context, or after about 20 proof runs, it commits its work in progress and returns `STATUS: RELAY` with a handoff note, and the session hands the task off to a fresh worker on the same branch. A task gets at most 2 hand-offs; then it goes to the user. An idle worker takes a new task only when it works in the same files and its context is under about 100k tokens. Text only; reaches an install on its next emit.
25
+
26
+ ### Fixed
27
+
28
+ - **An excluded rule is no longer cited when the source wraps the citation list.** The render drops an excluded rule's citations from the always-on file, but it missed a list that breaks onto a new line after a comma. So with `process 2` excluded, the lean *Bound the Loop* still ended `(*Surface Failures*, *Plan Before Acting*)`. Such a list is now one group, and only the kept citations stay.
29
+ - **`--exclude-skills` now counts relative links.** It protected only `{{DIR_SKILLS}}/<name>` links, so it accepted a skill another skill linked to by a relative path and shipped a dead link. `prototype` was one: the `minimal` profile excluded it and `wayfinder` linked it. The profile no longer excludes it, and an install whose `Excluded skills:` line names a now-linked skill has the exclusion dropped, with a notice, at its next rebuild.
30
+
11
31
  ## [5.6.0] — 2026-11-17
12
32
 
13
33
  ### Changed
package/README.md CHANGED
@@ -11,7 +11,7 @@
11
11
  [![Node >= 22.7](https://img.shields.io/badge/node-%3E%3D22.7-5fa04e)](package.json)
12
12
  [![zero dependencies](https://img.shields.io/badge/deps-zero-success)](package.json)
13
13
  [![Themes](https://img.shields.io/badge/themes-14-9cf)](themes/)
14
- [![Skills](https://img.shields.io/badge/skills-51-blueviolet)](src/skills/)
14
+ [![Skills](https://img.shields.io/badge/skills-46-blueviolet)](src/skills/)
15
15
  [![Agents](https://img.shields.io/badge/agents-20-orange)](src/agents/)
16
16
  [![Laws and doctrines](https://img.shields.io/badge/laws-9%20%2B%2030%20doctrines-critical)](src/doctrines/)
17
17
  [![Plugins](https://img.shields.io/badge/plugins-7-teal)](adapters/opencode/plugins/)
@@ -210,7 +210,7 @@ The harness ships as a small set of layers, and the web console's rail is the sa
210
210
  | **🛡️ Rules** (`laws/`) | 9 universal laws — always in force, never toggleable: sealed-secrets, one-intent-one-act, verify-before-asserting, deletion-is-deliberate, surface-failures, data-not-orders, least-privilege, cure-the-cause, echo-the-intent. Each rule has a permanent id; its number is only its position, and the harness cites rules by name |
211
211
  | **📐 Doctrines** (`doctrines/`) | practice packs, chosen per install at build time: **craft** (how code is written), **rigor** (how work is proven), **ops** (how the machine is operated), **process** (how a task is run), **comms** (how answers are presented). A doctrine rule may tighten a Rule, never repeal one, and the user's own `user-rules.md` outranks it. Pick with `geneseed-build --doctrines craft,rigor` (or `none`), a single rule with `--exclude-rules "process 7"`, in the setup wizard, or through the switches on the console's Constitution page; all five pack files ship on disk either way, so a citation into a pack you left out still resolves |
212
212
  | **🤖 Agents** (20) | capability specialists: `reviewer`, `tester`, `architect`, `docs`, `security`, `performance`, `explorer`, `researcher`, `developer`, `memory-curator` — plus a debate **council** the `council` skill convenes: `advocate`, `skeptic`, `pragmatist`, `steward`, `visionary`, `user-advocate`, `framer`, `empiricist`, `operator`, `historian` |
213
- | **🛠 Skills** (51) | repeatable workflows: brainstorm · plan · **codebase-design** · **wayfinder** · **develop** · **worktree** · debug · **prototype** · refactor · **ponytail** · **adhd** · **forge-mcp** · **bruno** · geneseed-code-review · **fresh-eyes** · **security-audit** · **dependencies** · **review-response** · commit · **ship** · **release** · **git-history** · document-project · **frontend-design** · **deck** · **prose** · **ingest** · **research** · **teach** · **learn-mode** · **ownership** · handoff · roast-me · **council** · parallel-agents · **workflow** · **wiki** · **geneseed** · **rule** · **profile** · **skill-forge** · **pipeline** · **loop** · **factory** · **factory-forge** · **brick-forge** · **daydream** · **react-view-transitions** · **token-report** · **explain-changes** · **diagram-design** |
213
+ | **🛠 Skills** (46) | repeatable workflows: **codebase-design** · **wayfinder** · **develop** · **worktree** · **prototype** · refactor · **ponytail** · **adhd** · **forge-mcp** · **bruno** · **fresh-eyes** · **security-audit** · **dependencies** · commit · **ship** · **release** · **git-history** · document-project · **frontend-design** · **deck** · **prose** · **ingest** · **research** · **teach** · **learn-mode** · **ownership** · handoff · roast-me · **council** · parallel-agents · **workflow** · **wiki** · **geneseed** · **rule** · **profile** · **skill-forge** · **pipeline** · **loop** · **factory** · **factory-forge** · **brick-forge** · **daydream** · **react-view-transitions** · **token-report** · **explain-changes** · **diagram-design** |
214
214
  | **🔌 Plugins** (OpenCode) | `geneseed-context` injects project docs *and your machine wiki* every session (and across compaction); `geneseed-learn` distils memory at session end; `geneseed-guard` enforces the safety Laws and protected wiki folders at the tool boundary; `geneseed-workflow` registers the `workflow` tool that runs saved orchestration scripts; `geneseed-notify` sends a native OS notification when a long run finishes; `geneseed-ponytail` holds a minimal-code mode (`/ponytail lite\|full\|ultra\|off`), opt-in, injecting the laziest-that-works ruleset every turn so it doesn't drift; `geneseed-activity` streams what each session is doing to the web console's Activity view |
215
215
  | **🧠 Memory** (`memory/`) | one-fact-per-file durable knowledge, indexed by `MEMORY.md` (git-ignored, personal) |
216
216
  | **🔗 Shared tier** (`~/.config/geneseed`) | one machine-wide home for memory, your rules, profile, wiki manifest, exclude paths and notes, read by every global install on every host; existing stores [fold into it](docs/guides/upgrade-to-5.md) on the next global rebuild, and a project install opts in with `--shared-tier on` |
package/SHIPPED.md CHANGED
@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
20
20
  > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
21
21
  > human-readable label only. The canonical identity of an installed harness is the
22
22
  > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
23
- > string. Current label: **5.6.0**.
23
+ > string. Current label: **6.0.0**.
24
24
 
25
25
  ## Capabilities
26
26
 
@@ -29,7 +29,7 @@ Every row below is present in the tree today; "Spec" names the design record.
29
29
  | Capability | What it is | Spec |
30
30
  | --- | --- | --- |
31
31
  | **Themed generator** | One neutral `src/` → 14 themed bundles via `geneseed-build` (zero dependencies); structure stays theme-independent | [DESIGN.md](DESIGN.md) |
32
- | **Laws / Agents / Skills / Memory / Notebook** | 9 laws, 20 agents, 51 skills, the memory convention, and the agent's sovereign notebook | `2026-06-11-notebook-sovereign-space` · `2026-06-10-notebook-agent-own-space` |
32
+ | **Laws / Agents / Skills / Memory / Notebook** | 9 laws, 20 agents, 46 skills, the memory convention, and the agent's sovereign notebook | `2026-06-11-notebook-sovereign-space` · `2026-06-10-notebook-agent-own-space` |
33
33
  | **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Ownership, Conduct — the Pact absorbed into Telos), the nine always-on **Invariants**, and five toggleable **Doctrine** packs (craft, rigor, ops, process, comms) addressed `<pack> <n>`. Every rule carries a permanent id; its number is its position, computed at render time, and a citation renders as the rule's principle name. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order: the Invariants, then the user's `user-rules.md`, then the Ontology, then the active Doctrines, then the mode, then `PROFILE.md`, posture and theme, which inform and never bind. `doctor`'s `constitutionProblems` gates rule ids (declared, unique, never a retired one), the per-rule Principle column, every `{{LAW:<id>}}` / `{{DOCTRINE:<id>}}` citation in `src/`, and the rule that an always-on tier may never cite a toggleable one | `2026-08-19-three-tier-constitution-design` |
34
34
  | **`doctor`** | One check: unresolved tokens, dead/non-hermetic links, theme-key parity, authoring gates, rendered-bundle drift | `2026-06-07-theme-aware-doctor-diff` |
35
35
  | **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements/improvements-<date>-<time>.md` back-port inside the install | `2026-06-12-improvements-export` |
@@ -361,10 +361,13 @@ behaviour** — nothing changes the machine's current agent/model unless you opt
361
361
  { "agents": { "reviewer": { "model": "anthropic/claude-haiku-4-5", "temperature": 0.1, "variant": "high", "steps": 20 } } }
362
362
  ```
363
363
  Re-emit to apply. (A future TUI screen will edit this map.) Unlisted keys are omitted,
364
- so the agent inherits OpenCode's defaults. The stub also carries an inert
365
- `_recommended.cheap-tier` list — the read-and-summarise seats (explorer, researcher,
366
- tester, and the council bench) worth routing to a cheaper model; copy the names you
367
- want into `agents`, nothing applies by itself.
364
+ so the agent inherits OpenCode's defaults. The agent sources carry a tier
365
+ (`strong`, `standard` as the default, or `light` for the read-and-summarise seats: explorer,
366
+ researcher and the council bench); a build with `--tiers auto` maps a tier to a model
367
+ through a `tiers` map beside `agents` (`{ "tiers": { "standard": "<model>", "light": "<model>" } }`),
368
+ and an `agents` entry always wins over its tier. Today that routing is written for Claude
369
+ Code only; on OpenCode the tier is recorded and every agent still inherits until its
370
+ resolver ships.
368
371
  - **Agent colours.** Each capability agent is emitted with a `color:` set to an OpenCode
369
372
  *named theme slot*, sourced from the active harness theme's `AGENT_COLORS` map
370
373
  (`themes/_TEMPLATE.json`; the shipped default — architect=`primary`, reviewer=`warning`,
@@ -38,6 +38,14 @@ An agent is picked by **what the work needs**, not by **where the file lives**.
38
38
 
39
39
  In [foreman mode](foreman-mode.md) the session hands each task that would block it to one background `developer` worker. A pipeline crew — explorer, developer and tester, plus whatever specialists the task needs — runs only when you ask for one.
40
40
 
41
+ ### Model tiers
42
+
43
+ Each agent source names a tier on a line of its own, `<!-- tier: strong|light -->`; an unmarked agent is `standard`. `strong` is the judgement seats (`reviewer`, `security`, `architect`, `performance`, and the kit seats `react-reviewer`, `spring-reviewer`, `spring-security`), `light` is the read-only seats (`explorer`, `researcher` and the ten council debaters), and the rest are `standard`. The line never reaches an install.
44
+
45
+ By default nothing changes: every agent runs on your session model. A build with `--tiers auto` (recorded in the install, kept by `rebuild-all`) makes a **Claude Code** install write `model: sonnet` for `standard` agents and `model: haiku` for `light` ones; `strong` agents write no line and inherit. OpenClaude and Bob inherit, and OpenCode records the choice and still inherits (its resolver is not built yet).
46
+
47
+ Two settings of yours steer it, both in `agent-overrides.json`. A `tiers` map renames the models (`{ "tiers": { "standard": "opus", "light": "claude-haiku-4-5" } }`; an empty value means inherit), and an `agents.<name>.model` pin beats its tier, a stronger model included. The build always writes the alias. On Bedrock or Vertex, Claude Code maps an alias through `ANTHROPIC_DEFAULT_SONNET_MODEL` or `ANTHROPIC_DEFAULT_HAIKU_MODEL`; without it, it uses its built-in model id, which may not exist in your cloud project. With `CLAUDE_CODE_USE_BEDROCK` or `CLAUDE_CODE_USE_VERTEX` set and the variable missing, `geneseed doctor` tells you to pin it.
48
+
41
49
  ### Agents learn too
42
50
 
43
51
  When a subagent finishes, the hook copies each `spec-feedback:` line its report ends with into a notes file, with no model call. The line picks its scope with one question: is it true in any repo, or only here? A flaw of the spec is true in any repo: `[agent]` goes into the machine notes, `agent-notes/<name>.md` under `~/.config/geneseed/notes/` (a `[general]` line into `agent-notes/_general.md` there, which every agent reads). A fact true only in this repo is tagged `[agent:project]` and goes into `notebook/agent-notes/<name>.md` at the project root, one folder for every host (in a linked worktree, the main checkout's); a `[general:project]` line goes into `notebook/agent-notes/_general.md`, which every agent reads in that repo. The agent reads the machine notes and then the project notes first at its next dispatch; where they disagree, the project notes win. So a flaw it reported is in front of it until the user folds the fix into the source. See [Hooks](hooks.md). (Not on Bob, which has no subagent-finished event: there the caller copies the line into the machine or the project file.)
@@ -80,7 +80,7 @@ geneseed build --emit claude-global --exclude-skills "bruno,react-view-transitio
80
80
 
81
81
  The skill's files are not written, its catalogue row goes, and an OpenCode `/command` that runs it goes too. The install records the list (`Excluded skills: …` under its skill section), and every rebuild and upgrade keeps it. `--exclude-skills none` puts them all back.
82
82
 
83
- A few skills cannot be excluded, because the harness itself links to them by path — `council`, `rule`, `skill-forge`, `workflow` and a handful more. The flag names them when it refuses one. Skills you installed yourself are not Geneseed's to exclude: remove those from the host's skills folder directly.
83
+ A few skills cannot be excluded, because the harness itself links to them, by path or by a relative link from another skill — `council`, `rule`, `skill-forge`, `workflow`, `prototype` and a handful more, the five [superpowers kit](superpowers-kit.md) skills among them. (Until the relative links were scanned, `--exclude-skills prototype` was accepted and left a dead link in `wayfinder`; an install that did so has the exclusion dropped, with a notice, at its next rebuild.) The flag names them when it refuses one. Skills you installed yourself are not Geneseed's to exclude: remove those from the host's skills folder directly.
84
84
 
85
85
  ### Law IV deletion gate — on or off
86
86
 
@@ -36,7 +36,7 @@ Bob's `start_subtask` (the `subtask` group, held by the `agent` mode) does not c
36
36
 
37
37
  ### The task worker
38
38
 
39
- A task worker is one `developer` agent in its own git worktree. It explores, implements and tests in a single context, loading skills as it needs them, so nothing it read is lost in a hand-off. After two repair rounds on its own failing tests it returns with its findings instead of looping.
39
+ A task worker is one `developer` agent in its own git worktree. It explores, implements and tests in a single context, loading skills as it needs them, so nothing it read is lost in a hand-off. While it iterates, it runs the targeted test file with output to a file. It reads only the count line and the failing test names. It waits for a background run's completion notice and never polls it. Two countable bounds stop it, and the task-worker section of the `developer` spec sets their numbers. When the same test stays red run after run, the worker returns `STATUS: ERROR` with its findings. When its context or its count of proof runs gets too large, it commits its work in progress. It then returns `STATUS: RELAY` with a handoff note: the failing tests, what it tried, the next step. The session hands the task off to a fresh worker on the same worktree and branch, with that note. A hand-off is no failure. After a first worker's `STATUS: ERROR`, the session hands off once, with the findings. The mode caps the hand-offs per task, and the ledger line counts them. Past the cap, or on an error from a worker that took a hand-off, the session takes the task to you.
40
40
 
41
41
  A worker can lead a small team inside its own worktree. It can start read-only helpers (`explorer`, `researcher`) at any time. It can also start writing **sub-workers**, each in its own worktree branched from the worker's branch. The worker commits and merges their branches into its own branch, locally, and re-runs the proof after each merge. *Consent Before Push* names this as a batch. The git gate lets a commit or merge through without a prompt only when all of these hold: the host marks the call as a sub-agent's (Claude Code's `agent_id`), the directory is a linked worktree, and its branch is not shared (`main`, `master`, `develop`, `development`, `release/*`, `hotfix/*`, a remote's default, or the branch the main checkout has, in any letter case). The command may hold only adds, read-only git commands, a plain `git fetch` (no `a:b` refspec, no option that names a program) and plain commit or merge arguments with one quoted message, after at most one `cd`; anything that can run a second command (`(`, `@`, `$`, `{`, a backtick) asks. A session that only runs in a worktree, as the desktop app's do, is judged by the own-branch pass instead ([Hooks](hooks.md)). A push still asks everywhere. Bob sends no sub-agent field, so Bob still logs its warning. On OpenCode the static `git commit*` permission still asks, because a permission glob sees only the command, not the worktree. The gate reads the command, not git's own hooks: a `post-commit` hook or a `core.hooksPath` can push on commit, on any branch, as it always could. Nesting stops at two levels below the session: session → worker → sub-worker. A sub-worker starts nothing. A lead holds every member's result before it ends. The blind reviewer is still the session's, never the worker's.
42
42
 
@@ -62,7 +62,9 @@ The session keeps a ledger in its notebook (`notebook/foreman-ledger.md`), one l
62
62
 
63
63
  A new worker starts only when the old one cannot be resumed, and it receives a note of the ask, the diff so far and what was tried.
64
64
 
65
- A new task gets a new worker by default. The session may give it to an idle worker whose own task is already merged or dropped, when the new task works in the same files or context and that worker has used little of its context. The worker then starts the new task on a new branch from the current BASE. It gets the full brief that any new worker gets (BASE, write set, proof commands, the Brief checklist), and the session checks its write set against every task in flight. Whether a context is light or heavy is a judgement call, not a number: the session writes its reason (same files, context used) in the new task's ledger line. A worker never holds two live tasks at once. A worker whose context is heavy, or whose last task touched other code, retires.
65
+ A worker that the official superpowers plugin supplies (`dispatching-parallel-agents`, `subagent-driven-development`, `executing-plans`) is bound by the same brief: the session writes it by the Brief checklist, and the Workflow provider block of the instructions file says so when the [superpowers kit](superpowers-kit.md) is off.
66
+
67
+ A new task gets a new worker by default. The session may give it to an idle worker whose own task is already merged or dropped, when the new task works in the same files and that worker's context is still under the size the mode sets. The worker then starts the new task on a new branch from the current BASE. It gets the full brief that any new worker gets (BASE, write set, proof commands, the Brief checklist), and the session checks its write set against every task in flight. The session writes its reason (same files, context size) in the new task's ledger line. Otherwise it starts a new worker. A worker never holds two live tasks at once. A worker past that size, or whose last task touched other code, retires.
66
68
 
67
69
  ### Status lines
68
70
 
@@ -6,7 +6,7 @@ kind: "concept"
6
6
  section: "Configuration"
7
7
  description: "Opt-in bundles of skills, agents and rules for one stack, off unless you name them."
8
8
  ---
9
- A **kit** is an opt-in bundle of skills, agents and rules for one stack. Kits are off by default and switched on per install, project or global, on every host. An install without a kit pays nothing for it. Inside an install that has it on, a kit's skills and agents are ordinary: the model picks them as it picks any other.
9
+ A **kit** is an opt-in bundle of skills, agents and rules for one stack. Kits are off by default and switched on per install, project or global, on every host. An install without a kit pays nothing for it, with one exception: with the [superpowers kit](superpowers-kit.md) off, the instructions file carries a short Workflow provider block that says where those five Rites come from. Inside an install that has it on, a kit's skills and agents are ordinary: the model picks them as it picks any other.
10
10
 
11
11
  > **You already know this:** an optional dependency group, like `pip install pkg[postgres]`. The core install stays small, and you opt into the extra parts for your stack.
12
12
 
@@ -63,6 +63,24 @@ The fifth kit is `terminal-tools`, for terminal programs the agent drives throug
63
63
 
64
64
  Its rules gate each tool on its environment, read live state before acting, close only what the agent opened, never stop the user's server or service, and leave every login and credential to the user. `herdr` is adapted from the official skill of [herdrdev/herdr](https://github.com/herdrdev/herdr) by herdrdev (Apache-2.0), condensed into house format; its skill folder ships `LICENSE-herdr.txt`. `opencode-cli` is first-party and targets OpenCode V2 only, verified against the V2 source at v2.3.0: the V1 commands top-level `export` and `import`, `attach`, `agent create` and `mcp debug` are not in its command table.
65
65
 
66
+ The sixth kit is `superpowers`: Geneseed's own, modified copies of five [obra/superpowers](https://github.com/obra/superpowers) skills (Jesse Vincent, MIT): `brainstorm`, `debug`, `plan`, `geneseed-code-review` and `review-response`. Unlike the others it is a stand-in: the official superpowers plugin offers the same skills, so an install has the kit or the plugin, never both. It is the one kit that core files link to, which the next section explains, and [its own page](superpowers-kit.md) covers what the plugin replaces, detection and the profiles.
67
+
68
+ ### A kit that a plugin can replace
69
+
70
+ A kit manifest may carry `replacedBy`. It is the only home of the member to plugin-skill mapping and of how each host spells a plugin skill:
71
+
72
+ ```json
73
+ "replacedBy": {
74
+ "upstream": "superpowers",
75
+ "provider": "kits/superpowers/provider.md",
76
+ "missing": "kits/superpowers/missing.md",
77
+ "hosts": { "claude": "superpowers:{name}", "opencode": "{name}" },
78
+ "skills": { "debug": "systematic-debugging" }
79
+ }
80
+ ```
81
+
82
+ The one rule that normally holds, that a core file may not link to a kit member, has this exception. With such a kit **off**, the render rewrites every core link to a member in its single `renderAll` pass: the link text stays and the target becomes the plugin's skill, in the host's spelling, or plain text on a host with no plugin (Bob, OpenClaude, the plain bundle). It also leaves a **Workflow provider** block in the instructions file. With the kit on, nothing changes. `doctor` checks that every member has a mapping, that `upstream` is a key of `src/upstreams.json`, that the two block files exist inside the word budget, and that no core spec names a member in prose without a link, because only links can be rewritten.
83
+
66
84
  ### Switching kits on and off
67
85
 
68
86
  ```bash
@@ -77,7 +95,7 @@ geneseed build --emit claude-global --kits none
77
95
 
78
96
  A build does exactly what its flags say, so a plain `build` without `--kits` would turn off a kit the install has on. Over an existing install it refuses instead: it names the change (`kits: <k> -> none`) and prints the command that keeps the kit. With `--reset` it goes ahead and first warns: `this install has kit <k>; this build turns it off — pass --kits <k> to keep it`.
79
97
 
80
- 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.
98
+ The setup wizard asks one yes/no question per kit, after the install mode, each defaulting to whether the install has that kit on. It asks them only when at least one kit exists. For a kit a plugin can replace it defaults by detection instead, and the question says what it saw.
81
99
 
82
100
  ### What an install records
83
101
 
@@ -34,6 +34,11 @@ all nest a short retry ring inside the iteration ring (`apply`↔`test`; `apply`
34
34
  tests, the second repairs CI directly through `ci-fix`, the third drafts a decision record and
35
35
  challenges it.
36
36
 
37
+ `ci-fix` names the `debug` skill, which belongs to the [superpowers kit](superpowers-kit.md). The loop
38
+ command reads the shipped bricks, never an install, so it cannot tell whether the kit is on; the brick
39
+ therefore carries its own CI steps and says to load the plugin's `systematic-debugging` when there is no
40
+ `debug` skill. It works the same with the kit on, off, or on a host with neither.
41
+
37
42
  Work closes into a commit whenever the graph re-enters the iteration loop's head — so any setup
38
43
  work before the loop starts (reproducing a bug, say) is its own unit, numbered iteration 0, kept
39
44
  out of iteration 1's diff. For the same reason the iteration has exactly one way in: its
@@ -46,7 +46,7 @@ Every skill ends with one beat of reflection: if a step misled or a step was mis
46
46
 
47
47
  ### Old names keep working
48
48
 
49
- When two skills merge, the old name still works as a slash command: `/deps-audit` runs `dependencies`, and `/ci-fix` runs `debug`. The old names are user-only, so the agent's list shows each skill once. If you had left out a skill that was later merged, a rebuild leaves out the merged skill instead. A skill removed with no replacement is dropped from that list, with a note.
49
+ When two skills merge, the old name still works as a slash command: `/deps-audit` runs `dependencies`, and `/ci-fix` runs `debug` (a skill of the [superpowers kit](superpowers-kit.md), so that alias exists only with the kit on). The old names are user-only, so the agent's list shows each skill once. If you had left out a skill that was later merged, a rebuild leaves out the merged skill instead. A skill removed with no replacement is dropped from that list, with a note.
50
50
 
51
51
  ### What they cost
52
52
 
@@ -0,0 +1,79 @@
1
+ ---
2
+ group: concepts
3
+ order: 13.5
4
+ title: "The superpowers kit"
5
+ kind: "concept"
6
+ section: "Configuration"
7
+ description: "Five Rites are Geneseed's vendored copies of obra/superpowers: keep this kit or the official plugin, never both."
8
+ ---
9
+ Five of Geneseed's skills are **vendored, modified copies of the skills in [obra/superpowers](https://github.com/obra/superpowers)** by Jesse Vincent (MIT). They live in the `superpowers` [kit](kits.md). An install has either the kit or the official superpowers plugin as its workflow provider, never both.
10
+
11
+ | Kit skill | Plugin skill it stands for |
12
+ |---|---|
13
+ | `brainstorm` | `brainstorming` |
14
+ | `debug` | `systematic-debugging` |
15
+ | `plan` | `writing-plans` |
16
+ | `geneseed-code-review` | `requesting-code-review` |
17
+ | `review-response` | `receiving-code-review` |
18
+
19
+ `parallel-agents`, `pipeline` and the `reviewer` agent are core in every install. Foreman's Brief checklist, the worktree rule and the blind reviewer live in them, and they credit superpowers in both states.
20
+
21
+ ## Kit on
22
+
23
+ The five skills ship as they always did, with their credit lines and `LICENSE-superpowers.txt`. The Kits block of the instructions file says what they are and asks the agent to tell you once if the official plugin is also loaded.
24
+
25
+ ## Kit off
26
+
27
+ The five skills are not written. Every core link to one is rewritten in the one render pass: the link text stays and the target becomes the plugin's skill in the host's spelling.
28
+
29
+ | Host | A link to `debug` reads |
30
+ |---|---|
31
+ | Claude Code | `debug Skill (superpowers:systematic-debugging)` |
32
+ | OpenCode V1 and V2 | `debug Skill (systematic-debugging)` (the plugin adds its skills folder to the host's skill paths, so both versions use bare names; V2 needs 2.0.4 or later) |
33
+ | Bob, OpenClaude, the plain bundle | `debugging pass`: the step in plain words, naming no skill, because there is no plugin to point at |
34
+
35
+ On Claude Code and OpenCode the instructions file also gains a **Workflow provider** block:
36
+
37
+ 1. **Rank.** The plugin's skills are procedure, never rank. "Invoke it at a 1% chance" never outranks a Dictate, a user rule or a Doctrina.
38
+ 2. **Routing.** The plugin's parallel and subagent skills are allowed, but the parent still writes every worker's brief by the parallel-agents Brief checklist. `finishing-a-development-branch` yields to `ship` (main changes only through a pull request with green checks), `test-driven-development` to `develop`, `using-git-worktrees` to `worktree` and `writing-skills` to `skill-forge`.
39
+ 3. **Missing provider.** If no superpowers skill is in the inventory, the agent tells you once to turn on the kit or install the plugin.
40
+
41
+ Bob and OpenClaude get the missing-provider line only. Building with the kit off is never refused: it is a legal state on every host, and `doctor` warns when it leaves no provider.
42
+
43
+ The `ci-fix` loop brick carries its CI-specific steps in its own body, so it works either way: it points at the `debug` skill, or at the plugin's `systematic-debugging` when the kit is off.
44
+
45
+ ## Who gets the kit
46
+
47
+ | Where | Default |
48
+ |---|---|
49
+ | Profiles `starter`, `corporate` | kit on (`"kits": ["superpowers"]`) |
50
+ | Profiles `mentor`, `minimal`, `autonomous` | by detection (`"kitsByDetection": ["superpowers"]`): on when the plugin is not seen |
51
+ | The setup wizard | by detection, and the question says what it saw; Bob and OpenClaude default to yes |
52
+ | `geneseed build` with no `--kits` | no kit, as for every kit |
53
+
54
+ ### How detection works
55
+
56
+ It only reads files, because the CLI may not start a process, and it names the file it read: `seen in <file>` or `not seen in <files read>`. It never says "not enabled".
57
+
58
+ | Host | Files read | Seen when |
59
+ |---|---|---|
60
+ | Claude Code | `~/.claude/settings.json` and `settings.local.json`; the project's `.claude/settings.json` and `settings.local.json` | `enabledPlugins` has a `superpowers@…` key set to `true` |
61
+ | Claude Code, desktop app | `<app data>/Claude/rpm/*/*/manifest.json` | an entry has `upstreamRepoUrl` `https://github.com/obra/superpowers` |
62
+ | OpenCode | global and project `opencode.json` or `.jsonc` | `plugin` (V1) or `plugins` (V2) has a `superpowers@…` entry |
63
+
64
+ The desktop file is the app's own undocumented state, read best-effort and labelled as such. On one machine the settings file said `false` while the plugin was loaded, which is why that file is read at all.
65
+
66
+ `geneseed doctor` and `geneseed status` warn in two cases: the kit on while the plugin is seen (duplicate Rites, about 800 tokens injected per session), and the kit off while no plugin is seen (no provider).
67
+
68
+ ## Installs made before the kit
69
+
70
+ An install built by a release before the kit has no `Active kits: superpowers` line, and its next rebuild would drop the five Rites. `rebuild-all`, `update` and `migrate` therefore read the release recorded in the install's `.geneseed-version` and, for an older one, turn the kit on unless the plugin is seen. Each install gets one line saying which and why. An install built after the kit keeps what its line says, so turning the kit off on purpose sticks.
71
+
72
+ ## Excluding one of the five
73
+
74
+ `--exclude-skills` refuses a name that core files link to, and since the scan counts relative links, `debug`, `plan`, `brainstorm`, `geneseed-code-review` and `review-response` cannot be excluded one by one: use the kit switch.
75
+
76
+ ## Known gaps
77
+
78
+ - Detection matches a `superpowers@<marketplace>` key. A fork under another marketplace is read as the plugin, and a plugin named by a git URL, an `obra/superpowers` spelling or a managed-settings file is missed: the failure is duplicate Rites (and no WARN), never no provider.
79
+ - `SUPERPOWERS_KIT_SINCE` is `6.0.0`: it is right only if the release that ships the kit is 6.0.0.
package/docs/extending.md CHANGED
@@ -392,6 +392,10 @@ global emit and leaves the install intact*) proves a refused emit leaves the pri
392
392
  a blank line, then a `>` blockquote holding `{{DESC_<NAME>}}` — title, blockquote, nothing
393
393
  between. `doctor` checks both the presence of the purpose line and that the blockquote is the
394
394
  *first* block (`authoringProblems`, via `firstBlockquote` and `descBlockProblem`).
395
+ **Agents only:** decide the model tier. No marker is `standard`; a read-only, read-and-summarise
396
+ seat adds `<!-- tier: light -->`, and a judgement seat that must run on the session model adds
397
+ `<!-- tier: strong -->`, on a line of its own directly above `## When to dispatch` (the build
398
+ strips it; `--tiers auto` reads it). A seat that writes code is never `light`.
395
399
  2. One row in the hand-authored table in `src/AGENT.md.tmpl` (the `## 3.` table for agents, the `## 4.` one for skills).
396
400
  Gated both ways: a row with no file, and a file with no row.
397
401
  3. `DESC_<NAME>` in **all fourteen** themes. Theme parity catches a missing one; nothing catches
@@ -515,6 +519,7 @@ it with `--kits` ([Kits](concepts/kits.md)). Nothing in the mechanism is specifi
515
519
  }
516
520
  ```
517
521
 
522
+ - `replacedBy` (optional, for a kit that a plugin can stand in for): `{ upstream, provider, missing, hosts, skills }`. `skills` maps each member to the plugin's skill and is complete (one per member, none extra); `hosts` spells a plugin skill per host with `{name}`; `upstream` is a key of `src/upstreams.json`; `provider` and `missing` are the two Workflow provider blocks the render leaves with the kit off (a host with a plugin, a host without), each inside `rulesWordBudget`. `kitProblems` checks all of it. It is the one case where a core file may link to a member: the render rewrites those links when the kit is off (`rewriteOffKitLinks`, `js/build/render.mjs`, in the one `renderAll` pass, never in an emitter). A new core mention of a member must therefore be a link, because `kitProblems` refuses a bare one (`<member> {{SKILL}}`).
518
523
  - `banned` (optional): strings no member file may contain, in the skill and agent specs, a skill's side files (flat, `skills/<m>/*.md`) and the kit's `rules.md`; `doctor` refuses each hit, naming file and line. A line carrying `<!-- banned: ok -->` is exempt (a rule that names the construct in order to forbid it).
519
524
 
520
525
  `loadKits` (`js/build/source.mjs`) reads every `src/kits/*.json`; `src/kits/` itself never ships
@@ -546,16 +551,16 @@ enumerates skills would miss it. `src/kits/<kit>/` holds only `rules.md`.
546
551
  `doctor` holds it to the manifest's `rulesWordBudget` (300 when unset).
547
552
  4. **Membership and links.** `doctor` (`kitProblems`) refuses a member listed in two kits, a
548
553
  core skill listed in a kit, a member with no file or no registry row, a core file that links
549
- to a kit member (it would dangle in an install without the kit), and a kit file that links to
554
+ to a kit member (it would dangle in an install without the kit; a kit with `replacedBy` is the exception, above), and a kit file that links to
550
555
  another kit's member. Links run kit → core only. A kit's links to its own members do not
551
556
  protect them from `--exclude-skills`; its link to a core skill still protects that skill.
552
- 5. **The setup wizard.** It asks one yes/no per kit, and only when at least one kit exists. Each
557
+ 5. **The setup wizard.** It asks one yes/no per kit, after the install mode, and only when at least one kit exists. A kit with `replacedBy` defaults by detection (`superpowersKitDefault`, `js/maintain/plugin-detect.mjs`) and the question names what was read. Each
553
558
  shipped kit therefore adds one answer line to the stdin strings in `tests/unit/wizard.test.mjs`,
554
559
  and the `wizard-no-kit` job holds that the questions are skipped on a tree with no kit.
555
560
  6. **Golden cells**: the matrix (`tests/helpers/matrix/emit.*.json`) carries kit on for `claude` and
556
561
  `opencode`, the kit-off baseline (`kits: []`, spelled `--kits none`), and three deletion cells
557
562
  (kit on to off). One deletion cell sets `edit` (a map of sandbox path to appended text) so a member
558
- is the user's own before the kit goes off, and `sovereign` excuses it: the prune keeps it (R6).
563
+ is the user's own before the kit goes off, and `sovereign` excuses it: the prune keeps it (R6). A kit with `replacedBy` also gets a Bob cell for each state (no plugin there). A deletion cell must remove something, so there is no off-to-on cell: that direction is a unit test.
559
564
 
560
565
  **What a kit costs an install** — what to weigh before adding one:
561
566
 
@@ -564,7 +569,9 @@ enumerates skills would miss it. `src/kits/<kit>/` holds only `rules.md`.
564
569
  `rulesWordBudget`, not the core carrier ceiling, which stays measured on core alone.
565
570
  - **The skill listing:** one description per kit skill, every session, while the kit is on.
566
571
  - **An install without the kit: nothing.** Its members are not written, and a default build
567
- stays byte-identical, with no `Active kits:` line.
572
+ has no `Active kits:` line. The one exception is a kit with `replacedBy`: with it off, the Kits
573
+ block carries its Workflow provider block (the `superpowers` kit's, today), so a default build is
574
+ no longer byte-identical to one made before that kit.
568
575
 
569
576
  **Retiring a kit** puts its id in `RETIRED_KIT_IDS` (`js/build/source.mjs`), with the reason
570
577
  beside it. An install whose `Active kits:` line names it drops it wherever that line is read back
@@ -18,7 +18,7 @@ The wizard, plain `setup`, needs an interactive terminal. In a script, a CI job,
18
18
  geneseed build --emit opencode-global --theme neutral
19
19
  ```
20
20
 
21
- `geneseed build` takes the same flags as the generator `geneseed-build`. `--emit` picks the host and its scope: `files`, `opencode`, `opencode-global`, `claude`, `claude-global`, `bob`, `bob-global`, `openclaude` or `openclaude-global`. A `-global` emit writes into the tool's own config directory. A project emit writes into the repo you name with `--out <repo> --root <repo>`. All the other flags (`--theme`, `--footprint`, `--posture`, `--mode`, `--trust`, `--doctrines`, `--exclude-rules`) are covered in [Choose your setup](choose-your-setup.md) and the two pages after it. `--exclude-skills` leaves skills you never use out of the install; see [Exclusions](../concepts/exclusions.md). `--kits <kit>` switches on an opt-in kit, and `--kits none` switches every kit off; see [Kits](../concepts/kits.md). `--context-window 1m` builds a Claude Code install for a 1M-token model (the default is `200k`); see [the listing budget](../concepts/skills.md#the-listing-budget-on-claude-code).
21
+ `geneseed build` takes the same flags as the generator `geneseed-build`. `--emit` picks the host and its scope: `files`, `opencode`, `opencode-global`, `claude`, `claude-global`, `bob`, `bob-global`, `openclaude` or `openclaude-global`. A `-global` emit writes into the tool's own config directory. A project emit writes into the repo you name with `--out <repo> --root <repo>`. All the other flags (`--theme`, `--footprint`, `--posture`, `--mode`, `--trust`, `--doctrines`, `--exclude-rules`) are covered in [Choose your setup](choose-your-setup.md) and the two pages after it. `--exclude-skills` leaves skills you never use out of the install; see [Exclusions](../concepts/exclusions.md). `--kits <kit>` switches on an opt-in kit, and `--kits none` switches every kit off; see [Kits](../concepts/kits.md). `--context-window 1m` builds a Claude Code install for a 1M-token model (the default is `200k`); see [the listing budget](../concepts/skills.md#the-listing-budget-on-claude-code). `--tiers auto` (default `off`) routes sub-agents to cheaper models by tier on Claude Code; see [Model tiers](../concepts/agents.md#model-tiers).
22
22
 
23
23
  To test a build before writing anything, use `geneseed validate` with the same flags. See [Verify](verify.md).
24
24
 
@@ -7,3 +7,5 @@ section: "CLI & environment"
7
7
  description: "Every geneseed subcommand, from the CLI's own table."
8
8
  ---
9
9
  The console renders this page from `js/cli-table.json`, the CLI's own description of itself, so it is always in step with the installed version. Outside the console, `geneseed --help` lists every command and `geneseed <command> --help` describes one.
10
+
11
+ Kits and detection touch four commands. `setup` asks one question per kit and, for the `superpowers` kit, defaults by what it reads of your plugin settings; `setup --profile` and `profile apply` resolve a profile's `kitsByDetection` the same way. `rebuild-all`, `update` and `migrate` give an install built before the kit existed the kit again, unless the plugin is seen, and print one line per install saying which. `doctor` and `status` warn when the kit and the plugin are both on, or both off. Every line names the file it read ("seen in", or "not seen in"), because detection only reads files. See [the superpowers kit](../concepts/superpowers-kit.md).
@@ -88,7 +88,9 @@ A gate that is off in the global install runs nowhere, so the line does not name
88
88
  | `excludeRules` | no | A list of rule ids, such as `craft.4` (the console's Constitution page lists them) |
89
89
  | `excludeSkills` | no | A list of skill names, as `geneseed build --exclude-skills` |
90
90
  | `kits` | no | A list of the kits in `src/kits/` |
91
+ | `kitsByDetection` | no | A list of kits that a plugin can stand in for (today `superpowers`), decided when the profile is applied: on when the plugin is **not** seen on that host, off when it is. The rule is the wizard's. A kit may not appear here and in `kits`. [The superpowers kit](../concepts/superpowers-kit.md) says what is read and where |
91
92
  | `sharedTier` | no | `true` lets a **project** install read the machine-wide shared tier (`geneseed build --shared-tier on`). A global apply ignores it, because a global install owns the tier |
93
+ | `tiers` | no | `"auto"` or `"off"`, as `geneseed build --tiers`: route sub-agents to cheaper models by tier ([Model tiers](../concepts/agents.md#model-tiers)). Absent means "not set by this profile": applying it keeps the install's own routing, and `off` on a new install. No shipped profile sets it. |
92
94
  | `contextWindow` | no | `"200k"` (the default) or `"1m"`, as `geneseed build --context-window`: the model context the install is built for. On Claude Code it sets the skill-listing budget ([Skills](../concepts/skills.md#the-listing-budget-on-claude-code)); other hosts record it and write nothing |
93
95
  | `gates` | no | An object that maps a gate switch to `false` to turn it off. Each key is a gate flag of `geneseed build --help` (`deletionGate: false` is `--no-deletion-gate`); a wrong key's refusal lists them all. `ownBranchPass: false` is `--strict-consent`, which adds asks |
94
96
  | `login` | no | `true` (default) lets `setup --profile` set the console to start at login and start it; `false` does neither, for a server or a CI machine. `profile apply` ignores it |
@@ -107,14 +109,14 @@ A gate that is off in the global install runs nowhere, so the line does not name
107
109
  "mode": "direct",
108
110
  "trust": "balanced",
109
111
  "doctrines": "all",
110
- "kits": [],
112
+ "kits": ["superpowers"],
111
113
  "contextWindow": "200k",
112
114
  "gates": { "ownershipGate": false },
113
115
  "login": true
114
116
  }
115
117
  ```
116
118
 
117
- `peer` and not `expert`, because `expert` does not explain the basics a new user needs; not `mentor`, because it checks understanding with questions. Every gate stays armed except the ownership gate, whose first-write stop is heavy for a new user. `200k`, because most machines run a 200k-token model, a locked-down work PC included; `guillaume-claude-global` sets `1m` for a 1M-token model.
119
+ `peer` and not `expert`, because `expert` does not explain the basics a new user needs; not `mentor`, because it checks understanding with questions. Every gate stays armed except the ownership gate, whose first-write stop is heavy for a new user. The `superpowers` kit is on: a new user has no workflow provider yet, and the kit is Geneseed's own copy of one ([the superpowers kit](../concepts/superpowers-kit.md)). `200k`, because most machines run a 200k-token model, a locked-down work PC included; `guillaume-claude-global` sets `1m` for a 1M-token model.
118
120
 
119
121
  ## `mentor`
120
122
 
@@ -129,6 +131,7 @@ A gate that is off in the global install runs nowhere, so the line does not name
129
131
  "trust": "prudent",
130
132
  "doctrines": "all",
131
133
  "kits": [],
134
+ "kitsByDetection": ["superpowers"],
132
135
  "contextWindow": "200k",
133
136
  "login": true
134
137
  }
@@ -148,7 +151,7 @@ A gate that is off in the global install runs nowhere, so the line does not name
148
151
  "mode": "direct",
149
152
  "trust": "prudent",
150
153
  "doctrines": "all",
151
- "kits": [],
154
+ "kits": ["superpowers"],
152
155
  "contextWindow": "200k",
153
156
  "gates": { "ownershipGate": false, "ownBranchPass": false },
154
157
  "login": false
@@ -170,6 +173,7 @@ A gate that is off in the global install runs nowhere, so the line does not name
170
173
  "trust": "aggressive",
171
174
  "doctrines": "all",
172
175
  "kits": [],
176
+ "kitsByDetection": ["superpowers"],
173
177
  "contextWindow": "1m",
174
178
  "gates": { "ownershipGate": false },
175
179
  "login": true
@@ -190,15 +194,16 @@ A gate that is off in the global install runs nowhere, so the line does not name
190
194
  "mode": "direct",
191
195
  "trust": "balanced",
192
196
  "doctrines": ["craft", "rigor"],
193
- "excludeSkills": ["brick-forge", "bruno", "daydream", "factory", "factory-forge", "forge-mcp", "prototype", "react-view-transitions"],
197
+ "excludeSkills": ["brick-forge", "bruno", "daydream", "factory", "factory-forge", "forge-mcp", "react-view-transitions"],
194
198
  "kits": [],
199
+ "kitsByDetection": ["superpowers"],
195
200
  "contextWindow": "200k",
196
201
  "gates": { "ownershipGate": false },
197
202
  "login": true
198
203
  }
199
204
  ```
200
205
 
201
- Each choice makes the always-on context smaller. `assistant` does what you ask and stops, so a small model gets a narrow task and few chances to drift. `craft` and `rigor` are the packs about how code is written and proven; the other packs stay in `doctrines/` for reference. The excluded skills serve rare tasks. A skill that the harness links to cannot be excluded, so `council`, `deck`, `pipeline` and `workflow` stay. Every gate except the ownership gate stays armed, because a gate costs no context. To measure the gain on your machine, build `starter` and `minimal` into two empty folders with `geneseed profile apply <name> --project <dir> --hosts claude`, then compare the size of each `CLAUDE.md` and the number of skills.
206
+ Each choice makes the always-on context smaller. `assistant` does what you ask and stops, so a small model gets a narrow task and few chances to drift. `craft` and `rigor` are the packs about how code is written and proven; the other packs stay in `doctrines/` for reference. The excluded skills serve rare tasks, and the `superpowers` kit is chosen by detection. A skill that the harness links to cannot be excluded, so `council`, `deck`, `pipeline` and `workflow` stay. Every gate except the ownership gate stays armed, because a gate costs no context. To measure the gain on your machine, build `starter` and `minimal` into two empty folders with `geneseed profile apply <name> --project <dir> --hosts claude`, then compare the size of each `CLAUDE.md` and the number of skills.
202
207
 
203
208
  ## Save your own
204
209
 
@@ -2,5 +2,5 @@
2
2
  "_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.",
3
3
  "theme": "neutral",
4
4
  "product": "Geneseed",
5
- "version": "5.6.0"
5
+ "version": "6.0.0"
6
6
  }
package/js/README.md CHANGED
@@ -241,6 +241,8 @@ Verbs that change an install that already exists, as opposed to rendering one.
241
241
  | `setup.mjs` | The install wizard. Its prompts go through `js/lib/prompt.mjs`'s stdin readers. `setup --profile` installs a profile with no prompt; `profile apply` (`cmdProfileApply`) shares its build loop |
242
242
  | `profiles.mjs` | Install profiles from two sources, Shipped (`profiles/*.json`) and Personal (`<machine tier>/profiles/`): load and validate against the generator's own sources, the per-host argv (global or project), `profile save` |
243
243
  | `profile-scope.mjs` | The scope half of `profile apply`: the project folder check (shared with the console's deploy) and what a global install still runs inside a project (`globalLayering`) |
244
+ | `plugin-detect.mjs` | Is the official superpowers plugin installed? File reads only (the CLI may not spawn), every root a parameter, and never on the hook path. Its answer always names the file |
245
+ | `kit-migration.mjs` | The one-time `superpowers` kit for an install built before the kit existed (`installProfile` calls it), and the `doctor`/`status` provider WARN |
244
246
  | `uninstall.mjs` | Removes or disables an install: manifest-driven reversal, plus stash deactivate/reactivate |
245
247
  | `migrate.mjs` | `geneseed migrate` — all-or-nothing re-emit moving installs onto the npm install shape |
246
248
  | `memory.mjs` | `geneseed memory list|rm|consolidate` — CLI-side fact removal (archive by default, `--purge` deletes), twin of the web delete endpoint; `consolidate` rebuilds the index by hand, twin of the hook's `learn --consolidate` |
package/js/build/args.mjs CHANGED
@@ -11,7 +11,7 @@ import { parseArgs as nodeParseArgs } from 'node:util';
11
11
  import { withPlatformNewlines } from '../lib/fs.mjs';
12
12
  import path from 'node:path';
13
13
  import {
14
- CONFIG, CONTEXT_WINDOWS, DEFAULT_CONTEXT_WINDOW, discoverNames, GATE_SWITCHES, PACK_ORDER, SRC, knownRuleIds, knownSkillIds, linkedSkillIds, loadKits,
14
+ CONFIG, CONTEXT_WINDOWS, DEFAULT_CONTEXT_WINDOW, DEFAULT_TIERS, discoverNames, GATE_SWITCHES, PACK_ORDER, SRC, TIERS_CHOICES, knownRuleIds, knownSkillIds, linkedSkillIds, loadKits,
15
15
  resolveSkillNames, retiredRuleAddresses, reusedRuleAddresses, ruleCanon, skillAliases,
16
16
  } from './source.mjs';
17
17
  // The loop engine's trust presets — the `--trust` choices. `score.mjs` imports nothing, which is
@@ -103,6 +103,7 @@ export const VALUED = {
103
103
  '--theme': 'theme', '--posture': 'posture', '--mode': 'mode', '--trust': 'trust',
104
104
  '--doctrines': 'doctrines', '--exclude-rules': 'excludeRules', '--exclude-skills': 'excludeSkills',
105
105
  '--kits': 'kits', '--shared-tier': 'sharedTier', '--context-window': 'contextWindow',
106
+ '--tiers': 'tiers',
106
107
  '--out': 'out', '--target': 'out', '--emit': 'emit',
107
108
  '--footprint': 'footprint', '--root': 'root', '--config-dir': 'cfgDir',
108
109
  };
@@ -168,6 +169,7 @@ export function choicesFor() {
168
169
  '--trust': Object.keys(PRESETS),
169
170
  '--shared-tier': ['on', 'off'],
170
171
  '--context-window': Object.keys(CONTEXT_WINDOWS),
172
+ '--tiers': [...TIERS_CHOICES],
171
173
  };
172
174
  }
173
175
 
@@ -377,7 +379,7 @@ export function parseArgs(argv, defaults) {
377
379
  excludeRules: defaults.excludeRules,
378
380
  excludeSkills: defaults.excludeSkills ?? [],
379
381
  kits: defaults.kits ?? [],
380
- sharedTier: 'off', contextWindow: DEFAULT_CONTEXT_WINDOW,
382
+ sharedTier: 'off', contextWindow: DEFAULT_CONTEXT_WINDOW, tiers: DEFAULT_TIERS,
381
383
  out: 'Harness', emit: 'files', footprint: 'lean', root: null,
382
384
  syncThemes: false, validateOnly: false, verbose: false, pruneGates: false, force: false, reset: false,
383
385
  ...Object.fromEntries(GATE_SWITCHES.map((g) => [g.arg, false])),
@@ -724,13 +724,13 @@ const PROJECT_EMITS = {
724
724
  * carry straight past the parameter default.
725
725
  */
726
726
  function axesCfg({
727
- posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, ...gates
727
+ posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, tiers, ...gates
728
728
  }) {
729
729
  return makeCfg({
730
730
  ...(posture ? { posture } : {}), ...(mode ? { mode } : {}), ...(trust ? { trust } : {}),
731
731
  ...(doctrines ? { doctrines } : {}), ...(excludeRules ? { excludeRules } : {}),
732
732
  ...(excludeSkills ? { excludeSkills } : {}), ...(kits ? { kits } : {}), ...(sharedTier ? { sharedTier } : {}),
733
- ...(contextWindow ? { contextWindow } : {}),
733
+ ...(contextWindow ? { contextWindow } : {}), ...(tiers ? { tiers } : {}),
734
734
  // The gate switches (`GATE_SWITCHES` keys): only an explicit `false` disarms; `null` (no
735
735
  // opinion) keeps the gate.
736
736
  ...Object.fromEntries(GATE_SWITCHES.filter((g) => gates[g.key] === false).map((g) => [g.arg, true])),
@@ -739,7 +739,7 @@ function axesCfg({
739
739
 
740
740
  export function emitProjectInto(host, {
741
741
  theme, out, root, footprint = 'full', posture = null, mode = null, trust = null,
742
- doctrines = null, excludeRules = null, excludeSkills = null, kits = null, sharedTier = false, contextWindow = null, seed = true, ...gates
742
+ doctrines = null, excludeRules = null, excludeSkills = null, kits = null, sharedTier = false, contextWindow = null, tiers = null, seed = true, ...gates
743
743
  }) {
744
744
  const emit = PROJECT_EMITS[host];
745
745
  // The axes ride the same rail into every `*Into`, and for the same reason: a drift reader
@@ -750,7 +750,7 @@ export function emitProjectInto(host, {
750
750
  // the git root, which for a temp dir inside a repo is that repo, outside the sandbox.
751
751
  return withPlatformNewlines(() => emit(
752
752
  axesCfg({
753
- posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, ...gates }),
753
+ posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, tiers, ...gates }),
754
754
  { theme, footprint, root, seed }, out,
755
755
  ));
756
756
  }
@@ -765,16 +765,16 @@ export function emitProjectInto(host, {
765
765
  */
766
766
  export function buildInto({
767
767
  theme, out, footprint = 'lean', posture = null, mode = null, trust = null, doctrines = null,
768
- excludeRules = null, excludeSkills = null, kits = null, sharedTier = false, contextWindow = null, ...gates
768
+ excludeRules = null, excludeSkills = null, kits = null, sharedTier = false, contextWindow = null, tiers = null, ...gates
769
769
  }) {
770
770
  return withPlatformNewlines(() => build(axesCfg({
771
- posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, ...gates }),
771
+ posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, tiers, ...gates }),
772
772
  theme, out, { footprint, nativeCatalog: false }));
773
773
  }
774
774
 
775
775
  export function emitGlobalInto(host, {
776
776
  theme, out, cfgDir, footprint, posture = null, mode = null, doctrines = null, trust = null,
777
- excludeRules = null, excludeSkills = null, kits = null, sharedTier = false, contextWindow = null,
777
+ excludeRules = null, excludeSkills = null, kits = null, sharedTier = false, contextWindow = null, tiers = null,
778
778
  sharedRoot = undefined, ...gates
779
779
  }) {
780
780
  // `build.HOSTS.get(host, build.HOSTS["opencode"])` — an unknown host falls back rather than
@@ -792,7 +792,7 @@ export function emitGlobalInto(host, {
792
792
  // the same scar the footprint left in `diffCollect`, one axis over each time.
793
793
  return withPlatformNewlines(() => emit(
794
794
  axesCfg({
795
- posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, ...gates }),
795
+ posture, mode, trust, doctrines, excludeRules, excludeSkills, kits, sharedTier, contextWindow, tiers, ...gates }),
796
796
  { theme, footprint, root: null, cfgDir, sharedRoot }, out,
797
797
  ));
798
798
  }
@@ -7,7 +7,7 @@
7
7
  */
8
8
  import path from 'node:path';
9
9
  import { VERSION_MARKER } from '../hosts/hosts.mjs';
10
- import { claimer, loadAgentOverrides, writeNativeLayer } from '../hosts/native.mjs';
10
+ import { claimer, loadAgentOverrides, loadTierMap, writeNativeLayer } from '../hosts/native.mjs';
11
11
  import { ensureAgentOverridesStub, writeAliasCommands } from '../hosts/opencode.mjs';
12
12
  import {
13
13
  managedBlockRemove, managedBlockWrite, mergeClaudeSettings,
@@ -64,7 +64,7 @@ export function emitClaudeRender(cfg, job) {
64
64
  const lawsPrefix = relCfg === '.' ? '' : `${relCfg}/`;
65
65
  // A re-render of a deployed install sends that install's root, null included.
66
66
  const { sharedRoot = scope === 'global' ? sharedRootFor(cfgDir, host) : null } = job;
67
- const { theme, items } = renderAll(cfg, themeName, { footprint, lawsPrefix, nativeCatalog, sharedRoot });
67
+ const { theme, items } = renderAll(cfg, themeName, { footprint, lawsPrefix, nativeCatalog, sharedRoot, pluginHost: host === 'claude' ? 'claude' : '' });
68
68
  assertSourceComplete(cfg, `claude-${scope}`);
69
69
  mkdirSync(cfgDir, { recursive: true });
70
70
 
@@ -137,7 +137,9 @@ export function emitClaudeRender(cfg, job) {
137
137
  const { nAgents, nSkills, written } = writeNativeLayer(
138
138
  items, path.join(cfgDir, 'agents'), path.join(cfgDir, 'skills'),
139
139
  loadAgentOverrides(cfgDir),
140
- { host: 'claude', bobDialect: isBob, oldOwned, cfg: cfgDir, src: cfg.src, skillDirOf, claim });
140
+ { host: 'claude', bobDialect: isBob, oldOwned, cfg: cfgDir, src: cfg.src, skillDirOf, claim,
141
+ // Claude Code only: OpenClaude and Bob inherit (spec B6, D8).
142
+ tiers: cfg.tiers === 'auto' && host === 'claude' ? { map: loadTierMap(cfgDir), env: process.env } : null });
141
143
  for (const p of written) owned.push(relPosix(cfgDir, p));
142
144
 
143
145
  // Bob host-compat O2/R1: an alias, or a genuinely user-only skill (unverified