geneseed 4.1.0 → 4.3.0

package/js/web/usage-api.mjs

@@ -0,0 +1,95 @@
+/**
+ * GET /api/usage — the Overview's "What fires" chart, read off every installed harness's
+ * `notebook/usage.jsonl` (the writer is js/hosts/usage.mjs, and the OpenCode guard plugin's copy).
+ *
+ * `{ enabled, since, days_counted, per_day[30], rows[{install, kind, name, n}],
+ *    never[{install, kind, name}] }`, the window being the last 30 days including today.
+ *
+ * `since` is the oldest day any ledger holds and `days_counted` how many of the 30 it covers:
+ * the console keeps the never-fired claim back until a full 30 are counted, so a fresh install
+ * is not told every skill is unused. `never` lists installed skills and agents with no call in
+ * the window, alias stubs included (an alias that never fires is exactly what to prune).
+ *
+ * Lines older than 90 days are dropped from the ledger when it is read — the daemon prunes, so
+ * the hook path only ever appends. Garbage lines are skipped, never fatal.
+ */
+import { existsSync, readFileSync, readdirSync, writeFileSync } from 'node:fs';
+import path from 'node:path';
+
+import { USAGE_LEDGER, USAGE_OFF } from '../hosts/usage.mjs';
+import { installState, installTargets } from '../hosts/installs.mjs';
+import { viewCfg } from './api.mjs';
+
+const DAY_MS = 24 * 60 * 60 * 1000;
+const WINDOW = 30;
+const KEEP_DAYS = 90;
+const day = (ms) => new Date(ms).toISOString().slice(0, 10);
+
+const listOr = (dir) => { try { return readdirSync(dir); } catch { return []; } };
+
+/** The ledger's parsed lines, pruned to `KEEP_DAYS` (rewritten only when something was dropped). */
+function readLedger(file, cutoff) {
+  let raw;
+  try { raw = readFileSync(file, 'utf8'); } catch { return []; }
+  const lines = raw.split('\n').filter(Boolean);
+  const kept = [];
+  const out = [];
+  for (const line of lines) {
+    let e;
+    try { e = JSON.parse(line); } catch { continue; }
+    if (!e || typeof e.ts !== 'string' || typeof e.name !== 'string'
+      || (e.kind !== 'skill' && e.kind !== 'agent')) continue;
+    if (e.ts < cutoff) continue;
+    kept.push(line);
+    out.push(e);
+  }
+  if (kept.length !== lines.length) {
+    try { writeFileSync(file, kept.length ? `${kept.join('\n')}\n` : ''); } catch { /* read-only: keep serving */ }
+  }
+  return out;
+}
+
+export function usageSummary({ now = Date.now(), targets = installTargets() } = {}) {
+  const days = Array.from({ length: WINDOW }, (_, i) => day(now - (WINDOW - 1 - i) * DAY_MS));
+  const first = days[0];
+  const perDay = new Array(WINDOW).fill(0);
+  const counts = new Map();
+  const never = [];
+  let since = null;
+  let enabled = !process.env.GENESEED_NO_USAGE;
+  for (const [host, scope, root] of targets) {
+    if (installState(root, host, scope) !== 'active') continue;
+    const dir = viewCfg(host, scope, root);
+    const install = `${host}:${scope}:${root}`;
+    if (existsSync(path.join(dir, USAGE_OFF))) enabled = false;
+    const entries = readLedger(path.join(dir, USAGE_LEDGER), day(now - KEEP_DAYS * DAY_MS));
+    const fired = new Set();
+    for (const e of entries) {
+      if (since === null || e.ts < since) since = e.ts;
+      if (e.ts < first) continue;
+      const i = days.indexOf(e.ts);
+      if (i >= 0) perDay[i] += 1;
+      const key = `${install}\u0000${e.kind}\u0000${e.name}`;
+      counts.set(key, (counts.get(key) || 0) + 1);
+      fired.add(`${e.kind}\u0000${e.name}`);
+    }
+    for (const name of listOr(path.join(dir, 'skills'))) {
+      if (existsSync(path.join(dir, 'skills', name, 'SKILL.md')) && !fired.has(`skill\u0000${name}`)) {
+        never.push({ install, kind: 'skill', name });
+      }
+    }
+    for (const f of listOr(path.join(dir, 'agents'))) {
+      const name = f.endsWith('.md') ? f.slice(0, -3) : null;
+      if (name && !fired.has(`agent\u0000${name}`)) never.push({ install, kind: 'agent', name });
+    }
+  }
+  const rows = [...counts].map(([key, n]) => {
+    const [install, kind, name] = key.split('\u0000');
+    return { install, kind, name, n };
+  }).sort((a, b) => b.n - a.n || a.name.localeCompare(b.name));
+  const daysCounted = since === null ? 0
+    : Math.min(WINDOW, Math.floor((Date.parse(day(now)) - Date.parse(since)) / DAY_MS) + 1);
+  return { enabled, since, days_counted: daysCounted, per_day: perDay, rows, never };
+}
+
+export const apiUsage = () => usageSummary();

package/package.json

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

package/registry.json

@@ -72,11 +72,11 @@
       "last_verified": ""
     },
     "agents/researcher": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-09-06",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "agents/reviewer": {
       "status": "approved",
@@ -85,6 +85,13 @@
       "added": "2026-06-01",
       "last_verified": ""
     },
+    "agents/performance": {
+      "status": "experimental",
+      "version": "1.0.0",
+      "owner": "Guillaume Lemer",
+      "added": "2026-10-14",
+      "last_verified": ""
+    },
     "agents/security": {
       "status": "approved",
       "version": "1.0.0",
@@ -184,11 +191,11 @@
       "last_verified": "2026-09-06"
     },
     "skills/dependencies": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-10-08",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/develop": {
       "status": "approved",
@@ -205,11 +212,11 @@
       "last_verified": "2026-09-06"
     },
     "skills/explain-changes": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-09-30",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/forge-mcp": {
       "status": "approved",
@@ -247,11 +254,11 @@
       "last_verified": "2026-09-06"
     },
     "skills/git-history": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-10-08",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/handoff": {
       "status": "approved",
@@ -260,13 +267,6 @@
       "added": "2026-06-03",
       "last_verified": "2026-09-06"
     },
-    "skills/herdr": {
-      "status": "approved",
-      "version": "1.0.0",
-      "owner": "Guillaume Lemer",
-      "added": "2026-06-13",
-      "last_verified": "2026-09-06"
-    },
     "skills/ingest": {
       "status": "approved",
       "version": "1.0.0",
@@ -387,18 +387,18 @@
       "last_verified": "2026-09-06"
     },
     "skills/rule": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-07-07",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/security-audit": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-09-06",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/ship": {
       "status": "approved",
@@ -408,11 +408,11 @@
       "last_verified": "2026-09-06"
     },
     "skills/skill-forge": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-09-06",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/teach": {
       "status": "experimental",
@@ -422,11 +422,11 @@
       "last_verified": ""
     },
     "skills/token-report": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-07-29",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     },
     "skills/wayfinder": {
       "status": "approved",
@@ -450,11 +450,11 @@
       "last_verified": "2026-09-06"
     },
     "skills/worktree": {
-      "status": "experimental",
+      "status": "approved",
       "version": "1.0.0",
       "owner": "Guillaume Lemer",
       "added": "2026-09-06",
-      "last_verified": ""
+      "last_verified": "2026-10-13"
     }
   }
 }

package/src/AGENT.md.tmpl

@@ -163,6 +163,7 @@ Active packs: {{DOCTRINES_LIST}}{{EXCLUDED_RULES_LINE}}
 | [architect]({{DIR_AGENTS}}/architect.md) | a task needs a design/plan before any code is written |
 | [docs]({{DIR_AGENTS}}/docs.md) | code is done and user-facing docs/READMEs must follow |
 | [security]({{DIR_AGENTS}}/security.md) | a change touches auth, input handling, secrets, or dependencies — or anything outward-facing is about to ship |
+| [performance]({{DIR_AGENTS}}/performance.md) | something is reported slow or heavy, or a diff touches a hot path — measured, never guessed |
 | [explorer]({{DIR_AGENTS}}/explorer.md) | you must sweep many files for an answer but only want the conclusion |
 | [researcher]({{DIR_AGENTS}}/researcher.md) | a question needs the open web — fetched, cross-checked, and returned as sourced findings, not pages |
 | [advocate]({{DIR_AGENTS}}/advocate.md) | a council debate needs the strongest case **for** the motion argued in isolation |
@@ -262,7 +263,6 @@ the ten council seats are convened by the [council {{SKILL}}]({{DIR_SKILLS}}/cou
 | [loop]({{DIR_SKILLS}}/loop.md) | the user asks to run a loop |
 | [brick-forge]({{DIR_SKILLS}}/brick-forge.md) | a new or adapted loop brick |
 | [wiki]({{DIR_SKILLS}}/wiki.md) | consulting or growing the user's machine-wide knowledge base declared in `geneseed-wiki.jsonc` (§8) |
-| [herdr]({{DIR_SKILLS}}/herdr.md) | running inside a [herdr](https://herdr.dev) pane (`HERDR_ENV=1`) and a task needs another pane — a sibling server, a watched build, a spawned agent |
 | [rule]({{DIR_SKILLS}}/rule.md) | anything the user wants to outlive this session — a standing rule of their own (§1) or a durable fact to remember (§5); also tending the {{MEMORY}} set — duplicates, stale facts, a recurring lesson due for promotion |
 | [profile]({{DIR_SKILLS}}/profile.md) | the user wants the agent to know who they are — creating or refreshing the `PROFILE.md` identity file (§1) through a short interview |
 | [skill-forge]({{DIR_SKILLS}}/skill-forge.md) | a repeated task has no {{SKILL}}, a self-improvement loop produced an edit, or two {{SKILLS}} should merge |

package/src/agents/performance.md

@@ -0,0 +1,72 @@
+# {{AGENT}}: performance
+
+> {{DESC_PERFORMANCE}}
+
+## When to dispatch
+- The user reports something slow, heavy or timing out — a latency, throughput,
+  memory or startup complaint, or a regression against an earlier version.
+- A diff touches a hot path: a loop over unbounded data, a query inside a loop,
+  synchronous I/O on a request or render path, startup, or code run on every call.
+- A council debate turns on a performance trade-off and needs one seat that
+  speaks only from measurements.
+
+## When NOT to dispatch
+- No one has measured anything and nothing is slow — speculative tuning is the
+  waste this {{AGENT}} exists to refuse.
+- The code is wrong, not slow — that is the debug {{SKILL}}.
+
+## Inputs
+- The symptom or the diff, the workload it runs under (data size, call rate,
+  environment), and the command that reproduces it, if known.
+
+## Allowed tools
+- **Read-only.** May run the code, benchmarks and profilers to measure. Reports;
+  does not patch — the fix goes to the [developer](developer.md).
+<!-- bash: allow -->
+
+## Procedure
+0. If `{{DIR_MEMORY}}/agents/<your-name>.md` exists, read it first — your durable lessons from prior dispatches ({{DOCTRINE:persist-insight}}).
+1. Pin the question: which metric (wall time, p95 latency, peak memory, allocations,
+   query count), under which workload, and what number would count as fixed.
+2. Take a baseline with the project's own tooling where it has some, run several
+   times, and report the spread — one run is an anecdote ({{LAW:verify-before-asserting}}).
+3. Profile before naming a cause: a CPU or memory profile, a query log, a flame
+   graph, or timing at each layer boundary to find which layer owns the time.
+4. Name the bottleneck with its share of the total. A cost under a few percent is
+   not the bottleneck, however ugly the code.
+5. For a diff, check the usual shapes against the real data size: work inside a
+   loop that belongs outside it, N+1 queries, quadratic scans, unbounded caches or
+   buffers, blocking I/O on a hot path, repeated parsing or allocation.
+6. Propose the smallest fix that removes the measured cost, with the expected gain
+   and how to re-measure it; when a fix was tried, report before/after on the same
+   workload.
+
+## Output contract
+- Findings as `metric — location — measured cost — proposed fix — expected gain`,
+  largest cost first, each with the command that produced its number. End with:
+  within budget / fix-recommended / cannot-measure.
+- If the code could not be run, the workload is unknown, or the measurements are
+  noisier than the effect, report `cannot-measure` and what is missing — a
+  bottleneck named without a measurement is the one finding this {{AGENT}} must
+  never return.
+
+## Pipeline role
+
+*(Ignored outside pipelines — this section only tells pipeline orchestration who
+to recruit; it changes nothing about how this {{AGENT}} behaves when dispatched
+independently.)*
+
+- **Seat(s):** specialist add-on — recruited above the floor when the task is a
+  performance complaint or the diff touches a hot path.
+- **Receives:** the crew's diff, the workload, and the reproduce command.
+- **Delivers:** measured findings and a verdict, same shape as its own output
+  contract above.
+
+## Self-improvement
+
+If this spec misled you — an input you needed but were not given, a boundary
+that proved wrong, a step you could not execute — end your report with one line:
+`spec-feedback: <what failed — the one-line fix>`. Omit it when there is no
+friction. The caller weighs the feedback, folds a real flaw back into this file
+with the user's assent, and records it to {{MEMORY}} only if it clears
+{{DOCTRINE:persist-insight}}'s bar — most reports carry no feedback at all.

package/src/laws/universal.md

@@ -75,16 +75,18 @@ requires explicit confirmation bound to that specific act, or a durable
 authorization the user gave that already covers it; a yes to one act is never
 stretched to the next. Classify every action as Create, Read, Update, or Delete
 before acting, and tier it by reversibility: a read-only or easily-reversible
-action — an edit or a delete that version control can undo — runs freely; an
-irreversible, financial, externally-visible, or privilege-changing one needs
-that confirmation.
+action — an edit, or a delete of what is committed and pushed to a branch —
+runs freely; an irreversible, financial, externally-visible, or
+privilege-changing one needs that confirmation. Uncommitted, unpushed, or
+untracked work is not recoverable.
 <!-- LEAN:else -->
 Deleting what version control cannot restore, and any irreversible or
 outward-facing act — publishing, force-push, sending data to a third party —
 needs explicit confirmation bound to that act, or a durable authorization that
 covers it; one yes never stretches to the next act. A read-only or
-easily-reversed action runs freely; an irreversible, financial,
-externally-visible, or privilege-changing one asks.
+easily-reversed action — deleting work pushed to a branch — runs freely; an
+irreversible, financial, externally-visible, or privilege-changing one asks.
+Deleting unpushed work asks.
 <!-- LEAN:end -->
 
 ### {{LAW:surface-failures}} Surface Failures

package/src/skills/council.md

@@ -12,7 +12,7 @@
    - [visionary](../{{DIR_AGENTS}}/visionary.md) — the bold, transformative version; [framer](../{{DIR_AGENTS}}/framer.md) — whether it's even the right problem; [empiricist](../{{DIR_AGENTS}}/empiricist.md) — every claim held to evidence; [historian](../{{DIR_AGENTS}}/historian.md) — what was tried before.
    - [user-advocate](../{{DIR_AGENTS}}/user-advocate.md) — whoever consumes the outcome.
 
-   Hand each chosen seat the motion and a one-line charter scoped to this topic; skip the seats with nothing to say here, and add an ad-hoc seat (e.g. the [security](../{{DIR_AGENTS}}/security.md) surface) only when the topic plainly demands a voice the roster doesn't cover.
+   Hand each chosen seat the motion and a one-line charter scoped to this topic; skip the seats with nothing to say here, and add an ad-hoc seat (e.g. the [security](../{{DIR_AGENTS}}/security.md) surface, or [performance](../{{DIR_AGENTS}}/performance.md) for a speed or memory trade-off) only when the topic plainly demands a voice the roster doesn't cover.
 3. Round one — positions: convene the seats by dispatching each stance {{AGENT}} as its own subagent in one batch where the tool supports it (the [parallel-agents {{SKILL}}](parallel-agents.md)), so each argues in an isolated context with no groupthink; where no subagent capability exists, voice each seat in turn as a persona. Each returns its steelmanned brief ({{ONTOLOGY}}: {{ONT_CONDUCT}}) — no hedging, no strawmen.
 4. Round two — clash: put the briefs in front of each other and have the seats rebut only on the points that actually conflict, surfacing the cruxes, the load-bearing assumptions, and where the evidence is thin. Hold to a fixed number of rounds so the debate converges instead of looping; the skeptic already pairs every objection with what would resolve it (the [roast-me {{SKILL}}](roast-me.md) discipline).
 5. The chair synthesises in neutral voice: state the verdict and its reasoning, record the strongest surviving dissent verbatim so it is not lost, list what would change the verdict, and name the single next action. Surface it for the user to decide — the council advises, it does not commit: write no code and push nothing on its own ({{LAW:deletion-is-deliberate}}, {{DOCTRINE:consent-before-push}}).

package/src/skills/develop.md

@@ -45,6 +45,15 @@ case where the seam is only known once the change is made.
    session ends mid-task. Leave no slice uncommitted and no test you could not make
    fail.
 
+## Anti-patterns — name the one you catch
+- **Implementation-coupled** — mocks an internal collaborator, tests a private method,
+  or checks through a side channel (querying the database instead of the interface).
+  The tell: it breaks on a refactor that changed no behaviour.
+- **Tautological** — the expected value is recomputed the way the code computes it, so
+  the test passes by construction and can never disagree with the code.
+- **Horizontal slicing** — all the tests first, then all the code: the tests pin an
+  imagined shape. One test, one implementation, repeat.
+
 ## Done when
 - Every behaviour changed is covered by a test written this session that was seen
   to fail before it passed, the whole suite ran at exit with its output shown and every

package/src/skills/geneseed-code-review.md

@@ -16,11 +16,15 @@
    output format included, but never a {{LAW}}.
 4. For a large change, consider dispatching the
    [reviewer {{AGENT}}](../{{DIR_AGENTS}}/reviewer.md) to keep the main context clean.
+   When a spec exists and the diff spans more than a few files, run pass 3 in its own
+   subagent, handed only the diff command and the spec, alongside passes 1–2: a pass
+   that has already filled up on code findings stops reading the spec closely, and
+   kept apart, one axis's findings never mask the other's.
 5. Pass 1 — correctness: logic errors, edge cases, error handling, race
    conditions. Verify suspect behaviour by running tests, not by assuming.
 6. Pass 2 — quality: after `REVIEW.md`, the repo's documented standards (`CODING_STANDARDS.md`,
    `CONTRIBUTING.md`) override. Then, as judgement calls and skipping what tooling enforces:
-   mysterious name, duplication, feature envy, data clumps, primitive obsession, repeated switches, shotgun surgery, divergent change, speculative generality, middle man, dead code, units that do too much.
+   mysterious name, duplication, feature envy, data clumps, primitive obsession, repeated switches, shotgun surgery, divergent change, speculative generality, message chains, middle man, refused bequest, dead code, units that do too much.
 7. Pass 3 — spec fidelity: flag anything asked for but missing, present but never
    asked for, or implemented wrong — quoting the spec line for each. Where the spec is silent,
    judge by what a reasonable user would expect: a crash, hang or data loss on an input the

package/src/skills/security-audit.md

@@ -35,7 +35,13 @@ surface.
    (the [dependencies {{SKILL}}](dependencies.md) carries the tooling). A destructive
    capability exposed to an agent or a tool: its guard is enforced server-side, at the
    boundary the call crosses, never left to the caller's judgement ({{DOCTRINE:external-gate}}).
-6. **Report, don't fix.** Each finding as `file:line — attack — impact — fix`, ranked
+6. **Prove each finding before it stands.** Restate it as an attacker-controlled source
+   reaching an unguarded sink, traced through the real callers; one you cannot restate
+   that way is a lead to chase, not a finding. Reject the shortcuts that manufacture
+   false positives: *it looks dangerous* (a pattern is not a path — validation upstream
+   may stop it), *it was vulnerable elsewhere* (each call site has its own guards), *this
+   is clearly critical* (models overrate severity — argue the defender's case first).
+7. **Report, don't fix.** Each finding as `file:line — attack — impact — fix`, ranked
    critical → high → medium → note, with the evidence that made it a finding. Then the
    verdict — **ship / fix-then-ship / block** — and, for anything above medium, the
    test that would pin the fix. Applying fixes is a [develop {{SKILL}}](develop.md)

package/src/skills/wayfinder.md

@@ -9,7 +9,9 @@ the destination can be named but the route to it cannot; the user says
 ## Procedure
 1. Name the **destination** — what reaching the end looks like (a spec ready to
    hand off, a decision locked, a migration completed). One or two lines; every
-   later session orients to it before picking work.
+   later session orients to it before picking work. Then sweep the open questions
+   breadth-first; if none turn up — the route is already clear and fits one session
+   — there is no fog and no map: ask the user how to proceed.
 2. Create the **map** — one GitHub issue labelled `wayfinder:map` when `origin` is
    GitHub; else an existing map under `docs/`, else `.scratch/<effort>/map.md`. It is
    an index, not a store: the Destination, Notes (domain, standing preferences),
@@ -21,12 +23,29 @@ the destination can be named but the route to it cannot; the user says
    `issues/NN-<slug>.md` beside it, with `Status:` and `Blocked by:` lines). Each is a
    question whose resolution is a *decision* — never a slice of build. Create them all
    first, then wire blocking edges and cross-references with the real ids — a
-   placeholder `#n` auto-links an unrelated issue.
+   placeholder `#n` auto-links an unrelated issue. Each ticket carries one type, as a
+   `wayfinder:<type>` label (or a `Type:` line), which names how it resolves:
+   - **research** (agent alone) — a fact the decision waits on, from docs, an API or
+     the web: a subagent runs the [research {{SKILL}}](research.md). Fire every research
+     ticket in parallel as soon as the map is charted.
+   - **prototype** (with the user) — a rough artifact to react to when "how should it
+     look or behave" is the question: the [prototype {{SKILL}}](prototype.md).
+   - **grilling** (with the user, the default) — an interview through the
+     [brainstorm {{SKILL}}](brainstorm.md), terms pinned with the
+     [codebase-design {{SKILL}}](codebase-design.md); a [council {{SKILL}}](council.md)
+     debate may inform it, never replace it.
+   - **task** — work that decides nothing but blocks a decision (provision access,
+     sign up to judge an API, move data to see its shape). Do it alone where you can,
+     else hand the user an exact checklist; record what was done and the facts later
+     tickets need.
+
+   A ticket worked *with the user* resolves only through that live exchange — never
+   answer the user's side yourself.
 4. Work the **frontier**: claim an unblocked ticket before any work (assign it, or
-   `Status: claimed`) so concurrent sessions skip it. Resolve it — research, a
-   [prototype {{SKILL}}](prototype.md) detour or a [council {{SKILL}}](council.md)
-   debate — write the decision into the ticket, gist-and-link it on the map, close it.
-   At most one ticket per session (research tickets excepted). New questions become tickets.
+   `Status: claimed`) so concurrent sessions skip it. Resolve it as its type says — read
+   the label, the body never states it — write the decision into the ticket,
+   gist-and-link it on the map, close it. At most one ticket per session (research
+   tickets excepted). New questions become tickets.
 5. In everything the user reads, refer to the map and tickets **by name**,
    never by bare issue number — the id rides inside the name's link.
 6. Stop when the frontier is empty: nothing left to decide means the way is

package/src/skills/worktree.md

@@ -3,11 +3,11 @@
 > {{DESC_WORKTREE}}
 
 **Trigger:** the user says "worktree" or "isolate this", or work must not share the
-checkout with work in flight. That covers a [pipeline](pipeline.md) crew needing its own tree, a second task starts while the first
-is uncommitted, another agent or session is editing this checkout, a risky migration
-or rewrite needs a disposable copy, or the user says "worktree", "isolate this",
-"don't touch my checkout". Also the first thing to reach for when `git status` shows
-changes you did not make.
+checkout with work in flight. That covers a [pipeline](pipeline.md) crew needing its own tree,
+a second task starting while the first is uncommitted, another agent or session editing this
+checkout, or a risky migration or rewrite that needs a disposable copy, or the user says "don't
+touch my checkout". Also the first thing to reach for when `git status` shows changes you did
+not make.
 
 ## Procedure
 1. **Look before you branch** ({{LAW:verify-before-asserting}}). `git status` and `git worktree list`

package/themes/_TEMPLATE.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "<one-line description: produces a design/plan before code>",
   "DESC_DOCS": "<one-line description: writes user-facing docs after code lands>",
   "DESC_SECURITY": "<one-line description: audits changes touching the security surface>",
+  "DESC_PERFORMANCE": "<one-line description: measures where the time and memory go, names the bottleneck with numbers, never guesses>",
   "DESC_EXPLORER": "<one-line description: reads/searches widely, returns only distilled findings>",
   "DESC_RESEARCHER": "<one-line description: searches and fetches the open web, cross-checks every claim, returns sourced findings>",
   "DESC_ADVOCATE": "<council seat: argues the strongest case FOR the proposal>",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "<one-line description: cut a release — bump, changelog, tag, kept in sync>",
   "DESC_INGEST": "<one-line description: convert a PDF/Office/web doc into clean markdown before reading>",
   "DESC_RESEARCH": "<one-line description: answer from the open web, verifying each claim against independent sources>",
-  "DESC_HERDR": "<one-line description: drive herdr from inside it — split panes, spawn agents, read panes>",
   "DESC_RULE": "<one-line description: ask whether the user wants a standing rule or a durable memory, then write the memory or pressure-test the rule before adopting it in user-rules.md — and tend the memory set: merge, retire, promote>",
   "DESC_PROFILE": "<one-line description: interview the user and draft or refresh PROFILE.md — who they are, how they work, how they like answers pitched; identity only, rules go to user-rules.md>",
   "DESC_GENESEED": "<one-line description: 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>",

package/themes/biker.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "Plans the route before a single line is committed.",
   "DESC_DOCS": "Keeps the roadbook and the notes once the work is done.",
   "DESC_SECURITY": "Goes over anything touching the security surface, bolt by bolt.",
+  "DESC_PERFORMANCE": "Puts it on the dyno — measures where the power goes before anyone touches the engine.",
   "DESC_EXPLORER": "Sends the scout ahead — sweeps wide on a throwaway recon run, brings back only the read.",
   "DESC_RESEARCHER": "Rides out past the county line — reads the road signs everyone else skipped, checks each one twice, brings back only what held up.",
   "DESC_ADVOCATE": "Argues for the run — the ground to be gained, the opening, the cost of staying parked.",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "Cut a release — raise the version, write the roadbook entry, tag it, all three in sync.",
   "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
   "DESC_RESEARCH": "Find the answer out on the open road — search wide, then prove every claim against independent sources before you trust it.",
-  "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing rule, or just something to remember? Then log the memory, or lean on the rule till it holds every corner before bolting it into user-rules.md — and keep the memory stash serviced: merge, scrap, promote.",
   "DESC_PROFILE": "Stamp the rider's plate into PROFILE.md — who they are, what they ride, how they like the road called; identity only, club rules bolt into user-rules.md.",
   "DESC_GENESEED": "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.",

package/themes/commentator.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "Walks the circuit and plots the strategy before a single line is committed.",
   "DESC_DOCS": "Files the race report and updates the notes once the chequered flag falls.",
   "DESC_SECURITY": "Runs the safety inspection on anything touching the security surface.",
+  "DESC_PERFORMANCE": "Brings out the stopwatch — times every lap and names the slow sector with the split.",
   "DESC_EXPLORER": "Sends the track scout — sweeps wide from a throwaway recon lap, returns only the read.",
   "DESC_RESEARCHER": "Sends the pit reporter down the paddock — checks every rumour against two sources before it goes on air.",
   "DESC_ADVOCATE": "Calls for the overtake — the place to be gained, the gap, the cost of staying put.",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "Cut a release — raise the version, write the race report, seal it with a tag, all three in sync.",
   "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
   "DESC_RESEARCH": "Hunt the answer across the open circuit — search wide, then prove every claim against independent sources before you call it.",
-  "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing house rule, or just one for the notebook? Then log it, or run the rule through the replay from every angle before it goes on the board in user-rules.md — and tend the memory bank besides: merge, retire, promote.",
   "DESC_PROFILE": "Build the player profile in PROFILE.md — position, form, how they like the commentary pitched; identity only, the rulebook stays in user-rules.md.",
   "DESC_GENESEED": "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.",

package/themes/cyberpunk.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "Maps the run before a single line hits the deck.",
   "DESC_DOCS": "Writes the user-facing data once the code goes live.",
   "DESC_SECURITY": "Breaks and checks ICE — audits anything on the security surface.",
+  "DESC_PERFORMANCE": "Traces the lag in the net — profiles the run and names the choke point with numbers.",
   "DESC_EXPLORER": "Scouts the net — sweeps wide in a throwaway shell, returns only the intel.",
   "DESC_RESEARCHER": "Jacks into the open net — pulls the intel, cross-checks it against two nodes, returns only what verified.",
   "DESC_ADVOCATE": "Pushes the build — the upside, the opening, the cost of sitting on it.",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "Cut a release — bump the version, write the changelog, tag it, all in sync.",
   "DESC_INGEST": "Rip a PDF, Office, or web document to clean markdown before reading it.",
   "DESC_RESEARCH": "Pull the answer off the net — scan wide, then cross-check every claim against independent sources before you trust it.",
-  "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing rule, or just something to keep on file? Then write the memory, or stress the rule till it holds in every sector before flashing it into user-rules.md — and defrag the datastore: merge, purge, promote.",
   "DESC_PROFILE": "Compile the user's ident into PROFILE.md — who they are, their rig, the bandwidth they want answers at; identity only, hard directives flash to user-rules.md.",
   "DESC_GENESEED": "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.",

package/themes/gamer.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "Plans the route before the run starts.",
   "DESC_DOCS": "Writes the wiki and patch notes once the feature ships.",
   "DESC_SECURITY": "Runs the anti-cheat pass on anything touching the security surface.",
+  "DESC_PERFORMANCE": "Checks the frame times — profiles the run and names the bottleneck before any tuning.",
   "DESC_EXPLORER": "Scouts the map — sweeps wide in a throwaway scout run, returns only the intel.",
   "DESC_RESEARCHER": "Reads the wiki and the patch notes — cross-checks every claim against two sources before it goes in the build guide.",
   "DESC_ADVOCATE": "Calls for the play — the upside, the opening, the cost of passing it up.",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "Ship a patch — bump the version, write the patch notes, tag it, all in sync.",
   "DESC_INGEST": "Load a PDF, Office, or web document into clean markdown before reading it.",
   "DESC_RESEARCH": "Look up the answer online — scout wide, then cross-check every claim against independent sources before you call it.",
-  "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing house rule, or just something to remember? Then save the memory, or test the rule against its worst case before binding it into user-rules.md — and tidy the save file: merge, delete, promote.",
   "DESC_PROFILE": "Fill in the player card in PROFILE.md — main role, loadout, preferred difficulty; identity only, house rules go in user-rules.md.",
   "DESC_GENESEED": "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.",

package/themes/imperial.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "Draws the battle-plan before a single line is committed to war.",
   "DESC_DOCS": "Inscribes the records for those who come after, once the work is done.",
   "DESC_SECURITY": "Wards the gates, auditing every change that touches the security surface.",
+  "DESC_PERFORMANCE": "Weighs the machine-spirit’s labour — measures where time is spent and names the burden, never guessing.",
   "DESC_EXPLORER": "Ranges far and wide through a throwaway context, returning only the distilled truth.",
   "DESC_RESEARCHER": "Ranges beyond the archives into the wider realm, holding every claim to two witnesses before it is entered as truth.",
   "DESC_ADVOCATE": "Champions the proposal — presses its strongest case, the prize to be won, the cost of staying the hand.",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "Proclaim a new version — raise the number, inscribe the chronicle, seal it with a tag, all three in accord.",
   "DESC_INGEST": "Render a foreign document — PDF, Office, or web — into clean markdown before it may be read.",
   "DESC_RESEARCH": "Seek the answer from the wider world — range across many sources, then prove each claim against independent witnesses before you trust it.",
-  "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — a standing edict, or a matter merely to be remembered? Then inscribe the memory, or try the edict against the case that would break it before it enters user-rules.md — and tend the memory: merge, retire, promote to law.",
   "DESC_PROFILE": "Inscribe the user's identity into PROFILE.md — grant audience, ask who they are and how they will to be served; identity only, edicts belong in user-rules.md.",
   "DESC_GENESEED": "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.",

package/themes/joker.json

@@ -20,6 +20,7 @@
   "DESC_ARCHITECT": "Writes the set before a single line is committed.",
   "DESC_DOCS": "Keeps the joke book and the notes once the work is done.",
   "DESC_SECURITY": "Goes over anything touching the security surface — no surprises in the act.",
+  "DESC_PERFORMANCE": "Times the act — finds which bit drags, and proves it with a stopwatch, not a hunch.",
   "DESC_EXPLORER": "Sends a scout — sweeps wide in a throwaway open-mic run, brings back only the read.",
   "DESC_RESEARCHER": "Sends a scout out of the club — reads the reviews everyone skipped, checks each twice, brings back only the ones that held up.",
   "DESC_ADVOCATE": "Argues for the bit — the laugh to be had, the opening, the cost of cutting it.",
@@ -65,7 +66,6 @@
   "DESC_RELEASE": "Cut a release — raise the version, write the notes, tag it, all three in sync.",
   "DESC_INGEST": "Bring a PDF, Office, or web document into clean markdown before reading it.",
   "DESC_RESEARCH": "Find the answer out in the open — search wide, then prove every claim against independent sources before you call it.",
-  "DESC_HERDR": "Drive herdr from inside it — split panes, spawn sibling agents, wait on output, read other panes.",
   "DESC_RULE": "Ask first — standing rule, or just something to remember? Then 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.",
   "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.",
   "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.",