@golden-frijoles/kit 0.43.0 → 1.0.0

package/dist/intent-reader.mjs

@@ -4,7 +4,7 @@
 //   node scripts/intent-reader.mjs --epic <slug> [--timeout <seconds>]
 //
 // The epic kickoff's lock step names this command on every run. With `intent.reader` off — the default — it prints
-// one line and exits before touching any CLI, so it costs nothing. Turned on (`gf-kit config set intent.reader on`),
+// one line and exits before touching any CLI, so it costs nothing. Turned on (`frijoles-kit config set intent.reader on`),
 // it hands the epic's seed (the pitch file, nothing else) to the first of codex, agy and vibe that is installed,
 // once, with a hard timeout, and asks Jev one Noul: would that reader build the same thing as the lock's plan? The
 // answer is the fifth signal, "agreement", and it is written into the epic README's `## Intent match` section.
@@ -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',
     '',
@@ -235,7 +235,7 @@ export async function run(argv, io) {
   const setting = io.setting();
   if (setting !== 'on') {
     io.out(
-      `intent reader: off (intent.reader: ${JSON.stringify(setting)}) — no reader asked. Turn it on with \`gf-kit config set intent.reader on\`.`
+      `intent reader: off (intent.reader: ${JSON.stringify(setting)}) — no reader asked. Turn it on with \`frijoles-kit config set intent.reader on\`.`
     );
     return 0;
   }

package/dist/jev-eval.mjs

@@ -423,7 +423,7 @@ export function formatReport(report) {
 export function liveRefusal(config, getKey) {
   if (config.egress !== true)
     // false: no text leaves this machine; null: nobody has said yes yet (D12). `--live` sends fixtures.
-    return `jev-eval --live: jev.egress is ${JSON.stringify(config.egress)}, not true — refusing to send fixtures to Jev. Say yes with \`gf-kit config set jev.egress true\` first.`;
+    return `jev-eval --live: jev.egress is ${JSON.stringify(config.egress)}, not true — refusing to send fixtures to Jev. Say yes with \`frijoles-kit config set jev.egress true\` first.`;
   if (!getKey())
     return 'jev-eval --live needs TYPESAFE_API_KEY: put TYPESAFE_API_KEY=… in .env.local (or the environment).';
   return null;

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

@@ -1,16 +1,16 @@
 // config-registry.mjs — every setting Golden Frijoles can ask for, in one table (golden-frijoles-plugin S4.3, D11).
 //
 // This is the audit §4.3 table as data. Setup reads it for its questions, a script reads it before asking
-// just-in-time (lib/config.mjs `needSetting`), and `gf doctor` reads it to say which modules are configured. A new
+// just-in-time (lib/config.mjs `needSetting`), and `frijoles doctor` reads it to say which modules are configured. A new
 // setting is a new row here, never a question hard-coded in a skill.
 //
 //   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 (gf init), never here
+//   choices   optional allowed values; `store: 'env'` means the answer lives in .env.local (frijoles init), never here
 //
 // Zero deps, no imports: config.mjs imports THIS, so it must not import back.
 
@@ -42,7 +42,7 @@ export const REGISTRY = Object.freeze([
     choices: ['later', 'now'],
     store: 'env',
     question:
-      'An account adds flags you can roll out and turn off, each bet measured on its read date, every product in one place and an outcome report you can send. Sign in now (recommended: gf login, then gf init), or later?',
+      'An account adds flags you can roll out and turn off, each bet measured on its read date, every product in one place and an outcome report you can send. Sign in now (recommended: frijoles login, then frijoles init), or later?',
   },
   {
     key: 'board.sink',
@@ -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?',
   },
@@ -140,7 +140,7 @@ export const REGISTRY = Object.freeze([
   {
     key: 'routines',
     module: 'Operate',
-    // never-yet: declares the section so readSection accepts it, while `gf doctor` (which skips never-yet
+    // never-yet: declares the section so readSection accepts it, while `frijoles doctor` (which skips never-yet
     // rows) never reports Operate unconfigured for it — its values are per-routine fill-ins that
     // routine-bootstrap.mjs names itself when one is missing (#191 review).
     askWhen: 'never-yet',
@@ -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?',
   },
@@ -173,7 +173,7 @@ export const REGISTRY = Object.freeze([
   },
   {
     // semantic-lint D4: the rules the lint rail's selectors run (id, globs, allowlist, patterns, question). never-yet,
-    // like `routines`: it declares the section so `config get/set` accept it, and `gf doctor` (which skips never-yet
+    // like `routines`: it declares the section so `config get/set` accept it, and `frijoles doctor` (which skips never-yet
     // rows and prints one line per MODULE) never reports Build unconfigured because a project has no lint rules.
     key: 'lint.rules',
     module: 'Build',

package/dist/lib/config.d.mts

@@ -1,5 +1,5 @@
 // Types for lib/config.mjs, the one config core (golden-frijoles-plugin D10). Shipped in @golden-frijoles/kit as
-// `@golden-frijoles/kit/config` so the TypeScript `gf` CLI imports the same rules instead of re-implementing them.
+// `@golden-frijoles/kit/config` so the TypeScript `frijoles` CLI imports the same rules instead of re-implementing them.
 
 export declare const CONFIG_FILENAME: 'golden-frijoles.config.json';
 export declare const SECTIONS: readonly string[];

package/dist/lib/config.mjs

@@ -15,7 +15,7 @@
 // Secrets never go in this file, only the NAMES of the env vars that hold them. `setKey` refuses a value that looks
 // like a credential.
 //
-// Zero deps. Imported by the kit's `gf-kit config` and, via `@golden-frijoles/kit/config`, by the `gf` CLI (D10).
+// Zero deps. Imported by the kit's `frijoles-kit config` and, via `@golden-frijoles/kit/config`, by the `frijoles` CLI (D10).
 
 import { existsSync, readFileSync, realpathSync, renameSync, writeFileSync } from 'node:fs';
 import { join, resolve, sep } from 'node:path';
@@ -24,7 +24,7 @@ import { REGISTRY } from './config-registry.mjs';
 
 // One import for every front end (D10): the CLI's doctor and setup read the registry through this module too.
 export { REGISTRY, MODULES } from './config-registry.mjs';
-// The project root this core reads and writes under, exported so the `gf` CLI resolves the SAME directory (D10).
+// The project root this core reads and writes under, exported so the `frijoles` CLI resolves the SAME directory (D10).
 export { projectRoot } from './project-root.mjs';
 
 export const CONFIG_FILENAME = 'golden-frijoles.config.json';
@@ -271,7 +271,7 @@ export const REDACTED = '<redacted: looks like a secret; keep it in .env.local>'
 
 /**
  * Pure — `value` with every secret-looking string replaced by REDACTED. `loadConfig` and `getKey` are what
- * `config list/get` and `gf doctor` PRINT, and a legacy file may still hold a literal token the write guard never saw
+ * `config list/get` and `frijoles doctor` PRINT, and a legacy file may still hold a literal token the write guard never saw
  * (copy-in review). Rails read through `readSection`, which is never redacted.
  */
 export function redactSecrets(key, value) {

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(
@@ -158,13 +158,13 @@ export function buildEpicRules({ risk, texts, appetite = null, slug = '<slug>' }
     );
   if (FLAG_RE.test(all))
     rules.push(
-      '- **Flag:** create it in Golden Frijoles in every env and ACTIVATE it; `gf flags get <key>` must show production.'
+      '- **Flag:** create it in Golden Frijoles in every env and ACTIVATE it; `frijoles flags get <key>` must show production.'
     );
   // fund-at-approval D7 — an L bet is funded one wave at a time; the re-bet is one line, asked where the builder stops.
   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

@@ -2,7 +2,7 @@
 //
 // ── Why this is a module and not a sentence in three READMEs ───────────────────────────────────
 // golden-flags-by-default S1.4's acceptance is that the text the agent prints, the install page's
-// CLI block and `gf init`'s own next-step line are **one surface**: "the three must say the same
+// CLI block and `frijoles init`'s own next-step line are **one surface**: "the three must say the same
 // thing". Two hand-written copies of `npx @golden-frijoles/cli init` agree right up until one of
 // them is edited, and the one that drifts is always the one nobody runs.
 //
@@ -12,7 +12,7 @@
 //
 // ── The cross-repo half, stated honestly ──────────────────────────────────────────────────────
 // The other two surfaces live in the Golden Frijoles product repo — its `/install` page reads
-// `apps/web/lib/cli-install.ts`, and `gf init` prints from `packages/cli/src/commands/init.ts`.
+// `apps/web/lib/cli-install.ts`, and `frijoles init` prints from `packages/cli/src/commands/init.ts`.
 // This file cannot import either: they are a different repo, and a template that npm-installs a
 // product's web app to read a string would be absurd. The weld there is the same discipline in the
 // other direction (`cli-install.test.ts` reads `packages/cli/package.json` off disk). Here the
@@ -22,10 +22,10 @@
 // reading it.
 //
 // ── The env var names are D6 of the CLI epic, and D3 of this one ──────────────────────────────
-// `gf init` writes exactly three names, and deliberately does NOT write `flag_sync` or an ingest
+// `frijoles init` writes exactly three names, and deliberately does NOT write `flag_sync` or an ingest
 // key: a verb whose job is "let this app READ its flags" must not put wider credentials on disk as
 // a side effect. `flag_sync` is an operator/deploy credential and belongs in CI secrets — minted on
-// purpose with `gf keys create --type flag_sync`. Never both in one place.
+// purpose with `frijoles keys create --type flag_sync`. Never both in one place.
 //
 // Zero deps — Node 18+.
 
@@ -34,7 +34,9 @@ export const CLI_PACKAGE = '@golden-frijoles/cli';
 export const SDK_PACKAGE = '@golden-frijoles/sdk';
 
 /** The binary `npm i -g` puts on PATH. */
-export const CLI_BIN = 'gf';
+export const CLI_BIN = 'frijoles';
+/** The CLI's name before 1.0 (plugin-1-0 D2). Still found, so an older install keeps working until it upgrades. */
+export const LEGACY_CLI_BIN = 'gf';
 
 /**
  * The minimum CLI this template's contract is written against.
@@ -47,8 +49,8 @@ export const CLI_BIN = 'gf';
 export const MIN_CLI_VERSION = '0.1.0';
 
 /**
- * The env var names `gf init` writes and the app reads. ONE definition, on purpose (CLI epic D6):
- * the file and its reader are generated together in `gf init`, and this is that pair's address on
+ * The env var names `frijoles init` writes and the app reads. ONE definition, on purpose (CLI epic D6):
+ * the file and its reader are generated together in `frijoles init`, and this is that pair's address on
  * the template side. `preflight.mjs` and `apps/example-app/flags.mjs` both read it from here.
  */
 export const ENV_KEYS = {
@@ -57,7 +59,7 @@ export const ENV_KEYS = {
   environment: 'GOLDEN_FRIJOLES_ENVIRONMENT',
 };
 
-/** The file `gf init` writes, and refuses to write if it cannot get it into `.gitignore`. */
+/** The file `frijoles init` writes, and refuses to write if it cannot get it into `.gitignore`. */
 export const ENV_FILE = '.env.local';
 
 /** The route a `flag_read` key is exercised against — the one that actually serves it. */
@@ -95,8 +97,8 @@ export const KILL_SWITCH_STORY = [
  * How to read the activation check's answer, in the CLI's OWN vocabulary.
  *
  * ⚠️ **This line shipped wrong once, and the way it was wrong is worth keeping.** It said
- * `gf flags ls --env production` and told the reader to look for the words *"never turned on"*. Two
- * separate errors: `gf flags ls` accepts only `--project` and prints all three environments as
+ * `frijoles flags ls --env production` and told the reader to look for the words *"never turned on"*. Two
+ * separate errors: `frijoles flags ls` accepts only `--project` and prints all three environments as
  * columns, so `--env` is a hard usage error that exits 1 before it ever reaches auth; and *"never
  * turned on here"* is the **web console's** wording, while the CLI's `describeServing` prints `—`.
  * A reader following it literally would have run a command that cannot run, looking for a string
@@ -174,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.
@@ -182,7 +184,7 @@ export const INSTALL_PROMPT =
  * ⚠️ **The LAST assignment wins.** `dotenv` assigns in file order, so a later line overrides an
  * earlier one — and a reader that returns the FIRST will confidently report on a value the running
  * app does not use. Two duplicate lines is not exotic: it is what a hand-edit plus a re-run of
- * `gf init` produces. Same rule, same reason, as the CLI's own `readEnvValue`.
+ * `frijoles init` produces. Same rule, same reason, as the CLI's own `readEnvValue`.
  *
  * No interpolation, deliberately: this reads a file to decide whether a credential is present, and
  * expanding `$VAR` would make that answer depend on the environment doing the reading.

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.
@@ -32,7 +32,7 @@ export function parseArgs(argv) {
 /**
  * The project whose Roadmap/ the kickoff is built from, first match wins:
  *   1. `--repo-root <path>` (the mod always passes it),
- *   2. `GF_PROJECT_ROOT` (`gf-kit --root` sets it), taken as given: a person named it,
+ *   2. `GF_PROJECT_ROOT` (`frijoles-kit --root` sets it), taken as given: a person named it,
  *   3. `projectRoot()` when it holds a Roadmap/ (a project's own `scripts/`, or the installed kit's walk from cwd),
  *      — a copied set answers its own parent, so the template's own copy here answers `skills/template/` (whose
  *        skeleton Roadmap/ has no epics); that is project-root.mjs's copied-mode rule, and no doc runs that copy,
@@ -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/project-root.mjs

@@ -2,7 +2,7 @@
 //
 // A script in this set runs in one of two places:
 //   • COPIED:    the project's own `scripts/<x>.mjs` (a project spawned from the template, or a deliberate fork).
-//   • INSTALLED: `@golden-frijoles/kit`, run by `npx … gf-kit <x>` from npm's cache, far from the project.
+//   • INSTALLED: `@golden-frijoles/kit`, run by `npx … frijoles-kit <x>` from npm's cache, far from the project.
 // The same bytes run in both. What differs is only where "the project" and "my own files" are, so every
 // path goes through exactly one of:
 //

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/preflight.mjs

@@ -20,7 +20,7 @@
 //     true until someone acts, and re-running changes nothing. Saying so loudly is the whole job.
 //
 //   • A REJECTED CREDENTIAL is a hard failure too (exit 1). A 401 is not an outage: the key is
-//     revoked, expired or for another project, and the remedy is another `gf init`.
+//     revoked, expired or for another project, and the remedy is another `frijoles init`.
 //
 //   • AN UNREACHABLE DEPLOYMENT IS A WARNING (exit 0). A transient outage, a captive-portal proxy,
 //     a 404 from a deployment with flag serving switched off, an offline laptop on a plane — none
@@ -39,13 +39,13 @@
 // ── Where this runs: at init and at session start, NOT as a CI gate ───────────────────────────
 // `.env.local` is gitignored — deliberately, it holds a live credential — so a CI checkout does not
 // have one and this check would fail there for a reason that is not a defect. Run it on a fresh
-// spawn, at session start, and after `gf init`. If you DO want it in CI, inject the same variables
+// spawn, at session start, and after `frijoles init`. If you DO want it in CI, inject the same variables
 // from CI secrets (the reader below falls back to the process environment for exactly that) and
 // pass `--offline` if your runner has no egress.
 //
 // ── What it does NOT prove ─────────────────────────────────────────────────────────────────────
 // That any particular flag exists, or that it is ACTIVATED. Definitions are catalog-as-code and
-// activations are not (D4) — `gf flags get <key>` is the verb that answers that, per flag and per
+// activations are not (D4) — `frijoles flags get <key>` is the verb that answers that, per flag and per
 // environment, and a kill-switch story names it as its own step. `—` in its SERVING column means
 // never activated here.
 //
@@ -63,6 +63,7 @@ import { join, resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import {
   CLI_BIN,
+  LEGACY_CLI_BIN,
   CLI_NPX_INIT,
   CLI_GLOBAL_INSTALL,
   DEFAULT_API_URL,
@@ -87,7 +88,7 @@ const ORDER = ['cli', 'cli-version', 'sdk', 'project', 'flag-read-key', 'snapsho
 /**
  * The whole decision, as a pure function of what was found.
  *
- * Every impure act — spawning `gf`, reading `.env.local`, the HTTP probe — happens in `main()` and
+ * Every impure act — spawning `frijoles`, reading `.env.local`, the HTTP probe — happens in `main()` and
  * arrives here as data, so all six states the sprint names (no project · no key · CLI absent · CLI
  * outdated · all good · unreachable) are unit-testable without a network, a CLI or a filesystem.
  *
@@ -136,7 +137,7 @@ export function evaluatePreflight({ cli, sdk = { found: false, source: null }, e
   }
 
   // ── 3. can the APP actually read a flag — is the SDK installed ────────────────────────────
-  // ⚠️ **Added after review.** The CLI and the SDK are different halves: `gf` creates and kills
+  // ⚠️ **Added after review.** The CLI and the SDK are different halves: `frijoles` creates and kills
   // flags, the SDK reads them. Without this check a project reached FIVE GREEN CHECKS, including a
   // live snapshot, while every flag resolved to its call-site default forever — because nothing had
   // ever installed `@golden-frijoles/sdk`. The seam imports it dynamically (deliberately: that is
@@ -226,18 +227,21 @@ export function evaluatePreflight({ cli, sdk = { found: false, source: null }, e
     warnings: warned.length,
     exitCode: failed.length === 0 ? 0 : 1,
     // The remedy is printed whenever the project is not wired — which is exactly the set of
-    // failures `gf init` fixes. A stale CLI is not one of them, so it does not drag the install
+    // failures `frijoles init` fixes. A stale CLI is not one of them, so it does not drag the install
     // block in behind it.
     showOnboarding: failed.some((c) => c.id === 'project' || c.id === 'flag-read-key' || c.id === 'snapshot'),
     checks,
   };
 }
 
-/** Is `gf` runnable, and what does it say its version is? */
+/** Is `frijoles` runnable, and what does it say its version is? */
 export function findCli({ cwd = REPO, spawn = spawnSync } = {}) {
   const candidates = [
     { source: `${CLI_BIN} (PATH)`, command: CLI_BIN },
     { source: `node_modules/.bin/${CLI_BIN}`, command: join(cwd, 'node_modules', '.bin', CLI_BIN) },
+    // An install from before 1.0 has only the old name. Found, but said, so the version check can ask for an upgrade.
+    { source: `${LEGACY_CLI_BIN} (PATH, the old name)`, command: LEGACY_CLI_BIN },
+    { source: `node_modules/.bin/${LEGACY_CLI_BIN} (the old name)`, command: join(cwd, 'node_modules', '.bin', LEGACY_CLI_BIN) },
   ];
   for (const candidate of candidates) {
     const result = spawn(candidate.command, ['--version'], { encoding: 'utf8', timeout: 20_000 });
@@ -325,7 +329,7 @@ export function readEnvFile(path, processEnv = process.env) {
  *
  * Four answers, and the fourth is the one D1 turns on:
  *   live               — a snapshot came back, for the environment this project says it is.
- *   dead               — 401. Unknown, revoked, expired. Configuration: re-run `gf init`.
+ *   dead               — 401. Unknown, revoked, expired. Configuration: re-run `frijoles init`.
  *   wrong-environment  — it resolves, for a DIFFERENT environment. A `flag_read` key is scoped to
  *                        one, so this is a production config holding a development credential with
  *                        nothing anywhere saying so — the worst shape a flag bug has.

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.