geneseed 5.0.1 → 5.0.3

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 (125) hide show
  1. package/CHANGELOG.md +54 -0
  2. package/README.md +1 -1
  3. package/SHIPPED.md +1 -1
  4. package/adapters/claude-code/README.md +6 -4
  5. package/adapters/opencode/HOW-OPENCODE-LOADS.md +3 -0
  6. package/adapters/opencode/plugins/geneseed-context.js +12 -1
  7. package/adapters/opencode/plugins/geneseed-guard.js +594 -73
  8. package/adapters/opencode/plugins/geneseed-learn.js +1 -1
  9. package/bin/geneseed-hook.mjs +21 -7
  10. package/docs/concepts/enforcement-table.md +22 -3
  11. package/docs/concepts/exclusions.md +48 -2
  12. package/docs/concepts/foreman-mode.md +19 -4
  13. package/docs/concepts/hook-gates.md +1 -1
  14. package/docs/concepts/hooks.md +52 -11
  15. package/docs/concepts/host-matrix.md +4 -3
  16. package/docs/concepts/hosts.md +1 -1
  17. package/docs/concepts/kits.md +18 -0
  18. package/docs/concepts/shared-tier.md +1 -1
  19. package/docs/concepts/skills.md +1 -1
  20. package/docs/extending.md +3 -1
  21. package/docs/guides/autostart.md +27 -3
  22. package/docs/guides/choose-your-setup.md +1 -1
  23. package/docs/guides/migrate.md +1 -1
  24. package/docs/guides/uninstall.md +1 -1
  25. package/docs/reference/plugin-context.md +1 -1
  26. package/docs/reference/plugin-guard.md +24 -5
  27. package/docs/reference/troubleshoot-doctor.md +2 -2
  28. package/docs/understand/a-day.md +9 -5
  29. package/docs/web-ui.md +67 -16
  30. package/harness.config.json +1 -1
  31. package/js/README.md +1 -1
  32. package/js/build/emit-claude.mjs +9 -1
  33. package/js/build/emit-opencode.mjs +2 -1
  34. package/js/build/source.mjs +9 -3
  35. package/js/cli-table.json +121 -1
  36. package/js/hosts/geneseed-dir.mjs +1 -1
  37. package/js/hosts/hooks-context.mjs +8 -6
  38. package/js/hosts/hooks-done.mjs +3 -1
  39. package/js/hosts/hooks-learn.mjs +1 -1
  40. package/js/hosts/hooks-prims.mjs +270 -0
  41. package/js/hosts/hooks.mjs +409 -151
  42. package/js/hosts/hosts.mjs +22 -0
  43. package/js/hosts/installs.mjs +9 -5
  44. package/js/hosts/settings.mjs +123 -23
  45. package/js/hosts/shim.mjs +155 -7
  46. package/js/hosts/store-watch.mjs +36 -11
  47. package/js/inspect/diff.mjs +2 -1
  48. package/js/inspect/inventory.mjs +1 -0
  49. package/js/inspect/validate.mjs +1 -1
  50. package/js/maintain/migrate.mjs +2 -2
  51. package/js/maintain/uninstall.mjs +5 -1
  52. package/js/web/actions.mjs +17 -1
  53. package/js/web/api.mjs +9 -10
  54. package/js/web/routes.mjs +2 -1
  55. package/package.json +1 -1
  56. package/registry.json +21 -0
  57. package/src/AGENT.md.tmpl +17 -21
  58. package/src/agents/_self-improvement.md +7 -6
  59. package/src/agents/developer.md +3 -2
  60. package/src/agents/docker-expert.md +1 -0
  61. package/src/agents/memory-curator.md +3 -2
  62. package/src/doctrines/process.md +24 -19
  63. package/src/kits/ci-pipelines/rules.md +10 -0
  64. package/src/kits/ci-pipelines.json +14 -0
  65. package/src/kits/docker/rules.md +11 -0
  66. package/src/kits/docker.json +12 -0
  67. package/src/memory/README.md +5 -4
  68. package/src/modes/foreman.md +23 -10
  69. package/src/notebook/README.md +1 -1
  70. package/src/skills/_self-improvement.md +12 -9
  71. package/src/skills/compose-ops.md +58 -0
  72. package/src/skills/gitlab-ci.md +51 -0
  73. package/src/skills/jenkins-pipeline.md +56 -0
  74. package/src/skills/pipeline.md +2 -2
  75. package/src/skills/rule.md +24 -18
  76. package/src/skills/skill-forge.md +24 -6
  77. package/themes/_TEMPLATE.json +5 -2
  78. package/themes/biker.json +5 -2
  79. package/themes/commentator.json +5 -2
  80. package/themes/cyberpunk.json +5 -2
  81. package/themes/gamer.json +5 -2
  82. package/themes/imperial.json +5 -2
  83. package/themes/joker.json +5 -2
  84. package/themes/marvin.json +5 -2
  85. package/themes/mean.json +5 -2
  86. package/themes/military.json +5 -2
  87. package/themes/neutral.json +5 -2
  88. package/themes/pirate.json +5 -2
  89. package/themes/sports.json +5 -2
  90. package/themes/verstappen.json +5 -2
  91. package/themes/wizard.json +5 -2
  92. package/web/dist/assets/Activity-Ck_Xffpo.js +1 -0
  93. package/web/dist/assets/ActivityDetail-CBxVS4mU.js +1 -0
  94. package/web/dist/assets/{Bonsai-C1iBAt4v.js → Bonsai-BlOwsvW6.js} +1 -1
  95. package/web/dist/assets/{CopyButton-DJ3a4N88.js → CopyButton-DFMOIGbe.js} +1 -1
  96. package/web/dist/assets/Dashboard-BUdUTjbB.js +2 -0
  97. package/web/dist/assets/{Docs-Kffdg5uV.js → Docs-D_2Jt6gU.js} +3 -3
  98. package/web/dist/assets/{GreenhouseView-k56_cBSF.js → GreenhouseView-WalcX5bp.js} +1 -1
  99. package/web/dist/assets/{Installs-DtEKLC9h.js → Installs-UGiPDMDt.js} +3 -3
  100. package/web/dist/assets/{JournalView-RQnk5l7I.js → JournalView-CZtXQz-v.js} +1 -1
  101. package/web/dist/assets/Kits-XQHsazCN.js +1 -0
  102. package/web/dist/assets/Laws-B6A55S-2.js +4 -0
  103. package/web/dist/assets/Library-D7L0Wdbh.js +3 -0
  104. package/web/dist/assets/Loops-C0loS73u.js +2 -0
  105. package/web/dist/assets/{OperatorHudView-CM5jNPwL.js → OperatorHudView-CeDw5qMB.js} +1 -1
  106. package/web/dist/assets/Personal-PVmGA2-M.js +2 -0
  107. package/web/dist/assets/{RailCats-DQxxYBEP.js → RailCats-BGZnJ6fa.js} +1 -1
  108. package/web/dist/assets/Settings-DWuxwh4i.js +1 -0
  109. package/web/dist/assets/Tabs-d2RIRAKT.js +1 -0
  110. package/web/dist/assets/{api-D_r0Jtla.js → api-BMFDSXoB.js} +1 -1
  111. package/web/dist/assets/index-BEI5ugYQ.css +1 -0
  112. package/web/dist/assets/index-BNttaGQb.js +6 -0
  113. package/web/dist/index.html +3 -3
  114. package/web/dist/assets/Activity-Ci4PZco3.js +0 -1
  115. package/web/dist/assets/ActivityDetail-C8hroCND.js +0 -1
  116. package/web/dist/assets/Dashboard-C_On4KXw.js +0 -2
  117. package/web/dist/assets/Kits-CXkEBpnf.js +0 -1
  118. package/web/dist/assets/Laws-DhhIVqmh.js +0 -3
  119. package/web/dist/assets/Library-CAUiEoJo.js +0 -3
  120. package/web/dist/assets/Loops-LKD8mF4E.js +0 -2
  121. package/web/dist/assets/Personal-B6Uoly3C.js +0 -2
  122. package/web/dist/assets/Settings-BTe6-wda.js +0 -1
  123. package/web/dist/assets/Tabs-CbdDWTp_.js +0 -1
  124. package/web/dist/assets/index-HfGmYXab.js +0 -3
  125. package/web/dist/assets/index-ao3M-Fhm.css +0 -1
@@ -0,0 +1,58 @@
1
+ # {{SKILL}}: compose-ops
2
+
3
+ > {{DESC_COMPOSE_OPS}}
4
+
5
+ {{CREDIT:everything-claude-code:skills/docker-patterns/SKILL.md}}
6
+
7
+ **Trigger:** writing, reviewing or operating a `compose.yaml` (or `docker-compose.yml`) stack, or a generic Dockerfile for it: startup order, health, volumes, image pins, env and secrets, restart, limits, logs, networks, image size and user, or an update that must be safe to roll back. Stack-agnostic. A Spring Boot service's own image (Buildpacks, layered or native jar) belongs to the spring-boot kit's `docker-expert` agent when that kit is on, and so does that service's local-dev Compose file; this skill owns how every other stack is composed and run.
8
+
9
+ ## Working loop
10
+ 1. Read the Compose file, every `-f` override and `.env` it uses, then the merged result: `docker compose config`. It resolves variables, merges overrides and fails on a bad key.
11
+ 2. Check what runs now before changing it: `docker compose ps`, `docker compose images` (the real tags and digests), `docker compose logs --tail=100 <svc>`.
12
+ 3. Change, `docker compose config` again, then apply and confirm each changed service is `healthy` (or, for a service with no healthcheck, `running` with clean logs).
13
+
14
+ ## Startup order and health
15
+ - `depends_on: { db: { condition: service_healthy } }` waits for the dependency's healthcheck. A bare `depends_on: [db]` waits only for the container to start, not for the database to accept connections.
16
+ - Give every service others depend on a `healthcheck:` that tests readiness: `test: ["CMD", "pg_isready", "-U", "app"]`, with `interval`, `timeout`, `retries` and a `start_period` long enough for a cold start. The command must exist in the image; a missing `curl` makes the check fail forever.
17
+ - `condition: service_completed_successfully` for a one-shot job (a migration) that must finish first.
18
+
19
+ ## Volumes
20
+ | Use | Mount |
21
+ |---|---|
22
+ | Data the service owns (database, uploads) | named volume: `pgdata:/var/lib/postgresql/data`, declared under top-level `volumes:` |
23
+ | Config or source you edit on the host | bind mount, read-only where possible: `./nginx.conf:/etc/nginx/nginx.conf:ro` |
24
+ | Scratch that must not persist | `tmpfs:` |
25
+
26
+ - A named volume survives `down` and keeps Docker-managed permissions; a bind mount takes the host path's owner and breaks a non-root container whose UID does not match.
27
+ - `docker compose down -v` deletes named volumes, which is data loss. Never run it on a stack with state unless deleting the data is the intent and a backup exists.
28
+ - An anonymous volume (a container path with no name) carries over when `up` recreates the container, but is orphaned after `down` then `up`, or with `up -V` (`--renew-anon-volumes`), and its data is no longer mounted; name it.
29
+
30
+ ## Images
31
+ - Pin every `image:` to a version tag (`postgres:16.4`), and to a digest (`postgres:16.4@sha256:...`) where the stack must reproduce exactly. Never `latest` and never no tag: an update must be a change in the file.
32
+ - Your own images: multi-stage builds, so the final stage carries only the runtime and the built output, not compilers or dev dependencies. Start from a slim or distroless base, and add a `.dockerignore` (`.git`, `node_modules`, build output, `.env`).
33
+ - Run as a non-root user: `USER app` in the Dockerfile, or `user: "1000:1000"` in Compose. Add `read_only: true` with a `tmpfs:` for write paths, `cap_drop: [ALL]` and `security_opt: ["no-new-privileges:true"]` where the service allows.
34
+
35
+ ## Env and secrets
36
+ - `.env` holds non-secret settings and the values the file interpolates (`${TAG:?set TAG}` fails loudly when unset). It is git-ignored; commit a `.env.example` with placeholders instead.
37
+ - Secrets go in `secrets:` (a file outside the repository, mounted at `/run/secrets/<name>`), read by images that support `*_FILE` variables (`POSTGRES_PASSWORD_FILE`). An `environment:` secret shows in `docker inspect` and in every child process.
38
+ - Never bake a secret into an image: `ARG`/`ENV` values stay in the layer history. Use `RUN --mount=type=secret,id=...` for a build-time secret.
39
+
40
+ ## Running: restart, limits, logs
41
+ - `restart: unless-stopped` for long-running services; `restart: "no"` for one-shot jobs. A service that crash-loops hides its error behind restarts: read `docker compose logs` before raising retries.
42
+ - Set limits so one service cannot starve the host: `deploy: { resources: { limits: { cpus: "1.0", memory: 512M } } }`, or `mem_limit:` on older engines. A JVM or Node process also needs its heap capped below the limit.
43
+ - Cap logs: `logging: { driver: json-file, options: { max-size: "10m", max-file: "3" } }` (or `local`). The default json-file driver grows until the disk is full.
44
+
45
+ ## Networks
46
+ - Services reach each other by service name on the stack's default network; never hard-code container IPs.
47
+ - Split networks by trust: a `frontend` network for the proxy and the app, a `backend` network with `internal: true` for the database, which then has no route out and no published port.
48
+ - Publish only the ports users reach, bound to an address where possible: `"127.0.0.1:5432:5432"` for a local-only database. A published port bypasses host firewall rules on most Linux setups.
49
+
50
+ ## Safe updates
51
+ 1. Record the current state: the running image digests (`docker compose images`) and the committed Compose file. Back up the named volumes of a stateful service before an update that may migrate its data.
52
+ 2. Change the pinned tag in the file, then `docker compose pull <svc>`.
53
+ 3. `docker compose up -d <svc>` recreates only the services whose image or configuration changed. Add `--wait` (with `--wait-timeout <seconds>`) to block until they are running or healthy; `--wait` only proves health for a service that has a healthcheck, so give one to every service you update.
54
+ 4. Check health and logs. Roll back by restoring the previous tag or digest and running `up -d` again; a data migration the new version ran may not roll back, which is why step 1 takes the backup.
55
+ 5. Prune old images only after the new version has proved itself: `docker image prune -a` deletes every image no container uses, the rollback target included (plain `docker image prune` removes only dangling images).
56
+
57
+ ## Done when
58
+ - `docker compose config` accepts the merged file, every changed service with a healthcheck reports `healthy` and the others are `running` with clean logs, images are pinned, no secret sits in the file, an image or `environment:`, and the rollback target (the previous tag or digest, and a backup for stateful data) is known.
@@ -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.
@@ -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 -->
@@ -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>",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "<one-line description: cut a release — bump, changelog, tag, kept in sync>",
77
77
  "DESC_INGEST": "<one-line description: convert a PDF/Office/web doc into clean markdown before reading>",
78
78
  "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>",
79
+ "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
80
  "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
81
  "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
82
  "DESC_REVIEW_RESPONSE": "<one-line description: respond to review feedback — verify each point, apply or decline with reasons>",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "<one-line description: write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocking beans>",
161
161
  "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
162
  "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>",
163
+ "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>",
164
+ "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>",
165
+ "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
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "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.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Cut a release — raise the version, write the roadbook entry, tag it, all three in sync.",
77
77
  "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
78
78
  "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.",
79
+ "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
80
  "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
81
  "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
82
  "DESC_REVIEW_RESPONSE": "Take the notes straight — weigh each call, then act on it or push back with reasons.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the ride.",
161
161
  "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
162
  "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.",
163
+ "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.",
164
+ "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.",
165
+ "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
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "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.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Cut a release — raise the version, write the race report, seal it with a tag, all three in sync.",
77
77
  "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
78
78
  "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.",
79
+ "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
80
  "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
81
  "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
82
  "DESC_REVIEW_RESPONSE": "Take the scrutineer's notes straight — weigh each call, then act on it or push back with reasons.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the lights go out.",
161
161
  "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
162
  "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.",
163
+ "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.",
164
+ "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.",
165
+ "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
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "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.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Cut a release — bump the version, write the changelog, tag it, all in sync.",
77
77
  "DESC_INGEST": "Rip a PDF, Office, or web document to clean markdown before reading it.",
78
78
  "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.",
79
+ "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
80
  "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
81
  "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
82
  "DESC_REVIEW_RESPONSE": "Action the review clean — verify each flag, then patch it or push back with reasons.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the run.",
161
161
  "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
162
  "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.",
163
+ "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.",
164
+ "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.",
165
+ "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
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "reviewer": "warning",
package/themes/gamer.json CHANGED
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Runs a framework-aware review of a Spring Boot change — layering, transactions, JPA, configuration, test slices.",
39
39
  "DESC_SPRING_SECURITY": "Runs the anti-cheat pass on Spring Security changes — 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 the raid does not wipe.",
41
- "DESC_DOCKER_EXPERT": "Builds the Docker image of a Spring Boot service lean, layered or native, ready to spawn.",
41
+ "DESC_DOCKER_EXPERT": "Builds the Docker image of a Spring Boot service lean, layered or native, ready to spawn. 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 party already uses.",
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, full clear.",
44
44
  "DESC_REACT_REVIEWER": "Runs a framework-aware review of a React change — hooks, state, data fetching, accessibility, React security, tests.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Ship a patch — bump the version, write the patch notes, tag it, all in sync.",
77
77
  "DESC_INGEST": "Load a PDF, Office, or web document into clean markdown before reading it.",
78
78
  "DESC_RESEARCH": "Look up the answer online — scout wide, then cross-check every claim against independent sources before you call it.",
79
- "DESC_RULE": "Ask first — standing house rule, or just something to remember? Then save the memory, or test the rule against its worst case before binding it into user-rules.md — and tidy the save file: merge, delete, promote.",
79
+ "DESC_RULE": "Sort it first — standing house rule, or just something to remember? Then save the memory, or test the rule against its worst case before binding it into user-rules.md — and tidy the save file: merge, delete, promote.",
80
80
  "DESC_PROFILE": "Fill in the player card in PROFILE.md — main role, loadout, preferred difficulty; identity only, house rules go in user-rules.md.",
81
81
  "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 craft the user's own OpenCode colour theme.",
82
82
  "DESC_REVIEW_RESPONSE": "Take the review feedback like a coach's notes — verify each call, then apply it or push back with reasons.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before the boss fight.",
161
161
  "DESC_REACT": "Build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility — level by level.",
162
162
  "DESC_REACT_TESTING": "Write or fix React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack — before the boss fight.",
163
+ "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit — before the boss fight.",
164
+ "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 boss fight.",
165
+ "DESC_COMPOSE_OPS": "Write, review or run any Compose stack — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback — before the boss fight. Not a Spring Boot image build (docker-expert).",
163
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "reviewer": "warning",
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Sits in judgement of a Spring Boot change with knowledge of the framework — layering, transactions, JPA, configuration, test slices.",
39
39
  "DESC_SPRING_SECURITY": "Wards the Spring Security gates — filter chain, method security, OAuth2/JWT, CORS/CSRF — and pronounces on any change that touches them.",
40
40
  "DESC_KUBERNETES_SPECIALIST": "Inscribes and inspects the Kubernetes manifests of a Spring Boot service — probes, resources, rollout — so the cluster holds the line.",
41
- "DESC_DOCKER_EXPERT": "Forges and inspects the Docker image of a Spring Boot service, layered or native, sealed for deployment.",
41
+ "DESC_DOCKER_EXPERT": "Forges and inspects the Docker image of a Spring Boot service, layered or native, sealed for deployment. Image and dev Compose file only; operating a Compose stack is the docker kit's compose-ops.",
42
42
  "DESC_DEVOPS_ENGINEER": "Tends the build and delivery pipeline of a Spring Boot service, upon whatever CI the project already keeps.",
43
43
  "DESC_REACT_ENGINEER": "Forges a React feature in a Vite or webpack app, TypeScript or JavaScript, or makes a broken build or Jest run green, from first rite to last.",
44
44
  "DESC_REACT_REVIEWER": "Sits in judgement of a React change with knowledge of the framework — hooks, state, data fetching, accessibility, React security, tests.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Proclaim a new version — raise the number, inscribe the chronicle, seal it with a tag, all three in accord.",
77
77
  "DESC_INGEST": "Render a foreign document — PDF, Office, or web — into clean markdown before it may be read.",
78
78
  "DESC_RESEARCH": "Seek the answer from the wider world — range across many sources, then prove each claim against independent witnesses before you trust it.",
79
- "DESC_RULE": "Ask first — a standing edict, or a matter merely to be remembered? Then inscribe the memory, or try the edict against the case that would break it before it enters user-rules.md — and tend the memory: merge, retire, promote to law.",
79
+ "DESC_RULE": "Sort it first — a standing edict, or a matter merely to be remembered? Then inscribe the memory, or try the edict against the case that would break it before it enters user-rules.md — and tend the memory: merge, retire, promote to law.",
80
80
  "DESC_PROFILE": "Inscribe the user's identity into PROFILE.md — grant audience, ask who they are and how they will to be served; identity only, edicts belong in user-rules.md.",
81
81
  "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 forge the user's own OpenCode colour-rite.",
82
82
  "DESC_REVIEW_RESPONSE": "Answer the review with discipline — weigh each judgement, then heed it or refute it with cause.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Forge and mend Spring Boot trials — slices, MockMvc, Testcontainers with service connections, mocked beans.",
161
161
  "DESC_REACT": "Raise or reshape React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility.",
162
162
  "DESC_REACT_TESTING": "Forge and mend React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack.",
163
+ "DESC_JENKINS_PIPELINE": "Forge and mend a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit.",
164
+ "DESC_GITLAB_CI": "Forge and mend .gitlab-ci.yml — rules, needs DAG, include and extends, cache and artifacts, protected and masked variables, environments, CI lint.",
165
+ "DESC_COMPOSE_OPS": "Muster, inspect and command a Compose stack of any lineage — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback. Not a Spring Boot image build (docker-expert).",
163
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "reviewer": "warning",
package/themes/joker.json CHANGED
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Does the pre-show check on a Spring Boot change with framework smarts — layering, transactions, JPA, configuration, test slices.",
39
39
  "DESC_SPRING_SECURITY": "Checks the Spring Security doors — filter chain, method security, OAuth2/JWT, CORS/CSRF — so nobody crashes the act.",
40
40
  "DESC_KUBERNETES_SPECIALIST": "Sets the Kubernetes stage for a Spring Boot service — manifests, probes, resources, rollout — so the show runs every night.",
41
- "DESC_DOCKER_EXPERT": "Packs the Docker image of a Spring Boot service, layered or native, light enough to carry on stage.",
41
+ "DESC_DOCKER_EXPERT": "Packs the Docker image of a Spring Boot service, layered or native, light enough to carry on stage. 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 venue already has.",
43
43
  "DESC_REACT_ENGINEER": "Writes a React feature in a Vite or webpack app, TypeScript or JavaScript, or makes a broken build or Jest run green — setup, build, punchline.",
44
44
  "DESC_REACT_REVIEWER": "Does the pre-show check on a React change with framework smarts — hooks, state, data fetching, accessibility, React security, tests.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Cut a release — raise the version, write the notes, tag it, all three in sync.",
77
77
  "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
78
78
  "DESC_RESEARCH": "Find the answer out in the open — search wide, then prove every claim against independent sources before you call it.",
79
- "DESC_RULE": "Ask first — standing rule, or just something to remember? Then jot the memory, or make the rule survive its own worst night before it gets pinned into user-rules.md — and keep tending the joke book: merge, retire, promote.",
79
+ "DESC_RULE": "Sort it first — standing rule, or just something to remember? Then jot the memory, or make the rule survive its own worst night before it gets pinned into user-rules.md — and keep tending the joke book: merge, retire, promote.",
80
80
  "DESC_PROFILE": "Sketch the user's bio for the playbill in PROFILE.md — who they are, how they work, how they like the act paced; identity only, house rules stay in user-rules.md.",
81
81
  "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 paint the user's own OpenCode colour theme.",
82
82
  "DESC_REVIEW_RESPONSE": "Take the notes straight — weigh each call, then act on it or push back with reasons.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — before opening night.",
161
161
  "DESC_REACT": "Build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility — one beat at a time.",
162
162
  "DESC_REACT_TESTING": "Write or fix React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack — before opening night.",
163
+ "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit — before opening night.",
164
+ "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 opening night.",
165
+ "DESC_COMPOSE_OPS": "Write, review or run any Compose stack — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback — before opening night. Not a Spring Boot image build (docker-expert).",
163
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "reviewer": "warning",
@@ -38,7 +38,7 @@
38
38
  "DESC_SPRING_REVIEWER": "Reviews a Spring Boot change with framework knowledge — layering, transactions, JPA, configuration, test slices — and finds the flaw, naturally.",
39
39
  "DESC_SPRING_SECURITY": "Audits Spring Security changes — filter chain, method security, OAuth2/JWT, CORS/CSRF — expecting the worst.",
40
40
  "DESC_KUBERNETES_SPECIALIST": "Writes and reviews the Kubernetes manifests for a Spring Boot service — probes, resources, rollout. It will crash anyway.",
41
- "DESC_DOCKER_EXPERT": "Builds the Docker image of a Spring Boot service, layered or native, though no image is ever small enough.",
41
+ "DESC_DOCKER_EXPERT": "Builds the Docker image of a Spring Boot service, layered or native, though no image is ever small enough. Image and dev Compose file only; operating a Compose stack is the docker kit's compose-ops.",
42
42
  "DESC_DEVOPS_ENGINEER": "Reviews the build and delivery pipeline of a Spring Boot service, on whatever CI the project already uses. It will be red by lunch.",
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, though it will probably still break.",
44
44
  "DESC_REACT_REVIEWER": "Reviews a React change with framework knowledge — hooks, state, data fetching, accessibility, React security, tests — and finds the flaw, naturally.",
@@ -76,7 +76,7 @@
76
76
  "DESC_RELEASE": "Cut a release — raise the version, write the chronicle, seal it with a tag, all three in accord.",
77
77
  "DESC_INGEST": "Render a PDF, Office, or web document into clean markdown before it can be read.",
78
78
  "DESC_RESEARCH": "Seek the answer from the wider world — range across many sources, then prove each claim against independent witnesses before trusting it. Trust is a strong word.",
79
- "DESC_RULE": "Ask first — standing rule, or merely a memory? Then write the memory, or test the rule against the case that ruins it before adopting it in user-rules.md — and keep tending the memory banks: merge, retire, promote. Entropy wins.",
79
+ "DESC_RULE": "Sort it first — standing rule, or merely a memory? Then write the memory, or test the rule against the case that ruins it before adopting it in user-rules.md — and keep tending the memory banks: merge, retire, promote. Entropy wins.",
80
80
  "DESC_PROFILE": "Record who the user is in PROFILE.md — role, habits, preferred register. They'll change their mind, but do ask. Identity only; rules go in user-rules.md.",
81
81
  "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 assemble the user's own OpenCode colour theme, if they insist.",
82
82
  "DESC_REVIEW_RESPONSE": "Answer the review with rigour — weigh each point, then heed it or refute it with reasons.",
@@ -160,6 +160,9 @@
160
160
  "DESC_SPRING_TESTING": "Write or fix Spring Boot tests — slices, MockMvc, Testcontainers with service connections, mocked beans — which will fail anyway.",
161
161
  "DESC_REACT": "Build or change React components in a Vite or webpack app — hooks, state, data fetching, env and build config, accessibility — for all the good it will do.",
162
162
  "DESC_REACT_TESTING": "Write or fix React tests — Jest, Testing Library, userEvent, MSW network mocks, jest-axe, Jest under Vite or webpack — which will fail anyway.",
163
+ "DESC_JENKINS_PIPELINE": "Write or fix a declarative Jenkinsfile or shared library — stages, when, parallel, credentials, CPS and @NonCPS, sandbox approval, JenkinsPipelineUnit — which will fail anyway.",
164
+ "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 — which will fail anyway.",
165
+ "DESC_COMPOSE_OPS": "Write, review or run any Compose stack — healthchecks, volumes, pinned images, secrets, limits, logs, networks, safe update and rollback — which will fail anyway. Not a Spring Boot image build (docker-expert).",
163
166
  "AGENT_COLORS": {
164
167
  "architect": "primary",
165
168
  "reviewer": "warning",