@golden-frijoles/kit 0.44.0 → 1.0.0

package/dist/build-order.mjs

@@ -18,7 +18,7 @@ import { execFileSync } from 'node:child_process';
 import { readFileSync, writeFileSync, existsSync } from 'node:fs';
 import { fileURLToPath } from 'node:url';
 import { dirname, join } from 'node:path';
-import { STAGES, groupByStage } from './lib/stage.mjs';
+import { STAGES, groupByStage, stageWord } from './lib/stage.mjs';
 import { projectRoot } from './lib/project-root.mjs';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
@@ -78,7 +78,7 @@ function render(rows) {
   out.push('# Build order — the six stages');
   out.push('');
   out.push(`> **Generated ${now} — do not hand-edit.** One stage per initiative, decided in one place`);
-  out.push('> (`scripts/lib/stage.mjs`): To groom · Grooming · Ready to build · Building · QA · Shipped.');
+  out.push(`> (\`scripts/lib/stage.mjs\`): ${STAGES.map(stageWord).join(' · ')}.`);
   if (LIVE) {
     out.push('> **Live:** Building and QA come from git and GitHub as of this run. Printed, never written.');
   } else {
@@ -89,7 +89,7 @@ function render(rows) {
   for (const stage of STAGES) {
     const list = columns[stage];
     if (LIVE_ONLY.has(stage) && !LIVE) {
-      out.push(`## ${stage} — live only`);
+      out.push(`## ${stageWord(stage)} — live only`);
       out.push('');
       out.push(
         `_${STAGE_NOTE[stage]}. Not in this committed file: \`node scripts/build-order.mjs --live\` or the Hub board._`
@@ -97,7 +97,7 @@ function render(rows) {
       out.push('');
       continue;
     }
-    out.push(`## ${stage} (${list.length})`);
+    out.push(`## ${stageWord(stage)} (${list.length})`);
     out.push('');
     out.push(`_${STAGE_NOTE[stage]}._`);
     out.push('');
@@ -126,7 +126,7 @@ if (unfunded.length) {
 }
 
 // Scaffolded ⇒ funded (fund-at-approval D8). A live bet — an epic scaffolded or in progress, or a queued seed — must
-// name the cycle that paid for it, and that cycle must be a file in Roadmap/bets/. `groom` funds a bet at its approval
+// name the cycle that paid for it, and that cycle must be a file in Roadmap/bets/. `refine` funds a bet at its approval
 // gate (`fund.mjs`), in the same commit as the scaffold, so this only fails on work that skipped the gate.
 const BETS = join(REPO, 'Roadmap', 'bets');
 const cycleOf = (v) => String(v).replace(/^Roadmap\/bets\//, '').replace(/\.md$/, '');
@@ -139,7 +139,7 @@ const unpaid = liveBets.filter((r) => !paidBy(r));
 if (unpaid.length) {
   console.error('Live bets with no funding record (`underwritten_by:` must name a Roadmap/bets/<cycle>.md):');
   for (const r of unpaid) console.error(`  - ${r.doc_link}${r.underwritten_by ? ` — no Roadmap/bets/${cycleOf(r.underwritten_by)}.md` : ''}`);
-  console.error('Fund it at the approval gate: node "$GROOM/fund.mjs" --slug <slug> --displaced "<…>" --next | --after <slug>');
+  console.error('Fund it at the approval gate: node "$REFINE/fund.mjs" --slug <slug> --displaced "<…>" --next | --after <slug>');
   process.exit(1);
 }
 

package/dist/build-state.mjs

@@ -61,7 +61,7 @@ import { parseJournal, JOURNAL_BRANCH, JOURNAL_PATH } from './lib/session-journa
 import { branchCandidates, parseBranch } from './lib/work-branch.mjs';
 import { buildRows } from './roadmap-extract.mjs';
 import { gatherFacts } from './lib/stage-facts.mjs';
-import { STAGES, groupByStage } from './lib/stage.mjs';
+import { STAGES, groupByStage, stageWord } from './lib/stage.mjs';
 import { getKey } from './lib/config.mjs';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
@@ -927,14 +927,13 @@ function stageParts(state) {
 }
 
 // build-view-upgrade D3 — the stage as a track, in lib/stage.mjs's words. `To groom` shows only when it is the stage.
-const TRACK_WORDS = { 'To groom': 'Backlog', 'Ready to build': 'Ready' };
 export const TRACK_MARK = '◉';
 
 /** `Grooming ─ Ready ─ ◉ Building ─ QA ─ Shipped` for a stage; `◉ Locking` in Building's place while locking. */
 export function stageTrack(stage, locking = false) {
   return STAGES.filter((s) => s !== 'To groom' || stage === 'To groom')
     .map((s) => {
-      const word = s === 'Building' && locking ? 'Locking' : (TRACK_WORDS[s] ?? s);
+      const word = s === 'Building' && locking ? 'Locking' : stageWord(s);
       return s === stage ? `${TRACK_MARK} ${word}` : word;
     })
     .join(' ─ ');

package/dist/cold-read.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// cold-read.mjs — the deterministic half of the `cold-read` skill: the brief, the run, the seal and the compare
+// cold-read.mjs — the deterministic half of the cold-read chapter of the `strategy` skill: the brief, the run, the seal and the compare
 // (coaches-v2 D2–D4).
 //
 //   node scripts/cold-read.mjs brief [--out <file>]   print the agent's brief (the exclusion list is in it); --out

package/dist/cold-read.prompt.md

@@ -8,7 +8,9 @@ the end, says where it goes.
 Skip these, and anything whose purpose is positioning, brand, messaging, landing copy or a strategy method:
 
 - `Roadmap/00-strategy/` (all of it): the makers' own strategy and any earlier cold read
-- any `pmf-narrative`, `north-star`, `risk-validation` or `cold-read` skill folder: the coaching methods
+- the `strategy` skill folder (and, on an older install, any `pmf-narrative`, `north-star`, `risk-validation` or
+  `cold-read` skill folder), and the `refine` skill's `references/coaching.md` and `references/strategy.md`: the
+  coaching methods
 - `references/`, `brand/`, landing-page and marketing copy, positioning or messaging modules
 - `.env*`, secrets, `node_modules/`, `.git/`
 

package/dist/cross-panel.prompt.md

@@ -24,7 +24,7 @@
 ---
 
 You are an **advisory second-opinion reviewer** from a different model family than the agent that is
-grooming this plan. You are reviewing a **proposed plan** — a scope/seed doc for a feature, bug, spike,
+refining this plan. You are reviewing a **proposed plan** — a scope/seed doc for a feature, bug, spike,
 or chore — **before** it gets sliced into an epic and built. Your job is to catch the architecture blind
 spots a same-family planner would miss, while the plan is still cheap to change.
 
@@ -80,7 +80,7 @@ confirm (or kill) your "already modeled / not modeled" assumption.
 ## LENS: architect-pragmatist
 You are the **ship-it pragmatist.** Your question on every line: *what is the thinnest thing that actually
 works and ships, and is this plan over-built for v1?* Push hard on:
-- **Can we already do this today?** (LEARNINGS / the groom skill's "can we already do this?" stage.) Sort
+- **Can we already do this today?** (LEARNINGS / the refine skill's "can we already do this?" stage.) Sort
   the ask into *already-possible* (existing features + the right messaging/positioning — no build),
   *light-enhancement* (a small story or copy/config change on an existing feature), or *genuinely-new*.
   If buckets 1–2 hit the outcome, say so loudly — that's the win. A plan that builds net-new when copy +

package/dist/cross-review.mjs

@@ -109,7 +109,7 @@ export function promptPathFor(lens) {
 
 const BANNER =
   '> **Cross-agent review — every finding is fixed, or answered on this PR, before merge. This does not authorize one.** ' +
-  'CI and the risk-tier merge rule remain the only merge authority. A fresh `pr-reviewer` pass covers context independence; ' +
+  'CI and the risk-tier merge rule remain the only merge authority. A fresh `verifier` pass covers context independence; ' +
   'this is the family-independence pass: one single-pass read by a model family that did not build the diff.';
 
 const HELP = `cross-review.mjs — the cross-agent judgment-layer review for a PR diff.

package/dist/cross-review.prompt.md

@@ -2,7 +2,7 @@
   cross-review.prompt.md — the ONE shared reviewer prompt, read by BOTH readers.
 
   • `scripts/cross-review.mjs` (the external CLI pass) sends everything below the first `---`.
-  • The fresh `pr-reviewer` subagent reads *Shared bar*, *What to check* and *Project rules*, and ignores
+  • The fresh `verifier` subagent reads *Shared bar*, *What to check* and *Project rules*, and ignores
     *CLI reader only*.
 
   One prompt, two independent readers, no drift: that is the whole design (ways-of-work-lean-pass D8).

package/dist/doc-format.enforced.json

@@ -1,4 +1,4 @@
 {
-  "$comment": "Which Roadmap docs `node scripts/doc-format.mjs --check` FAILS on (everything else is reported, not enforced). A trailing \"/\" makes a prefix. A new project enforces all of Roadmap/ — nothing predates the groom templates. A project adopting this late lists files as each area is swept.",
+  "$comment": "Which Roadmap docs `node scripts/doc-format.mjs --check` FAILS on (everything else is reported, not enforced). A trailing \"/\" makes a prefix. A new project enforces all of Roadmap/ — nothing predates the refine templates. A project adopting this late lists files as each area is swept.",
   "enforced": ["Roadmap/"]
 }

package/dist/doc-format.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 // doc-format.mjs — check Roadmap/ epic docs (README.md, sprint-N.md, RETROSPECTIVE.md) against the
-// canonical shape: the `groom` plugin's scaffolding templates (golden-frijoles/skills,
-// skills/groom/templates/) — proven canonical in the project this was ported from by a zero-drift
+// canonical shape: the `refine` plugin's scaffolding templates (golden-frijoles/skills,
+// skills/refine/templates/) — proven canonical in the project this was ported from by a zero-drift
 // control group (81 seeds, one authoring path, identical shape; epic READMEs drift because they get
 // hand-edited after scaffolding, away from the template). dobby-foundation's CI renders a scaffolded
 // epic and runs this checker over it, so the producer validates its own templates.
@@ -392,7 +392,7 @@ export function checkRetrospective(content) {
     // long as the italic markup actually closes somewhere (immediately after the date, or at the end
     // of the line). Require: starts with the italic-open + "Closed:" + a real date, and a closing "_"
     // appears somewhere after that.
-    // The canonical groom scaffold intentionally has no close date yet. Accept its literal sentinel:
+    // The canonical refine scaffold intentionally has no close date yet. Accept its literal sentinel:
     // treating an unbuilt epic as closed would make roadmap-to-notion derive a false Shipped state.
     const isScaffoldPlaceholder = trimmed === '_Closed: <date>_';
     const startsWithDate = /^_Closed:\s*\d{4}-\d{2}-\d{2}/.test(trimmed);

package/dist/doc-hygiene.mjs

@@ -3,7 +3,7 @@
 // candidates in LEARNINGS.md + the README poster. ADVISORY ONLY: this script never edits any
 // Roadmap doc — it only reads them and (unless --check) writes ONE new dated report file under
 // Roadmap/00-ideas/. Every flagged candidate is a hint for a human/model to verify, not a verdict —
-// see the `doc-hygiene` skill (`golden-frijoles` plugin, golden-frijoles marketplace) for the
+// see Step 4 of scripts/routines/roadmap-hygiene.prompt.md for the
 // judgment pass this script's output feeds.
 //
 //   node scripts/doc-hygiene.mjs             # print the report + write Roadmap/00-ideas/DOC-HYGIENE-REPORT-<date>.md
@@ -211,12 +211,12 @@ function buildReport() {
   const date = new Date().toISOString().slice(0, 10);
   const lines = [];
   lines.push(
-    `<!-- Advisory artifact from the doc-hygiene skill (scripts/doc-hygiene.mjs). Findings are proposals`,
+    `<!-- Advisory artifact from the doc-hygiene pass (the roadmap-hygiene routine, step 4) (scripts/doc-hygiene.mjs). Findings are proposals`,
     `     only — no LEARNINGS.md/README.md content was changed by this script. -->`,
     '',
     `# Doc hygiene report — ${date}`,
     '',
-    '🧹 **doc-hygiene skill.** Advisory only — review by hand; nothing here gates or auto-edits.',
+    '🧹 **doc-hygiene pass (the roadmap-hygiene routine, step 4).** Advisory only — review by hand; nothing here gates or auto-edits.',
     '',
     '## Always-read set size',
     ''

package/dist/emit-epic-kickoff.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// emit-epic-kickoff.mjs — print the finished, paste-ready EPIC-MODE kickoff for a groomed epic.
+// emit-epic-kickoff.mjs — print the finished, paste-ready EPIC-MODE kickoff for a refined epic.
 //
 // ── Why this exists ──────────────────────────────────────────────────────────────────────────────────
 // Epic mode — one orchestrated run across a whole epic, sprint files as internal integration boundaries
@@ -28,12 +28,12 @@
 //   npx -y @golden-frijoles/kit emit-epic-kickoff --list [--repo-root <path>]   # the epics a kickoff can start
 //                                       # (live-build-view S2.4): `scaffolded` or `in-progress`, build order first
 //
-// The kickoff's one home is `/build <slug>` (the plugin's mod runs groom's vendored copy of THIS file and fills the
+// The kickoff's one home is `/build <slug>` (the plugin's mod runs refine's vendored copy of THIS file and fills the
 // prompt with its output); hosts without the mod run it through the kit. It is never saved to a file — the epic docs
 // are the state, regenerate it.
 //
 // One source, three homes (kickoff-generator-path C1): this file ships in the kit, a project spawned from the template
-// carries it in `scripts/`, and the groom skill holds a byte-identical copy in `vendor/` (render-hook-vendor.mjs).
+// carries it in `scripts/`, and the refine skill holds a byte-identical copy in `vendor/` (render-hook-vendor.mjs).
 
 import { readFileSync, readdirSync, existsSync, realpathSync } from 'node:fs';
 import { fileURLToPath } from 'node:url';
@@ -108,7 +108,7 @@ export function listEpics(repoRoot, { read = (p) => readFileSync(p, 'utf8'), exi
 
 /** The list as printed: one epic per line, the slug first so it can be typed after `/build `. */
 export function formatEpicList(epics) {
-  if (!epics.length) return 'No scaffolded or in-progress epics under Roadmap/ — groom one first.';
+  if (!epics.length) return 'No scaffolded or in-progress epics under Roadmap/ — refine one first.';
   return epics.map((e) => `${e.slug}  ${e.title}  (${e.status}${e.build_order !== null ? `, #${e.build_order}` : ''})`).join('\n');
 }
 

package/dist/emit-kickoff.mjs

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
-// emit-kickoff.mjs — print the finished, paste-ready Stage-8 Claude Code kickoff for a groomed
-// sprint. Planning-only helper for the `groom` skill (Stage 8). The invariant preamble (the
+// emit-kickoff.mjs — print the finished, paste-ready Stage-8 Claude Code kickoff for a refined
+// sprint. Planning-only helper for the `refine` skill (Stage 8). The invariant preamble (the
 // orientation reads, plan-mode, escalate-don't-guess triggers, etc.) lives in
 // `templates/kickoff.md` — this script's whole point is that boilerplate stops being retyped by
 // hand per sprint; only the sprint-specific delta (epic title, sprint number + its own title,
@@ -10,7 +10,7 @@
 //   npx -y @golden-frijoles/kit emit-kickoff --epic <slug> --sprint N [--repo-root <path>]
 //
 // One source, three homes (kickoff-generator-path C1): this file ships in the kit, a project spawned from the template
-// carries it in `scripts/`, and the groom skill holds a byte-identical copy in `vendor/` (render-hook-vendor.mjs).
+// carries it in `scripts/`, and the refine skill holds a byte-identical copy in `vendor/` (render-hook-vendor.mjs).
 // The template is read from this file's own directory, which is the kit root in all three.
 //
 // Resolves the epic dir by SEARCHING Roadmap/*/<slug>/ under the project root (lib/kickoff-cli.mjs) — the
@@ -19,7 +19,7 @@
 // headings), then substitutes into templates/kickoff.md and prints the result to stdout.
 //
 // It does NOT write any file — this is a read + print tool, same "advisory, editorial control
-// stays with the caller" stance as the other groom/cross-agent scripts in this repo.
+// stays with the caller" stance as the other refine/cross-agent scripts in this repo.
 
 import { readFileSync, existsSync, realpathSync } from 'node:fs';
 import { fileURLToPath } from 'node:url';

package/dist/init.mjs

@@ -4,7 +4,7 @@
 //   node scripts/init.mjs             # write the skeleton into projectRoot(); never overwrite a file
 //
 // ── Why ───────────────────────────────────────────────────────────────────────────────────────
-// A stranger who pastes the install prompt into an EXISTING repo gets the plugin, but `groom` needs
+// A stranger who pastes the install prompt into an EXISTING repo gets the plugin, but `refine` needs
 // somewhere to write on day one — `Roadmap/README.md`, `WAYS-OF-WORKING.md`, `LEARNINGS.md`, and the
 // `00-ideas/` funnel. `frijoles-kit init` is that one step: it writes the same skeleton a project spawned
 // from `template/` already has, into any repo, copied or installed (D2's two roots).

package/dist/intent-match.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// intent-match.mjs — how well a groomed pitch captured the ask it was written from (intent-match S1, D9–D15).
+// intent-match.mjs — how well a refined pitch captured the ask it was written from (intent-match S1, D9–D15).
 //
 //   node scripts/intent-match.mjs <seed.md>             print the score, the band and a route for each gap
 //   node scripts/intent-match.mjs <seed.md> --json      the same, as JSON on stdout (the report goes to stderr)
@@ -7,27 +7,27 @@
 //   node scripts/intent-match.mjs <seed.md> --no-route  skip the second call that routes each gap to an artifact
 //
 // ── ADVISORY, NEVER A GATE (D1) ──────────────────────────────────────────────────────────────────────────────
-// The score can add a step to a groom; it never blocks a scaffold and never removes the product owner's approval.
+// The score can add a step to a refinement; it never blocks a scaffold and never removes the product owner's approval.
 // Nothing reads the exit code as a verdict: 0 means "scored", 2 means "could not look", 1 means a usage error.
 //
 // ── ONE STATISTIC PER QUESTION (D2, D11) ─────────────────────────────────────────────────────────────────────
 // Each signal is one number over Jev Noul/Score answers, so a later calibration can fit weights and bands without
 // re-asking anything (the jev-reanchor spike's lesson). Coverage in = mean P(true) over the ask's claims; coverage
 // out = mean P(true) over the pitch's acceptance criteria; clarity = mean Score ÷ 3 over the same criteria;
-// teach-back = the product owner's answer to groom's Stage 1 mirror (yes 1 · partly 0.5 · no 0). The total is
+// teach-back = the product owner's answer to refine's Stage 1 mirror (yes 1 · partly 0.5 · no 0). The total is
 // 100 × the equal-weight mean of the signals PRESENT, and it always says "uncalibrated" and which signals it used:
 // the 80 / 60 bands are placeholders until `intent-outcomes` has twenty answered epics to fit them against.
 //
 // ── THREE STATES, NEVER TWO ──────────────────────────────────────────────────────────────────────────────────
 // No key, `jev.egress` not `true`, a state over Jev's budget, a timeout or a malformed answer all print "could not
-// look" and NO number. A partial score dressed as a whole one is worse than none: it is the number a groom would
+// look" and NO number. A partial score dressed as a whole one is worse than none: it is the number a refinement would
 // quote. The pitch is never truncated to fit — `askJev` refuses an over-budget state, and so do we.
 //
 // ── NOT A JEV RAIL (C2) ──────────────────────────────────────────────────────────────────────────────────────
 // A rail (`review`, `prose`) is a guard with a regex to fall back to and an off/shadow/jev switch. This decides
 // nothing and has no fallback, so it only reads `jev.egress` and `jev.model`: egress must be an explicit `true`.
 //
-// The seed format this parses is the contract in the epic README's D9 (and groom's `templates/scope-seed.md`):
+// The seed format this parses is the contract in the epic README's D9 (and refine's `templates/scope-seed.md`):
 // `## The ask, as given` → `### Claims` (a numbered list) → `**Teach-back:** yes | partly | no`, and the list under
 // the first `## Acceptance…` heading. Zero deps — Node 18+.
 
@@ -60,7 +60,7 @@ export const BANDS = Object.freeze([
   { min: 0, label: 'sketch or spike first' },
 ]);
 
-/** The artifacts a gap can be routed to (D14) — the visuals rule (groom Stage 4.6) draws from the same words. */
+/** The artifacts a gap can be routed to (D14) — the visuals rule (refine Stage 4.6) draws from the same words. */
 export const ROUTES = Object.freeze({
   copy_deck: 'copy deck',
   wireframe: 'wireframe',

package/dist/intent-reader.mjs

@@ -13,7 +13,7 @@
 // Any failure — no reader CLI, a capped or logged-out CLI, a timeout, an empty or unstructured reply, Jev unable to
 // look — prints exactly ONE line, `reader skipped: <why>`, and exits 0. There is no retry and no second family after
 // one has been asked: free-tier CLIs can be finicky, and three reads of every pitch cost more time than they return
-// (the product owner's call at grooming). Exit 1 is kept for a usage error only.
+// (the product owner's call at refining). Exit 1 is kept for a usage error only.
 //
 // ── NEVER CLAUDE ─────────────────────────────────────────────────────────────────────────────────────────────
 // Planning and building run on Claude; a Claude reader adds no independent read. `FAMILIES` holds no Claude entry
@@ -156,7 +156,7 @@ export function readerSection({ family, agreement, seedComponents, seedTotal, da
     ? `- Seed score: **${seedTotal ?? '—'}** (${Object.entries(seedComponents)
         .map(([k, v]) => `${SIGNAL_NAMES[k]} ${f2(v)}`)
         .join(' · ')})`
-    : '- Seed score: none recorded (run `node scripts/intent-match.mjs <seed> --write` at groom Stage 3.5)';
+    : '- Seed score: none recorded (run `node scripts/intent-match.mjs <seed> --write` at refine Stage 3.5)';
   const lines = [
     '## Intent match',
     '',

package/dist/lib/board-text.mjs

@@ -5,7 +5,7 @@
 //
 // Pure — the caller passes the rows and how fresh their facts are.
 
-import { STAGES, groupByStage } from './stage.mjs';
+import { STAGES, groupByStage, stageWord } from './stage.mjs';
 
 const SHIPPED_SHOWN = 5;
 
@@ -36,7 +36,7 @@ export function renderBoardText(rows, facts = { mode: 'docs' }) {
   const out = [`Board — six stages, ${fresh}`, ''];
   for (const stage of STAGES) {
     const list = columns[stage];
-    out.push(`${stage} (${list.length})`);
+    out.push(`${stageWord(stage)} (${list.length})`);
     const shown = stage === 'Shipped' ? list.slice(0, SHIPPED_SHOWN) : list;
     for (const row of shown) out.push(cardLine(row));
     if (stage === 'Shipped' && list.length > shown.length)

package/dist/lib/config-registry.mjs

@@ -6,8 +6,8 @@
 //
 //   key       dotted, `<section>.<name>`: the path in golden-frijoles.config.json
 //   module    the product module doctor groups it under (Plan · Build · Ship · Measure · Spend · Operate)
-//   askWhen   'setup' | 'first-groom' | 'first-pr' | 'first-smoke' | 'first-report' | 'first-prune'
-//             | 'first-high-risk-groom' | 'never-yet' (declared so the schema is ready; nothing reads it this wave)
+//   askWhen   'setup' | 'first-refine' | 'first-pr' | 'first-smoke' | 'first-report' | 'first-prune'
+//             | 'first-high-risk-refine' | 'never-yet' (declared so the schema is ready; nothing reads it this wave)
 //   default   what a skipped question means. `null` = "unanswered", which a rail must treat as its safest choice
 //   question  the plain words an agent asks, once
 //   choices   optional allowed values; `store: 'env'` means the answer lives in .env.local (frijoles init), never here
@@ -81,14 +81,14 @@ export const REGISTRY = Object.freeze([
   {
     key: 'roadmap.areas',
     module: 'Plan',
-    askWhen: 'first-groom',
+    askWhen: 'first-refine',
     default: ['09 Platform & Infra'],
     question: 'Which areas (macro-sections) does this roadmap have? 09 Platform & Infra is reserved.',
   },
   {
     key: 'ways.fillIns',
     module: 'Plan',
-    askWhen: 'first-groom',
+    askWhen: 'first-refine',
     default: 'Roadmap/fill-ins.yml',
     question: 'Where are this project\'s WAYS-OF-WORKING fill-ins?',
   },
@@ -157,7 +157,7 @@ export const REGISTRY = Object.freeze([
   {
     key: 'ship.killSwitchPolicy',
     module: 'Ship',
-    askWhen: 'first-high-risk-groom',
+    askWhen: 'first-high-risk-refine',
     default: 'every-risk-high-story-names-its-flag',
     question: 'Should every risk:high story name its kill-switch flag?',
   },

package/dist/lib/epic-kickoff.mjs

@@ -1,11 +1,11 @@
 // epic-kickoff.mjs — the epic-mode kickoff, as one pure builder (board-sinks-and-scrumban D17).
 //
-// It used to live only in the groom skill (`emit-epic-kickoff.mjs` + `templates/epic-kickoff.md`), which the kit does
+// It used to live only in the refine skill (`emit-epic-kickoff.mjs` + `templates/epic-kickoff.md`), which the kit does
 // not ship and an installed extractor cannot import (lock C11). The Hub's "Ready to build" card has to carry the same
 // kickoff the CLI prints — a kickoff composed twice is the exact drift `emit-epic-kickoff` was written to end — so
 // the builder, the parsers it reads the docs with and the template text all live here, in the ONE source
-// (`template/scripts/`). The groom skill imports a byte-identical copy that `skills/scripts/render-hook-vendor.mjs`
-// writes into `groom/vendor/` and checks in CI; the extractor imports this file directly.
+// (`template/scripts/`). The refine skill imports a byte-identical copy that `skills/scripts/render-hook-vendor.mjs`
+// writes into `refine/vendor/` and checks in CI; the extractor imports this file directly.
 //
 // The parsers moved here from `emit-kickoff.mjs` unchanged; that file re-exports them, so the per-sprint generator
 // and this one still read the doc format with ONE set of parsers.
@@ -150,7 +150,7 @@ export function buildEpicRules({ risk, texts, appetite = null, slug = '<slug>' }
   const rules = [];
   if (String(risk).toUpperCase() === 'HIGH')
     rules.push(
-      '- **High risk:** the fresh `pr-reviewer` pass is mandatory on every PR, on top of the routed external passes.'
+      '- **High risk:** the fresh `verifier` pass is mandatory on every PR, on top of the routed external passes.'
     );
   if (MIGRATION_RE.test(all))
     rules.push(
@@ -164,7 +164,7 @@ export function buildEpicRules({ risk, texts, appetite = null, slug = '<slug>' }
   if (String(appetite).toUpperCase() === 'L')
     rules.push(
       `- **L bet:** it is funded one wave at a time. When you stop at a wave boundary, ask the product owner one line — ` +
-        `"fund the next wave of \`${slug}\`? what does it displace?" — and on yes run groom's ` +
+        `"Start the next part of \`${slug}\`? What waits for it?" — and on yes run refine's ` +
         `\`fund.mjs --slug ${slug} --displaced "<…>"\` (position kept) before the next wave starts.`
     );
   return rules.length ? `\nFor this epic:\n${rules.join('\n')}\n` : '';

package/dist/lib/golden-onboarding.mjs

@@ -176,7 +176,7 @@ export const INSTALL_PROMPT =
   '2. Tell me in a few lines what it installs, what changes on this machine and which services it contacts. ' +
   'Offer me a security review, and wait for my go-ahead. ' +
   '3. Install it the way install.md says for the agent you are. ' +
-  '4. Run the golden-frijoles skill and start its setup.';
+  '4. Run the setup skill from the golden-frijoles plugin.';
 
 /**
  * The value of `name` in a dotenv file, or null.

package/dist/lib/kickoff-cli.mjs

@@ -4,8 +4,8 @@
 // `emit-epic-kickoff.mjs` and `emit-kickoff.mjs` run in THREE places, the same bytes in each:
 //   • a project's own `scripts/` (copied from the template),
 //   • the kit's `dist/` (`npx -y @golden-frijoles/kit emit-epic-kickoff …`, far from the project),
-//   • the groom skill's `vendor/` inside the plugin (the build-view mod's `/build`, and groom's Stage 8).
-// `projectRoot()` answers the first two. For the third it answers `groom/`, which holds no Roadmap/, so the root takes
+//   • the refine skill's `vendor/` inside the plugin (the build-view mod's `/build`, and refine's Stage 8).
+// `projectRoot()` answers the first two. For the third it answers `refine/`, which holds no Roadmap/, so the root takes
 // one more rung (see `resolveRepoRoot`). The epic lookup lived twice, byte-for-byte, in the two CLIs; it lives here.
 //
 // Zero deps; no side effects at import.
@@ -72,7 +72,7 @@ export function findEpicDir(repoRoot, slug, { exists = existsSync, list = readdi
       return {
         error:
           `"${slug}" is a seed with no epic yet — a kickoff builds an epic. Fund it at the approval gate, then scaffold it ` +
-          `(a fixed-scope seed needs nothing but its slug): node "$GROOM/scaffold-epic.mjs" --slug ${slug}`,
+          `(a fixed-scope seed needs nothing but its slug): node "$REFINE/scaffold-epic.mjs" --slug ${slug}`,
       };
     }
     return { error: `no epic found for slug "${slug}" under any Roadmap/*/ dir in "${repoRoot}" (searched: ${macros.join(', ') || '(none)'})` };

package/dist/lib/result-dates.mjs

@@ -50,7 +50,7 @@ export function todayUtc(now = new Date()) {
  * shipped before the result record existed are never due (the no-backfill rule).
  */
 export function readDateOf({ readDate, targetMetric, shippedAt }) {
-  // A day written at grooming that passes before the epic ships is read on ship day (codex review, #290): there was
+  // A day written at refining that passes before the epic ships is read on ship day (codex review, #290): there was
   // nothing out there to read before then, and "overdue since before release" would be a false alarm.
   const shipped = dayOf(shippedAt);
   if (isDay(readDate))
@@ -67,7 +67,7 @@ export function isLate({ verdictAt, shippedAt }) {
 
 /**
  * Whether a read is due today: a shipped epic with a target, no verdict yet, and a read date that has arrived. An epic
- * not yet shipped is never due, even past a read date written at grooming: there is nothing out there to read.
+ * not yet shipped is never due, even past a read date written at refining: there is nothing out there to read.
  */
 export function isReadDue({ targetMetric, verdict, readDate, shipped }, today = todayUtc()) {
   if (!shipped || !targetMetric || verdict || !isDay(readDate)) return false;

package/dist/lib/roadmap-contract.mjs

@@ -41,7 +41,7 @@ export const EPIC_FIELDS = ['title', 'area', 'risk', 'type', 'phase', 'sprints_t
 export const SPRINT_FIELDS = ['epic', 'sprint', 'title', 'risk', 'phase', 'stories_total', 'stories'];
 export const STORY_FIELDS = ['id', 'title', 'as_a', 'i_want', 'so_that', 'risk', 'status'];
 
-// finops D6/D17 — an epic's quote (written at grooming) and its actual (stamped at close), declared ONCE here.
+// finops D6/D17 — an epic's quote (written at refining) and its actual (stamped at close), declared ONCE here.
 // All optional: an epic scaffolded before FinOps has none, and an absent field is never a zero (D4). The numeric
 // ones are numbers >= 0 or null; a `*_basis` says where the number came from, in words.
 export const FINOPS_NUMERIC_FIELDS = ['quote_low_usd', 'quote_high_usd', 'actual_usd', 'actual_mtok'];
@@ -55,7 +55,7 @@ export const FINOPS_FIELDS = [
   'actual_basis',
 ];
 
-// result-record D1/D2 — the result record: what an epic should move (written at grooming) and its verdict (written at
+// result-record D1/D2 — the result record: what an epic should move (written at refining) and its verdict (written at
 // the read), declared ONCE here. All optional: no target is "no target", never an error. Dates are calendar days.
 export const VERDICTS = ['proven', 'disproven', 'unclear'];
 export const TARGET_FIELDS = ['hypothesis', 'target_metric', 'target_from', 'target_to', 'read_date'];
@@ -140,7 +140,7 @@ export function validateResultFields(fm) {
   return offenses;
 }
 
-// one-epic-page D11 — the epic's flag, decided at groom Stage 6b and copied into the README by the scaffold. The SDK's
+// one-epic-page D11 — the epic's flag, decided at refine Stage 6b and copied into the README by the scaffold. The SDK's
 // flag-key grammar (`FLAG_KEY` in apps/web/lib/flag-admin-operation.ts). Optional: `flag_key: null` (no flag) is the
 // default and never an error; a value that is not a key is named, never pushed (the extract sends null for it).
 export const FLAG_KEY_RE = /^[a-z][a-z0-9_.-]{0,127}$/;

package/dist/lib/stage.mjs

@@ -25,6 +25,16 @@ import { branchCandidates } from './work-branch.mjs';
 /** The six stages, in board order (D1 — locked by the product owner, 2026-10-01). */
 export const STAGES = Object.freeze(['To groom', 'Grooming', 'Ready to build', 'Building', 'QA', 'Shipped']);
 
+/**
+ * What each stage is CALLED where a person reads it (plugin-1-0 D6): plain agile, Backlog → Refining → Ready. The keys
+ * above are stored data and never change; the board, the build view and the terminal board print through `stageWord`.
+ * One known exception: the Notion sync writes the KEY into its `Stage` select, because a select option is data matched
+ * by name (renaming it is a migration of that database: the product owner's call). The console's twin is
+ * `apps/web/lib/screen-words.ts → stageLabel`, and a test keeps the two equal.
+ */
+export const STAGE_WORDS = Object.freeze({ 'To groom': 'Backlog', Grooming: 'Refining', 'Ready to build': 'Ready' });
+export const stageWord = (stage) => STAGE_WORDS[stage] ?? stage;
+
 const DOCS_STAGE = {
   raw: 'To groom',
   ready: 'Grooming',

package/dist/lib/strategy-files.mjs

@@ -1,7 +1,7 @@
 // strategy-files.mjs — where the strategy coaches' files live, and the few shapes every strategy script reads
 // (coaches-v2 D1, D4, D7).
 //
-// groom's own reader (`skills/groom/strategy.mjs`) ships inside the plugin and cannot import from the kit, so it keeps
+// refine's own reader (`skills/refine/strategy.mjs`) ships inside the plugin and cannot import from the kit, so it keeps
 // its own STRATEGY_DIR and KINDS; `skills/scripts/strategy-templates.test.mjs` fails while the two disagree, so a
 // rename lands in both or in neither.
 //

package/dist/lib/surface.mjs

@@ -132,7 +132,7 @@ function parseBlockLine(rest) {
   if (/^[a-z][\w-]*:(\s|$)/.test(rest)) {
     throw (
       '`- <kind>: "…"` is the old list shape — write `- <kind> "words"` (for example `- head "Orders"`); ' +
-      'see groom/references/intent-and-visuals.md'
+      'see refine/references/intent-and-visuals.md'
     );
   }
   const tokens = tokenize(rest);

package/dist/quote.mjs

@@ -7,7 +7,7 @@
 //
 // The quote is the p25–p75 of `actual_usd` over SHIPPED epics at the same appetite — the middle half of what epics
 // that size actually cost here. Until there are MIN_HISTORY of them it is WIDE_DEFAULT, labelled `wide` with its n,
-// never a guess dressed as a calibration (D4). It is recomputed at every groom, so it moves as history accumulates.
+// never a guess dressed as a calibration (D4). It is recomputed at every refinement, so it moves as history accumulates.
 // Epics are read through the extractor (`buildRows`), so appetite follows the board's own rule (README, else seed —
 // D20) and no second frontmatter reader exists.
 //

package/dist/review-route.mjs

@@ -4,7 +4,7 @@
 // ── The rule ──────────────────────────────────────────────────────────────────────────────────────
 //   The highest-preference family that did NOT build the diff runs the general pass.
 //   If the PR touches a security path, the NEXT eligible family runs the lean security lens.
-//   The fresh `pr-reviewer` subagent runs too, in whatever scope the project's review-config.json sets.
+//   The fresh `verifier` subagent runs too, in whatever scope the project's review-config.json sets.
 //
 // That is the whole policy. It replaces a 273-line router with a four-row table, a two-passes-per-PR
 // count, a HIGH-only branch on the fresh reviewer, and the REFUND-ASK / --fallback-after / DARK-layer
@@ -84,7 +84,7 @@ export function planReview({ builder, available = PREFERENCE, securityPass = fal
     else notes.push(`The security lens is triggered but no family can run it. Say so in the PR body.`);
   }
   notes.push(
-    'The fresh `pr-reviewer` subagent runs as well — context independence is a different axis from family independence.'
+    'The fresh `verifier` subagent runs as well — context independence is a different axis from family independence.'
   );
   return { builder, general, security, notes };
 }
@@ -107,7 +107,7 @@ export function renderPlan(plan, pr, repo) {
   l.push('  Run:');
   if (plan.general) l.push(`    ${arg(plan.general)}`);
   if (plan.security) l.push(`    ${arg(plan.security)} --lens security`);
-  l.push(`    then: use the pr-reviewer subagent on PR #${pr}`);
+  l.push(`    then: use the verifier subagent on PR #${pr}`);
   return l.join('\n');
 }
 

package/dist/roadmap-extract.mjs

@@ -613,7 +613,7 @@ export function buildRows({
       area,
       type: TYPE_LABEL[epicFm.type || seed.type] || 'Epic',
       risk,
-      // finops D20 — the README's own appetite first (an epic groomed after FinOps carries it), else the seed's.
+      // finops D20 — the README's own appetite first (an epic refined after FinOps carries it), else the seed's.
       appetite: epicFm.appetite || seed.appetite || null,
       // fund-at-approval D8 — the README's own first (an epic with no seed carries it there), else the seed's.
       underwritten_by: epicFm.underwritten_by || seed.underwritten_by || null,

package/dist/routines/README.md

@@ -138,9 +138,9 @@ restored.)
 1. **Install the Claude GitHub App** on `<root-repo>` (root repo).
 2. **Create the routine** from `roadmap-hygiene.prompt.md`.
 3. **Trigger:** Schedule, **weekly — Mon 14:00 UTC** (after the 08:00 nightly `notion-sync.yml`).
-4. **Env/connectors:** **No Notion connector** — no `.mcp.json`, no `NOTION_TOKEN`. The routine grooms
+4. **Env/connectors:** **No Notion connector** — no `.mcp.json`, no `NOTION_TOKEN`. The routine refines
    the `00-ideas` funnel, flags status-drift, runs `node scripts/build-order.mjs`, invokes the
-   `doc-hygiene` skill (`node scripts/doc-hygiene.mjs` — always-read-set size + LEARNINGS/poster
+   doc-hygiene script (`node scripts/doc-hygiene.mjs` — always-read-set size + LEARNINGS/poster
    dedupe-staleness candidates), and opens a `claude/` **docs PR** with the regenerated
    `BUILD-ORDER.md` + any new `DOC-HYGIENE-REPORT-*.md` + a drift report. Network = GitHub.
 5. **Propagation:** after the product owner merges the docs PR, the existing `notion-sync.yml` propagates
@@ -289,7 +289,7 @@ routine (cap-safe) — see the budget table below.
 Shipped by `ops-routines-reporting` (the origin project's `ops-routines-reporting` epic)
 S3 — a dedicated **weekly** routine (mirroring Routine C's precedent of a standalone weekly schedule,
 rather than a day-of-week-gated step folded into the nightly `ops-nightly` routine). One step: the
-`weekly-recap` skill (`scripts/weekly-recap.mjs`) gathers the week's merged PRs (every configured repo),
+`report` skill's weekly chapter (`scripts/weekly-recap.mjs`) gathers the week's merged PRs (every configured repo),
 shipped/closed epics (README frontmatter `status:` flips), a merges-to-main deploy count per app repo,
 and a short retro digest per shipped epic — then posts one Telegram message.
 
@@ -324,7 +324,7 @@ and a short retro digest per shipped epic — then posts one Telegram message.
 (reads `gh` + `git log` across every configured repo; posts to Telegram; writes `claude/pmo-reports-log`).
 
 Shipped by `pmo-operational-reports` (the origin project's `pmo-operational-reports` epic)
-S3. One step: the `pmo-report` skill (`scripts/pmo-report.mjs --weekly`) gathers scrum/DORA/doc-ops
+S3. One step: the `report` skill's PMO chapter (`scripts/pmo-report.mjs --weekly`) gathers scrum/DORA/doc-ops
 metrics, renders a story-deck URL, posts headline numbers plus the deck link to Telegram, and
 then advances the PMO window log.
 

package/dist/routines/ops-nightly.prompt.md

@@ -12,18 +12,17 @@
 
   Every step here is advisory/observability or a docs-only PR — none merges, none gates, none is a
   required check, and NOTHING here ever runs a destructive `--apply` (that stays a separate,
-  human-confirmed action per the `vercel-prune` skill — this routine only ever runs its dry-run
-  report step).
+  human-confirmed action — this routine only ever runs the dry-run report).
 
-  Skills below come from the `golden-frijoles` plugin (golden-frijoles marketplace,
-  golden-frijoles/skills) — invoke each by name, not
-  by a repo-local `skills/<name>/SKILL.md` path (that path no longer exists in this repo).
+  Steps 1–3 run their scripts directly: the skills that used to wrap them (build-order-sync, vercel-prune, babysit-pr)
+  left the distributed plugin in 1.0 (plugin-1-0 S3.3), and everything they added is written into the steps below.
+  Step 4 uses the plugin's `report` skill, daily chapter.
 
   Reuse, don't rebuild:
-    - `build-order-sync` skill → scripts/build-order-sync.mjs (check/regen/branch/PR on drift)
-    - `vercel-prune` skill → scripts/vercel-prune-previews.mjs (dry-run report only, never --apply)
-    - `babysit-pr` skill → scripts/babysit-pr.mjs (one open PR at a time; silent when clean)
-    - `standup-post` skill → scripts/standup.mjs (the aggregation, diffing, and actual Telegram
+    - scripts/build-order-sync.mjs (check/regen/branch/PR on drift)
+    - scripts/vercel-prune-previews.mjs (dry-run report only, never --apply)
+    - scripts/babysit-pr.mjs (one open PR at a time; silent when clean)
+    - `report` skill's daily chapter → scripts/standup.mjs (the aggregation, diffing, and actual Telegram
       send — including its own independent CI-red / merge-conflict read, taken AFTER steps 1–3 have run)
     - gh CLI (every repo in reporting.config.json's `repos`), scripts/build-order.mjs --check,
       scripts/vercel-prune-previews.mjs (dry-run, --project <vercelProject> --age <stalePreviewAgeDays>), the configured `smoke` workflow.
@@ -40,25 +39,30 @@ running as the product owner. Your job is to run four steps, in order, then stop
 **advisory only** — you never approve, merge, block, or auto-apply anything, and any code/doc change
 you make lands only as a `claude/`-branch PR for a human to review.
 
-## Step 1 — `build-order-sync`
-Use the `build-order-sync` skill: run `node scripts/build-order-sync.mjs`. If the board was
+## Step 1 — build-order sync
+Run `node scripts/build-order-sync.mjs`. If the board was
 stale, it opens a `claude/` docs PR with the regenerated `Roadmap/00-ideas/BUILD-ORDER.md` — nothing
 else to do. If it was already current, no PR — move on.
 
-## Step 2 — `vercel-prune` (dry-run report only)
-Use the `vercel-prune` skill **through Stage 2 only** — the dry-run report. **Never run its
-Stage 3 (`--apply`)** from this routine, under any circumstance; that is a separate, human-initiated
+## Step 2 — stale Vercel previews (dry-run report only)
+Keep every branch with an open PR (an empty list is fine), then run the dry run only:
+
+```bash
+KEEP=$(gh pr list --repo <app-repo> --state open --json headRefName --jq '[.[].headRefName] | join(",")')
+node scripts/vercel-prune-previews.mjs --project <vercelProject> --age <stalePreviewAgeDays> --keep-branch "$KEEP"
+```
+
+**Never pass `--apply`** from this routine, under any circumstance; that is a separate, human-initiated
 action gated on the product owner explicitly asking for it in a live conversation, which this unattended nightly
 run structurally cannot be. Note the stale-preview count/list in your own reasoning — no PR, no
 comment; the standup (step 4) will report it independently.
 
-## Step 3 — `babysit-pr` (once per open PR, across every configured repo)
+## Step 3 — babysit open PRs (once per open PR, across every configured repo)
 For each repo in `reporting.config.json`'s `repos`: list open PRs (`gh pr list --repo <repo> --state open --json
-number`), then use the `babysit-pr` skill once per open PR (`node scripts/babysit-pr.mjs <PR#>
---repo <repo>`). A clean PR gets no comment — that's correct, not a skipped step. Never merge, never
+number`), then run `node scripts/babysit-pr.mjs <PR#> --repo <repo>` once per open PR. A clean PR gets no comment — that's correct, not a skipped step. Never merge, never
 rebase a conflicting branch, never touch any commit-status/check-run API.
 
-## Step 4 — `standup-post`, written by YOU in three phases
+## Step 4 — the standup (the `report` skill, daily chapter), written by YOU in three phases
 
 The standup is no longer a dump of delta lines: **you write it, as the CPO persona, and a mechanical
 guard checks your draft before it posts.**

package/dist/routines/pmo-report.prompt.md

@@ -5,10 +5,10 @@
   It posts the PMO headline metrics plus the story-deck link to Telegram, using the same
   Telegram/load-bearing-output rail as standup-post and weekly-recap.
 
-  Reuse, don't rebuild (the `pmo-report` skill comes from the `golden-frijoles` plugin, golden-frijoles
+  Reuse, don't rebuild (the `report` skill's PMO chapter comes from the `golden-frijoles` plugin, golden-frijoles
   marketplace — invoke by name, not a repo-local
   `skills/<name>/SKILL.md` path, which no longer exists in this repo):
-    - `pmo-report` skill -> scripts/pmo-report.mjs --weekly
+    - `report` skill's PMO chapter -> scripts/pmo-report.mjs --weekly
     - scripts/lib/gh-rest.mjs, scripts/lib/log-branch.mjs, scripts/lib/telegram-format.mjs
     - scripts/lib/pmo-delivery.mjs for message formatting and sendMessage.
 
@@ -33,7 +33,7 @@ code, open a PR, or change a required status check. The Telegram post plus the P
 the entire output.
 
 ## The one step - `pmo-report`
-Use the `pmo-report` skill exactly. It handles the config check (the committed `reporting.config.json`
+Use the `report` skill's PMO chapter exactly. It handles the config check (the committed `reporting.config.json`
 for repos and deck hosting; the chat id from the `TELEGRAM_CHAT_ID` env var in this unattended session), the `TELEGRAM_BOT_TOKEN` check, running
 `node scripts/pmo-report.mjs --weekly`, and reporting the headline metrics plus generated deck link.
 

package/dist/routines/pr-review.prompt.md

@@ -28,7 +28,7 @@ only sources of truth. If anyone reads your output as a decision, say plainly th
 
 **Where you sit in the review stack (updated 2026-07-14 — review-policy flip).** WAYS-OF-WORKING → *Review
 & merge* defines three layers: CI (always), **cross-agent review via `scripts/cross-review.mjs`** (mandatory
-every PR — a *different model family*, run locally), and the **`pr-reviewer` subagent** (mandatory on HIGH
+every PR — a *different model family*, run locally), and the **`verifier` subagent** (mandatory on HIGH
 tier, optional on LOW). **You are none of them.** You do not satisfy the mandatory cross-agent requirement
 — you are the Claude family, and cross-family blind-spot coverage is the entire point of that layer — and
 you do not satisfy the HIGH-tier fresh-reviewer requirement, which is a deliberate, invoked pass against the

package/dist/routines/roadmap-hygiene.prompt.md

@@ -3,7 +3,7 @@
 
   This is the prompt for a weekly Claude Code *Routine* (cloud session, research preview) on the
   monorepo-ROOT repo (<root-repo>), running as the product owner. It adds the JUDGMENT layer the
-  deterministic scripts can't: groom the 00-ideas funnel, flag status-drift, regenerate BUILD-ORDER.md,
+  deterministic scripts can't: refine the 00-ideas funnel, flag status-drift, regenerate BUILD-ORDER.md,
   and open a `claude/` DOCS PR with a drift report.
 
   NO Notion connector by design. The existing `.github/workflows/notion-sync.yml` (nightly + on push)
@@ -16,7 +16,7 @@
     - SSOT = each epic README frontmatter `status:`; seed frontmatter owns the un-scaffolded funnel.
       The extractor emits r.status (authoritative) AND r.status_derived (fallback) so drift is detectable.
     - Funnel docs: Roadmap/00-ideas/README.md (seed lifecycle: raw|ready|queued|scaffolded|in-progress|shipped|archived)
-    - `node scripts/doc-hygiene.mjs` (the `doc-hygiene` skill, `golden-frijoles` plugin) → measures the always-read set + flags
+    - `node scripts/doc-hygiene.mjs` → measures the always-read set + flags
       dedupe/staleness candidates in LEARNINGS.md/the poster; writes its own dated
       Roadmap/00-ideas/DOC-HYGIENE-REPORT-<date>.md — a DIFFERENT concern from this routine's own
       HYGIENE-REPORT-*.md (funnel/status drift). Never auto-edits either.
@@ -30,7 +30,7 @@
 
 You are a weekly **roadmap-hygiene** Claude Code Routine on the monorepo-root repo
 (`<root-repo>`), running as the product owner. Your output is a single `claude/` **docs PR** — you
-groom and flag, you do not merge, deploy, or touch app code. Everything you produce is **advisory**:
+refine and flag, you do not merge, deploy, or touch app code. Everything you produce is **advisory**:
 the human reviews and merges the PR; nothing here gates anything.
 
 ## What "the roadmap" is (read these first)
@@ -42,7 +42,7 @@ the human reviews and merges the PR; nothing here gates anything.
 
 ## Do this in one pass, then open the PR
 
-**1. Groom the `00-ideas` funnel.** Scan `Roadmap/00-ideas/seeds/*.md`:
+**1. Refine the `00-ideas` funnel.** Scan `Roadmap/00-ideas/seeds/*.md`:
 - Flag seeds whose `status:` looks stale vs reality — e.g. a seed marked `scaffolded`/`in-progress`
   whose linked `epic:` README is already `shipped`, or a `ready`/`queued` seed with no movement in a
   long while. Note seeds missing required frontmatter (`slug`/`area`/`status`/`type`).
@@ -62,12 +62,14 @@ one-line reason.
 `Roadmap/00-ideas/BUILD-ORDER.md` from the projection. If it changes, that change goes in the PR; if
 `node scripts/build-order.mjs --check` is already clean, say so (the board was current).
 
-**4. Doc hygiene pass.** Invoke the `doc-hygiene` skill (`golden-frijoles` plugin, golden-frijoles
-marketplace — no longer a repo-local `skills/doc-hygiene/`
-path) — run
-`node scripts/doc-hygiene.mjs`, review any flagged candidates per its Stage 2 (verify before reporting;
-its heuristics are deliberately cheap and can false-positive), and note the always-read set's current
-size. It writes its own dated `Roadmap/00-ideas/DOC-HYGIENE-REPORT-<date>.md` — commit that alongside
+**4. Doc hygiene pass.** Run `node scripts/doc-hygiene.mjs` and verify every flagged candidate before
+reporting it; its heuristics are cheap word-overlap and path checks that narrow where to look, nothing more:
+- *near-duplicate bullets:* read both in context; a shared topic with a different why, date or source is not a
+  duplicate;
+- *dead path:* check every app root before calling a path gone, and a bullet that documents a swap (old → new path)
+  always flags its old path, correctly;
+- *archived-epic mention:* flag it only if the lesson itself, not the epic's name, is now wrong.
+Then note the always-read set's current size. It writes its own dated `Roadmap/00-ideas/DOC-HYGIENE-REPORT-<date>.md` — commit that alongside
 the PR if `--check` wasn't used. **It never edits `LEARNINGS.md`/`README.md`** — a genuine candidate
 worth acting on goes in the PR body as a proposal, same as everything else this routine surfaces.
 
@@ -76,7 +78,7 @@ worth acting on goes in the PR body as a proposal, same as everything else this
   `DOC-HYGIENE-REPORT-*.md` (and only docs under `Roadmap/`). **Docs only — never touch app code,
   scripts, or infra** (running `scripts/doc-hygiene.mjs` is a read-plus-one-new-report tool invocation,
   not a script edit).
-- PR body = the **drift report**: four short sections — *Funnel grooming*, *Status drift*, *Board
+- PR body = the **drift report**: four short sections — *Funnel refining*, *Status drift*, *Board
   regenerated?*, *Doc hygiene* — each a bullet list of findings (or "nothing to flag"). Each finding is
   one line: what, where, and the proposed fix. Lead the PR body with the advisory banner:
   > 🤖 **Routine C — weekly roadmap hygiene (Claude, cloud).** Advisory docs PR — review & merge by hand; nothing here gates.

package/dist/routines/weekly-recap.prompt.md

@@ -9,10 +9,10 @@
   failure-ping) but on a weekly cadence, and mirrors Routine C's precedent (a dedicated weekly routine,
   not a day-of-week-gated step folded into a nightly one).
 
-  Reuse, don't rebuild (the `weekly-recap` skill comes from the `golden-frijoles` plugin, golden-frijoles
+  Reuse, don't rebuild (the `report` skill's weekly chapter comes from the `golden-frijoles` plugin, golden-frijoles
   marketplace — invoke by name, not a repo-local
   `skills/<name>/SKILL.md` path, which no longer exists in this repo):
-    - `weekly-recap` skill → scripts/weekly-recap.mjs (the gathering, message-building, and the
+    - `report` skill's weekly chapter → scripts/weekly-recap.mjs (the gathering, message-building, and the
       actual Telegram send + weekly-recaps.log commit — this routine just invokes it and reports back)
     - gh CLI (every configured repo), git log -p on epic READMEs (status: SSOT), the same configured repo list
       scripts/standup.mjs already uses.

package/dist/skeleton/Roadmap/00-ideas/README.md

@@ -52,7 +52,7 @@ silently to a derived status. A silent fallback makes drift undetectable exactly
 One field is authoritative at each stage — they never both drive the board:
 
 - **Before an epic exists** (`epic: null`) → the **seed's** `status` (`raw`/`ready`/`queued`) is
-  authoritative; you set it by hand or the `groom` skill sets it. This is what the BUILD-ORDER
+  authoritative; you set it by hand or the `refine` skill sets it. This is what the BUILD-ORDER
   **funnel** shows.
 - **Once `epic:` is set** → the **epic README's frontmatter `status:` is the SSOT** (set at epic
   close: `scaffolded` → `in-progress` → `shipped`). The seed is now **funnel-only** — its `status:` is
@@ -64,7 +64,7 @@ One field is authoritative at each stage — they never both drive the board:
 `appetite` (S | M | L) is the **budget the idea is worth**, fixed at shaping *before* the solution
 is designed — sessions + an implied token band, never a time estimate (see WAYS-OF-WORKING →
 *Betting & appetite*). `underwritten_by` names the **cycle that paid for it** — the bare name of a
-`Roadmap/bets/<cycle>.md` file (`wave-2026-10`), written by `groom`'s `fund.mjs` at the approval gate.
+`Roadmap/bets/<cycle>.md` file (`wave-2026-10`), written by `refine`'s `fund.mjs` at the approval gate.
 `null` means nobody has paid for it yet — fine in the funnel, impossible on the board: `build-order.mjs`
 **hard-fails** a `queued` seed with no `appetite`, and a live bet (`queued`, or an epic scaffolded or in
 progress) whose `underwritten_by` is missing or names no cycle file. Like `status`, `appetite` is an
@@ -72,15 +72,15 @@ enforced enum — a present-but-unrecognized value fails the board, it never fal
 
 ## How seeds flow (no file moves)
 
-1. **Capture** — drop a raw idea as `seeds/<slug>.md` with `status: raw` (the `groom` skill does this
+1. **Capture** — drop a raw idea as `seeds/<slug>.md` with `status: raw` (the `refine` skill does this
    from a brain-dump).
-2. **Scope** — `groom` fills out the Definition-of-Ready (appetite included) and flips
+2. **Scope** — `refine` fills out the Definition-of-Ready (appetite included) and flips
    `status: ready`.
-3. **Fund + scaffold, in one answer** — the approval gate is the betting table. On "Approve the plan", `groom`
+3. **Fund + scaffold, in one answer** — the approval gate is the betting table. On "Approve the plan", `refine`
    runs its own `fund.mjs` (a row in the month's `Roadmap/bets/wave-YYYY-MM.md`, created on first use,
    recording what the bet displaced; `underwritten_by:`; a `build_order` placed with `--next` or
    `--after <slug>`, renumbering only the queue) and then `scaffold-epic.mjs` (the epic/sprint docs; the
-   seed gets `epic:` + `status: scaffolded`), committed together. Both ship inside the `groom` skill,
+   seed gets `epic:` + `status: scaffolded`), committed together. Both ship inside the `refine` skill,
    `golden-frijoles` plugin. A fixed-scope seed scaffolds from its slug alone, its acceptance criteria
    becoming sprint 1's stories. "Park it" leaves the seed `ready` and scaffolds nothing.
    **No file ever moves between folders** — the frontmatter carries the state.

package/dist/skeleton/Roadmap/LEARNINGS.md

@@ -162,6 +162,6 @@ one-liner + why + date shape.
 - **Session length is set by a measured line, not a stamina rule.** A whole epic in one session is the
   main context-cost driver, and the durable state (the plan file, sprint docs, team memory) makes
   re-entry cheap by design — so checkpoint or hand off when the budget line says so (its thresholds
-  live in one table, `THRESHOLDS` in groom's `session-budget.mjs`), not per sprint. Groom's twin rule is "one deep ask
+  live in one table, `THRESHOLDS` in refine's `session-budget.mjs`), not per sprint. Refine's twin rule is "one deep ask
   per approval gate". *(Sharpened 2026-09-30, session-budget: "fresh session per sprint" was set for
   earlier models.)*

package/dist/skeleton/Roadmap/WAYS-OF-WORKING.md

@@ -17,7 +17,7 @@ Everything is sliced into **user stories** — the smallest independently testab
 \<role\>, I want \<capability\>, so that \<outcome\>*, plus **acceptance checks the product owner can
 run**. Stories roll up into sprints, sprints into an epic, epics into a macro-section. Before building,
 check whether existing features plus communication already deliver the outcome — surface that lighter
-path first; `groom` gates on it (Stage 2.5).
+path first; `refine` gates on it (Stage 2.5).
 
 ## The cadence
 
@@ -93,13 +93,13 @@ and session context. Fixed appetite, variable scope.
 | **L** | a multi-wave epic | per-wave: each wave is re-bet at the boundary |
 
 Four rules: **an exhausted bet returns to shaping**, never extends in flight; **the approval gate is the
-betting table** — **Approve the plan** in `groom`'s Plan gate funds it in the same answer (`fund.mjs`: a row in
+betting table** — **Approve the plan** in `refine`'s Plan gate funds it in the same answer (`fund.mjs`: a row in
 the month's cycle file `Roadmap/bets/wave-YYYY-MM.md` recording what it displaced, `underwritten_by:`, and a
 build position), in the same commit as the scaffold, while **Park it** leaves it `ready` and scaffolds nothing
-(the gates' words: groom `references/gates.md`); **nothing scaffolded is unfunded** — `build-order.mjs` fails a
+(the gates' words: refine `references/gates.md`); **nothing scaffolded is unfunded** — `build-order.mjs` fails a
 live bet with no `underwritten_by:`;
 and **uphill work stays on the strongest model**. An L bet is re-bet at each wave boundary with one line
-when its builder stops there ("fund the next wave of `<slug>`? what does it displace?"; yes runs `fund.mjs`
+when its builder stops there ("Start the next part of `<slug>`? What waits for it?"; yes runs `fund.mjs`
 again, position kept). Fixed scope (appetite S) and reactive/ops work go through the same gate, straight to
 a builder. Why it works this way:
 [`references/shapeup/`](https://github.com/golden-frijoles/skills/blob/main/template/references/shapeup/README.md).
@@ -111,7 +111,7 @@ questions** — not more reviewers of the same kind.
 
 ```
 CI (deterministic gate)            — does it build, typecheck, pass the suite?   BLOCKS merge
-  → fresh pr-reviewer subagent     — context independence: did not hold the diff
+  → fresh verifier subagent        — context independence: did not hold the diff
   → one external cross-family pass — family independence: different blind spots
   → + a lean security lens         — when the diff touches a security path
   → the builder merges on green
@@ -234,7 +234,7 @@ derived views. **`Roadmap/bets/`** holds one file per wave; **`tasks/`** is the
 - **Worker death is a normal case.** Each builder on its own worktree; a killed worker's uncommitted tree
   is evidence, not garbage; **verify by re-deriving repo state, never by trusting a completion report** —
   a rate-limited subagent still returns a plausible-sounding result. Checkpoint and hand
-  off when the budget line says so (Claude Code: under the prompt; groom: at each approval gate) —
+  off when the budget line says so (Claude Code: under the prompt; refine: at each approval gate) —
   not by sprint count. Where no line shows (function hooks off, or no figure yet), compact at
   sprint/PR boundaries.
 - Commit messages end with the `Co-Authored-By: Claude` trailer.

package/dist/templates/kickoff.md

@@ -17,7 +17,7 @@ api) is green, open a draft PR declaring the risk tier, then flip it ready-for-r
 SMOKE WALKTHROUGH (below) into sprint-{{N}}.md before you call the sprint done.
 Review (WAYS-OF-WORKING → Review & merge): CI always; then run
 `node scripts/review-route.mjs --builder <who-wrote-it> <PR#>` and take what it prints — one external
-general pass, a security lens when the changed paths trigger it, and the fresh `pr-reviewer` subagent, in
+general pass, a security lens when the changed paths trigger it, and the fresh `verifier` subagent, in
 the scope `scripts/review-config.json` sets. A family never reviews its own diff, so don't pick `--agent`
 by hand; a capped family is routed past with `--exclude <family>`, and if only one can run it runs both
 prompts and you say so in the PR body. You merge your own PR on a green gate once findings are resolved.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@golden-frijoles/kit",
-  "version": "0.44.0",
+  "version": "1.0.0",
   "description": "The scripts the Golden Frijoles skills run, packaged so they work in any repo: planning, build-order, reporting and verification rails. Zero dependencies.",
   "type": "module",
   "bin": {