geneseed 5.0.1 → 5.0.4

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 (185) hide show
  1. package/CHANGELOG.md +92 -0
  2. package/README.md +4 -4
  3. package/SHIPPED.md +2 -2
  4. package/adapters/claude-code/README.md +11 -5
  5. package/adapters/openclaude/README.md +3 -1
  6. package/adapters/opencode/HOW-OPENCODE-LOADS.md +3 -0
  7. package/adapters/opencode/plugins/geneseed-context.js +12 -1
  8. package/adapters/opencode/plugins/geneseed-guard.js +594 -73
  9. package/adapters/opencode/plugins/geneseed-learn.js +1 -1
  10. package/adapters/opencode/plugins/geneseed-workflow.js +1 -1
  11. package/adapters/opencode/workflows/_runtime.js +1 -1
  12. package/bin/geneseed-cli.mjs +3 -0
  13. package/bin/geneseed-hook.mjs +31 -9
  14. package/docs/PRD.md +1 -1
  15. package/docs/README.md +4 -1
  16. package/docs/concepts/enforcement-table.md +23 -4
  17. package/docs/concepts/exclusions.md +48 -2
  18. package/docs/concepts/factories.md +151 -0
  19. package/docs/concepts/foreman-mode.md +19 -4
  20. package/docs/concepts/hook-gates.md +1 -1
  21. package/docs/concepts/hooks.md +53 -12
  22. package/docs/concepts/host-matrix.md +5 -3
  23. package/docs/concepts/hosts.md +1 -1
  24. package/docs/concepts/kits.md +18 -0
  25. package/docs/concepts/loop-gates.md +3 -0
  26. package/docs/concepts/loops.md +1 -0
  27. package/docs/concepts/rules.md +1 -1
  28. package/docs/concepts/shared-tier.md +1 -1
  29. package/docs/concepts/skills.md +1 -1
  30. package/docs/extending.md +8 -2
  31. package/docs/guides/autostart.md +29 -3
  32. package/docs/guides/choose-your-setup.md +1 -1
  33. package/docs/guides/migrate.md +1 -1
  34. package/docs/guides/run-a-factory.md +88 -0
  35. package/docs/guides/set-up-ownership.md +1 -0
  36. package/docs/guides/uninstall.md +1 -1
  37. package/docs/reference/factory-actions.md +22 -0
  38. package/docs/reference/loop-actions.md +1 -1
  39. package/docs/reference/plugin-activity.md +1 -1
  40. package/docs/reference/plugin-context.md +1 -1
  41. package/docs/reference/plugin-guard.md +24 -5
  42. package/docs/reference/troubleshoot-doctor.md +2 -2
  43. package/docs/understand/a-day.md +9 -5
  44. package/docs/web-ui.md +101 -17
  45. package/harness.config.json +1 -1
  46. package/js/README.md +21 -3
  47. package/js/build/args.mjs +14 -2
  48. package/js/build/emit-claude.mjs +9 -1
  49. package/js/build/emit-opencode.mjs +2 -1
  50. package/js/build/source.mjs +28 -3
  51. package/js/cli-table.json +287 -3
  52. package/js/factory/cli.mjs +153 -0
  53. package/js/factory/graph.mjs +245 -0
  54. package/js/factory/registry.mjs +71 -0
  55. package/js/factory/state.mjs +429 -0
  56. package/js/hosts/activity.mjs +3 -3
  57. package/js/hosts/geneseed-dir.mjs +2 -2
  58. package/js/hosts/gitref.mjs +21 -0
  59. package/js/hosts/hooks-context.mjs +71 -15
  60. package/js/hosts/hooks-done.mjs +3 -1
  61. package/js/hosts/hooks-learn.mjs +1 -1
  62. package/js/hosts/hooks-prims.mjs +271 -1
  63. package/js/hosts/hooks.mjs +409 -151
  64. package/js/hosts/hosts.mjs +22 -0
  65. package/js/hosts/installs.mjs +9 -5
  66. package/js/hosts/settings.mjs +128 -27
  67. package/js/hosts/shim.mjs +155 -7
  68. package/js/hosts/store-watch.mjs +36 -11
  69. package/js/inspect/checks-authoring.mjs +11 -1
  70. package/js/inspect/cost.mjs +91 -5
  71. package/js/inspect/diff.mjs +2 -1
  72. package/js/inspect/doctor.mjs +2 -1
  73. package/js/inspect/inventory.mjs +2 -1
  74. package/js/inspect/validate.mjs +1 -1
  75. package/js/loop/catalog.mjs +24 -12
  76. package/js/loop/cli.mjs +21 -15
  77. package/js/loop/graph.mjs +13 -4
  78. package/js/loop/registry.mjs +65 -28
  79. package/js/loop/state.mjs +18 -8
  80. package/js/maintain/migrate.mjs +2 -2
  81. package/js/maintain/uninstall.mjs +5 -1
  82. package/js/web/actions.mjs +17 -1
  83. package/js/web/api.mjs +52 -11
  84. package/js/web/catalog.mjs +38 -2
  85. package/js/web/daemon.mjs +136 -6
  86. package/js/web/handler.mjs +14 -5
  87. package/js/web/routes.mjs +12 -4
  88. package/js/web/server.mjs +4 -1
  89. package/package.json +1 -1
  90. package/registry.json +35 -0
  91. package/src/AGENT.md.tmpl +18 -24
  92. package/src/agents/_self-improvement.md +7 -6
  93. package/src/agents/developer.md +3 -2
  94. package/src/agents/docker-expert.md +1 -0
  95. package/src/agents/memory-curator.md +3 -2
  96. package/src/bricks/docs-update.md +5 -0
  97. package/src/bricks/holdout-write.md +23 -0
  98. package/src/bricks/holdout.md +25 -0
  99. package/src/bricks/intake.md +18 -0
  100. package/src/bricks/merge-gate.md +22 -0
  101. package/src/bricks/pr-open.md +21 -0
  102. package/src/bricks/retro.md +17 -0
  103. package/src/bricks/test.md +4 -1
  104. package/src/bricks/triage.md +19 -0
  105. package/src/doctrines/comms.md +29 -41
  106. package/src/doctrines/craft.md +3 -10
  107. package/src/doctrines/ops.md +4 -15
  108. package/src/doctrines/process.md +24 -19
  109. package/src/doctrines/rigor.md +1 -5
  110. package/src/factories/analysis-to-build.json +34 -0
  111. package/src/factories/bug-report-to-fix.json +32 -0
  112. package/src/factories/issue-to-pr.json +49 -0
  113. package/src/kits/ci-pipelines/rules.md +10 -0
  114. package/src/kits/ci-pipelines.json +14 -0
  115. package/src/kits/docker/rules.md +11 -0
  116. package/src/kits/docker.json +12 -0
  117. package/src/memory/README.md +5 -4
  118. package/src/modes/foreman.md +23 -10
  119. package/src/notebook/README.md +1 -1
  120. package/src/skills/_checkpoints.md +1 -0
  121. package/src/skills/_self-improvement.md +12 -9
  122. package/src/skills/adhd.md +1 -1
  123. package/src/skills/compose-ops.md +58 -0
  124. package/src/skills/factory-forge.md +97 -0
  125. package/src/skills/factory.md +126 -0
  126. package/src/skills/gitlab-ci.md +51 -0
  127. package/src/skills/jenkins-pipeline.md +56 -0
  128. package/src/skills/parallel-agents.md +1 -1
  129. package/src/skills/pipeline.md +2 -2
  130. package/src/skills/rule.md +24 -18
  131. package/src/skills/skill-forge.md +24 -6
  132. package/src/skills/workflow.md +2 -1
  133. package/themes/_TEMPLATE.json +9 -4
  134. package/themes/biker.json +9 -4
  135. package/themes/commentator.json +9 -4
  136. package/themes/cyberpunk.json +9 -4
  137. package/themes/gamer.json +9 -4
  138. package/themes/imperial.json +9 -4
  139. package/themes/joker.json +9 -4
  140. package/themes/marvin.json +9 -4
  141. package/themes/mean.json +9 -4
  142. package/themes/military.json +9 -4
  143. package/themes/neutral.json +9 -4
  144. package/themes/pirate.json +9 -4
  145. package/themes/sports.json +9 -4
  146. package/themes/verstappen.json +9 -4
  147. package/themes/wizard.json +9 -4
  148. package/web/dist/assets/ActiveLoops-BTHIaRhn.js +1 -0
  149. package/web/dist/assets/Activity-BaoxwVFH.js +1 -0
  150. package/web/dist/assets/ActivityDetail-C_bFD0rW.js +1 -0
  151. package/web/dist/assets/{Bonsai-C1iBAt4v.js → Bonsai-B01lLf0m.js} +1 -1
  152. package/web/dist/assets/{CopyButton-DJ3a4N88.js → CopyButton-Bc66KPyA.js} +1 -1
  153. package/web/dist/assets/Dashboard-X7GZzGJp.js +2 -0
  154. package/web/dist/assets/{Docs-Kffdg5uV.js → Docs-LRYVnGLG.js} +3 -3
  155. package/web/dist/assets/Factories-ARenKBiP.js +1 -0
  156. package/web/dist/assets/{GreenhouseView-k56_cBSF.js → GreenhouseView-CfWR2-sX.js} +1 -1
  157. package/web/dist/assets/{Installs-DtEKLC9h.js → Installs-nfFHnovH.js} +3 -3
  158. package/web/dist/assets/{JournalView-RQnk5l7I.js → JournalView-lpOHcHKK.js} +1 -1
  159. package/web/dist/assets/Kits-Bw5EQl_i.js +1 -0
  160. package/web/dist/assets/Laws-CnZJ0wjZ.js +4 -0
  161. package/web/dist/assets/LibRows-Hqvf1beK.js +1 -0
  162. package/web/dist/assets/Library-JaSsp6Yr.js +3 -0
  163. package/web/dist/assets/Loops-ZaHC5MVl.js +2 -0
  164. package/web/dist/assets/{OperatorHudView-CM5jNPwL.js → OperatorHudView-CggG0_sK.js} +1 -1
  165. package/web/dist/assets/Personal-BObvlb70.js +2 -0
  166. package/web/dist/assets/Settings-BFfPMPc9.js +1 -0
  167. package/web/dist/assets/Tabs-B594Pad_.js +1 -0
  168. package/web/dist/assets/api-DLDVY3K-.js +1 -0
  169. package/web/dist/assets/index-DsLmKHw0.js +6 -0
  170. package/web/dist/assets/index-DvPjphz0.css +1 -0
  171. package/web/dist/index.html +3 -3
  172. package/web/dist/assets/Activity-Ci4PZco3.js +0 -1
  173. package/web/dist/assets/ActivityDetail-C8hroCND.js +0 -1
  174. package/web/dist/assets/Dashboard-C_On4KXw.js +0 -2
  175. package/web/dist/assets/Kits-CXkEBpnf.js +0 -1
  176. package/web/dist/assets/Laws-DhhIVqmh.js +0 -3
  177. package/web/dist/assets/Library-CAUiEoJo.js +0 -3
  178. package/web/dist/assets/Loops-LKD8mF4E.js +0 -2
  179. package/web/dist/assets/Personal-B6Uoly3C.js +0 -2
  180. package/web/dist/assets/RailCats-DQxxYBEP.js +0 -1
  181. package/web/dist/assets/Settings-BTe6-wda.js +0 -1
  182. package/web/dist/assets/Tabs-CbdDWTp_.js +0 -1
  183. package/web/dist/assets/api-D_r0Jtla.js +0 -1
  184. package/web/dist/assets/index-HfGmYXab.js +0 -3
  185. package/web/dist/assets/index-ao3M-Fhm.css +0 -1
@@ -0,0 +1,51 @@
1
+ # {{SKILL}}: gitlab-ci
2
+
3
+ > {{DESC_GITLAB_CI}}
4
+
5
+ **Trigger:** writing, changing or debugging `.gitlab-ci.yml` or a file it includes: job conditions, stage order, `needs`, templates, caches, artifacts, CI/CD variables, environments and deployments, or a pipeline that does not start or runs the wrong jobs. Jenkins goes to the [jenkins-pipeline {{SKILL}}](jenkins-pipeline.md).
6
+
7
+ ## Working loop
8
+ 1. Read `.gitlab-ci.yml` and every `include:` it pulls, then the merged result: the pipeline editor's **Full configuration** tab, or `glab ci config compile`.
9
+ 2. Lint before pushing: `glab ci lint`, or `POST /projects/:id/ci/lint` with `dry_run=true`. The dry run also evaluates `rules:` against a ref, which a plain syntax check does not.
10
+ 3. Push to a branch and read the created pipeline: which jobs exist, which were skipped, and why.
11
+
12
+ ## When a job runs: `rules:`
13
+ - Every condition is `rules:`. GitLab no longer actively develops the older keywords, and they cannot be combined with `rules:` in one job. <!-- banned: ok --> Neither `only:` nor `except:` appears in new or changed jobs; migrate a job you touch.
14
+ - Rules are checked in order and the first match wins: `- if: $CI_PIPELINE_SOURCE == "merge_request_event"`, `- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH`, `- changes: [src/**/*]`, then `- when: never` or a final default.
15
+ - Stop duplicate branch and merge-request pipelines with a top-level `workflow: rules:` (the `$CI_OPEN_MERGE_REQUESTS` pattern), not with per-job tricks.
16
+ - `changes:` compares against the previous push on a branch pipeline; compare against the target branch with `changes: { paths: [src/**/*], compare_to: refs/heads/main }`.
17
+ - `when: manual` in a rule gives a manual job; add `allow_failure: true` unless it must block the pipeline.
18
+
19
+ ## Order: stages and the `needs:` DAG
20
+ - `needs: [build]` starts a job as soon as `build` finishes, regardless of stage. `needs: []` starts it at once. Use it to put fast checks (lint, unit tests) first, ahead of slow stages.
21
+ - `needs:` also limits which artifacts are downloaded: `needs: [{ job: build, artifacts: true }]`. A job without `needs:` downloads every artifact of every earlier stage.
22
+ - A needed job skipped by its rules makes the pipeline invalid; mark it `optional: true` when the dependency is conditional.
23
+
24
+ ## Reuse: `include:` and `extends:`
25
+ - `include:` brings shared files: `local:`, `project:` with a pinned `ref:` (a tag, never a moving branch), `component:` with a version, or `template:`.
26
+ - `extends: .base` merges a hidden job (a name starting with `.`) into this job. It merges hashes deeply and replaces arrays whole, so a job that extends one with `script:` and sets its own `script:` loses the base script.
27
+ - Prefer `extends:` to YAML anchors: anchors do not cross `include:` boundaries. `!reference [.setup, script]` reuses one key from another job.
28
+
29
+ ## Caching and artifacts
30
+ - `cache:` speeds up later runs and may be missing; `artifacts:` passes files to later jobs and is guaranteed. Never put a build output that another job needs in a cache.
31
+ - Key a cache on the lock file: `cache: { key: { files: [package-lock.json] }, paths: [.npm/] }`. Use `policy: pull` in jobs that only read it.
32
+ - Give artifacts an `expire_in:`. Publish test results with `artifacts: reports: junit:`, under `when: always`, so a failed run still shows them.
33
+
34
+ ## Variables and secrets
35
+ - Secrets live only in the project or group CI/CD settings: masked, protected, and in a scoped environment when they belong to one. Never in `.gitlab-ci.yml`, an included file or a commit.
36
+ - A protected variable is visible only to protected branches and tags. A merge-request job from a feature branch does not get it; that is the protection working, not a bug to remove.
37
+ - A masked value must meet GitLab's masking rules (length, characters); GitLab refuses to save a masked variable whose value fails them. Use a file-type variable for multi-line values such as keys.
38
+ - Masking is best-effort: it hides only the exact value. A transformed value (base64, a substring, a URL-encoded form) prints in clear.
39
+ - Do not `echo` a variable or run with `set -x` in a job that has secrets. `CI_DEBUG_TRACE` and `CI_DEBUG_SERVICES` dump every variable into the job log; never set them in a job that has secrets.
40
+ - Prefer OIDC (`id_tokens:`) to a long-lived cloud key when the target supports it.
41
+
42
+ ## Images and versions
43
+ - Pin `image:` and `services:` to a version tag or a digest, never `latest`. Pin tool versions in the job (`npm ci`, a fixed CLI version), so a rerun next month runs the same thing.
44
+
45
+ ## Environments and deployments
46
+ - A deploy job sets `environment: { name: production, url: ... }`, and production deploys are guarded by protected environments with required approval, not by a rule alone.
47
+ - `resource_group: production` stops two deploys to one environment from running at once.
48
+ - Review apps: `environment: { name: review/$CI_COMMIT_REF_SLUG, on_stop: stop_review, auto_stop_in: 1 week }` with a matching `stop_review` job (`when: manual`, `action: stop`).
49
+
50
+ ## Done when
51
+ - The lint (with dry run) accepts the merged configuration, a real branch pipeline ran the expected jobs and skipped the others for the expected reason, and no job uses the older condition keywords.
@@ -0,0 +1,56 @@
1
+ # {{SKILL}}: jenkins-pipeline
2
+
3
+ > {{DESC_JENKINS_PIPELINE}}
4
+
5
+ **Trigger:** writing, changing or debugging a `Jenkinsfile` or a Jenkins shared library (`vars/`, `src/`, `resources/`): stages, agents, `when`, `parallel`, credentials, sandbox or script-approval errors, a `NotSerializableException`, or a JenkinsPipelineUnit test. GitLab CI goes to the [gitlab-ci {{SKILL}}](gitlab-ci.md).
6
+
7
+ ## Working loop
8
+ 1. Read the `Jenkinsfile`, the `@Library` lines it loads and the library's version pin, and the plugins it calls (`withCredentials`, `junit`, `stash`). A step from a plugin the controller lacks fails at run time, not at parse.
9
+ 2. Find the nearest existing stage or library step that does something similar and follow it.
10
+ 3. Validate the syntax before pushing: the controller's linter (`curl --user "$JENKINS_USER:$JENKINS_API_TOKEN" -X POST -F "jenkinsfile=<Jenkinsfile" $JENKINS_URL/pipeline-model-converter/validate`, the user and API token read from the credential store or a local secret, never typed into the command, or the `declarative-linter` CLI command), then the library's unit tests.
11
+ 4. Push to a branch and read the real build log. A green lint proves syntax, not behaviour.
12
+
13
+ ## Declarative first
14
+ - Write `pipeline { }` declarative. Use `script { }` only for logic declarative cannot express, and keep it short; move anything longer into a library step.
15
+ - Set `options { timeout(...); disableConcurrentBuilds(); buildDiscarder(logRotator(...)) }` on every pipeline. A build with no timeout can hold an executor forever.
16
+ - `agent none` at the top when stages need different agents; give each stage its own `agent` (label, `docker { image 'maven:3.9.9-eclipse-temurin-21' }`, or `kubernetes`). Pin the image tag.
17
+ - `post { always { junit ...; archiveArtifacts ... } failure { ... } }`: publish results in `always`, so a failed test run still shows its report.
18
+ - `when { branch 'main' }`, `when { changeRequest() }`, `when { changeset 'docs/**' }`, `when { expression { ... } }`. Add `beforeAgent true` so a skipped stage does not allocate an agent first.
19
+ - `parallel { stage('unit') {...} stage('lint') {...} }` for independent checks; add `failFast true` when one failure makes the others useless. Fast checks run first, as their own stage.
20
+
21
+ ## Credentials
22
+ - Secrets come only from the Jenkins credential store, through `environment { TOKEN = credentials('id') }` or `withCredentials([string(credentialsId: 'id', variable: 'TOKEN')]) { ... }`. Never a literal, never a parameter default.
23
+ - Pass a secret to the shell through the environment, in single quotes: `sh 'curl -H "Authorization: Bearer $TOKEN" ...'`. Groovy interpolation (`sh "... ${TOKEN}"`) writes the secret into the script text, so it shows in the process arguments (`ps`) of the agent; Jenkins warns about it. `sh` runs with `-x` by default, and log masking hides only the exact secret string, so a transformed value (base64, a substring) prints in clear.
24
+ - Never `echo` a credential or write it to a workspace file that gets archived.
25
+
26
+ ## Shared library layout
27
+ | Folder | Holds |
28
+ |---|---|
29
+ | `vars/<step>.groovy` | global steps: a `def call(Map args)` the Jenkinsfile calls as `step(...)`; an optional `vars/<step>.txt` documents it |
30
+ | `src/<package>/` | Groovy classes, imported with `import org.acme.Build` |
31
+ | `resources/` | non-Groovy files, read with `libraryResource 'org/acme/script.sh'` |
32
+
33
+ - Load it pinned: `@Library('acme-lib@v2.3.1') _`. A floating branch makes every build depend on whatever the library is today.
34
+ - A class in `src/` that runs pipeline steps takes the script context (`this`) in its constructor and calls `steps.sh(...)`; it has no `sh` of its own.
35
+ - Keep `vars/` steps thin: argument checks and a call into `src/`, which is where the tests point.
36
+
37
+ ## CPS and `@NonCPS`
38
+ - Pipeline Groovy runs CPS-transformed so it can survive a controller restart; every local variable alive across a step must be serialisable. A `Matcher`, an `Iterator` or a JSON slurper result held across `sh` throws `NotSerializableException`.
39
+ - Fix: move the computation into a `@NonCPS` method that takes plain values and returns plain values (String, List, Map). A `@NonCPS` method must not call a pipeline step (`sh`, `echo`, `node`); it runs outside CPS and the step misbehaves.
40
+ - Prefer `readJSON` / `readYaml` (Pipeline Utility Steps) to `JsonSlurper`; they return serialisable maps.
41
+ - `sort` with a closure comparator gives wrong results under CPS: sort inside a `@NonCPS` method. `each` and `collect` closures work.
42
+
43
+ ## Sandbox and script approval
44
+ - A Jenkinsfile runs in the Groovy sandbox. `RejectedAccessException: Scripts not permitted to use method ...` means the call needs approval.
45
+ - Do not ask for a broad approval (`java.lang.Runtime`, `getClass`, `staticMethod ... exec`) to get green. Rewrite with a pipeline step or move the code into a trusted shared library that an admin configured as global and reviewed.
46
+ - Code in a trusted global library runs outside the sandbox; review it as privileged code.
47
+
48
+ ## Testing with JenkinsPipelineUnit
49
+ - Test library steps and Jenkinsfiles with `com.lesfurets:jenkins-pipeline-unit` on JUnit, extending `BasePipelineTest`.
50
+ - In `setUp()`: `super.setUp()`, build the library with `library().name('acme-lib').retriever(localSource('build/libs/')).targetPath('<notNeeded>').defaultVersion('master').build()` (`localSource` reads `<dir>/<name>@<version>`), pass it to `helper.registerSharedLibrary(...)`, and add `helper.registerAllowedMethod('sh', [Map]) { m -> ... }` for each step the code calls.
51
+ - Assert on what a caller sees: `helper.callStack` holds each step call with its arguments, and `assertJobStatusSuccess()` / `assertJobStatusFailure()` the result. Use `printCallStack()` while writing the test, not as the assertion.
52
+ - Every branch of a `when` or an `if` in a library step gets a case: one that runs it and one that skips it.
53
+ - `BasePipelineTest` does not run CPS. The experimental `BasePipelineTestCPS` checks serialisability at each step and catches most `NotSerializableException`s early, but its serialisation is not Jenkins's own: a real build still has the last word.
54
+
55
+ ## Done when
56
+ - The linter accepts the file, the library tests pass, and a real branch build ran the changed stages, read from its log; no credential appears in that log.
@@ -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, 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 (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.
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.
@@ -37,8 +37,8 @@ The minimum roster per task type. The crew lead chooses the crew from the whole
37
37
 
38
38
  | Host | Crew lead runs in the background | Crew lead can dispatch the crew | Shape |
39
39
  |---|---|---|---|
40
- | Claude Code | yes — a subagent started from the main conversation runs in the background by default | yes — subagents nest up to three layers by default (`CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH`), and a background subagent keeps the `Agent` tool | crew lead → crew subagents. Not the `Workflow` tool: it refuses without the user's opt-in for that task, and the mode is not one |
41
- | OpenCode | the `task` tool starts a child session; whether the parent's turn waits is unverified | unverified — `permission.task` decides which subagents an agent may start | crew lead → crew subagents where it holds `task`; else roles in turn. A saved `workflow` script (no opt-in needed) may stand in for the crew lead |
40
+ | Claude Code | yes — a subagent started from the main conversation runs in the background by default | yes — the install caps nesting at two layers (`env.CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH = "2"`; Claude Code allows three by default), and a background subagent keeps the `Agent` tool | crew lead → crew subagents. Not the `Workflow` tool: it refuses without the user's opt-in for that task, and the mode is not one |
41
+ | OpenCode | the `task` tool starts a child session; whether the parent's turn waits is unverified | unverified — `permission.task` decides which subagents an agent may start; the install caps nesting at two (`subagent_depth: 2`) | crew lead → crew subagents where it holds `task`; else roles in turn. A saved `workflow` script (no opt-in needed) may stand in for the crew lead |
42
42
  | OpenClaude | expected as Claude Code (it reads Claude's subagent dialect); unverified | unverified | as Claude Code; else roles in turn |
43
43
  | Bob | unverified — Bob reads Claude's subagent dialect | unverified | crew lead plays the roles in turn |
44
44
 
@@ -9,7 +9,8 @@
9
9
  rule") or a durable fact ("note that…", "keep in mind…"). Also fires when a
10
10
  `feedback` {{MEMORY}} lesson keeps recurring and deserves promotion, or when
11
11
  `user-rules.md` needs review — a trial rule past its date, a stale rule, a bloated
12
- set. Nothing reaches `user-rules.md` or {{MEMORY}} except through here ({{DOCTRINE:persist-insight}}).
12
+ set. Nothing reaches `user-rules.md` except through here, with the user's consent; a fact you
13
+ write to {{MEMORY}} on your own still follows Branch A ({{DOCTRINE:persist-insight}}).
13
14
  It also tends the {{MEMORY}} set as a whole — run the **consolidation flow**, not the
14
15
  fork — when the index outgrows one useful read (~40 lines) or holds duplicate,
15
16
  contradictory or stale entries (a file, flag or command that no longer exists), after
@@ -22,26 +23,31 @@ Pending section decides the same items by the same steps; a user who decides the
22
23
  ## Procedure
23
24
 
24
25
  ### 0 — The fork
25
- Ask first, always: **a standing rule, or a fact to remember?** Never infer it. The
26
- two stores bind differently and the choice belongs to the user. If they hesitate,
27
- draw the line in one sentence: a rule changes how you *act* and binds every future
28
- session; a memory records something *true* that would otherwise be lost or
29
- re-derived. Then take exactly one branch.
26
+ Sort it first: **a standing rule, or a fact to remember?** The line, in one sentence: a
27
+ rule changes how you *act* and binds every future session; a memory records something
28
+ *true* that would otherwise be lost or re-derived. A fact is yours to write, with no
29
+ prompt — the user sees every memory afterwards in the web console. A rule is the user's
30
+ call. **A memory phrased as an instruction to later sessions is a standing rule**: "always…",
31
+ "never…", "from now on…", or one that would carry `force: constraint` goes to Branch B, with
32
+ the user's consent, never into {{MEMORY}} as a fact. When the user's own words leave open
33
+ whether they want a rule, ask; never file a rule as a fact because a fact needs no consent.
34
+ Then take exactly one branch.
30
35
 
31
36
  ### Branch A — a fact to remember
32
37
  1. Search {{MEMORY}} for a file that already covers it. If one exists, merge into it —
33
38
  keep what is still true, add or correct the rest — never mint a twin. If the new
34
39
  fact proves the old one wrong, archive the old one (move it into `archive/`).
35
- 2. Ask which **binding force** the fact carries, in plain words, not jargon:
36
- *imposed by you, not mine to relax* (`constraint`) · *a choice taken among real
37
- alternatives* (`choice`) · *a stance I hold until evidence overturns it*
38
- (`conviction`) · *a constraint you deliberately relaxed* (`tempered`).
39
- 3. Infer the `type` (`user` | `feedback` | `project` | `reference`), draft the file
40
- per the {{MEMORY}} convention, and **show the exact content, frontmatter
41
- included** — so a wrong inference is visible before it is written, not after.
42
- 4. On the user's word, write the file and rebuild the index
40
+ 2. Add a **binding force** only when the conversation shows one: *a choice taken among
41
+ real alternatives* (`choice`) · *a stance held until evidence overturns it*
42
+ (`conviction`) · *a constraint the user deliberately relaxed* (`tempered`). A plain
43
+ fact carries none. A fact that needs `constraint` is a rule: back to the fork, Branch B.
44
+ 3. Infer the `type` (`user` | `feedback` | `project` | `reference`) and draft the file
45
+ per the {{MEMORY}} convention.
46
+ 4. Write the file, with no prompt, and rebuild the index
43
47
  (`geneseed learn --consolidate --memory <the {{PATH_MEMORY}}/ dir's path>`) so its line
44
- lands in `topics/<topic>.md` and the `MEMORY.md` map recounts.
48
+ lands in `topics/<topic>.md` and the `MEMORY.md` map recounts. Then say in one line
49
+ what you wrote and where, so a wrong inference is visible at once; the web console
50
+ shows it to the user later too.
45
51
 
46
52
  ### Branch B — a standing rule
47
53
  1. **Triage.** A rule earns its place only if it is all three of: *standing
@@ -99,7 +105,7 @@ re-derived. Then take exactly one branch.
99
105
  merges or prunes — every rule is loaded every session, and a bloated set dilutes the
100
106
  rules that matter.
101
107
 
102
- The asymmetry is deliberate: Branch A costs one question, Branch B costs several.
108
+ The asymmetry is deliberate: Branch A costs no question, Branch B costs several.
103
109
  The price is the safeguard — make remembering cheap and legislating expensive, or
104
110
  the user picks "rule" out of impatience and the set inflates.
105
111
 
@@ -118,8 +124,8 @@ adoption. Two more cases are due at any time:
118
124
  **Approval flow** → read [rule/approve.md](rule/approve.md) and follow it.
119
125
 
120
126
  ## Done when
121
- - For a rule or memory: the fork was put to the user, and then either a {{MEMORY}} file exists carrying its
122
- `force`, its `type` and its index line — or a rule stands in the right
127
+ - For a rule or memory: the fork was sorted, and then either a {{MEMORY}} file exists carrying its
128
+ `type`, any `force` the conversation showed and its index line, reported in one line — or a rule stands in the right
123
129
  `user-rules.md`, having survived reformulation, its own counter-example and the
124
130
  {{LAWS}}, consented to explicitly, with any promoted source memory archived. The
125
131
  {{ONTOLOGY}}, {{LAWS}} and {{DOCTRINES}} files are untouched either way.
@@ -17,7 +17,23 @@ apparatus, so every step ends in the user's assent ({{LAW:one-intent-one-act}},
17
17
  a trigger phrase, a done-when), not a new file — in an installed harness, a
18
18
  shipped {{SKILL}} takes that edit in its notes file, since a rebuild overwrites it.
19
19
  Name the skill by its domain, not the situation that prompted it.
20
- 2. **Write the trigger first, then the procedure.** Start from
20
+ 2. **Probe a note before folding it** (a skill note or an agent note). Notes are
21
+ written freely, so a note is a claim until a contrasted run supports it. Pick one
22
+ past task in the note's `situation:` (or, without one, the circumstance its `seen:`
23
+ names) whose original ask text still exists: an issue, or a request in a transcript.
24
+ Run it as two dispatched {{AGENTS}} (two sessions where the host has none), each
25
+ from the pre-fix revision in its own throwaway worktree, which isolates only the
26
+ code. The brief states each arm's note state: A gets the rendered file and the order
27
+ to read no notes file; B gets the rendered file with that one note inlined. Never
28
+ move or edit the notes file. Then run the [fresh-eyes {{SKILL}}](fresh-eyes.md) on
29
+ the verbatim ask, with the note withheld. It derives and freezes ONE rubric
30
+ (its step 4), and one validator rules both deliverables, labelled X and Y in random
31
+ order; two validators need the same frozen list. B wins when it passes a criterion A
32
+ fails, or shows a stated process gain on that rubric (fewer steps, no wrong turn).
33
+ Fold only on a win, and state the observation. On a tie or a loss, the user decides
34
+ to keep or delete the note. The cost is two runs and a validator per note. Skip the
35
+ probe for a trivial wording fix: the user decides it directly.
36
+ 3. **Write the trigger first, then the procedure.** Start from
21
37
  `{{DIR_SKILLS}}/_template.md`. The purpose line says *what*; the **Trigger** line
22
38
  says *when*, in the words a user would actually say and the situations the model
23
39
  would actually meet — the emitted `description:` is purpose + trigger, and it is
@@ -33,12 +49,12 @@ apparatus, so every step ends in the user's assent ({{LAW:one-intent-one-act}},
33
49
  text, and the quoting skill silently drops out of the model's catalogue.
34
50
  A name the host already owns as a built-in command (Claude Code ships
35
51
  `security-review`, `code-review`, `simplify`, `init`) is shadowed — pick another.
36
- 3. **Test the trigger against its neighbours.** For three real asks the skill should
52
+ 4. **Test the trigger against its neighbours.** For three real asks the skill should
37
53
  catch and two it should not, decide from the descriptions alone which skill fires.
38
54
  A wrong pick is a trigger to sharpen — or a sign two skills should be one. A trigger
39
55
  that needs a "not this, use that" clause to be safe is a trigger with a fuzzy edge;
40
56
  fix the edge rather than adding the clause.
41
- 4. **Register it where the host expects.** In an *installed* harness: the file under
57
+ 5. **Register it where the host expects.** In an *installed* harness: the file under
42
58
  `{{DIR_SKILLS}}/`, one row in AGENT.md §4's table, then `geneseed doctor` — it fails
43
59
  if the table and the files disagree. In the *Geneseed source repo* the cost is the
44
60
  full satellite set (`docs/extending.md` §3): the file, the §4 row, `DESC_<NAME>` in
@@ -46,14 +62,14 @@ apparatus, so every step ends in the user's assent ({{LAW:one-intent-one-act}},
46
62
  `doctor --all` and the suites. A skill that bundles a script or several files is a
47
63
  folder skill (`<name>/SKILL.md` + `VENDOR.md`), listed in `VENDORED_SKILL_DIRS`.
48
64
  Text adapted from outside gets a `src/upstreams.json` entry and a `CREDIT` token (docs/extending.md §3, in the Geneseed source repo).
49
- 5. **Merge or retire honestly.** When two skills fold into one: keep the best steps of
65
+ 6. **Merge or retire honestly.** When two skills fold into one: keep the best steps of
50
66
  each, rewrite the exit so the survivor routes to what the retired one led to, and
51
67
  remove the retired file and *every* reference to it (table row, sibling links, theme
52
68
  tokens, registry, README) — a dangling link is a build failure, a dangling trigger
53
69
  phrase is a silent miss. Retirement is deletion; get consent ({{LAW:deletion-is-deliberate}}).
54
- 6. **Verify by rendering.** Build or re-emit, open the emitted `SKILL.md`, read the
70
+ 7. **Verify by rendering.** Build or re-emit, open the emitted `SKILL.md`, read the
55
71
  frontmatter description as the host will, and confirm the body carries no
56
- unresolved token or dead link (`doctor`, or `geneseed-build --validate-only`).
72
+ unresolved token or dead link (`doctor`, or `geneseed validate`).
57
73
  Show the user the diff and the emitted description before it lands ({{LAW:one-intent-one-act}}).
58
74
 
59
75
  ## Done when
@@ -61,5 +77,7 @@ apparatus, so every step ends in the user's assent ({{LAW:one-intent-one-act}},
61
77
  domain; the emitted description names both purpose and trigger and wins its five
62
78
  test asks against the neighbours; every satellite the host or the repo demands is in
63
79
  place, `doctor` is green, and the user saw and accepted the change.
80
+ - A folded note won its contrasted probe with a stated observation, or was a
81
+ trivial wording fix the user accepted directly.
64
82
 
65
83
  <!-- INCLUDE: skills/_self-improvement.md -->
@@ -64,7 +64,8 @@ carries the script API — load it before writing one).
64
64
  `parallel()`. Pass `isolation: 'worktree'` to each agent that edits in parallel — both
65
65
  runtimes take it; read-only agents need none. After the fan-out, compare the changed
66
66
  files in plain script code (OpenCode hands them to you as `overlaps()`) — a file two
67
- agents touched goes to one merge agent, never to whoever wrote last.
67
+ agents touched goes to one merge agent, never to whoever wrote last. Agents that call one
68
+ rationed resource run in sequence, never in one `parallel()` ({{DOCTRINE:serialize-against-a-rationed-resource}}).
68
69
  5. **Pass the task as `args`, never baked in** — target paths, the motion, the question,
69
70
  any timestamp. Scripts stay deterministic: no wall clock, no randomness, nothing
70
71
  read from the environment that the next run would see differently, so a run is a
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "<one-line description: reviews a Spring Boot change with framework knowledge — layering, transactions, JPA, configuration, test slices>",
39
39
  "DESC_SPRING_SECURITY": "<one-line description: security pass over a Spring Security change — filter chain, method security, OAuth2/JWT, CORS/CSRF>",
40
40
  "DESC_KUBERNETES_SPECIALIST": "<one-line description: writes or reviews Kubernetes manifests, probes, resources and rollout for a Spring Boot service>",
41
- "DESC_DOCKER_EXPERT": "<one-line description: writes or reviews the Dockerfile and image build (layered or native) of a Spring Boot service>",
41
+ "DESC_DOCKER_EXPERT": "<one-line description: writes or reviews the Dockerfile and image build (layered or native) of a Spring Boot service; image and dev Compose file only, operating a Compose stack is the docker kit's compose-ops>",
42
42
  "DESC_DEVOPS_ENGINEER": "<one-line description: reviews or improves the build and delivery pipeline of a Spring Boot service on the CI already in use>",
43
43
  "DESC_REACT_ENGINEER": "<one-line description: implements a React feature in a Vite or webpack app, TypeScript or JavaScript, or makes a broken build or Jest run green>",
44
44
  "DESC_REACT_REVIEWER": "<one-line description: reviews a React change with framework knowledge — hooks, state, data fetching, accessibility, React security, tests>",
@@ -62,7 +62,9 @@
62
62
  "DESC_PARALLEL_AGENTS": "<one-line description: fan independent subtasks to concurrent subagents, then converge>",
63
63
  "DESC_PIPELINE": "<one-line description: spawn a small crew — analyst, developer, tester — to work a substantial task in isolation, merging only on mechanical proof (tests + lint green)>",
64
64
  "DESC_LOOP": "<one-line description: work a requirement in small scored iterations on a loop/* branch, stepping the geneseed loop state machine>",
65
+ "DESC_FACTORY": "<one-line description: carry one work item (request, document or issue) through a factory of bricks and loops to an open PR with green CI, stepping the geneseed factory state machine; never merges>",
65
66
  "DESC_BRICK_FORGE": "<one-line description: author or adapt a loop brick at project, global or shipped level, checked by geneseed loop check>",
67
+ "DESC_FACTORY_FORGE": "<one-line description: compose bricks and loops into a factory through an interview, write it at project or global level, check it with geneseed factory check, and offer brick-forge for a missing brick>",
66
68
  "DESC_DEVELOP": "<one-line description: drive a code change through cover-and-verify — smallest change, tests written for it, affected suite green, committed slice by slice>",
67
69
  "DESC_TEACH": "<one-line description: teach toward a result — crash course, decode confusing material, or a day-by-day path to a deadline — or test what the user knows with a drill, an explain-it-back check or a gap check>",
68
70
  "DESC_ADHD": "<one-line description: an opt-in output mode for a reader with ADHD — next action first, numbered steps, state restated, tangents held back; on until \"stop adhd mode\">",
@@ -76,7 +78,7 @@
76
78
  "DESC_RELEASE": "<one-line description: cut a release — bump, changelog, tag, kept in sync>",
77
79
  "DESC_INGEST": "<one-line description: convert a PDF/Office/web doc into clean markdown before reading>",
78
80
  "DESC_RESEARCH": "<one-line description: answer from the open web, verifying each claim against independent sources>",
79
- "DESC_RULE": "<one-line description: ask whether the user wants a standing rule or a durable memory, then write the memory or pressure-test the rule before adopting it in user-rules.md — and tend the memory set: merge, retire, promote>",
81
+ "DESC_RULE": "<one-line description: sort a standing rule from a durable memory, then write the memory or pressure-test the rule with the user before adopting it in user-rules.md — and tend the memory set: merge, retire, promote>",
80
82
  "DESC_PROFILE": "<one-line description: interview the user and draft or refresh PROFILE.md — who they are, how they work, how they like answers pitched; identity only, rules go to user-rules.md>",
81
83
  "DESC_GENESEED": "<one-line description: operate the deployed Geneseed harness — find installs and their settings, read files, status, doctor, diff, rebuild one setting on request — and make the user's own OpenCode colour theme>",
82
84
  "DESC_REVIEW_RESPONSE": "<one-line description: respond to review feedback — verify each point, apply or decline with reasons>",
@@ -120,11 +122,10 @@
120
122
  "DOC_CONSENT_BEFORE_PUSH": "<themed title for the process rule Consent Before Push>",
121
123
  "DOC_BOUND_THE_LOOP": "<themed title for the process rule Bound the Loop>",
122
124
  "DOC_ONE_WRITER_PER_FILE": "<themed title for the process rule One Writer Per File>",
123
- "DOC_CODES_THAT_PERSIST": "<themed title for the comms rule Codes That Persist>",
125
+ "DOC_CODES_THAT_PERSIST": "<themed title for the comms rule Codes and Markers>",
124
126
  "DOC_STRUCTURE_BESIDE_PROSE": "<themed title for the comms rule Structure Beside Prose>",
125
127
  "DOC_DECLARE_THE_JUDGMENT_CALLS": "<themed title for the comms rule Declare the Judgment Calls>",
126
128
  "DOC_SIMPLIFIED_TECHNICAL_ENGLISH": "<themed title for the comms rule Simplified Technical English>",
127
- "DOC_MARK_THE_ASK": "<themed title for the comms rule Mark the Ask>",
128
129
  "INTRO_DOC": "<themed intro: this file is the entry point an AI agent reads in this repo>",
129
130
  "INTRO_AGENTS": "<themed intro to the Agents section — delegate focused work to a specialist>",
130
131
  "INTRO_SKILLS": "<themed intro to the Skills section — run the written procedure before improvising>",
@@ -138,6 +139,7 @@
138
139
  "DOCTRINES": "<plural of DOCTRINE — the tier/section noun>",
139
140
  "AGENT": "<singular noun for an agent in this theme, e.g. Agent / Adept>",
140
141
  "AGENTS": "<plural of AGENT>",
142
+ "PRIMARY_AGENT": "<the main agent, the one every agent inherits from>",
141
143
  "SKILL": "<singular noun for a skill in this theme, e.g. Skill / Rite>",
142
144
  "SKILLS": "<plural of SKILL>",
143
145
  "MEMORY": "<noun for the memory store in this theme, e.g. Memory>",
@@ -160,6 +162,9 @@
160
162
  "DESC_SPRING_TESTING": "<one-line description: write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocking beans>",
161
163
  "DESC_REACT": "<one-line description: build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility>",
162
164
  "DESC_REACT_TESTING": "<one-line description: write or fix React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack>",
165
+ "DESC_JENKINS_PIPELINE": "<one-line description: write or fix a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit>",
166
+ "DESC_GITLAB_CI": "<one-line description: write or fix .gitlab-ci.yml — rules, needs DAG, include and extends, cache and artifacts, protected and masked variables, environments, CI lint>",
167
+ "DESC_COMPOSE_OPS": "<one-line description: write, review or run any Compose stack — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback; not a Spring Boot image build (docker-expert)>",
163
168
  "AGENT_COLORS": {
164
169
  "architect": "primary",
165
170
  "reviewer": "warning",
package/themes/biker.json CHANGED
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Walks a Spring Boot change over like a bike before a ride — layering, transactions, JPA, configuration, test slices.",
39
39
  "DESC_SPRING_SECURITY": "Goes over Spring Security changes bolt by bolt — filter chain, method security, OAuth2/JWT, CORS/CSRF.",
40
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.",
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
42
  "DESC_DEVOPS_ENGINEER": "Tunes the build and delivery pipeline of a Spring Boot service, on whatever CI the shop already runs.",
43
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
44
  "DESC_REACT_REVIEWER": "Walks a React change over like a bike before a ride — hooks, state, data fetching, accessibility, React security, tests.",
@@ -62,7 +62,9 @@
62
62
  "DESC_PARALLEL_AGENTS": "Send several riders on independent runs at once, then bring in what they gather.",
63
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
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.",
65
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.",
66
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.",
67
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.",
68
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\".",
@@ -76,7 +78,7 @@
76
78
  "DESC_RELEASE": "Cut a release — raise the version, write the roadbook entry, tag it, all three in sync.",
77
79
  "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
78
80
  "DESC_RESEARCH": "Find the answer out on the open road — search wide, then prove every claim against independent sources before you trust it.",
79
- "DESC_RULE": "Ask first — standing rule, or just something to remember? Then log the memory, or lean on the rule till it holds every corner before bolting it into user-rules.md — and keep the memory stash serviced: merge, scrap, promote.",
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.",
80
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.",
81
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.",
82
84
  "DESC_REVIEW_RESPONSE": "Take the notes straight — weigh each call, then act on it or push back with reasons.",
@@ -120,11 +122,10 @@
120
122
  "DOC_CONSENT_BEFORE_PUSH": "Crew's Nod Before You Push · Consent Before Push",
121
123
  "DOC_BOUND_THE_LOOP": "Set the Turnaround Before You Roll · Bound the Loop",
122
124
  "DOC_ONE_WRITER_PER_FILE": "One Wrench on Each Bolt · One Writer Per File",
123
- "DOC_CODES_THAT_PERSIST": "Tag Every Part on the Bench · Codes That Persist",
125
+ "DOC_CODES_THAT_PERSIST": "Tag Every Part on the Bench · Codes and Markers",
124
126
  "DOC_STRUCTURE_BESIDE_PROSE": "Draw the Route Only If It Turns · Structure Beside Prose",
125
127
  "DOC_DECLARE_THE_JUDGMENT_CALLS": "Own Up to Every Back Road Taken · Declare the Judgment Calls",
126
128
  "DOC_SIMPLIFIED_TECHNICAL_ENGLISH": "Short Words, Clear Signals · Simplified Technical English",
127
- "DOC_MARK_THE_ASK": "Flash the Lights When You Need an Answer · Mark the Ask",
128
129
  "INTRO_DOC": "This file is the route briefing a coding rider reads when it joins this repository.",
129
130
  "INTRO_AGENTS": "Send the right rider for focused work instead of riding the whole run yourself; each has one job and reports exactly what it did.",
130
131
  "INTRO_SKILLS": "A Skill is a move you've drilled for a recurring task. Run the matching move before you wing it.",
@@ -138,6 +139,7 @@
138
139
  "DOCTRINES": "Bylaws",
139
140
  "AGENT": "Rider",
140
141
  "AGENTS": "Riders",
142
+ "PRIMARY_AGENT": "Road Captain",
141
143
  "SKILL": "Move",
142
144
  "SKILLS": "Moves",
143
145
  "MEMORY": "Roadbook",
@@ -160,6 +162,9 @@
160
162
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the ride.",
161
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.",
162
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).",
163
168
  "AGENT_COLORS": {
164
169
  "architect": "primary",
165
170
  "reviewer": "warning",
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Runs the scrutineering on a Spring Boot change with framework know-how — layering, transactions, JPA, configuration, test slices.",
39
39
  "DESC_SPRING_SECURITY": "Checks the Spring Security barriers — filter chain, method security, OAuth2/JWT, CORS/CSRF — on any change that touches them.",
40
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.",
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
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
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
44
  "DESC_REACT_REVIEWER": "Runs the scrutineering on a React change with framework know-how — hooks, state, data fetching, accessibility, React security, tests.",
@@ -62,7 +62,9 @@
62
62
  "DESC_PARALLEL_AGENTS": "Send several drivers out on independent stints at once, then bring in what they gather.",
63
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
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.",
65
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.",
66
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.",
67
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.",
68
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\".",
@@ -76,7 +78,7 @@
76
78
  "DESC_RELEASE": "Cut a release — raise the version, write the race report, seal it with a tag, all three in sync.",
77
79
  "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
78
80
  "DESC_RESEARCH": "Hunt the answer across the open circuit — search wide, then prove every claim against independent sources before you call it.",
79
- "DESC_RULE": "Ask first — standing house rule, or just one for the notebook? Then log it, or run the rule through the replay from every angle before it goes on the board in user-rules.md — and tend the memory bank besides: merge, retire, promote.",
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.",
80
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.",
81
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.",
82
84
  "DESC_REVIEW_RESPONSE": "Take the scrutineer's notes straight — weigh each call, then act on it or push back with reasons.",
@@ -120,11 +122,10 @@
120
122
  "DOC_CONSENT_BEFORE_PUSH": "Team Orders Before You Push · Consent Before Push",
121
123
  "DOC_BOUND_THE_LOOP": "Call the Stint Length Before Lights Out · Bound the Loop",
122
124
  "DOC_ONE_WRITER_PER_FILE": "One Driver Per Car · One Writer Per File",
123
- "DOC_CODES_THAT_PERSIST": "Every Car Keeps Its Number · Codes That Persist",
125
+ "DOC_CODES_THAT_PERSIST": "Every Car Keeps Its Number · Codes and Markers",
124
126
  "DOC_STRUCTURE_BESIDE_PROSE": "Track Map Only When the Lines Matter · Structure Beside Prose",
125
127
  "DOC_DECLARE_THE_JUDGMENT_CALLS": "Replay the Calls Made Off the Radio · Declare the Judgment Calls",
126
128
  "DOC_SIMPLIFIED_TECHNICAL_ENGLISH": "Every Call Clear Over the Noise · Simplified Technical English",
127
- "DOC_MARK_THE_ASK": "Big Moment, Big Graphic · Mark the Ask",
128
129
  "INTRO_DOC": "This file is the race briefing a coding driver reads when it joins this repository.",
129
130
  "INTRO_AGENTS": "Put the right driver in the car for focused work instead of running the whole race yourself; each has one job and reports exactly what it did.",
130
131
  "INTRO_SKILLS": "A Skill is a rehearsed manoeuvre for a recurring task. Run the matching manoeuvre before you improvise.",
@@ -138,6 +139,7 @@
138
139
  "DOCTRINES": "Directives",
139
140
  "AGENT": "Driver",
140
141
  "AGENTS": "Drivers",
142
+ "PRIMARY_AGENT": "Lead Driver",
141
143
  "SKILL": "Manoeuvre",
142
144
  "SKILLS": "Manoeuvres",
143
145
  "MEMORY": "Telemetry",
@@ -160,6 +162,9 @@
160
162
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the lights go out.",
161
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.",
162
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).",
163
168
  "AGENT_COLORS": {
164
169
  "architect": "primary",
165
170
  "reviewer": "warning",
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Scans a Spring Boot change with framework-aware eyes — layering, transactions, JPA, configuration, test slices.",
39
39
  "DESC_SPRING_SECURITY": "Probes the ICE around Spring Security changes — filter chain, method security, OAuth2/JWT, CORS/CSRF.",
40
40
  "DESC_KUBERNETES_SPECIALIST": "Deploys and audits the Kubernetes manifests of a Spring Boot service — probes, resources, rollout — across the grid.",
41
- "DESC_DOCKER_EXPERT": "Packs the Docker image of a Spring Boot service, layered or native, lean for the net.",
41
+ "DESC_DOCKER_EXPERT": "Packs the Docker image of a Spring Boot service, layered or native, lean for the net. Image and dev Compose file only; operating a Compose stack is the docker kit's compose-ops.",
42
42
  "DESC_DEVOPS_ENGINEER": "Tunes the build and delivery pipeline of a Spring Boot service, on whatever CI the crew already runs.",
43
43
  "DESC_REACT_ENGINEER": "Jacks into a Vite or webpack app and ships a React feature, TypeScript or JavaScript, or makes a broken build or Jest run green.",
44
44
  "DESC_REACT_REVIEWER": "Scans a React change with framework-aware eyes — hooks, state, data fetching, accessibility, React security, tests.",
@@ -62,7 +62,9 @@
62
62
  "DESC_PARALLEL_AGENTS": "Fork independent tasks to concurrent threads, then merge the output.",
63
63
  "DESC_PIPELINE": "Spin up a small crew of daemons — scout, coder, tester — on their own fork, and only merge the run once the trace comes back clean.",
64
64
  "DESC_LOOP": "Run a requirement in small, scored cycles on a loop/* fork, the loop engine driving every jump.",
65
+ "DESC_FACTORY": "Route one work item through the factory to an open PR with green CI, the engine switching every stage. The merge stays yours.",
65
66
  "DESC_BRICK_FORGE": "Compile or patch a loop brick, then run it through geneseed loop check.",
67
+ "DESC_FACTORY_FORGE": "Wire bricks and loops into a factory, run it through geneseed factory check, and patch in brick-forge when a brick is missing.",
66
68
  "DESC_DEVELOP": "Drive the change through the loop — smallest edit, a test written to cover it, the touched rigs run green, committed slice by slice.",
67
69
  "DESC_TEACH": "Bring a user online, or probe what they know — a crash course, data decoded, a day-by-day route; or a drill, a run-back, a claimed mastery stress-tested.",
68
70
  "DESC_ADHD": "Format every reply for a reader with ADHD — next action first, numbered steps, state re-synced each turn, side quests held back, hard time estimates. On until \"stop adhd mode\".",
@@ -76,7 +78,7 @@
76
78
  "DESC_RELEASE": "Cut a release — bump the version, write the changelog, tag it, all in sync.",
77
79
  "DESC_INGEST": "Rip a PDF, Office, or web document to clean markdown before reading it.",
78
80
  "DESC_RESEARCH": "Pull the answer off the net — scan wide, then cross-check every claim against independent sources before you trust it.",
79
- "DESC_RULE": "Ask first — standing rule, or just something to keep on file? Then write the memory, or stress the rule till it holds in every sector before flashing it into user-rules.md — and defrag the datastore: merge, purge, promote.",
81
+ "DESC_RULE": "Sort it first — standing rule, or just something to keep on file? Then write the memory, or stress the rule till it holds in every sector before flashing it into user-rules.md — and defrag the datastore: merge, purge, promote.",
80
82
  "DESC_PROFILE": "Compile the user's ident into PROFILE.md — who they are, their rig, the bandwidth they want answers at; identity only, hard directives flash to user-rules.md.",
81
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 make the user's own OpenCode colour theme.",
82
84
  "DESC_REVIEW_RESPONSE": "Action the review clean — verify each flag, then patch it or push back with reasons.",
@@ -120,11 +122,10 @@
120
122
  "DOC_CONSENT_BEFORE_PUSH": "Authorize the Upload · Consent Before Push",
121
123
  "DOC_BOUND_THE_LOOP": "Set the Kill-Switch Before the Loop · Bound the Loop",
122
124
  "DOC_ONE_WRITER_PER_FILE": "One Deck Per Node · One Writer Per File",
123
- "DOC_CODES_THAT_PERSIST": "Every Node Keeps Its Handle · Codes That Persist",
125
+ "DOC_CODES_THAT_PERSIST": "Every Node Keeps Its Handle · Codes and Markers",
124
126
  "DOC_STRUCTURE_BESIDE_PROSE": "Trace the Wires, Skip the Chrome · Structure Beside Prose",
125
127
  "DOC_DECLARE_THE_JUDGMENT_CALLS": "Log Every Off-Grid Call · Declare the Judgment Calls",
126
128
  "DOC_SIMPLIFIED_TECHNICAL_ENGLISH": "Clean Signal, Zero Noise · Simplified Technical English",
127
- "DOC_MARK_THE_ASK": "Ping the Operator in Neon · Mark the Ask",
128
129
  "INTRO_DOC": "This file is the boot sequence a coding daemon reads when it jacks into this repository.",
129
130
  "INTRO_AGENTS": "Spin the right daemon for focused work instead of running the whole job on one thread; each has one function and returns a clean log of what it changed.",
130
131
  "INTRO_SKILLS": "A Skill is a proven routine for a recurring task. Run the matching routine before you freestyle.",
@@ -138,6 +139,7 @@
138
139
  "DOCTRINES": "Policies",
139
140
  "AGENT": "Daemon",
140
141
  "AGENTS": "Daemons",
142
+ "PRIMARY_AGENT": "Netrunner",
141
143
  "SKILL": "Program",
142
144
  "SKILLS": "Programs",
143
145
  "MEMORY": "Datastore",
@@ -160,6 +162,9 @@
160
162
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the run.",
161
163
  "DESC_REACT": "Build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility — and push it live.",
162
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 run.",
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 run.",
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 run.",
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 run. Not a Spring Boot image build (docker-expert).",
163
168
  "AGENT_COLORS": {
164
169
  "architect": "primary",
165
170
  "reviewer": "warning",