@golden-frijoles/kit 0.43.0 → 0.44.0

package/README.md

@@ -15,7 +15,7 @@ npx -y @golden-frijoles/kit@<version> --root ../other build-order
   `Roadmap/00-ideas/BUILD-ORDER.md`.
 - **Your own copy wins.** If your project has `scripts/<name>.mjs`, the skills run that instead of the kit, so a
   deliberate fork keeps working. That's by name, so an unrelated `scripts/preflight.mjs` of your own would be run in
-  its place. Rename yours, or pass the script through `gf-kit` directly.
+  its place. Rename yours, or pass the script through `frijoles-kit` directly.
 - **Some files stay yours even when the kit runs:** `scripts/prose/cpo-persona.md`, `scripts/prose-lessons.md`,
   `scripts/cross-panel.prompt.md` and `scripts/doc-format.enforced.json` override the kit's defaults.
 - **Zero dependencies.** A script that drives another tool, like Playwright or a reviewer CLI, uses *your*

package/bin.mjs

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
-// gf-kit — run one of the Golden Frijoles skills' scripts in the current project (golden-frijoles-plugin D1–D3).
+// frijoles-kit — run one of the Golden Frijoles skills' scripts in the current project (golden-frijoles-plugin D1–D3).
 //
-//   gf-kit <name> [args…]        run dist/<name>.mjs against the project you're standing in
-//   gf-kit --root <dir> <name>   …against <dir> instead (exported to the script as GF_PROJECT_ROOT)
-//   gf-kit --list                the scripts this kit carries
-//   gf-kit --version
+//   frijoles-kit <name> [args…]        run dist/<name>.mjs against the project you're standing in
+//   frijoles-kit --root <dir> <name>   …against <dir> instead (exported to the script as GF_PROJECT_ROOT)
+//   frijoles-kit --list                the scripts this kit carries
+//   frijoles-kit --version
 //
 // The script is SPAWNED, never imported: every entry guards `main()` behind an isMain check on process.argv[1]
 // and several end with process.exit, so an import() would silently run nothing. stdio, the exit code and a
@@ -26,7 +26,7 @@ export function listScripts(dist = DIST) {
     .sort();
 }
 
-/** Pure — split gf-kit's own flags from the script's. Only flags BEFORE the script name belong to gf-kit. */
+/** Pure — split frijoles-kit's own flags from the script's. Only flags BEFORE the script name belong to frijoles-kit. */
 export function parseArgs(argv) {
   const out = { root: null, list: false, version: false, help: false, name: null, rest: [] };
   for (let i = 0; i < argv.length; i++) {
@@ -51,7 +51,18 @@ export function parseArgs(argv) {
   return out;
 }
 
-const USAGE = 'usage: gf-kit [--root <dir>] <script> [args…]   ·   gf-kit --list   ·   gf-kit --version';
+const USAGE = 'usage: frijoles-kit [--root <dir>] <script> [args…]   ·   frijoles-kit --list   ·   frijoles-kit --version';
+
+/**
+ * plugin-1-0 D2 — started as the old name `gf-kit`? One line on stderr (stdout is a script's own output, often parsed),
+ * until the date `scripts/check-deprecations.mjs` enforces. Pure, so the test pins it.
+ */
+export function deprecatedNameNotice(invokedPath) {
+  const name = String(invokedPath ?? '').split(/[\\/]/).pop() ?? '';
+  // Unix only: npm's Windows shims start `node …\\bin.mjs`, so argv[1] is the entry file there (verifier, #324).
+  if (name !== 'gf-kit') return null;
+  return 'gf-kit is now frijoles-kit. gf-kit stops working on 2026-12-31 (or in kit 1.1.0).\n';
+}
 
 function main(argv) {
   const args = parseArgs(argv);
@@ -69,12 +80,12 @@ function main(argv) {
     return args.help ? 0 : 2;
   }
   if (args.root === '') {
-    process.stderr.write('gf-kit: --root needs a directory\n');
+    process.stderr.write('frijoles-kit: --root needs a directory\n');
     return 2;
   }
   // A plain name from the list only — never a path, so nothing outside dist/ can be reached through it.
   if (!scripts.includes(args.name)) {
-    process.stderr.write(`gf-kit: no script "${args.name}". This kit carries:\n  ${scripts.join('\n  ')}\n`);
+    process.stderr.write(`frijoles-kit: no script "${args.name}". This kit carries:\n  ${scripts.join('\n  ')}\n`);
     return 2;
   }
   const env = { ...process.env };
@@ -83,21 +94,21 @@ function main(argv) {
     // re-resolved against that cwd in every child (fresh review of #45: pmo-report read zero rows, silently).
     const root = resolve(args.root);
     if (!existsSync(root)) {
-      process.stderr.write(`gf-kit: --root ${args.root}: no such directory\n`);
+      process.stderr.write(`frijoles-kit: --root ${args.root}: no such directory\n`);
       return 2;
     }
     env.GF_PROJECT_ROOT = root;
   }
   const run = spawnSync(process.execPath, [join(DIST, `${args.name}.mjs`), ...args.rest], { stdio: 'inherit', env });
   if (run.error) {
-    process.stderr.write(`gf-kit: could not start ${args.name}: ${run.error.message}\n`);
+    process.stderr.write(`frijoles-kit: could not start ${args.name}: ${run.error.message}\n`);
     return 1;
   }
   if (run.signal) process.kill(process.pid, run.signal);
   return run.status ?? 1;
 }
 
-// npm installs `gf-kit` as a symlink in node_modules/.bin, so compare real paths on both sides.
+// npm installs `frijoles-kit` as a symlink in node_modules/.bin, so compare real paths on both sides.
 const isMain = (() => {
   try {
     return !!process.argv[1] && realpathSync(process.argv[1]) === realpathSync(fileURLToPath(import.meta.url));
@@ -105,4 +116,8 @@ const isMain = (() => {
     return false;
   }
 })();
-if (isMain) process.exitCode = main(process.argv.slice(2));
+if (isMain) {
+  const notice = deprecatedNameNotice(process.argv[1]);
+  if (notice) process.stderr.write(notice);
+  process.exitCode = main(process.argv.slice(2));
+}

package/dist/cold-read.mjs

@@ -316,7 +316,7 @@ function run(root) {
       err: 'cold-read: no other model family reachable (codex is not installed). Run the brief with a same-family agent and record `family: claude (same family)`.',
     };
   }
-  // Codex reads the repository it is started in. Under `gf-kit --root <dir>` that is not this process's cwd, so move
+  // Codex reads the repository it is started in. Under `frijoles-kit --root <dir>` that is not this process's cwd, so move
   // there first: otherwise it reads one repo and the read is sealed into another's strategy folder (review of #314).
   process.chdir(root);
   const r = tryCodex(brief, '');

package/dist/config.mjs

@@ -1,19 +1,19 @@
 #!/usr/bin/env node
-// config.mjs — `gf-kit config`: read and change golden-frijoles.config.json (golden-frijoles-plugin S4.1, D10).
+// config.mjs — `frijoles-kit config`: read and change golden-frijoles.config.json (golden-frijoles-plugin S4.1, D10).
 //
-//   gf-kit config list [--json]            every section's effective value, where it came from, any duplicates
-//   gf-kit config get <key> [--json]       one key's effective value (or its registry default)
-//   gf-kit config set <key> <value>        write one key; <value> is parsed as JSON when it is valid JSON
-//   gf-kit config migrate [--dry-run]      fold the legacy files into golden-frijoles.config.json (never edits them)
+//   frijoles-kit config list [--json]            every section's effective value, where it came from, any duplicates
+//   frijoles-kit config get <key> [--json]       one key's effective value (or its registry default)
+//   frijoles-kit config set <key> <value>        write one key; <value> is parsed as JSON when it is valid JSON
+//   frijoles-kit config migrate [--dry-run]      fold the legacy files into golden-frijoles.config.json (never edits them)
 //
 // A thin front end: every rule (precedence, the secret guard, what migrate folds) lives in lib/config.mjs, which the
-// `gf` CLI imports too. Exit 0 ok · 1 usage · 2 configuration error (a malformed file, a secret, an unknown section).
+// `frijoles` CLI imports too. Exit 0 ok · 1 usage · 2 configuration error (a malformed file, a secret, an unknown section).
 
 import { realpathSync } from 'node:fs';
 import { fileURLToPath } from 'node:url';
 import { CONFIG_FILENAME, ConfigError, getKey, loadConfig, migrate, setKey } from './lib/config.mjs';
 
-const USAGE = 'usage: gf-kit config list|get <key>|set <key> <value>|migrate [--dry-run] [--json]';
+const USAGE = 'usage: frijoles-kit config list|get <key>|set <key> <value>|migrate [--dry-run] [--json]';
 
 /** Pure — a CLI value: JSON when it parses (true, 3, ["a"], null), otherwise the literal string. */
 export function parseValue(text) {
@@ -63,7 +63,7 @@ export function main(argv, { out = (s) => process.stdout.write(s), err = (s) =>
     }
   } catch (e) {
     if (e instanceof ConfigError) {
-      err(`gf-kit config: ${e.message}\n`);
+      err(`frijoles-kit config: ${e.message}\n`);
       return 2;
     }
     throw e;

package/dist/epic-actuals.mjs

@@ -660,7 +660,7 @@ export async function pushUsage({
     return { sent: 0, reason: `config unreadable — ${err && err.message ? err.message : err}` };
   }
   if (setting !== 'on')
-    return { sent: 0, reason: 'off — spend.telemetry is not on (gf-kit config set spend.telemetry on)' };
+    return { sent: 0, reason: 'off — spend.telemetry is not on (frijoles-kit config set spend.telemetry on)' };
   // The throttle counts ATTEMPTS, not successes: a persistent 401 or 429 retries every 10 minutes, not every minute.
   const last = Math.max(index.pushed_at ?? -Infinity, index.push_attempt_at ?? -Infinity);
   if (throttle && Number.isFinite(last) && now - last < PUSH_EVERY_MS)

package/dist/epic-read.mjs

@@ -1,14 +1,14 @@
 #!/usr/bin/env node
 // epic-read.mjs — read an epic's result on its read date: draft the verdict with its evidence; write it on approval.
 //
-//   node scripts/epic-read.mjs --epic <slug>                               # fetches the number through gf, drafts
+//   node scripts/epic-read.mjs --epic <slug>                               # fetches the number through frijoles, drafts
 //   node scripts/epic-read.mjs --epic <slug> --experiment smart-defaults   # … and cites the A/B decision record
 //   node scripts/epic-read.mjs --epic <slug> --actual 72 --evidence north-star:invoices_paid_on_time@2026-11-04
 //   node scripts/epic-read.mjs --epic <slug> --evidence "traffic too low (n = 18)"          # no number: unclear
 //   node scripts/epic-read.mjs --epic <slug> --verdict proven --evidence https://…           # an owner verdict
 //   … --write                                                              # the approval: stamp verdict_* into the README
-//   options: --project <slug> (gf's; default: the remembered one) · --today YYYY-MM-DD (default: today, UTC)
-//            · --repo-root <dir> · --json · GF_BIN=<path to gf> (default: gf on PATH)
+//   options: --project <slug> (frijoles's; default: the remembered one) · --today YYYY-MM-DD (default: today, UTC)
+//            · --repo-root <dir> · --json · GF_BIN=<path to frijoles> (default: frijoles on PATH)
 //
 // ── The shape (result-record D8) ─────────────────────────────────────────────────────────────────────────────────
 // The agent does the legwork, the owner decides. Without `--write` this prints a draft and the exact command that
@@ -25,11 +25,11 @@
 //   • An epic shipped with no target can be read too — an owner verdict and its evidence, one epic per run.
 //
 // ── The agent fetches the number (result-record S3, D17) ─────────────────────────────────────────────────────────
-// With a target and no `--actual`, this runs `gf north-star readings <target_metric> --to <today> --json` and takes
+// With a target and no `--actual`, this runs `frijoles north-star readings <target_metric> --to <today> --json` and takes
 // `latest`: the actual is its value, the evidence `north-star:<input>@<its day>`. A reading dated before the epic shipped
-// is no evidence for it. `--experiment <key>` also runs `gf experiments decision <key> --json`; a recorded decision
-// becomes the evidence, `ab:<key>`. gf is spawned without a shell (`$GF_BIN`, else `gf` on PATH), so a shell alias of
-// the same name never applies. `--actual` / `--evidence` still win: they are the owner's word. No gf, not signed in, no
+// is no evidence for it. `--experiment <key>` also runs `frijoles experiments decision <key> --json`; a recorded decision
+// becomes the evidence, `ab:<key>`. frijoles is spawned without a shell (`$GF_BIN`, else `frijoles` on PATH), so a shell alias of
+// the same name never applies. `--actual` / `--evidence` still win: they are the owner's word. No frijoles, not signed in, no
 // project chosen, or any failure is one "could not fetch (why)" line, and the read asks the owner as before — it never
 // fails because the platform is not linked. Grounded is now "the readings route knows this input".
 
@@ -138,17 +138,22 @@ export function planRead({ fm, shippedAt, shipped, today, actual = null, evidenc
   return { state: 'ready', target, drafted, owner, fields, late, readDate, derived };
 }
 
-/** Run one `gf … --json` and read its single JSON document. Never throws; `why` says what went wrong in words. */
+/** Run one `frijoles … --json` and read its single JSON document. Never throws; `why` says what went wrong in words. */
 export function runGf(args, { env = process.env, spawnFn = spawnSync } = {}) {
-  const bin = env.GF_BIN || 'gf';
-  const res = spawnFn(bin, [...args, '--json'], { encoding: 'utf8', timeout: 30_000, env, shell: false });
+  // `frijoles` since CLI 1.0; `gf` is the name an older install still has (plugin-1-0 D2). GF_BIN pins one.
+  const bins = env.GF_BIN ? [env.GF_BIN] : ['frijoles', 'gf'];
+  let res = null;
+  for (const bin of bins) {
+    res = spawnFn(bin, [...args, '--json'], { encoding: 'utf8', timeout: 30_000, env, shell: false });
+    if (res.error?.code !== 'ENOENT') break; // only "not installed under this name" tries the next name
+  }
   if (res.error)
     return {
       ok: false,
       why:
         res.error.code === 'ENOENT'
-          ? 'gf is not installed (npm i -g @golden-frijoles/cli, then gf login)'
-          : `gf did not run: ${res.error.message}`,
+          ? 'frijoles is not installed (npm i -g @golden-frijoles/cli, then frijoles login)'
+          : `frijoles did not run: ${res.error.message}`,
     };
   let body = null;
   try {
@@ -157,13 +162,13 @@ export function runGf(args, { env = process.env, spawnFn = spawnSync } = {}) {
     body = null;
   }
   if (body && body.ok === true) return { ok: true, body };
-  if (res.status === 2) return { ok: false, code: 'unauthorized', why: 'gf is not signed in (run gf login)' };
+  if (res.status === 2) return { ok: false, code: 'unauthorized', why: 'frijoles is not signed in (run frijoles login)' };
   const code = body?.code ?? null;
-  return { ok: false, code, why: body?.error ?? `gf exited ${res.status}` };
+  return { ok: false, code, why: body?.error ?? `frijoles exited ${res.status}` };
 }
 
 /**
- * The number and its evidence, fetched through gf (D17). Pure apart from the injected `run`.
+ * The number and its evidence, fetched through frijoles (D17). Pure apart from the injected `run`.
  * Returns `{ fetched, actual?, evidence?, reading?, decision?, grounded, why? }`.
  */
 export function fetchEvidence({ metric, experiment = null, today, shippedAt, project = null, run }) {
@@ -214,12 +219,12 @@ export function renderPlan(plan, { slug, fetched, write, written }) {
       out.push(`  not grounded: ${t.metric} is not one of the project's North Star inputs`);
     if (fetched.fetched)
       out.push(
-        `  fetched:  ${fig(fetched.reading.value)} on ${longDay(fetched.reading.date)} (gf north-star readings)`
+        `  fetched:  ${fig(fetched.reading.value)} on ${longDay(fetched.reading.date)} (frijoles north-star readings)`
       );
     else if (fetched.why) out.push(`  could not fetch the number: ${fetched.why}`);
     if (fetched.decision)
       out.push(
-        `  decision: ${fetched.decision.outcome ?? 'recorded'}${fetched.decision.chosenVariantKey ? ` (${fetched.decision.chosenVariantKey})` : ''} (gf experiments decision)`
+        `  decision: ${fetched.decision.outcome ?? 'recorded'}${fetched.decision.chosenVariantKey ? ` (${fetched.decision.chosenVariantKey})` : ''} (frijoles experiments decision)`
       );
     else if (fetched.decisionWhy) out.push(`  decision: ${fetched.decisionWhy}`);
   }

package/dist/init.mjs

@@ -1,12 +1,12 @@
 #!/usr/bin/env node
-// init.mjs — `gf-kit init`: adopt any repo by writing the Roadmap/ skeleton (golden-frijoles-plugin S3.2, D2).
+// init.mjs — `frijoles-kit init`: adopt any repo by writing the Roadmap/ skeleton (golden-frijoles-plugin S3.2, D2).
 //
 //   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
 // somewhere to write on day one — `Roadmap/README.md`, `WAYS-OF-WORKING.md`, `LEARNINGS.md`, and the
-// `00-ideas/` funnel. `gf-kit init` is that one step: it writes the same skeleton a project spawned
+// `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).
 //
 // ── Where the skeleton's SOURCE lives ─────────────────────────────────────────────────────────
@@ -45,7 +45,7 @@ import { dirname, join, resolve } from 'node:path';
 import { isInstalled, kitRoot, projectRoot } from './lib/project-root.mjs';
 
 /**
- * The Roadmap skeleton `gf-kit init` writes, relative both to its source root (template/, or
+ * The Roadmap skeleton `frijoles-kit init` writes, relative both to its source root (template/, or
  * kit/dist/skeleton/ once built) and to the project it writes into. ONE list: `build-kit.mjs` reads
  * this export to populate `kit/dist/skeleton/`, so there is no second copy of the file names to drift.
  */
@@ -104,7 +104,7 @@ export function initSkeleton({
 }
 
 /**
- * True when `project` resolves to the operator's own home directory — the one place `gf-kit init`
+ * True when `project` resolves to the operator's own home directory — the one place `frijoles-kit init`
  * must never write, even though `projectRoot()`'s walk-up can legitimately land there (a non-git
  * folder under a dotfiles repo tracked at `$HOME`). Pure given its injected `home`.
  */
@@ -116,7 +116,7 @@ function main() {
   const project = projectRoot();
   if (isHomeDirectory({ project })) {
     console.error(
-      `gf-kit init: refusing to run — the resolved project root is your home directory (${project}).\n` +
+      `frijoles-kit init: refusing to run — the resolved project root is your home directory (${project}).\n` +
         '  This usually means no Roadmap/ or .git was found between the current directory and $HOME,\n' +
         '  and $HOME itself is a git repo (a dotfiles checkout, for example). Run this from inside a\n' +
         '  real project — a directory with its own .git — or pass --root explicitly.'
@@ -124,7 +124,7 @@ function main() {
     return 2;
   }
   const { wrote, skipped } = initSkeleton({ project, log: (line) => console.log(line) });
-  console.log(`gf-kit init: ${wrote.length} written, ${skipped.length} already present.`);
+  console.log(`frijoles-kit init: ${wrote.length} written, ${skipped.length} already present.`);
   return 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.
@@ -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/config-registry.mjs

@@ -1,7 +1,7 @@
 // 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
@@ -10,7 +10,7 @@
 //             | 'first-high-risk-groom' | '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',
@@ -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',
@@ -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

@@ -158,7 +158,7 @@ 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')

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
@@ -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

@@ -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,

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/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/package.json

@@ -1,9 +1,10 @@
 {
   "name": "@golden-frijoles/kit",
-  "version": "0.43.0",
+  "version": "0.44.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": {
+    "frijoles-kit": "bin.mjs",
     "gf-kit": "bin.mjs"
   },
   "files": [