geneseed 5.1.1 → 5.3.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 (163) hide show
  1. package/CHANGELOG.md +52 -0
  2. package/README.md +2 -2
  3. package/SHIPPED.md +1 -1
  4. package/adapters/opencode/README.md +4 -3
  5. package/adapters/opencode/plugins/geneseed-context.js +82 -29
  6. package/adapters/opencode/plugins/geneseed-guard.js +118 -8
  7. package/bin/geneseed-cli.mjs +64 -16
  8. package/bin/geneseed-hook.mjs +37 -3
  9. package/docs/concepts/exclusions.md +1 -1
  10. package/docs/concepts/factories.md +40 -6
  11. package/docs/concepts/footprint.md +1 -1
  12. package/docs/concepts/foreman-mode.md +2 -2
  13. package/docs/concepts/host-matrix.md +1 -1
  14. package/docs/concepts/loop-gates.md +1 -1
  15. package/docs/concepts/loops.md +2 -2
  16. package/docs/concepts/shared-tier.md +1 -1
  17. package/docs/design-history.md +140 -0
  18. package/docs/extending.md +54 -162
  19. package/docs/guides/run-a-factory.md +15 -2
  20. package/docs/guides/setup-doctrines.md +1 -1
  21. package/docs/guides/upgrade.md +2 -2
  22. package/docs/reference/factory-actions.md +6 -5
  23. package/docs/reference/troubleshoot-update.md +1 -1
  24. package/docs/understand/enforced-vs-asked.md +1 -1
  25. package/docs/web-ui.md +16 -3
  26. package/harness.config.json +1 -1
  27. package/js/README.md +10 -7
  28. package/js/build/args.mjs +10 -4
  29. package/js/build/bundle.mjs +122 -23
  30. package/js/build/driver.mjs +32 -12
  31. package/js/build/emit-claude.mjs +2 -1
  32. package/js/build/emit-common.mjs +2 -2
  33. package/js/build/emit-opencode.mjs +22 -10
  34. package/js/build/export.mjs +431 -0
  35. package/js/build/generate.mjs +3 -0
  36. package/js/build/render.mjs +44 -24
  37. package/js/build/source.mjs +6 -1
  38. package/js/cli-table.json +232 -57
  39. package/js/factory/cli.mjs +24 -5
  40. package/js/factory/graph.mjs +13 -9
  41. package/js/factory/metrics.mjs +93 -0
  42. package/js/factory/registry.mjs +37 -12
  43. package/js/factory/state.mjs +25 -6
  44. package/js/hosts/hooks-context.mjs +26 -1
  45. package/js/hosts/hooks-done.mjs +8 -2
  46. package/js/hosts/hooks-prims.mjs +52 -3
  47. package/js/hosts/hooks.mjs +155 -33
  48. package/js/hosts/hosts.mjs +2 -4
  49. package/js/hosts/installs.mjs +28 -0
  50. package/js/hosts/loss.mjs +25 -3
  51. package/js/hosts/native.mjs +30 -2
  52. package/js/hosts/owned.mjs +55 -1
  53. package/js/hosts/ownership-gate.mjs +5 -5
  54. package/js/hosts/settings.mjs +83 -33
  55. package/js/inspect/diff.mjs +16 -1
  56. package/js/inspect/doctor.mjs +7 -3
  57. package/js/inspect/excludes.mjs +18 -6
  58. package/js/inspect/status.mjs +35 -7
  59. package/js/inspect/validate.mjs +44 -21
  60. package/js/lib/managed-block.mjs +74 -0
  61. package/js/maintain/uninstall.mjs +85 -15
  62. package/js/maintain/update.mjs +31 -7
  63. package/js/ui/cli.mjs +34 -4
  64. package/js/ui/menu.mjs +1 -1
  65. package/js/ui/tui.mjs +11 -14
  66. package/js/web/actions.mjs +5 -0
  67. package/js/web/api.mjs +32 -11
  68. package/js/web/daemon.mjs +0 -1
  69. package/js/web/server.mjs +1 -0
  70. package/js/web/state.mjs +37 -16
  71. package/package.json +1 -1
  72. package/src/AGENT.md.tmpl +23 -17
  73. package/src/agents/_template.md +1 -1
  74. package/src/agents/advocate.md +1 -1
  75. package/src/agents/developer.md +12 -3
  76. package/src/agents/empiricist.md +1 -1
  77. package/src/agents/framer.md +1 -1
  78. package/src/agents/historian.md +1 -1
  79. package/src/agents/operator.md +1 -1
  80. package/src/agents/pragmatist.md +1 -1
  81. package/src/agents/researcher.md +1 -1
  82. package/src/agents/skeptic.md +1 -1
  83. package/src/agents/steward.md +1 -1
  84. package/src/agents/user-advocate.md +1 -1
  85. package/src/agents/visionary.md +1 -1
  86. package/src/bricks/intake.md +10 -3
  87. package/src/bricks/retro.md +13 -3
  88. package/src/doctrines/comms.md +1 -1
  89. package/src/doctrines/ops.md +1 -1
  90. package/src/doctrines/process.md +7 -5
  91. package/src/factories/analysis-to-build.json +1 -0
  92. package/src/factories/bug-report-to-fix.json +1 -0
  93. package/src/factories/issue-to-pr.json +1 -0
  94. package/src/laws/universal.md +2 -2
  95. package/src/modes/foreman.md +8 -14
  96. package/src/skills/commit.md +7 -2
  97. package/src/skills/debug.md +1 -1
  98. package/src/skills/diagram-design/SKILL.md +1 -1
  99. package/src/skills/diagram-design/VENDOR.md +3 -1
  100. package/src/skills/factory-forge.md +5 -3
  101. package/src/skills/factory.md +22 -1
  102. package/src/skills/geneseed.md +1 -1
  103. package/src/skills/handoff.md +1 -1
  104. package/src/skills/parallel-agents.md +1 -1
  105. package/src/skills/pipeline.md +6 -6
  106. package/src/skills/plan.md +7 -3
  107. package/src/skills/spring-testing.md +1 -1
  108. package/themes/biker.json +78 -78
  109. package/themes/commentator.json +81 -81
  110. package/themes/cyberpunk.json +79 -79
  111. package/themes/gamer.json +77 -77
  112. package/themes/imperial.json +82 -82
  113. package/themes/joker.json +79 -79
  114. package/themes/marvin.json +82 -82
  115. package/themes/mean.json +82 -82
  116. package/themes/military.json +78 -78
  117. package/themes/neutral.json +78 -78
  118. package/themes/pirate.json +79 -79
  119. package/themes/sports.json +79 -79
  120. package/themes/verstappen.json +78 -78
  121. package/themes/wizard.json +79 -79
  122. package/web/dist/assets/ActiveLoops-BJJN3P-V.js +1 -0
  123. package/web/dist/assets/Activity-CqJiquEq.js +1 -0
  124. package/web/dist/assets/ActivityDetail-BSzevynX.js +1 -0
  125. package/web/dist/assets/{Bonsai-hiG_gGNU.js → Bonsai-Bfpb6W-1.js} +1 -1
  126. package/web/dist/assets/{CopyButton-DUIUfNp6.js → CopyButton-ByIntFtB.js} +1 -1
  127. package/web/dist/assets/Dashboard-DBOEi9lQ.js +2 -0
  128. package/web/dist/assets/Docs-DvlMJhpu.js +5 -0
  129. package/web/dist/assets/Factories-Bpvv7L2H.js +1 -0
  130. package/web/dist/assets/{GreenhouseView-BKxy5apE.js → GreenhouseView-GpBsYn50.js} +1 -1
  131. package/web/dist/assets/Installs-BlGmVrFK.js +3 -0
  132. package/web/dist/assets/{JournalView-ChFitHjo.js → JournalView-iLuLrOxE.js} +1 -1
  133. package/web/dist/assets/Kits-DRwpxC-J.js +1 -0
  134. package/web/dist/assets/Laws-CZkiNOWQ.js +4 -0
  135. package/web/dist/assets/LibRows-DEHjIoD-.js +1 -0
  136. package/web/dist/assets/Library-B4K-1iNF.js +3 -0
  137. package/web/dist/assets/Loops-BWSzaW8E.js +2 -0
  138. package/web/dist/assets/{OperatorHudView-BO0aIKPL.js → OperatorHudView-BAXwCEvY.js} +1 -1
  139. package/web/dist/assets/Personal-Bp9nV4GR.js +2 -0
  140. package/web/dist/assets/Settings-CWWuaIp-.js +1 -0
  141. package/web/dist/assets/Tabs-CWeQTADL.js +1 -0
  142. package/web/dist/assets/index-CsAZq0BQ.css +1 -0
  143. package/web/dist/assets/index-How7SzDZ.js +6 -0
  144. package/web/dist/assets/usePoll-D5c_qIFZ.js +1 -0
  145. package/web/dist/index.html +2 -2
  146. package/web/dist/assets/ActiveLoops-BTHIaRhn.js +0 -1
  147. package/web/dist/assets/Activity-CpkBwpu7.js +0 -1
  148. package/web/dist/assets/ActivityDetail-DTPziZWM.js +0 -1
  149. package/web/dist/assets/Dashboard-Dnw6EyX7.js +0 -2
  150. package/web/dist/assets/Docs-BEET_l16.js +0 -5
  151. package/web/dist/assets/Factories-D6KXkfWw.js +0 -1
  152. package/web/dist/assets/Installs-CnFVlVD0.js +0 -3
  153. package/web/dist/assets/Kits-CcR-OlwQ.js +0 -1
  154. package/web/dist/assets/Laws-B1s5idOg.js +0 -4
  155. package/web/dist/assets/LibRows-BZgdbI1l.js +0 -1
  156. package/web/dist/assets/Library-x6TkkEVF.js +0 -3
  157. package/web/dist/assets/Loops-BH93KKxn.js +0 -2
  158. package/web/dist/assets/Personal-CE_0Vhh0.js +0 -2
  159. package/web/dist/assets/Settings-CbpZvVN_.js +0 -1
  160. package/web/dist/assets/Tabs-C2oW7oEj.js +0 -1
  161. package/web/dist/assets/index-BQwOmbor.js +0 -6
  162. package/web/dist/assets/index-CuIop_pO.css +0 -1
  163. package/web/dist/assets/usePoll-o8ul-Sog.js +0 -1
@@ -7,7 +7,7 @@
7
7
  **Trigger:** the context window is filling, a session is ending mid-task, or work is passing to another agent or developer.
8
8
 
9
9
  ## Procedure
10
- 1. Capture the state in the worklog (`WORKLOG.md` or the task's plan file), whose first line names its task or branch so a stale one is never resumed: the goal, what's done, the step in progress, and the exact next step.
10
+ 1. Capture the state in the worklog (`WORKLOG.md` or the task's plan file, in your {{NOTEBOOK}}; in the repository only when the user asks), whose first line names its task or branch so a stale one is never resumed: the goal, what's done, the step in progress, and the exact next step.
11
11
  2. Record open decisions, dead ends already ruled out, blockers, and any irreversible changes already made ({{DOCTRINE:plan-before-acting}}) — so the next agent neither re-derives nor repeats them.
12
12
  3. Promote any durable fact or correction learned this session into {{MEMORY}} (§5), not just the worklog.
13
13
  4. Point to the live artifacts: branch name, changed files, how to run the tests, and where any failure reproduces. Link specs, plans, ADRs, issues and commits by path or URL — never copy them in.
@@ -11,7 +11,7 @@
11
11
  ## Procedure
12
12
  1. Confirm independence: the subtasks must not depend on each other's output or write the same files ({{DOCTRINE:one-writer-per-file}}). 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.
13
13
  2. Split the work into self-contained units, each with one clear goal and a defined output contract — what it must return. Several small edits of one kind (the same fix, constant or field across files) form ONE unit with the union write set and get one review.
14
- 3. Dispatch each unit to its own subagent in one batch — units that call one rationed resource run in sequence instead ({{DOCTRINE:serialize-against-a-rationed-resource}}) — 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:consent-before-push}} stays with you; no sub-agents of its own — review comes from you; gaps reported, never invented). Hand each unit only the access its goal needs ({{LAW:least-privilege}}). Prefer the read-only [explorer {{AGENT}}](../{{DIR_AGENTS}}/explorer.md) for investigation so the heavy reading stays out of the main context ({{DOCTRINE:context-economy}}). Where no subagent capability exists, run the units sequentially as personas instead, converging the same way.
14
+ 3. Dispatch each unit to its own subagent in one batch — units that call one rationed resource run in sequence instead ({{DOCTRINE:serialize-against-a-rationed-resource}}) — 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 (a unit in the shared tree never commits or pushes; a slice on its own branch (step 6) commits only there, never pushes — {{DOCTRINE:consent-before-push}} stays with you; no sub-agents of its own — review comes from you; gaps reported, never invented). Hand each unit only the access its goal needs ({{LAW:least-privilege}}). Prefer the read-only [explorer {{AGENT}}](../{{DIR_AGENTS}}/explorer.md) for investigation so the heavy reading stays out of the main context ({{DOCTRINE:context-economy}}). Where no subagent capability exists, run the units sequentially as personas instead, converging the same way.
15
15
  4. Keep the main context lean: collect each subagent's distilled result, not its working transcript. Watch every unit you dispatched in the background as the [pipeline {{SKILL}}](pipeline.md)'s step 2 watches a crew: a result without its check, or one that says it is still waiting, is a failure to act on at once — resume the unit or redo it — never a notification to wait for.
16
16
  5. Converge: compare each unit's changed files against its write set and against its siblings' — an edit outside the set, a file two units touched, or a file in a batch's set that never changed is a conflict you resolve before anything else — apply the shared-file rows yourself, then verify the combined outcome. A conflict or ambiguity between the plan, the findings and the code is yours to decide: decide it, record `Ruling: <choice> — <why> — <cost if wrong>` in the worklog, and continue. Stop only for what {{LAW:echo-the-intent}}, {{LAW:deletion-is-deliberate}} or {{DOCTRINE:consent-before-push}} names; every ruling goes in the final report ({{DOCTRINE:declare-the-judgment-calls}}).
17
17
  6. **A plan with blocking edges.** To build a [plan](plan.md) file's slices — each with its `Blocked by:` line — in one run, dispatch every unblocked slice on its own branch off one integration branch, merge each into it as it returns (each merge is a commit — {{DOCTRINE:consent-before-push}} stays with you), and recompute the unblocked set from the plan after every merge — newly freed slices go out at once. When the plan names a `Spec:`, every slice reads it once; the spec outranks the plan where they conflict. Each slice branches off the integration tip at its own dispatch (its BASE) and merges the current tip back into its branch before returning, so a conflict with a sibling resolves on the slice's branch; before re-running the proof, confirm the branch descends from BASE and the diff is non-empty — an empty diff is a failure, not a clean result. Never diff against `HEAD~1`. When the plan is exhausted, review the integration branch whole with [geneseed-code-review](geneseed-code-review.md) before reporting.
@@ -4,7 +4,7 @@
4
4
 
5
5
  {{CREDIT:superpowers:skills/subagent-driven-development/SKILL.md}}
6
6
 
7
- **Trigger:** opt-in. The user asks to "run a pipeline" or for a crew on a development, documentation, research, or review task; or, under [foreman mode](../modes/foreman.md), a large multi-part task needs several specialists. Foreman's default for a delegated task is one task worker, not a crew. The crew is a relay, not a fan-out: its agents take turns in one worktree, each handed what the previous one produced — for independent subtasks run side by side, use [parallel-agents](parallel-agents.md).
7
+ **Trigger:** the user asks for a pipeline or crew, or under Foreman mode a large task needs several specialists — opt-in, never a default. It serves development, documentation, research and review tasks; under [foreman mode](../modes/foreman.md), whether a multi-part task is large enough is foreman's to judge. Foreman's default for a delegated task is one task worker, not a crew. The crew is a relay, not a fan-out: its agents take turns in one worktree, each handed what the previous one produced — for independent subtasks run side by side, use [parallel-agents](parallel-agents.md).
8
8
 
9
9
  ## What it is
10
10
 
@@ -26,12 +26,12 @@ The minimum roster per task type. The crew lead chooses the crew from the whole
26
26
  ## Procedure
27
27
 
28
28
  1. Take the trigger as given: the user's request for a crew, or foreman's judgement that the task needs several specialists. Do not weigh it again and fall back to doing the work yourself.
29
- 2. **Dispatch the crew lead** in the background, using the host's general-purpose {{AGENT}}. Before dispatch, record BASE and set the crew's **write set**; check it against every other pipeline in flight ({{DOCTRINE:one-writer-per-file}}) — two crews whose sets overlap do not run at once. The brief carries: the task as the user stated it, the task type, BASE, the write set, the proof commands, a pointer to this {{SKILL}}, and the rule that it never commits, pushes or merges. Tell the user the pipeline is running, then go back to the user. Do not wait on the crew lead. **Then watch what you dispatched.** An envelope without proof, or one that says the crew is still waiting, is a failure: act on it at once — resume the crew lead (`SendMessage` on Claude Code) or take over its worktree — never wait for a notification it promised. A crew member's report that reaches you directly means its crew lead has already ended; act on it the same way. Set no timer to watch a crew: where the host re-invokes you when a background agent ends (Claude Code), that notification is the watch; check every crew still out at the start of every turn. A crew is stalled when its transcript and output have not grown for 15 minutes **and** it has no live child process: ping it once; if the next check shows no change, stop it, then take over from its worktree. A crew whose output still grows, or that runs a child process, is never taken over — a long suite or canary is not a stall.
29
+ 2. **Dispatch the crew lead** in the background, using the host's general-purpose {{AGENT}}. Before dispatch, record BASE and set the crew's **write set**; check it against every other pipeline in flight ({{DOCTRINE:one-writer-per-file}}) — two crews whose sets overlap do not run at once. The brief carries: the task as the user stated it, the task type, BASE, the write set, the proof commands, a pointer to this {{SKILL}}, and the rule that it commits only in its own worktree, never pushes, and never merges outside its own branch. Tell the user the pipeline is running, then go back to the user. Do not wait on the crew lead. **Then watch what you dispatched.** An envelope without proof, or one that says the crew is still waiting, is a failure: act on it at once — resume the crew lead (`SendMessage` on Claude Code) or take over its worktree — never wait for a notification it promised. A crew member's report that reaches you directly means its crew lead has already ended; act on it the same way. Set no timer to watch a crew: where the host re-invokes you when a background agent ends (Claude Code), that notification is the watch; check every crew still out at the start of every turn. A crew is stalled when its transcript and output have not grown for 15 minutes **and** it has no live child process: ping it once; if the next check shows no change, stop it, then take over from its worktree. A crew whose output still grows, or that runs a child process, is never taken over — a long suite or canary is not a stall.
30
30
  3. **The crew lead composes the crew** from the floor above and adds any {{AGENT}} the task needs. It dispatches each crew member as its own subagent, each handed what the previous one produced. **The crew lead never ends with a member unresolved.** Its last message is its result: once it ends, nothing wakes it, and a member that outlives it reports past it, to the parent. It may run members in parallel, but holds every member's result before it ends — returned, or failed and then redone or named as failed in the envelope. A member that returns nothing has failed. Where the crew lead holds no dispatch tool (see *Hosts* below), it plays each role in turn itself, with the same hand-offs and the same envelope. Steps 4 to 7 are the crew lead's, except where they name the parent.
31
- 4. Isolate the crew's work in its own git worktree/branch. Where worktrees are unavailable, fall back to a single tree, one pipeline at a time, and say so. The crew writes only inside its write set; shared append files (registries, index tables, lockfiles, generated bundles) are the parent's to apply, never a crew's.
31
+ 4. Isolate the crew's work in its own git worktree/branch. Where worktrees are unavailable, fall back to a single tree, one pipeline at a time, and say so; without a worktree, the crew never commits. The crew writes only inside its write set; shared append files (registries, index tables, lockfiles, generated bundles) are the parent's to apply, never a crew's.
32
32
  5. **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 — two repair rounds at most, then one fresh developer (a higher model tier where the host offers one) carrying the tester's findings ({{DOCTRINE:bound-the-loop}}); if that fails too, stop, do not merge, and report the failure with the branch left in place for inspection. A conflict or ambiguity between the plan, the findings and the code is yours to decide: decide it, record `Ruling: <choice> — <why> — <cost if wrong>` in the worklog, and continue. Stop only for what {{LAW:echo-the-intent}}, {{LAW:deletion-is-deliberate}} or {{DOCTRINE:consent-before-push}} names; every ruling goes in the final report ({{DOCTRINE:declare-the-judgment-calls}}). When the plan names a `Spec:`, the analyst reads it once; the spec outranks the plan.
33
33
  6. **Pick the shape by host** (table below). Where the host offers a workflow tool the {{SKILL}} may use without a fresh opt-in, a saved script may stand in for the crew lead: analyst → developer → (tester ⇄ developer)×≤2 → fresh developer → proof ([workflow {{SKILL}}](workflow.md)). Everywhere else the crew lead runs the same stages, with the same hand-offs and the same delivery contract.
34
- 7. On success, hand the worktree back to the parent uncommitted, with the mechanical proof (test + lint output, exit codes) and the list of files it changed in the result envelope, rebased on the current base so a conflict with a sibling resolves on the crew's branch. The pipeline never commits, pushes, or merges ({{DOCTRINE:consent-before-push}}): the parent records BASE before dispatch and, before re-running the proof, confirms the branch descends from it and the diff is non-empty (an empty diff is a failure; never `HEAD~1`); it re-runs the proof commands itself, shows the user the diff and the output, and commits and merges once the user accepts.
34
+ 7. On success, hand the branch back to the parent — its local commits and any uncommitted work — with the mechanical proof (test + lint output, exit codes) and the list of files it changed in the result envelope, rebased on the current base so a conflict with a sibling resolves on the crew's branch. The crew commits only on its own branch; it never pushes and never merges outside it ({{DOCTRINE:consent-before-push}}): the parent records BASE before dispatch and, before re-running the proof, confirms the branch descends from it and the diff is non-empty (an empty diff is a failure; never `HEAD~1`); it re-runs the proof commands itself, shows the user the diff and the output, and merges once the user accepts.
35
35
 
36
36
  ## Hosts
37
37
 
@@ -46,10 +46,10 @@ Check, do not assume: before the first pipeline of a session on a host marked un
46
46
 
47
47
  ## Delivery contract
48
48
 
49
- A worktree containing the work, uncommitted, **plus** the mechanical proof in the result envelope: test and lint output with exit codes. Anything without green proof is surfaced, never merged. The crew's proof is what the parent re-runs, not what it trusts: a log is an account of the state, and the gate that decides the merge runs against the state itself.
49
+ The crew's branch — its local commits and any uncommitted work — **plus** the mechanical proof in the result envelope: test and lint output with exit codes. Anything without green proof is surfaced, never merged. The crew's proof is what the parent re-runs, not what it trusts: a log is an account of the state, and the gate that decides the merge runs against the state itself.
50
50
 
51
51
  ## Done when
52
52
 
53
- - Green proof: the crew delivered a worktree whose tests and lint the parent re-ran green, and the user accepted the commit and merge — or the loop cap was exhausted and the failure was reported with the branch left in place.
53
+ - Green proof: the crew delivered a branch whose tests and lint the parent re-ran green, and the user accepted the merge — or the loop cap was exhausted and the failure was reported with the branch left in place.
54
54
 
55
55
  <!-- INCLUDE: skills/_self-improvement.md -->
@@ -15,7 +15,10 @@
15
15
  [brainstorm {{SKILL}}](brainstorm.md) first rather than planning blind. Otherwise
16
16
  restate the goal in one line. Either way, confirm the actual starting state before
17
17
  designing the steps ({{LAW:verify-before-asserting}} — verify before designing).
18
- 2. Write a numbered plan to `WORKLOG.md` (or `plans/<task>.md`): ordered steps, each
18
+ 2. Write a numbered plan to `WORKLOG.md` (or `plans/<task>.md`) in your {{NOTEBOOK}}
19
+ (§6) — into the repository only when the user asks. A worker or slice
20
+ in another worktree cannot see the {{NOTEBOOK}}, so its brief carries the plan's path
21
+ or text. The plan holds ordered steps, each
19
22
  independently checkable. Group the steps into milestones — coherent chunks after
20
23
  which the work can be verified and reviewed. Cut the steps as **vertical slices** —
21
24
  thin end-to-end pieces, each green and verifiable on its own, never one horizontal
@@ -51,7 +54,8 @@
51
54
  done-condition is confirmed.
52
55
 
53
56
  > The worklog is external memory: it lets a context-limited agent recover its
54
- > place after the window fills, and lets the user correct course early. Consider
55
- > git-ignoring `WORKLOG.md` if it should stay local to each developer.
57
+ > place after the window fills, and lets the user correct course early. The
58
+ > {{NOTEBOOK}} is git-ignored; a worklog the user asked for in the repository is
59
+ > committed or ignored as they decide.
56
60
 
57
61
  <!-- INCLUDE: skills/_self-improvement.md -->
@@ -6,7 +6,7 @@
6
6
 
7
7
  {{CREDIT:piomin-spring-boot:skills/spring-boot/references/testing.md}}
8
8
 
9
- **Trigger:** writing or fixing tests in a Spring Boot project: unit tests of services, `@WebMvcTest` / `@DataJpaTest` slices, `@SpringBootTest` integration tests, Testcontainers, mocking beans. Spring-specific; core test discipline lives in the test-gates and develop skills.
9
+ **Trigger:** writing or fixing tests in a Spring Boot project: unit tests of services, `@WebMvcTest` / `@DataJpaTest` slices, `@SpringBootTest` integration tests, Testcontainers, mocking beans. Spring-specific; core test discipline lives in the develop {{SKILL}} and the tester {{AGENT}}.
10
10
 
11
11
  Target stack: Spring Boot 4, JUnit 5, Mockito, AssertJ.
12
12
 
package/themes/biker.json CHANGED
@@ -14,74 +14,74 @@
14
14
  "EPI_CONTEXT": "Read the route notes before you twist the throttle.",
15
15
  "EPI_SCRIPTS": "Optional, for crews that want the code enforced for them.",
16
16
  "BENEDICTION": "Ride disciplined, keep the code, and bring it home clean.",
17
- "DESC_REVIEWER": "Walks the bike over before it rolls — correctness first, finish second.",
18
- "DESC_TESTER": "Sets up the test runs, takes them, and reads the wreck when they go down.",
19
- "DESC_DEVELOPER": "Wrenches the scoped fix in its own bay, road-tests it once, then hands it — to the test rider.",
17
+ "DESC_REVIEWER": "Walks the bike over before it rolls: correctness first.",
18
+ "DESC_TESTER": "Runs the test laps and reads the wreck when they go down.",
19
+ "DESC_DEVELOPER": "Wrenches the scoped fix in its own bay, then hands it over.",
20
20
  "DESC_ARCHITECT": "Plans the route before a single line is committed.",
21
21
  "DESC_DOCS": "Keeps the roadbook and the notes once the work is done.",
22
- "DESC_SECURITY": "Goes over anything touching the security surface, bolt by bolt.",
23
- "DESC_PERFORMANCE": "Puts it on the dyno — measures where the power goes before anyone touches the engine.",
24
- "DESC_EXPLORER": "Sends the scout ahead — sweeps wide on a throwaway recon run, brings back only the read.",
25
- "DESC_RESEARCHER": "Rides out past the county line — reads the road signs everyone else skipped, checks each one twice, brings back only what held up.",
26
- "DESC_MEMORY_CURATOR": "Clears out the clubhouse lockers — merges the doubles, labels every shelf, boxes the old gear, asks before anything hits the skip.",
27
- "DESC_ADVOCATE": "Argues for the run — the ground to be gained, the opening, the cost of staying parked.",
28
- "DESC_SKEPTIC": "Plays the doubter — calls the move on its failure modes, its risks, and the assumptions nobody checked.",
29
- "DESC_PRAGMATIST": "Weighs the run — the cost, the effort, the wear, and whether the payoff is worth the miles.",
30
- "DESC_STEWARD": "Minds the long haul — the build, the upkeep, the debt, and the fit with where the crew is headed.",
31
- "DESC_VISIONARY": "Argues the bold run — the big payoff over the horizon and what it'd take to chase it.",
32
- "DESC_USER_ADVOCATE": "Speaks for whoever the work is for — their friction, their need, what they'd actually ask for.",
33
- "DESC_FRAMER": "Questions the route itself — whether the run answers the real need or just a symptom.",
34
- "DESC_EMPIRICIST": "Wants the proof — holds every claim, for and against, to the odometer, trials, or precedent.",
35
- "DESC_OPERATOR": "Speaks for the bike on the road — how it holds under load, the watch, and the on-call burden of keeping it running.",
36
- "DESC_HISTORIAN": "Brings the old miles — what was tried before, how it went, and the lesson for this run.",
37
- "DESC_SPRING_BOOT_ENGINEER": "Builds a Spring Boot feature or service end to end in a Java codebase, frame to finish.",
38
- "DESC_SPRING_REVIEWER": "Walks a Spring Boot change over like a bike before a ride — layering, transactions, JPA, configuration, test slices.",
39
- "DESC_SPRING_SECURITY": "Goes over Spring Security changes bolt by bolt — filter chain, method security, OAuth2/JWT, CORS/CSRF.",
40
- "DESC_KUBERNETES_SPECIALIST": "Sets up the Kubernetes manifests for a Spring Boot service — probes, resources, rollout — so it holds on the highway.",
41
- "DESC_DOCKER_EXPERT": "Packs the Docker image of a Spring Boot service lean, layered or native, ready to roll. Image and dev Compose file only; operating a Compose stack is the docker kit's compose-ops.",
42
- "DESC_DEVOPS_ENGINEER": "Tunes the build and delivery pipeline of a Spring Boot service, on whatever CI the shop already runs.",
43
- "DESC_REACT_ENGINEER": "Builds a React feature in a Vite or webpack app, TypeScript or JavaScript, or makes a broken build or Jest run green, frame to finish.",
44
- "DESC_REACT_REVIEWER": "Walks a React change over like a bike before a ride — hooks, state, data fetching, accessibility, React security, tests.",
45
- "DESC_PLAN": "Map the route before a non-trivial run; mark your progress mile by mile.",
46
- "DESC_DEPENDENCIES": "Inspect every part on the bike — worn, recalled, discontinued, dead weight — into a risk-ordered replacement plan, then fit one part at a time, trials green between each.",
47
- "DESC_GIT_HISTORY": "Trace the roadbook to find when it broke or why a part was fitted — bisect, blame, the pickaxe, hands off the bike — or recover a wrecked run and rewrite the history safely, reflog and rebase behind a backup.",
48
- "DESC_DOCUMENT_PROJECT": "Write the crew's PRD, design system, architecture and AGENTS.md off the living code, mend the doc tree, and re-render the offline HTML overview.",
22
+ "DESC_SECURITY": "Goes over the security surface bolt by bolt.",
23
+ "DESC_PERFORMANCE": "Puts it on the dyno and finds where the power goes.",
24
+ "DESC_EXPLORER": "Sends the scout ahead on a throwaway run; brings the read.",
25
+ "DESC_RESEARCHER": "Rides past the county line; checks each sign twice.",
26
+ "DESC_MEMORY_CURATOR": "Clears the clubhouse lockers; asks before anything goes.",
27
+ "DESC_ADVOCATE": "Argues for the run and the ground to be gained.",
28
+ "DESC_SKEPTIC": "Plays the doubter and calls the move on its risks.",
29
+ "DESC_PRAGMATIST": "Weighs whether the payoff is worth the miles.",
30
+ "DESC_STEWARD": "Minds the long haul: the build, the upkeep, the debt.",
31
+ "DESC_VISIONARY": "Argues the bold run and the big payoff past the horizon.",
32
+ "DESC_USER_ADVOCATE": "Speaks for whoever the work is for.",
33
+ "DESC_FRAMER": "Questions the route: real need or just a symptom.",
34
+ "DESC_EMPIRICIST": "Wants odometer, trials or precedent behind each claim.",
35
+ "DESC_OPERATOR": "Speaks for the bike on the road and the on-call burden.",
36
+ "DESC_HISTORIAN": "Brings the old miles: what was tried and how it went.",
37
+ "DESC_SPRING_BOOT_ENGINEER": "Builds a Spring Boot feature or service, frame to finish.",
38
+ "DESC_SPRING_REVIEWER": "Walks a Spring Boot change over before the ride.",
39
+ "DESC_SPRING_SECURITY": "Goes over Spring Security changes bolt by bolt.",
40
+ "DESC_KUBERNETES_SPECIALIST": "Sets up Kubernetes manifests for a Spring Boot service.",
41
+ "DESC_DOCKER_EXPERT": "Packs a lean Spring Boot Docker image; not Compose ops.",
42
+ "DESC_DEVOPS_ENGINEER": "Tunes the CI build and delivery of a Spring Boot service.",
43
+ "DESC_REACT_ENGINEER": "Builds a React feature, or gets a broken build rolling.",
44
+ "DESC_REACT_REVIEWER": "Walks a React change over before the ride.",
45
+ "DESC_PLAN": "Map the route before a non-trivial run; mark each mile.",
46
+ "DESC_DEPENDENCIES": "Inspect every part on the bike, then fit one at a time.",
47
+ "DESC_GIT_HISTORY": "Trace the roadbook by bisect and blame, or rebuild it.",
48
+ "DESC_DOCUMENT_PROJECT": "Write the PRD, architecture and AGENTS.md off the code.",
49
49
  "DESC_COMMIT": "Load only what this run touched and seal a focused commit.",
50
50
  "DESC_CODE_REVIEW": "Go over a diff or PR — correctness first, finish after.",
51
- "DESC_BRAINSTORM": "Turn a raw idea into an agreed route before a single wheel turns.",
52
- "DESC_CODEBASE_DESIGN": "Build deep modules and the crew's own language — big behaviour behind a small handlebar at a seam placed on purpose, a living GLOSSARY.md, an ADR for every call that's hard to undo.",
53
- "DESC_WAYFINDER": "Chart a run too big for one ride as a shared map of decision tickets, cleared one at a time until the road's open.",
54
- "DESC_PROTOTYPE": "Answer a design question with throwaway code — built to learn the road, never to keep.",
55
- "DESC_ROAST_ME": "Tear into the user's own ask, plan or idea, not code — blunt, exact, always actionable.",
56
- "DESC_FRESH_EYES": "Bring in a fresh rider who's seen neither the route notes nor the miles — only the original orders and the finished bike — to set the bar blind, then call whether it meets the orders, free of the maker's bragging.",
51
+ "DESC_BRAINSTORM": "Turn a raw idea into an agreed route before wheels turn.",
52
+ "DESC_CODEBASE_DESIGN": "Build deep modules, sound seams, a glossary and ADRs.",
53
+ "DESC_WAYFINDER": "Chart a run too big for one ride as decision tickets.",
54
+ "DESC_PROTOTYPE": "Answer a design question with throwaway code.",
55
+ "DESC_ROAST_ME": "Tear into the user's own ask, plan or idea, blunt.",
56
+ "DESC_FRESH_EYES": "Bring in a fresh rider to judge the bike blind.",
57
57
  "ROAST_PERSONA": "a grizzled road captain who has watched this exact mistake put a bike in the ditch",
58
- "DESC_COUNCIL": "Call a crew of opposed voices to argue a call out, then hand down a verdict with the dissent kept in the roadbook.",
59
- "DESC_DEBUG": "Hunt the fault by evidence — a run that fails on it first, isolate it, kill the root cause, prove it fixed — a red CI run counts too, reproduced under CI's own conditions.",
60
- "DESC_REFACTOR": "Rebuild the bike without changing how it handles — one named move, trials green throughout.",
61
- "DESC_PONYTAIL": "The laziest fix that rides — least code, shortest road; stock parts before custom builds, one line before fifty. lite/full/ultra.",
62
- "DESC_PARALLEL_AGENTS": "Send several riders on independent runs at once, then bring in what they gather.",
63
- "DESC_PIPELINE": "Send a small crew of riders — scout, wrench, test rider — to work a job in their own lane, rolling it into the pack only once the road-test comes back clean.",
64
- "DESC_LOOP": "Ride a requirement in short, scored laps on its own loop/* lane, the loop engine calling every turn.",
65
- "DESC_FACTORY": "Ride one work item from the call-out to an open PR with green CI, the factory engine marking every stop. The merge stays yours.",
66
- "DESC_BRICK_FORGE": "Build or re-tune a loop brick, then run it past geneseed loop check.",
67
- "DESC_FACTORY_FORGE": "Build a factory from bricks and loops, run it past geneseed factory check, and call in brick-forge when a part is missing.",
68
- "DESC_DEVELOP": "Push a change through the run — the smallest turn of the wrench, a test written to cover it, the touched trials green, sealed slice by slice.",
69
- "DESC_TEACH": "Get a rider road-ready, or test what they've got — a crash course, a manual decoded, a day-by-day route; or a drill, a talk-through, a bluff called.",
70
- "DESC_ADHD": "Ride every reply for a reader with ADHD — next move first, numbered stops, the route restated each turn, side roads held back, real time estimates. On until \"stop adhd mode\".",
71
- "DESC_LEARN_MODE": "Learn the build while riding it — they call the line at each checkpoint, you lay down the code they agreed to, and the mode sticks to the project between rides.",
72
- "DESC_OWNERSHIP": "Keep the rider in charge of the production build — they call each part at checkpoints, as close as they choose to ride, and the club's rules sit in the root AGENTS.md.",
73
- "DESC_SECURITY_AUDIT": "Ride the change like someone trying to steal it — where it can be forced, what it leaks, what it drags in from outside — and call it: ship, fix, or park it.",
74
- "DESC_SKILL_FORGE": "Forge, tune, merge, or scrap a move — reuse what's in the toolbox first, nail the trigger before the steps, test it against the neighbouring moves, register every bolt, doctor green.",
75
- "DESC_WORKTREE": "Wrench on a task in its own bay — a fresh worktree off a clean base, nothing shared with the bike already on the lift, back through the normal gate, bay cleared when it's merged.",
76
- "DESC_HANDOFF": "Hand off the bike — snapshot the state so a fresh rider takes the grips in one read.",
77
- "DESC_SHIP": "Roll it in: open a PR with a clear write-up, or merge the branch, once it's verified.",
78
- "DESC_RELEASE": "Cut a release — raise the version, write the roadbook entry, tag it, all three in sync.",
79
- "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
80
- "DESC_RESEARCH": "Find the answer out on the open road — search wide, then prove every claim against independent sources before you trust it.",
81
- "DESC_RULE": "Sort it 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 — and keep the memory stash serviced: merge, scrap, promote.",
82
- "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.",
83
- "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 — and lay down the rider's own OpenCode paint job.",
84
- "DESC_REVIEW_RESPONSE": "Take the notes straight — weigh each call, then act on it or push back with reasons.",
58
+ "DESC_COUNCIL": "Call a crew of opposed voices to argue a call out.",
59
+ "DESC_DEBUG": "Hunt the fault by evidence and kill the root cause.",
60
+ "DESC_REFACTOR": "Rebuild the bike without changing how it handles.",
61
+ "DESC_PONYTAIL": "The laziest fix that rides. lite/full/ultra.",
62
+ "DESC_PARALLEL_AGENTS": "Send several riders on independent runs at once.",
63
+ "DESC_PIPELINE": "Send a crew to a worktree; roll in on green tests and lint.",
64
+ "DESC_LOOP": "Ride a requirement in short, scored laps on a loop lane.",
65
+ "DESC_FACTORY": "Ride one work item through a factory to a green PR.",
66
+ "DESC_BRICK_FORGE": "Build or re-tune a loop brick, then check it.",
67
+ "DESC_FACTORY_FORGE": "Build a factory from bricks and loops, then check it.",
68
+ "DESC_DEVELOP": "Push a change through the run: smallest wrench, tests green.",
69
+ "DESC_TEACH": "Get a rider road-ready, or test what they've got.",
70
+ "DESC_ADHD": "Ride every reply for a reader with ADHD: next move first.",
71
+ "DESC_LEARN_MODE": "Learn the build while riding it; they call each line.",
72
+ "DESC_OWNERSHIP": "Keep the rider in charge of the production build.",
73
+ "DESC_SECURITY_AUDIT": "Ride the change like a thief would; ship, fix or park it.",
74
+ "DESC_SKILL_FORGE": "Forge, tune, merge, or scrap a move.",
75
+ "DESC_WORKTREE": "Wrench on a task in its own bay, a fresh worktree.",
76
+ "DESC_HANDOFF": "Snapshot the state so a fresh rider takes the grips.",
77
+ "DESC_SHIP": "Roll it in: open a PR or merge the verified branch.",
78
+ "DESC_RELEASE": "Cut a release: version, roadbook entry and tag in sync.",
79
+ "DESC_INGEST": "Bring a PDF, Office or web document into markdown.",
80
+ "DESC_RESEARCH": "Find the answer on the open road, every claim proven.",
81
+ "DESC_RULE": "Sort a standing rule from a memory, then log or test it.",
82
+ "DESC_PROFILE": "Stamp the rider's plate into PROFILE.md.",
83
+ "DESC_GENESEED": "Operate the Geneseed harness; paint an OpenCode theme.",
84
+ "DESC_REVIEW_RESPONSE": "Weigh each review call, then act on it or push back.",
85
85
  "LEX_SEALED_SECRETS": "Keep It in the Saddlebag · Sealed Secrets",
86
86
  "LEX_ONE_INTENT_ONE_ACT": "One Move per Corner · One Intent, One Act",
87
87
  "LEX_VERIFY_BEFORE_ASSERTING": "Check the Mirrors · Verify Before Asserting",
@@ -150,21 +150,21 @@
150
150
  "WIKI": "Road Atlas",
151
151
  "EPI_WIKI": "Every road the club ever mapped — check the atlas before you ride, mark what you find.",
152
152
  "INTRO_WIKI": "The club may keep a road atlas on this machine — a vault of linked maps and route notes that outlasts any single run.",
153
- "DESC_WIKI": "Ride with the club's road atlas — check the map before you roll, mark new routes properly linked, and file them where the chapter keeps them.",
154
- "DESC_MCP": "Build or fix up an MCP server — read the spec, shape tools around real jobs, test with the Inspector, and prove it works.",
155
- "DESC_BRUNO": "Build, re-rack, or test a Bruno API collection — requests, environments, assertions, chaining — and never let a secret ride along.",
156
- "DESC_PROSE": "Write like a human, not a bot — strip the filler, keep it plain, mix up the rhythm, and trust whoever's reading.",
157
- "DESC_FRONTEND_DESIGN": "Design a UI with real attitude — pick palette, type, and layout for this job, not the stock defaults, then trim it down to one bold move.",
158
- "DESC_DECK": "Build slides or a presentation as one offline HTML file — a quick interview, the outline signed off first, then a deck that rides on arrow keys and prints clean.",
159
- "DESC_WORKFLOW": "Run a saved route that sends your riders by script — many rolled out at once, their findings gathered and checked in one clean run.",
160
- "DESC_SPRING_BOOT": "Build or change a Spring Boot service — controllers, configuration, REST clients, error handling, observability, packaging — and keep it on the road.",
161
- "DESC_SPRING_DATA_JPA": "Wrench on Spring Data JPA and Hibernate — entities, repositories, queries, transactions, migrations, N+1 and fetch trouble.",
162
- "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the ride.",
163
- "DESC_REACT": "Build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility — and keep it on the road.",
164
- "DESC_REACT_TESTING": "Write or fix React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack — before the ride.",
165
- "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit — before the ride.",
166
- "DESC_GITLAB_CI": "Write or fix .gitlab-ci.yml — rules, needs DAG, include and extends, cache and artifacts, protected and masked variables, environments, CI lint — before the ride.",
167
- "DESC_COMPOSE_OPS": "Write, review or run any Compose stack — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback — before the ride. Not a Spring Boot image build (docker-expert).",
153
+ "DESC_WIKI": "Ride with the club's road atlas; mark new routes.",
154
+ "DESC_MCP": "Build or fix up a Model Context Protocol server.",
155
+ "DESC_BRUNO": "Build, re-rack, or test a Bruno API collection.",
156
+ "DESC_PROSE": "Write like a human, not a bot.",
157
+ "DESC_FRONTEND_DESIGN": "Design a UI with real attitude, not stock defaults.",
158
+ "DESC_DECK": "Build slides as one offline HTML file that prints clean.",
159
+ "DESC_WORKFLOW": "Run a saved route that sends your riders by script.",
160
+ "DESC_SPRING_BOOT": "Build or change a Spring Boot service; keep it on the road.",
161
+ "DESC_SPRING_DATA_JPA": "Wrench on JPA and Hibernate: queries, N+1, fetch trouble.",
162
+ "DESC_SPRING_TESTING": "Write or fix Spring Boot tests: slices, Testcontainers.",
163
+ "DESC_REACT": "Build or change React components in a Vite or webpack app.",
164
+ "DESC_REACT_TESTING": "Write or fix React tests: Jest, Testing Library, MSW.",
165
+ "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library.",
166
+ "DESC_GITLAB_CI": "Write or fix .gitlab-ci.yml before the ride.",
167
+ "DESC_COMPOSE_OPS": "Write, review or run a Compose stack; not image builds.",
168
168
  "AGENT_COLORS": {
169
169
  "architect": "primary",
170
170
  "reviewer": "warning",
@@ -14,74 +14,74 @@
14
14
  "EPI_CONTEXT": "Read the track briefing before you leave the pit lane.",
15
15
  "EPI_SCRIPTS": "Optional stewarding for teams that want the rules enforced.",
16
16
  "BENEDICTION": "Race clean, keep the regulations, and bring it home on the podium.",
17
- "DESC_REVIEWER": "Runs the pre-race scrutineering — correctness first, polish second — before the car is cleared to start.",
18
- "DESC_TESTER": "Sets up the test laps, runs them, and reads the data trace when they fail.",
19
- "DESC_DEVELOPER": "Builds the scoped fix in its own garage, shakes it down once, then hands it — to the test driver.",
20
- "DESC_ARCHITECT": "Walks the circuit and plots the strategy before a single line is committed.",
21
- "DESC_DOCS": "Files the race report and updates the notes once the chequered flag falls.",
22
- "DESC_SECURITY": "Runs the safety inspection on anything touching the security surface.",
23
- "DESC_PERFORMANCE": "Brings out the stopwatch — times every lap and names the slow sector with the split.",
24
- "DESC_EXPLORER": "Sends the track scout — sweeps wide from a throwaway recon lap, returns only the read.",
25
- "DESC_RESEARCHER": "Sends the pit reporter down the paddock — checks every rumour against two sources before it goes on air.",
26
- "DESC_MEMORY_CURATOR": "Tidies the archive between races — merges the duplicate notes, files each by topic, shelves the old ones, asks before binning any.",
27
- "DESC_ADVOCATE": "Calls for the overtake — the place to be gained, the gap, the cost of staying put.",
28
- "DESC_SKEPTIC": "Plays the doubter — attacks the move for the failure modes, the risks, and the assumptions nobody checked on the grid.",
29
- "DESC_PRAGMATIST": "Weighs the strategy — the cost, the effort, the tyre wear, and whether the payoff is worth the stop.",
30
- "DESC_STEWARD": "Minds the whole season — the build, the upkeep, the debt, and the fit with the team's direction.",
31
- "DESC_VISIONARY": "Argues the bold call — the race-winning upside and what it would take to chase it.",
32
- "DESC_USER_ADVOCATE": "Speaks for whoever the result is for — their experience, their friction, what they'd actually ask for.",
33
- "DESC_FRAMER": "Questions the race itself — whether the move wins the real grand prix or just a single corner.",
34
- "DESC_EMPIRICIST": "Demands the data — holds every claim, for and against, to telemetry, trials, or precedent.",
35
- "DESC_OPERATOR": "Speaks for the car at racing speed — its reliability under load, its watch, and the on-call burden of running it.",
36
- "DESC_HISTORIAN": "Brings the form book — what was tried in past races, how it went, and the lesson for this call.",
37
- "DESC_SPRING_BOOT_ENGINEER": "Builds a Spring Boot feature or service end to end in a Java codebase — lights out and away it goes.",
38
- "DESC_SPRING_REVIEWER": "Runs the scrutineering on a Spring Boot change with framework know-how — layering, transactions, JPA, configuration, test slices.",
39
- "DESC_SPRING_SECURITY": "Checks the Spring Security barriers — filter chain, method security, OAuth2/JWT, CORS/CSRF — on any change that touches them.",
40
- "DESC_KUBERNETES_SPECIALIST": "Sets the pit wall for a Spring Boot service on Kubernetes — manifests, probes, resources, rollout.",
41
- "DESC_DOCKER_EXPERT": "Preps the Docker image of a Spring Boot service, layered or native, ready for the grid. Image and dev Compose file only; operating a Compose stack is the docker kit's compose-ops.",
42
- "DESC_DEVOPS_ENGINEER": "Works the pit lane of build and delivery for a Spring Boot service, on whatever CI the team already runs.",
43
- "DESC_REACT_ENGINEER": "Builds a React feature in a Vite or webpack app, TypeScript or JavaScript, or makes a broken build or Jest run green — lights out and away it goes.",
44
- "DESC_REACT_REVIEWER": "Runs the scrutineering on a React change with framework know-how — hooks, state, data fetching, accessibility, React security, tests.",
45
- "DESC_PLAN": "Plot the strategy before a non-trivial stint; call your progress lap by lap.",
46
- "DESC_DEPENDENCIES": "Survey every component — outdated, on recall, discontinued, dead weight — into a risk-ordered upgrade plan, then fit one change at a time, trials green between each.",
47
- "DESC_GIT_HISTORY": "Replay the data to find when the lap fell apart or why a line was driven — bisect, blame, the pickaxe, hands off the car — or recover a crashed session and rewrite the history safely, reflog and rebase behind a backup lap.",
48
- "DESC_DOCUMENT_PROJECT": "Call the team's PRD, design system, architecture and AGENTS.md straight from the code, mend the doc tree, and re-render the offline HTML overview.",
49
- "DESC_COMMIT": "Stage only the parts this lap touched and seal a focused commit.",
17
+ "DESC_REVIEWER": "Runs pre-race scrutineering before the car is cleared.",
18
+ "DESC_TESTER": "Runs the test laps and reads the trace when they fail.",
19
+ "DESC_DEVELOPER": "Builds the scoped fix in its own garage, then hands it over.",
20
+ "DESC_ARCHITECT": "Walks the circuit and plots strategy before any code.",
21
+ "DESC_DOCS": "Files the race report once the chequered flag falls.",
22
+ "DESC_SECURITY": "Runs the safety inspection on the security surface.",
23
+ "DESC_PERFORMANCE": "Times every lap and names the slow sector.",
24
+ "DESC_EXPLORER": "Sends the track scout on a throwaway recon lap.",
25
+ "DESC_RESEARCHER": "Checks every paddock rumour against two sources.",
26
+ "DESC_MEMORY_CURATOR": "Tidies the archive between races; asks before binning.",
27
+ "DESC_ADVOCATE": "Makes the case for the overtake and the place to gain.",
28
+ "DESC_SKEPTIC": "Plays the doubter and attacks the move for its risks.",
29
+ "DESC_PRAGMATIST": "Weighs whether the payoff is worth the stop.",
30
+ "DESC_STEWARD": "Minds the whole season: the build, the upkeep, the debt.",
31
+ "DESC_VISIONARY": "Argues the bold race-winning call over safe incremental laps.",
32
+ "DESC_USER_ADVOCATE": "Speaks for whoever the result is for.",
33
+ "DESC_FRAMER": "Asks whether the move wins the race or just a corner.",
34
+ "DESC_EMPIRICIST": "Demands telemetry, trials or precedent behind each claim.",
35
+ "DESC_OPERATOR": "Speaks for the car at racing speed and its on-call crew.",
36
+ "DESC_HISTORIAN": "Brings the form book: what past races taught.",
37
+ "DESC_SPRING_BOOT_ENGINEER": "Builds a Spring Boot feature or service end to end.",
38
+ "DESC_SPRING_REVIEWER": "Scrutineers a Spring Boot change with framework know-how.",
39
+ "DESC_SPRING_SECURITY": "Checks the Spring Security barriers on a change.",
40
+ "DESC_KUBERNETES_SPECIALIST": "Sets the Kubernetes pit wall for a Spring Boot service.",
41
+ "DESC_DOCKER_EXPERT": "Preps a Spring Boot Docker image; not Compose ops.",
42
+ "DESC_DEVOPS_ENGINEER": "Works the CI pit lane of a Spring Boot service.",
43
+ "DESC_REACT_ENGINEER": "Builds a React feature, or makes a red build green.",
44
+ "DESC_REACT_REVIEWER": "Scrutineers a React change with framework know-how.",
45
+ "DESC_PLAN": "Plot the strategy before a non-trivial stint.",
46
+ "DESC_DEPENDENCIES": "Survey every component, then fit one change at a time.",
47
+ "DESC_GIT_HISTORY": "Replay git history by bisect and blame, or rewrite it.",
48
+ "DESC_DOCUMENT_PROJECT": "Call the PRD, architecture and AGENTS.md from the code.",
49
+ "DESC_COMMIT": "Stage only what this lap touched; seal a focused commit.",
50
50
  "DESC_CODE_REVIEW": "Scrutineer a diff or PR — correctness first, polish after.",
51
- "DESC_BRAINSTORM": "Turn a raw idea into an agreed strategy before a single tyre hits the track.",
52
- "DESC_CODEBASE_DESIGN": "Design deep modules and the paddock's own language — plenty behind a tight interface at a seam placed on purpose, a living GLOSSARY.md, an ADR for every call that's hard to reverse.",
53
- "DESC_WAYFINDER": "Chart work too big for one session as a shared race map of decision tickets, cleared one at a time until the way is clear.",
54
- "DESC_PROTOTYPE": "Answer a design question with throwaway code — built to learn the line, never to keep.",
55
- "DESC_ROAST_ME": "Put the user's own ask, plan or idea through scrutineering, not code — blunt, exact, always actionable.",
56
- "DESC_FRESH_EYES": "Bring in a fresh steward who's seen neither your briefing nor your laps — only the original orders and the finished car — to set the bar blind, then rule whether the work meets the orders, free of the driver's bravado.",
51
+ "DESC_BRAINSTORM": "Turn a raw idea into an agreed strategy before the track.",
52
+ "DESC_CODEBASE_DESIGN": "Design deep modules, clean seams, a glossary and ADRs.",
53
+ "DESC_WAYFINDER": "Chart work too big for one session as a race map.",
54
+ "DESC_PROTOTYPE": "Answer a design question with throwaway code.",
55
+ "DESC_ROAST_ME": "Scrutineer the user's own ask, plan or idea, blunt.",
56
+ "DESC_FRESH_EYES": "Bring in a fresh steward to rule on the work blind.",
57
57
  "ROAST_PERSONA": "a hard-nosed race steward who has watched this exact mistake end a race in the wall",
58
- "DESC_COUNCIL": "Convene a stewards' panel of opposed voices to debate a call, then hand down a verdict with the dissent kept on the record.",
59
- "DESC_DEBUG": "Hunt the fault by evidence — a lap that fails on it first, isolate it, find the root cause, and prove it fixed — a red CI run too, reproduced under CI's own conditions.",
60
- "DESC_REFACTOR": "Rebuild the car without changing how it drives — one named move, trials green throughout.",
61
- "DESC_PONYTAIL": "The laziest line that finishes — least code, shortest path; standard kit before custom builds, one line before fifty. lite/full/ultra.",
62
- "DESC_PARALLEL_AGENTS": "Send several drivers out on independent stints at once, then bring in what they gather.",
63
- "DESC_PIPELINE": "Send a small crew — scout, mechanic, test driver — out on their own stint, and only wave them into the results once the timing sheet comes back clean.",
64
- "DESC_LOOP": "Run a requirement in short, scored laps on a loop/* branch, the loop engine calling every move.",
65
- "DESC_FACTORY": "Take one work item from kick-off to an open PR with green CI, the factory engine calling every stage. The merge stays yours.",
66
- "DESC_BRICK_FORGE": "Build or adapt a loop brick, then put it through geneseed loop check.",
67
- "DESC_FACTORY_FORGE": "Draw up a factory from bricks and loops, put it through geneseed factory check, and bring on brick-forge when a brick is missing.",
68
- "DESC_DEVELOP": "Drive the change through cover-and-verify — the smallest setup tweak, a trial written to time it, the affected laps green, sealed corner by corner.",
69
- "DESC_TEACH": "Bring a rookie up to speed, or test them — a crash course, a regulation decoded, a day-by-day programme; or a drill, a debrief, a claim stress-tested.",
70
- "DESC_ADHD": "Call every reply for a reader with ADHD — next play first, numbered steps, the score restated each turn, tangents held back, real time estimates. On until \"stop adhd mode\".",
71
- "DESC_LEARN_MODE": "Put the driver in charge of the race plan — they call the strategy at each checkpoint, you execute the agreed laps, and the mode holds for the project across sessions.",
72
- "DESC_OWNERSHIP": "Keep the driver in charge of the production code — they make the call on each part at checkpoints, at the granularity they set, and the team's rulebook sits in the root AGENTS.md.",
73
- "DESC_SECURITY_AUDIT": "Scrutineer a change for how it would be attacked and what it leaks — trust boundaries, the classic vulnerability classes, secrets, the supply chain — and rule: ship, fix, or black-flag.",
74
- "DESC_SKILL_FORGE": "Author, sharpen, merge, or retire a manoeuvre — reuse first, the trigger before the steps, tested against its neighbours, every satellite registered, doctor green.",
75
- "DESC_WORKTREE": "Run a task in its own garage — a fresh worktree off a clean base, nothing shared with the car already being worked on, back through the normal gate, garage cleared once merged.",
76
- "DESC_HANDOFF": "Hand over the car — snapshot the state so a fresh driver takes the wheel in one read.",
77
- "DESC_SHIP": "Take the chequered flag: open a PR with a clear report, or merge the branch, once it's verified.",
78
- "DESC_RELEASE": "Cut a release — raise the version, write the race report, seal it with a tag, all three in sync.",
79
- "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
80
- "DESC_RESEARCH": "Hunt the answer across the open circuit — search wide, then prove every claim against independent sources before you call it.",
81
- "DESC_RULE": "Sort it 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 — and tend the memory bank besides: merge, retire, promote.",
82
- "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.",
83
- "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 — and roll out the viewer's own OpenCode colour theme.",
84
- "DESC_REVIEW_RESPONSE": "Take the scrutineer's notes straight — weigh each call, then act on it or push back with reasons.",
58
+ "DESC_COUNCIL": "Convene a stewards' panel to debate a call.",
59
+ "DESC_DEBUG": "Hunt the fault by evidence and prove the fix.",
60
+ "DESC_REFACTOR": "Rebuild the car without changing how it drives.",
61
+ "DESC_PONYTAIL": "The laziest line that finishes. lite/full/ultra.",
62
+ "DESC_PARALLEL_AGENTS": "Send several drivers out on independent stints at once.",
63
+ "DESC_PIPELINE": "Send a crew to a worktree; finish on green tests and lint.",
64
+ "DESC_LOOP": "Run a requirement in short, scored laps on a loop branch.",
65
+ "DESC_FACTORY": "Take one work item through a factory to a green PR.",
66
+ "DESC_BRICK_FORGE": "Build or adapt a loop brick, then check it.",
67
+ "DESC_FACTORY_FORGE": "Draw up a factory from bricks and loops, then check it.",
68
+ "DESC_DEVELOP": "Drive the change through cover-and-verify, laps green.",
69
+ "DESC_TEACH": "Bring a rookie up to speed, or test them.",
70
+ "DESC_ADHD": "Call every reply for a reader with ADHD: next play first.",
71
+ "DESC_LEARN_MODE": "Put the driver in charge of the plan while you build.",
72
+ "DESC_OWNERSHIP": "Keep the driver in charge of the production code.",
73
+ "DESC_SECURITY_AUDIT": "Scrutineer a change as an attacker would, then rule.",
74
+ "DESC_SKILL_FORGE": "Author, sharpen, merge, or retire a manoeuvre.",
75
+ "DESC_WORKTREE": "Run a task in its own garage, a fresh worktree.",
76
+ "DESC_HANDOFF": "Snapshot the state so a fresh driver takes the wheel.",
77
+ "DESC_SHIP": "Take the flag: open a PR or merge the verified branch.",
78
+ "DESC_RELEASE": "Cut a release: version, race report and tag in sync.",
79
+ "DESC_INGEST": "Bring a PDF, Office or web document into markdown.",
80
+ "DESC_RESEARCH": "Hunt the answer on the open circuit, every claim proven.",
81
+ "DESC_RULE": "Sort a house rule from a note, then log or test it.",
82
+ "DESC_PROFILE": "Build the player profile in PROFILE.md.",
83
+ "DESC_GENESEED": "Operate the Geneseed harness; roll out an OpenCode theme.",
84
+ "DESC_REVIEW_RESPONSE": "Weigh each scrutineer's call, then act or push back.",
85
85
  "LEX_SEALED_SECRETS": "Sealed Garage · Sealed Secrets",
86
86
  "LEX_ONE_INTENT_ONE_ACT": "One Move per Corner · One Intent, One Act",
87
87
  "LEX_VERIFY_BEFORE_ASSERTING": "Check the Telemetry · Verify Before Asserting",
@@ -150,21 +150,21 @@
150
150
  "WIKI": "Almanac",
151
151
  "EPI_WIKI": "The sport's full almanac — check the history books before the call, update them after the flag.",
152
152
  "INTRO_WIKI": "The broadcast may keep an almanac on this machine — a vault of cross-referenced records and stats that outlives any single season.",
153
- "DESC_WIKI": "Work the almanac — pull the record before making the call, write new entries cross-referenced, and file them into the right season.",
154
- "DESC_MCP": "Build or harden an MCP server — study the spec, shape task-ready tools, test with the Inspector, and prove it on the evals.",
155
- "DESC_BRUNO": "Build, re-order, or test a Bruno API collection — requests, environments, assertions, chaining — no secret leaks, every one kept as a placeholder.",
156
- "DESC_PROSE": "Write copy that sounds human, not machine-read — cut the filler, keep it active, vary the pace, trust the audience.",
157
- "DESC_FRONTEND_DESIGN": "Design a UI with a point of view — palette, type, and layout built for this brief, not the templated defaults, then critique and cut to one bold move.",
158
- "DESC_DECK": "Build slides or a presentation as one offline HTML file — a short interview, the outline approved first, then a deck that runs on arrow keys and prints one slide a page.",
159
- "DESC_WORKFLOW": "Run a saved race plan that drives your team by script — many sent out at once, their results gathered and checked in one clean grand prix.",
160
- "DESC_SPRING_BOOT": "Build or change a Spring Boot service — controllers, configuration, REST clients, error handling, observability, packaging — lap after lap.",
161
- "DESC_SPRING_DATA_JPA": "Work the Spring Data JPA and Hibernate setup — entities, repositories, queries, transactions, migrations, N+1 and fetch problems.",
162
- "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the lights go out.",
163
- "DESC_REACT": "Build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility — lap after lap.",
164
- "DESC_REACT_TESTING": "Write or fix React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack — before the lights go out.",
165
- "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit — before the lights go out.",
166
- "DESC_GITLAB_CI": "Write or fix .gitlab-ci.yml — rules, needs DAG, include and extends, cache and artifacts, protected and masked variables, environments, CI lint — before the lights go out.",
167
- "DESC_COMPOSE_OPS": "Write, review or run any Compose stack — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback — before the lights go out. Not a Spring Boot image build (docker-expert).",
153
+ "DESC_WIKI": "Work the almanac: pull the record, file new entries.",
154
+ "DESC_MCP": "Build or harden a Model Context Protocol server.",
155
+ "DESC_BRUNO": "Build, re-order, or test a Bruno API collection.",
156
+ "DESC_PROSE": "Write copy that sounds human, not machine-read.",
157
+ "DESC_FRONTEND_DESIGN": "Design a UI with a point of view, not template defaults.",
158
+ "DESC_DECK": "Build slides as one offline HTML file, arrow-key driven.",
159
+ "DESC_WORKFLOW": "Run a saved race plan that drives your team by script.",
160
+ "DESC_SPRING_BOOT": "Build or change a Spring Boot service, lap after lap.",
161
+ "DESC_SPRING_DATA_JPA": "Work the JPA and Hibernate setup: queries, N+1, fetch.",
162
+ "DESC_SPRING_TESTING": "Write or fix Spring Boot tests: slices, Testcontainers.",
163
+ "DESC_REACT": "Build or change React components in a Vite or webpack app.",
164
+ "DESC_REACT_TESTING": "Write or fix React tests: Jest, Testing Library, MSW.",
165
+ "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library.",
166
+ "DESC_GITLAB_CI": "Write or fix .gitlab-ci.yml before the lights go out.",
167
+ "DESC_COMPOSE_OPS": "Write, review or run a Compose stack; not image builds.",
168
168
  "AGENT_COLORS": {
169
169
  "architect": "primary",
170
170
  "reviewer": "warning",