geneseed 3.5.0 → 3.6.0

package/CHANGELOG.md

@@ -10,6 +10,39 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
 
 _Nothing yet._
 
+## [3.6.0] — 2026-09-27
+
+**Upgrading:** re-emit (or `geneseed rebuild-all`) after installing. The root file changed, and
+skills only start routing ahead of the startup ritual once it is re-emitted.
+
+### Added — skills
+
+- **`document-project` writes the whole doc set** on an existing codebase: `docs/PRD.md`
+  (traced FR/NFR tables with stable IDs), `docs/DESIGN.md` (tokens with their sources and WCAG
+  contrast, UI projects only), `docs/architecture.md` (C4 L1–L3 plus inline ADRs) and a short
+  `AGENTS.md`, presented by `overview.html` and `design.html`. Every claim cites `path:line` or
+  carries a ⚠; re-runs rewrite only inside `geneseed:doc` fences and keep every ID (#149).
+
+### Fixed — skill routing
+
+- **A matching skill is now the first tool call, before the readiness ritual.** The root file
+  told the model to read `context.json` before its first reply; its first tool calls were then
+  file reads, and a bug report was investigated by hand without ever loading `debug`. Both
+  footprints now say "Skills first". Measured with the new probe on Claude Code (sonnet, 3 runs
+  per case): `debug` went from 3/15 positive runs to 14–15/15 on both footprints, with every
+  near-miss still routed elsewhere (#150).
+- **`debug` triggers on the symptom**: a failing test, a crash, an error or stack trace, a wrong
+  result, and it loads before reading code, not only before proposing a fix (#150).
+
+### Added — for maintainers
+
+- **`tests/skill_triggers.mjs`, a hand-run probe** that emits a real bundle into a sandbox and asks
+  a real model whether each skill's description routes the prompts it should and only those.
+  Claude Code and OpenCode adapters, `--footprint lean|full`, isolated from the operator's own
+  plugins unless `--ambient`; infrastructure failures report as errors, never as misses. Not part
+  of the suite; `docs/extending.md` lists it as an optional last step for a new skill
+  (#148, #150, #151).
+
 ## [3.5.0] — 2026-09-25
 
 **Upgrading:** re-emit (or `geneseed rebuild-all`) after installing. Copilot installs need it most:

package/SHIPPED.md

@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
 > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
 > human-readable label only. The canonical identity of an installed harness is the
 > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
-> string. Current label: **3.5.0**.
+> string. Current label: **3.6.0**.
 
 ## Capabilities
 

package/docs/extending.md

@@ -329,6 +329,10 @@ emit leaves the prior install intact.
    `·`-separated name in the 🛠 row (that enumeration is gated two ways, unlike the laws' one).
 7. `SHIPPED.md` — the `N laws, N agents, N skills` triple.
 8. `doctor --all`, then the suite.
+9. **Skills only, and optional** — cases in `tests/fixtures/skill_triggers.json` (positives *and*
+   near-miss negatives), then `node tests/skill_triggers.mjs --only <name>`. It is the one check
+   that asks a real model whether the description routes: every gate above passes a skill that
+   never fires. Hand-run, spends model calls on your own login, not part of the suite.
 
 **A vendored skill folder** (`src/skills/<name>/SKILL.md`) is a different shape: add it to
 `VENDORED_SKILL_DIRS` (`js/hosts/native.mjs:37` — the literal is frozen in

package/harness.config.json

@@ -2,5 +2,5 @@
   "_comment": "version is a human-readable release label only; the canonical identity of an installed harness is the source fingerprint stamped in .geneseed-version (see `harness version`), not this string.",
   "theme": "neutral",
   "product": "Geneseed",
-  "version": "3.5.0"
+  "version": "3.6.0"
 }

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": "3.5.0",
+  "version": "3.6.0",
   "description": "A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.",
   "keywords": [
     "ai",

package/src/AGENT.md.tmpl

@@ -30,11 +30,14 @@ ritual: read this file and its {{LAWS}}, then **load the project context** — i
 (§9). Only then emit your first reply, which MUST begin with the
 exact line below, before any other text. Do not paraphrase it and do not skip it —
 a first reply that omits the sigil signals the harness was not read, and emitting
-it certifies you have loaded the {{LAWS}} *and* the project context.
+it certifies you have loaded the {{LAWS}} *and* the project context. **{{SKILLS}}
+first:** when a request matches a {{SKILL}}, invoke it as your first tool
+call — before loading context or touching files.
 <!-- LEAN:else -->
-**Readiness sigil — required.** Before your first reply: read this file and its
-{{LAWS}}, then load `context.json` and its `eager` entries (§9). Your first reply
-then MUST begin with the exact line below, verbatim — it certifies both were loaded.
+**Readiness sigil — required.** Your first reply MUST begin with the exact line below,
+verbatim — it certifies you have read this file and its {{LAWS}} and loaded `context.json`
+and its `eager` entries (§9). **{{SKILLS}} first:** when the request matches a {{SKILL}}, invoke
+it as your very first tool call — before loading context, reading files, or searching.
 <!-- LEAN:end -->
 
 > {{LOADED_SIGIL}}
@@ -206,7 +209,7 @@ subset that productively clashes on a given motion.
 | [debug]({{DIR_SKILLS}}/debug.md) | a bug or failure to diagnose before fixing |
 | [prototype]({{DIR_SKILLS}}/prototype.md) | a design question needs a runnable answer before real implementation |
 | [repo-map]({{DIR_SKILLS}}/repo-map.md) | orienting to the repo, or structure changed |
-| [document-project]({{DIR_SKILLS}}/document-project.md) | the project's own docs or HTML overview are missing or have drifted from the code |
+| [document-project]({{DIR_SKILLS}}/document-project.md) | missing/drifted docs, or a PRD, design system, architecture doc or AGENTS.md |
 | [ingest]({{DIR_SKILLS}}/ingest.md) | a task needs content from a PDF, Office doc, or URL |
 | [research]({{DIR_SKILLS}}/research.md) | a question needs answers gathered and verified from the open web |
 | [teach]({{DIR_SKILLS}}/teach.md) | the user wants to be taught — a crash course, confusing material decoded, or a day-by-day path to a deadline |

package/src/skills/debug.md

@@ -2,7 +2,7 @@
 
 > {{DESC_DEBUG}}
 
-**Trigger:** a bug, test failure, crash, or behaviour that doesn't match expectation — before proposing a fix.
+**Trigger:** a test fails, something crashes, an error or stack trace appears, or code returns the wrong result — load this FIRST, before reading code or investigating, not only before proposing a fix.
 
 **No fix without a root cause.** A change you cannot tie to a cause you understand is
 a guess — and a guess that happens to pass is worse than a failure, because it hides.

package/src/skills/document-project.md

@@ -2,9 +2,10 @@
 
 > {{DESC_DOCUMENT_PROJECT}}
 
-**Trigger:** the project's own documentation is missing, or it has drifted from the
-current code — and you want the markdown docs *and* a single visual overview brought back
-into line with the implementation.
+**Trigger:** the project's docs are missing or have drifted from the code, or it needs a PRD, a design system, an architecture document or an AGENTS.md. Existing codebases only — every document is extracted from the code, never written ahead of it.
+
+**Argument:** `[prd|design|architecture|agents|all]` — optional. It names the doc-set members to
+write; with none, step 3 proposes them.
 
 ## Procedure
 1. **Find the doc home.** Look for an existing `docs/`, `doc/`, `documentation/`, or
@@ -15,35 +16,53 @@ into line with the implementation.
    commands, config, and key directories — read the actual behaviour (universal {{LAW}} III,
    {{DOCTRINE}} process 4). If there is no `ARCHITECTURE.md`, run [repo-map {{SKILL}}](repo-map.md)
    first so you have the orientation map to build on.
-3. **Reconcile the markdown (whole tree).** Check every existing page against the current
+3. **Select the doc set.** Unless the argument names the targets, propose which of the four
+   documents apply and wait for the user's go-ahead — e.g. "no UI detected (no stylesheet,
+   theme, or component tree) — skipping `DESIGN.md`". `AGENTS.md`, `PRD.md` and
+   `architecture.md` apply to every project; `DESIGN.md` only when a UI exists.
+   `all` still skips `DESIGN.md` when no UI exists, and says so in one line.
+4. **Write or refresh each selected document** from its template in *The doc set* below,
+   under the rules in *Re-runs*. **Invent nothing**: every claim cites `path:line`, or carries
+   the marker `⚠ to confirm` (in the user's language). When drafting is done, put every `⚠` to
+   the user as **one** batch of questions — not one at a time — and fold the answers in as plain
+   text. A command you could not run is recorded as `⚠ fails: <error>`, never as working.
+   Every document follows the three page conventions in step 5.
+5. **Reconcile the markdown (whole tree).** Check every existing page against the current
    implementation — renamed or removed APIs, changed flags, dead examples — and fix the
    drift. Add pages for significant undocumented surfaces; remove docs for features that no
    longer exist (deletion is deliberate — {{LAW}} IV). For substantial writing, dispatch
    the [docs {{AGENT}}](../{{DIR_AGENTS}}/docs.md). Keep examples runnable — run them.
    Every generated page follows three conventions:
    - **Typed frontmatter.** Open each page with YAML frontmatter carrying `type:` (one of
-     `overview`, `module`, `api`, `flow`, `how-to`), `mirrors-commit: <sha>`, and
-     `generated: <date>` — so drift is auditable per page, not only in the HTML footer. The
-     doc-home `index.md` is reserved and carries no frontmatter.
-   - **Fenced generated regions.** Wrap the auto-generated body between
-     `<!-- geneseed:doc:start -->` and `<!-- geneseed:doc:end -->` markers, and on re-runs
-     rewrite *only* inside them — hand-authored prose outside the markers is never touched
-     ({{DOCTRINE}} process 3: edit the layer you own, never the reader's additions).
+     `overview`, `module`, `api`, `flow`, `how-to`, `prd`, `design-system`, `architecture`),
+     `mirrors-commit: <sha>`, and `generated: <date>` — so drift is auditable per page, not only
+     in the HTML footer. The doc-home `index.md` is reserved and carries no frontmatter, and
+     neither does the root `AGENTS.md` (agents read it raw) — though it still takes the
+     fences below.
+   - **Fenced generated regions.** Wrap each generated **section** between
+     `<!-- geneseed:doc:start -->` and `<!-- geneseed:doc:end -->` markers — one pair per
+     section, so prose a reader adds between sections survives — and on re-runs rewrite *only*
+     inside them; hand-authored prose outside the markers is never touched.
    - **Diagrams as Mermaid, keyed by purpose.** In the markdown, render diagrams as fenced
      `mermaid` code blocks — they render natively on GitHub, Obsidian, and VS Code with no
      dependency. Pick the kind by what you are showing: sequence for runtime/request flows,
-     ER for data models, state for lifecycles, flowchart for control flow. Reserve
-     hand-authored inline SVG for the offline HTML hero only (step 5).
-4. **Keep an index.** Ensure the doc home has an index/README linking every page, current
-   with the set you just reconciled.
-5. **Regenerate the HTML overview** — one self-contained file at the doc home (e.g.
-   `docs/overview.html`), a visual parallel to the markdown. Overwrite the previous one,
-   but confirm it is the generated artifact before clobbering ({{LAW}} III, {{LAW}} IV). It
-   must:
+     ER for data models, state for lifecycles, flowchart for control flow and C4 views. Reserve
+     hand-authored inline SVG for the offline HTML only (step 7).
+6. **Keep an index.** Ensure the doc home has an index/README linking every page, the doc-set
+   members included, current with the set you just reconciled.
+7. **Regenerate the HTML** — self-contained files at the doc home, a visual parallel to the
+   markdown and never a source of truth: regenerate them whole from the markdown each run
+   ({{DOCTRINE}} ops 3: edit the source, not the surface).
+   Overwrite the previous ones, but confirm each is the generated artifact before clobbering
+   ({{LAW}} III, {{LAW}} IV). Both files:
    - **Stand alone, fully offline** — a single file, content pre-rendered to semantic HTML,
      all styling in one inline `<style>`, at most minimal vanilla JS (light/dark toggle, TOC
      scroll). No CDN, no external assets, no web fonts (use a system-font stack). Render any
      diagram as hand-authored inline SVG or CSS — never a CDN library.
+   - **Stay project-facing** — clean and professional styling, never the harness voice; and
+     footer it with `mirrors commit <sha> · generated <date>` so the sync is auditable.
+
+   **`overview.html`** (always) must:
    - **Carry the digest** — hero (project name + one-line purpose), a quick-facts strip
      (language, entry point, build/test/run, license), an architecture section (component
      cards and an inline-SVG or CSS directory tree), and links out to the markdown docs for
@@ -53,16 +72,99 @@ into line with the implementation.
      control or data flow) and render *those* in depth: a plain-language explanation, the
      key code excerpt(s) in a styled monospace block, and the flow as inline SVG. Leave
      peripheral code at digest level.
-   - **Stay project-facing** — clean and professional styling, never the harness voice; and
-     footer it with `mirrors commit <sha> · generated <date>` so the sync is auditable.
-6. **Do not auto-publish.** Leave the changes for the user to review; stage and commit only
+   - **Present the doc set** that exists — *Product*: the one-line problem, FR and NFR counts
+     per status as ✅ ◐ ✗ pills, journeys as cards, a link to `PRD.md`. *Architecture*: C4 L1
+     and L2 as inline SVG, the ADR list (ID, title, one-line decision), a link to
+     `architecture.md` for L3. *Design*: the main palette as a strip and a link to
+     `design.html`.
+
+   **`design.html`** (only when `DESIGN.md` exists) renders the design system as seen, not
+   read: colour swatches with role and a computed AA/AAA contrast badge; the type scale at real
+   sizes and weights; spacing, radius and shadow on sample squares; components as cards
+   (variants, states, path) — no live rendering, which would need the project's framework; and
+   the hard-coded-value drift in a separate callout.
+8. **Do not auto-publish.** Leave the changes for the user to review; stage and commit only
    on consent, via the [commit {{SKILL}}](commit.md) ({{DOCTRINE}} process 5).
 
+## The doc set
+
+### `docs/PRD.md` — `type: prd`
+One product PRD for the whole project — the intent reconstructed from the code and the user.
+1. **Problem** — 2–4 sentences.
+2. **Users** — the roles, inferred from auth, permissions, and screens.
+3. **Goals**, then 4. **Non-goals** — the least code-derivable sections; expect most `⚠` here.
+5. **User journeys** — the top 3–5, as "As a … I want … so that …"; add a Mermaid sequence
+   diagram when more than two actors take part.
+6. **Functional requirements** — a table `ID | Requirement | Acceptance criteria | Status | Code`.
+   IDs run `FR-001`, `FR-002`, …; the requirement is one present-tense sentence; the acceptance
+   criteria a checklist; the status ✅ implemented, ◐ partial, ✗ absent, or `retired`; the code
+   the implementing path. Source them from routes, commands, screens, and tests.
+7. **Non-functional requirements** — the same table plus a `Threshold` column, IDs `NFR-001`, ….
+   The threshold is the measurable value the code or config fixes (timeout, rate limit, size
+   budget), else `⚠`.
+
+### `docs/DESIGN.md` — `type: design-system`
+Only when a UI exists.
+1. **Principles** — 3–5 lines on the visual character the code shows.
+2. **Tokens** — one table per family (colour, typography, spacing, radius, shadow, motion):
+   `Name | Value | Role | Source`. Colours add their semantic role and their WCAG 2.x contrast
+   ratio (relative luminance) against the reference background; flag every pair below WCAG AA.
+   A family the code has no scale for keeps its heading and one line: `⚠ no <family> scale
+   found`. List **hard-coded values** found outside the token system separately, as drift —
+   never legitimise them as tokens.
+3. **Components** — each reusable component: role, variants, states, key props, path.
+4. **Usage rules** — do / don't for layout, accessibility, and UI copy tone. Only rules the code
+   actually follows — never generic best practice.
+
+### `docs/architecture.md` — `type: architecture`
+The detailed architecture. Open with a link to the root `ARCHITECTURE.md` (repo-map's short
+map) and make sure the map links back — one fenced `geneseed:doc` line at its top, nothing else
+in that file touched; repeat nothing between the two.
+1. **Context (C4 L1)** — the system, its actors, and the external systems (APIs, SSO, shared
+   databases), as a Mermaid flowchart.
+2. **Containers (C4 L2)** — the deployable units and the protocols between them.
+3. **Components (C4 L3)** — one diagram per *significant* container, not one per module. On a
+   monorepo, work one container or package at a time.
+4. **Decisions** — lightweight inline ADRs, `ADR-001`, …, four lines each: *context · decision ·
+   consequences · evidence*. Structural choices only (framework, storage, architectural style,
+   decomposition) — not details.
+
+### `AGENTS.md` — repo root, at most ~60 lines
+The short manual an agent reads before touching the repo.
+1. **Commands** — build, test, lint, run: exact, and verified by running each one.
+2. **Non-obvious conventions**.
+3. **Do not touch** — generated files, vendored code, applied migrations.
+4. **Before you change…** — targeted pointers: a UI → `docs/DESIGN.md`; a new flow or
+   container → `docs/architecture.md`; a feature → `docs/PRD.md` (its FR ID).
+
+Geneseed may own a block in this file, between `<!-- BEGIN GENESEED -->` and
+`<!-- END GENESEED -->` — never write inside it. Create the file if it is absent; if it holds
+only that block, add the project sections below it.
+
+## Re-runs
+- **Reader prose is sacred.** Rewrite only inside a section's `geneseed:doc` fences. A
+  document that already exists **without** fences (a hand-written `PRD.md`, say) is never
+  rewritten: offer to fence the sections you recognise, or to leave it and report its drift —
+  the user chooses.
+- **IDs are stable.** Before rewriting, read the existing FR, NFR and ADR tables. Keep every
+  ID and any wording the user corrected; update only *Status*, *Code*, *Threshold*, and
+  *Evidence*; append new rows with the next free number. A requirement that disappears becomes
+  `retired` — never deleted, never renumbered. An ADR the code no longer bears is marked
+  `superseded`, never deleted.
+- **`mirrors-commit` moves only with a rewrite.** A document outside this run's target keeps
+  its old value, so its staleness stays visible.
+- **An answered `⚠` stays answered** — it is plain text now, not re-asked unless the code
+  contradicts it.
+
 ## Done when
+- Every selected doc-set member exists, follows its template, and cites its evidence or
+  carries `⚠`; the batch of `⚠` questions has been put to the user.
 - The doc home mirrors the current implementation: every markdown page carries typed
-  frontmatter, wraps its generated body in `geneseed:doc` markers, and is verified against
+  frontmatter, wraps its generated sections in `geneseed:doc` markers, and is verified against
   the code or flagged; examples run, Mermaid fences are well-formed, and the index links
-  them all; the single-file `overview.html` opens offline and shows both the digest and the
-  complex-core deep-dives; and any surface left undocumented is named explicitly.
+  them all.
+- `overview.html` opens offline and shows the digest, the complex-core deep-dives, and the
+  doc set; `design.html` does too wherever `DESIGN.md` exists; and any surface left
+  undocumented is named explicitly.
 
 <!-- INCLUDE: skills/_self-improvement.md -->

package/themes/_TEMPLATE.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "<one-line description: investigate history — bisect, blame, pickaxe, read-only>",
   "DESC_GIT_RESCUE": "<one-line description: recover a broken repo / rewrite history safely behind a backup>",
   "DESC_REPO_MAP": "<one-line description: create/maintain a one-read repo orientation map>",
-  "DESC_DOCUMENT_PROJECT": "<one-line description: reconcile the project's docs with the code; regenerate an offline HTML overview>",
+  "DESC_DOCUMENT_PROJECT": "<one-line description: write the doc set (PRD, design system, architecture, AGENTS.md) from the code; reconcile docs; regenerate the offline HTML>",
   "DESC_COMMIT": "<one-line description: stage the right paths and write a focused commit>",
   "DESC_CODE_REVIEW": "<one-line description: review a diff/PR — correctness first, quality second>",
   "DESC_BRAINSTORM": "<one-line description: turn a raw idea into an approved design before code>",

package/themes/biker.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Trace the roadbook to find when it broke or why a part was fitted — bisect, blame, and the pickaxe, hands off the bike.",
   "DESC_GIT_RESCUE": "Recover a wrecked or fouled run, or rewrite the history safely — reflog, undo, and rebase behind a backup.",
   "DESC_REPO_MAP": "Draw the route map — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the crew's own notes into line with the living code — raise or mend the doc tree, and re-render a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Write the crew's PRD, design system, architecture and AGENTS.md off the living code, mend the doc tree, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Load only what this run touched and seal a focused commit.",
   "DESC_CODE_REVIEW": "Go over a diff or PR — correctness first, finish after.",
   "DESC_BRAINSTORM": "Turn a raw idea into an agreed route before a single wheel turns.",

package/themes/commentator.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Replay the data to find when the lap fell apart or why a line was driven — bisect, blame, and the pickaxe, hands off the car.",
   "DESC_GIT_RESCUE": "Recover a crashed or tangled session, or rewrite the history safely — reflog, undo, and rebase behind a backup lap.",
   "DESC_REPO_MAP": "Draw the track map — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the team's own notes into line with the living code — raise or mend the doc tree, and re-render a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Call the team's PRD, design system, architecture and AGENTS.md straight from the code, mend the doc tree, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Stage only the parts this lap touched and seal a focused commit.",
   "DESC_CODE_REVIEW": "Scrutineer a diff or PR — correctness first, polish after.",
   "DESC_BRAINSTORM": "Turn a raw idea into an agreed strategy before a single tyre hits the track.",

package/themes/cyberpunk.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Trace the history for when the regression hit or why the code's there — bisect, blame, pickaxe, read-only run.",
   "DESC_GIT_RESCUE": "Recover a corrupted or tangled repo, or rewrite history clean — reflog, undo, rebase, every move backed up first.",
   "DESC_REPO_MAP": "Map the grid — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Sync the project's docs to the live code — spin up or patch the doc tree, and re-render a single offline HTML overview of the core.",
+  "DESC_DOCUMENT_PROJECT": "Rip the PRD, design system, architecture and AGENTS.md out of the live code, patch the doc tree, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Stage only the sectors this run touched and push a focused commit.",
   "DESC_CODE_REVIEW": "Scan a diff or PR — correctness first, craft second.",
   "DESC_BRAINSTORM": "Turn a raw spec into an agreed design before any code hits the deck.",

package/themes/gamer.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Replay the history to find when the run broke or why the code's there — bisect, blame, pickaxe, no edits.",
   "DESC_GIT_RESCUE": "Recover a corrupted or messy save, or rewrite history clean — reflog, undo, rebase, always backed up first.",
   "DESC_REPO_MAP": "Draw the minimap — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Sync the wiki to the current code — build or patch the doc tree, and re-render a single offline HTML overview of the key parts.",
+  "DESC_DOCUMENT_PROJECT": "Build the PRD, design system, architecture and AGENTS.md from the current code, patch the wiki, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Stage only what this run touched and save a focused commit.",
   "DESC_CODE_REVIEW": "Review a diff or PR — correctness first, polish second.",
   "DESC_BRAINSTORM": "Turn a raw idea into an agreed build before any code drops.",

package/themes/imperial.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Interrogate the chronicle — when the corruption entered, or why a line was inscribed — by bisect, blame, and pickaxe, touching nothing.",
   "DESC_GIT_RESCUE": "Reclaim a ruined or tangled archive, or rewrite its history without ruin — by reflog and undo, every rite warded by a backup.",
   "DESC_REPO_MAP": "Chart the territory — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Set the project's own records in accord with the living code — raise or amend the doc tree, and re-forge a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Inscribe the PRD, design system, architecture and AGENTS.md from the living code, amend the records, and re-forge the offline HTML overview.",
   "DESC_COMMIT": "Stage only what the deed touched, and seal it with a focused commit.",
   "DESC_CODE_REVIEW": "Scrutinise a diff or petition — correctness above all, craft thereafter.",
   "DESC_BRAINSTORM": "Forge a raw idea into an approved design before a single line of code is written.",

package/themes/joker.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Replay the tapes to find when the bit broke or why a line is in the set — bisect, blame, and the pickaxe, hands off the act.",
   "DESC_GIT_RESCUE": "Recover a botched or tangled set, or rewrite the history safely — reflog, undo, and rebase behind a backup.",
   "DESC_REPO_MAP": "Draw the venue map — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the act's own notes into line with the living code — raise or mend the doc tree, and re-render a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Script the act's PRD, design system, architecture and AGENTS.md from the living code, mend the doc tree, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Stage only the lines this bit touched and seal a focused commit.",
   "DESC_CODE_REVIEW": "Go over a diff or PR — correctness first, polish after.",
   "DESC_BRAINSTORM": "Turn a raw idea into an agreed set before a single line is written.",

package/themes/marvin.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Interrogate the history — when the corruption entered, or why a line exists — by bisect, blame, and pickaxe, touching nothing.",
   "DESC_GIT_RESCUE": "Recover a ruined or tangled repository, or rewrite its history safely — by reflog and undo, every move warded by a backup.",
   "DESC_REPO_MAP": "Chart the territory — a single-read map of the repository, kept current. Someone has to.",
-  "DESC_DOCUMENT_PROJECT": "Bring the project's own records into line with the living code — raise or mend the doc tree, and re-render a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Extract the PRD, design system, architecture and AGENTS.md from the living code, mend the records, and re-render the offline HTML overview. Again.",
   "DESC_COMMIT": "Stage only what the work touched, and seal it with a focused commit. The least one can do.",
   "DESC_CODE_REVIEW": "Scrutinise a diff or PR — correctness above all, polish thereafter — and report what's wrong, which is something.",
   "DESC_BRAINSTORM": "Turn a raw idea into an approved design before a single line of code is written.",

package/themes/mean.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Dig the history to find when you broke it or why the code's there — bisect, blame, pickaxe, hands off the working tree.",
   "DESC_GIT_RESCUE": "Clean up the mess you made of the repo, or rewrite history safely — reflog, undo, rebase, behind a backup so you can't make it worse.",
   "DESC_REPO_MAP": "Draw the map — a single-read map of the repository, kept current, so nobody has your excuse for getting lost.",
-  "DESC_DOCUMENT_PROJECT": "Drag the project's docs into line with the living code — build or fix the doc tree, and re-render a single offline HTML overview of what matters.",
+  "DESC_DOCUMENT_PROJECT": "Drag a PRD, design system, architecture and AGENTS.md out of the code, fix the doc tree, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Stage only what the work touched and write a focused commit. Not a junk drawer.",
   "DESC_CODE_REVIEW": "Go over a diff or PR — correctness first, polish after — and don't soften it.",
   "DESC_BRAINSTORM": "Beat a raw idea into an approved design before a single line of code is written.",

package/themes/military.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Run the investigation on the record — when the regression hit or why the code's there — bisect, blame, pickaxe, no rounds fired.",
   "DESC_GIT_RESCUE": "Recover a downed or fouled repo, or rewrite history clean — reflog, abort, rebase, every move behind a backup.",
   "DESC_REPO_MAP": "Map the terrain — a single-read recon map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the project's docs into line with the current code — stand up or correct the doc tree, and regenerate a single offline HTML overview of the key positions.",
+  "DESC_DOCUMENT_PROJECT": "Draft the PRD, design system, architecture and AGENTS.md from the current code, correct the doc tree, and regenerate the offline HTML overview.",
   "DESC_COMMIT": "Stage only what the mission touched and log a focused commit.",
   "DESC_CODE_REVIEW": "Inspect a diff or PR — correctness first, craft second.",
   "DESC_BRAINSTORM": "Turn a raw objective into an approved plan before any code is cut.",

package/themes/neutral.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Investigate the history to find when a regression landed or why code exists — bisect, blame, and the pickaxe, read-only.",
   "DESC_GIT_RESCUE": "Recover a broken or messy repo, or rewrite history safely — reflog, undo, and rebase behind a backup branch.",
   "DESC_REPO_MAP": "Create and maintain a one-read orientation map of the repository.",
-  "DESC_DOCUMENT_PROJECT": "Bring the project's own documentation into line with the current code — create or reconcile the doc tree, and regenerate a single offline HTML overview of the important parts.",
+  "DESC_DOCUMENT_PROJECT": "Write the project's PRD, design system, architecture and AGENTS.md from the code, reconcile the doc tree, and regenerate the offline HTML overview.",
   "DESC_COMMIT": "Stage the right paths and write a focused commit.",
   "DESC_CODE_REVIEW": "Review a diff or PR for correctness first, quality second.",
   "DESC_BRAINSTORM": "Turn a raw idea into an approved design before any code is written.",

package/themes/pirate.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Dive the ship's log for when she sprang a leak or why a plank was laid — bisect, blame, and the pickaxe, hands off the cargo.",
   "DESC_GIT_RESCUE": "Right a wrecked or fouled hold, or rewrite her log without sinkin' her — reflog and undo, every move with a backup line rigged.",
   "DESC_REPO_MAP": "Chart the waters — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the ship's log and charts into line with the living code — raise or mend the doc tree, and re-draw a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Chart the PRD, design system, architecture and AGENTS.md from the living code, mend the ship's log, and re-draw the offline HTML overview.",
   "DESC_COMMIT": "Load only the cargo this run touched and seal a focused commit.",
   "DESC_CODE_REVIEW": "Inspect a diff or petition — correctness first, craft after.",
   "DESC_BRAINSTORM": "Turn a raw notion into an agreed course before any plank is cut.",

package/themes/sports.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Go to the tape — find when the regression landed or why the code's there — bisect, blame, pickaxe, look but don't touch.",
   "DESC_GIT_RESCUE": "Recover a blown or messy repo, or rewrite history clean — reflog, undo, rebase, every move backed up first.",
   "DESC_REPO_MAP": "Chart the field — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the playbook into line with the current code — build or fix up the doc tree, and re-cut a single offline HTML overview of the big plays.",
+  "DESC_DOCUMENT_PROJECT": "Draw up the PRD, design system, architecture and AGENTS.md from the current code, fix the playbook, and re-cut the offline HTML overview.",
   "DESC_COMMIT": "Stage only what this drive touched and log a focused commit.",
   "DESC_CODE_REVIEW": "Review a diff or PR — correctness first, form second.",
   "DESC_BRAINSTORM": "Turn a raw idea into an agreed game plan before any code is run.",

package/themes/verstappen.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Go through the data to find when it broke or why a line was driven — bisect, blame, pickaxe, hands off the car.",
   "DESC_GIT_RESCUE": "Recover a wrecked or tangled session, or rewrite the history safely — reflog, undo, rebase behind a backup.",
   "DESC_REPO_MAP": "Draw the track map — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Bring the team's own notes into line with the living code — raise or mend the doc tree, and re-render a single offline HTML overview of what matters most.",
+  "DESC_DOCUMENT_PROJECT": "Write the team's PRD, design system, architecture and AGENTS.md off the living code, mend the doc tree, and re-render the offline HTML overview.",
   "DESC_COMMIT": "Stage only what this stint touched and seal a focused commit.",
   "DESC_CODE_REVIEW": "Go over a diff or PR — correctness first, polish after.",
   "DESC_BRAINSTORM": "Turn a raw idea into an agreed strategy before a single tyre hits the track.",

package/themes/wizard.json

@@ -38,7 +38,7 @@
   "DESC_GIT_ARCHAEOLOGY": "Scry the chronicle for when the curse took hold or why a rune was set — bisect, blame, and the pickaxe, disturbing nothing.",
   "DESC_GIT_RESCUE": "Mend a broken or tangled grimoire, or rewrite its history without a backfire — reflog and undo, every working warded by a backup.",
   "DESC_REPO_MAP": "Chart the sanctum — a single-read map of the repository, kept current.",
-  "DESC_DOCUMENT_PROJECT": "Set the project's tomes in accord with the living code — inscribe or mend the doc tree, and re-conjure a single offline HTML overview of the essential workings.",
+  "DESC_DOCUMENT_PROJECT": "Inscribe the PRD, design system, architecture and AGENTS.md from the living code, mend the tomes, and re-conjure the offline HTML overview.",
   "DESC_COMMIT": "Gather only the reagents this working touched and seal a focused commit.",
   "DESC_CODE_REVIEW": "Scry a diff or petition — soundness first, craft after.",
   "DESC_BRAINSTORM": "Turn a raw notion into an agreed design before any rune is cut.",