rcf-lite 0.9.0 → 0.10.0

package/rcf/user-stories/us-1003.json

@@ -5,16 +5,16 @@
   "version": "0.1.0",
   "status": "draft",
   "title": "Standards ingestion: reference by default, copy only when out of root",
-  "description": "Standards packs are per operator or organisation and register at `rcf init` (or later via `rcf standards add`). Manifest registration is authoritative. In-repo sources are referenced in place. Out-of-root sources are copied into `rcf/standards/<slug>/` so the tree remains portable. Provenance (personal vs corporate) is recorded per pack.",
+  "description": "Standards packs are per operator or organisation and register at `rcf init` (or later via `rcf define standards add`). Manifest registration is authoritative. In-repo sources are referenced in place. Out-of-root sources are copied into `rcf/standards/<slug>/` so the tree remains portable. Provenance (personal vs corporate) is recorded per pack.",
   "asA": "operator on an RCF project",
   "iWant": "to register standards packs against my project tree, referencing in place when the source is already inside the repo and copying into `rcf/standards/<slug>/` only when the source lives outside the project root",
   "soThat": "duplication inside the repo is not accepted, portability across machines is preserved for external sources, and the manifest is the single source of truth for what standards apply",
   "acceptanceCriteria": [
     {
       "id": "AC-1003-1",
-      "description": "`rcf standards add <path>` writes a manifest entry with the pack's id, slug, sourcePath, tag vocabulary, testsProvidedBy and provenance",
+      "description": "`rcf define standards add <path>` writes a manifest entry with the pack's id, slug, sourcePath, tag vocabulary, testsProvidedBy and provenance",
       "given": "a project with no standards registered and a valid standards folder anywhere on disk",
-      "when": "`rcf standards add <path> --slug wsd-naming --tags naming,conventions --tests-provided-by agent --provenance corporate` runs",
+      "when": "`rcf define standards add <path> --slug wsd-naming --tags naming,conventions --tests-provided-by agent --provenance corporate` runs",
       "then": "the manifest gains one `standards[]` entry with all named fields populated and validates against the schema",
       "testable": true
     },
@@ -22,7 +22,7 @@
       "id": "AC-1003-2",
       "description": "In-repo sources are referenced in place; no copy is written",
       "given": "a standards folder path inside the project root (e.g. `docs/standards/wsd-naming`)",
-      "when": "`rcf standards add` runs against it",
+      "when": "`rcf define standards add` runs against it",
       "then": "the `sourcePath` records the in-repo path, `copyPath` is absent, and no file is written under `rcf/standards/`",
       "testable": true
     },
@@ -30,7 +30,7 @@
       "id": "AC-1003-3",
       "description": "Out-of-root sources are mirrored into `rcf/standards/<slug>/` and `copyPath` records the mirror",
       "given": "a standards folder path outside the project root (an absolute path pointing outside the repo)",
-      "when": "`rcf standards add` runs against it",
+      "when": "`rcf define standards add` runs against it",
       "then": "the source is copied into `rcf/standards/<slug>/`, the manifest entry records the original `sourcePath` and the in-tree `copyPath`, and re-running the verb is idempotent (no double copy)",
       "testable": true
     },
@@ -38,7 +38,7 @@
       "id": "AC-1003-4",
       "description": "The manifest.standards[] entry validates against the shipped schema (@stravica-ai/rcf-schemas standardsPackRecord)",
       "given": "a manifest with one or more standards[] entries",
-      "when": "`rcf validate` runs",
+      "when": "`rcf define validate` runs",
       "then": "the manifest validates without errors under the shipped schema",
       "testable": true
     }

package/rcf/user-stories/us-805.json

@@ -1,7 +1,7 @@
 {
   "createdAt": "2026-07-20T17:04:24.904Z",
   "updatedAt": "2026-07-28T16:39:51.461Z",
-  "description": "The method carries guidance for a periodic and end-of-build fresh-context self-review that drives the app against its acceptance criteria to catch the defect classes green test suites miss, honestly scoped as an in-loop check subordinate to the independent verification gate that rcf finalise runs.",
+  "description": "The method carries guidance for a periodic and end-of-build fresh-context self-review that drives the app against its acceptance criteria to catch the defect classes green test suites miss, honestly scoped as an in-loop check subordinate to the independent verification gate that rcf build finalise runs.",
   "asA": "non-coding product owner",
   "iWant": "the build to include a periodic fresh look that actually drives the app against what it is supposed to do",
   "soThat": "defects my passing tests miss are caught before I rely on the result",
@@ -41,7 +41,7 @@
       "description": "The guidance scopes the self-review honestly as an in-loop check and not the independent gate",
       "given": "the self-review guidance",
       "when": "it frames the review",
-      "then": "it states plainly that this is an in-loop check and not the independent verification gate, names rcf finalise (section 7) as the gate, and says it is guidance and not a new subsystem",
+      "then": "it states plainly that this is an in-loop check and not the independent verification gate, names rcf build finalise (section 7) as the gate, and says it is guidance and not a new subsystem",
       "testable": true
     }
   ],

package/rcf/user-stories/us-901.json

@@ -2,39 +2,39 @@
   "usId": "US-901",
   "prdId": "PRD-001",
   "reqId": "REQ-009",
-  "title": "Route `rcf verify` through the same dispatcher as the alias bin",
-  "description": "A consumer running the unified `rcf` CLI can reach the adversarial ship-gate verifier as `rcf verify <verb>` and get identical behaviour to the legacy `rcf-verify <verb>` invocation. The legacy bin remains available and emits a one-line deprecation notice on stderr so scripts can be migrated at their own pace.",
+  "title": "Route the verify suite under the `rcf verify` group and delete the legacy alias bin",
+  "description": "A consumer running the unified `rcf` CLI reaches the adversarial ship-gate verifier as `rcf verify <verb>` (run | report | provision | cleanup | mcp | browser). The pre-0.10.0 standalone `rcf-verify` bin is deleted outright; the historical 0.7.1 transition-grace alias is gone. The old flat `rcf-verify <verb>` invocation form is not available at all; consumers scripting against it must move to `rcf verify <verb>`.",
   "asA": "consumer of the RCF Lite CLI",
   "iWant": "to invoke the verify suite as `rcf verify <verb>` inside the unified CLI",
   "soThat": "verify sits inside the same verb space as the rest of the RCF chain and I only have to install one package",
   "acceptanceCriteria": [
     {
       "id": "AC-901-1",
-      "description": "The `rcf` bin exposes `verify` as a top-level subcommand routed to the same dispatcher as the `rcf-verify` alias bin",
+      "description": "The `rcf` bin exposes `verify` as a top-level group whose sub-verbs run | report | provision | cleanup | mcp | browser dispatch to the verify-suite handlers",
       "given": "the unified `rcf` binary imported from bin/rcf.js",
-      "when": "`verify` is looked up on the top-level SUBCOMMANDS map",
-      "then": "the handler resolves to the same `main` function that bin/rcf-verify.js exports and dispatches over run/report/provision/cleanup/mcp/help",
+      "when": "`verify` is looked up on the top-level GROUPS map",
+      "then": "the sub-verb resolves to the corresponding main() from src/verify/cli/{run,report,provision,cleanup,mcp}.js or src/cli/browser-verify.js",
       "testable": true
     },
     {
       "id": "AC-901-2",
-      "description": "The top-level `rcf --help` output advertises `verify` as an available subcommand",
+      "description": "The top-level `rcf help` output advertises the `verify` group with its sub-verbs",
       "given": "the unified `rcf` binary",
       "when": "`--help` or `help` runs",
-      "then": "the printed usage lists `verify <verb>` alongside the other top-level commands",
+      "then": "the printed usage lists the verify group header with the sub-verb catalogue (run, report, provision, cleanup, mcp, browser)",
       "testable": true
     },
     {
       "id": "AC-901-3",
-      "description": "The `rcf-verify` alias bin emits a one-line stderr deprecation notice when invoked directly and stays fully functional",
-      "given": "the `rcf-verify` alias bin invoked as the entry point (isMain)",
-      "when": "the entry point runs without RCF_QUIET",
-      "then": "a single line describing the deprecation and the `rcf verify` replacement is written to stderr before dispatch, and the dispatch itself is unchanged",
+      "description": "The legacy standalone `rcf-verify` bin is deleted; invoking `rcf-verify <verb>` is not possible from an rcf-lite install, and calling any old flat top-level token via the umbrella `rcf` bin exits 2 with a stderr hint naming the new grouped form",
+      "given": "an installed rcf-lite@0.10.0",
+      "when": "the operator invokes `rcf <old-flat-verb>` where old-flat-verb is a pre-0.10.0 name (validate, coverage, browser-verify, ...)",
+      "then": "package.json:bin carries no `rcf-verify` entry, bin/rcf-verify.js does not exist in the package, and bin/rcf.js writes '[error] usage unknown top-level command <verb>. Try rcf <group> <verb>' to stderr and exits 2 (not a back-compat fallback)",
       "testable": true
     }
   ],
-  "version": "0.1.0",
+  "version": "0.2.0",
   "status": "draft",
   "createdAt": "2026-08-11T00:00:00Z",
-  "updatedAt": "2026-08-11T00:00:00Z"
+  "updatedAt": "2026-08-26T00:00:00Z"
 }

package/src/blueprint/conflicts.js

@@ -45,8 +45,8 @@ import { matchingResolution } from './resolutions.js';
  * )} Conflict
  *
  * `incoming.source` on the globalAdrTopic shape is the CLI-supplied
- * source label the operator typed on `rcf blueprint add SRC`; the
- * renderer inlines it into option 3 (`rcf blueprint supersede <topic>
+ * source label the operator typed on `rcf define blueprint add SRC`; the
+ * renderer inlines it into option 3 (`rcf define blueprint supersede <topic>
  * --incoming <source>`) so the printed command is copy-paste-runnable
  * verbatim from the refused-add state. Absent when the caller did not
  * thread a source label (unit-test paths).
@@ -58,7 +58,7 @@ import { matchingResolution } from './resolutions.js';
  * Optional `manifest` argument: when supplied and the manifest carries a
  * matching entry in `manifest.resolutions[]`, the conflict is honoured
  * (dropped from the returned list). Callers that want the raw shape
- * (`rcf blueprint diff <topic>` needs to inspect both ADRs even when a
+ * (`rcf define blueprint diff <topic>` needs to inspect both ADRs even when a
  * resolution exists) can pass `manifest: null` to bypass the honour step.
  *
  * @param {Array<{
@@ -203,7 +203,7 @@ export function renderConflictReport(conflicts) {
       // Round-3 (Baz ruling): option 3 must be executable VERBATIM
       // from this refused-add state. supersede accepts `--incoming
       // <source>` and carries the SAME source path the operator just
-      // typed on `rcf blueprint add SRC`, so the printed command is
+      // typed on `rcf define blueprint add SRC`, so the printed command is
       // copy-paste-runnable. Fall back to `<source>` only when the
       // caller did not thread the source label onto the conflict
       // (unit-test paths that call renderConflictReport directly).
@@ -212,15 +212,15 @@ export function renderConflictReport(conflicts) {
         : '<source>';
       lines.push('  resolutions (pick one, honest options only):');
       lines.push(`    1. Adopt the incoming blueprint. Run:`);
-      lines.push(`         rcf blueprint remove ${c.existing.slug}`);
-      lines.push(`       then re-run \`rcf blueprint add ${sourceLabel}\`.`);
+      lines.push(`         rcf define blueprint remove ${c.existing.slug}`);
+      lines.push(`       then re-run \`rcf define blueprint add ${sourceLabel}\`.`);
       lines.push(`    2. Keep the existing blueprint. Do not add ${c.incoming.slug} on this project.`);
       lines.push(`    3. Author a project-level ADR that supersedes both. Run:`);
-      lines.push(`         rcf blueprint supersede ${c.topic} --incoming ${sourceLabel}`);
+      lines.push(`         rcf define blueprint supersede ${c.topic} --incoming ${sourceLabel}`);
       lines.push(`       which scaffolds the project ADR (both blueprint ADRs listed as superseded)`);
-      lines.push(`       and registers the resolution in the manifest, then re-run \`rcf blueprint add ${sourceLabel}\`.`);
+      lines.push(`       and registers the resolution in the manifest, then re-run \`rcf define blueprint add ${sourceLabel}\`.`);
       lines.push(`    4. Declare the resolution on the add itself:`);
-      lines.push(`         rcf blueprint add ${sourceLabel} --resolve ${c.topic}=project:<ADR-id>`);
+      lines.push(`         rcf define blueprint add ${sourceLabel} --resolve ${c.topic}=project:<ADR-id>`);
       lines.push(`       which records the resolution and skips the remove/re-add ceremony.`);
     } else if (c.kind === 'crossBlueprintOwnership') {
       lines.push(`conflict on id ${c.id}:`);
@@ -229,7 +229,7 @@ export function renderConflictReport(conflicts) {
       lines.push('');
       lines.push('  resolutions (pick one, honest options only):');
       lines.push(`    1. Adopt the incoming blueprint. Run:`);
-      lines.push(`         rcf blueprint remove ${c.existing.slug}`);
+      lines.push(`         rcf define blueprint remove ${c.existing.slug}`);
       lines.push(`       then re-run the incoming add.`);
       lines.push(`    2. Keep the existing blueprint. Do not add ${c.incoming.slug} on this project.`);
       lines.push(`    3. Fix the incoming blueprint's contribution ids (author-side change);`);
@@ -280,7 +280,7 @@ export function conflictReportJson(conflicts) {
             {
               id: 'adoptIncoming',
               description: `Adopt the incoming blueprint (${c.incoming.slug}); remove the existing (${c.existing.slug}).`,
-              commands: [`rcf blueprint remove ${c.existing.slug}`, `rcf blueprint add ${sourceLabel}`],
+              commands: [`rcf define blueprint remove ${c.existing.slug}`, `rcf define blueprint add ${sourceLabel}`],
             },
             {
               id: 'keepExisting',
@@ -290,12 +290,12 @@ export function conflictReportJson(conflicts) {
             {
               id: 'supersede',
               description: `Author a project-level ADR that supersedes both blueprint ADRs on topic '${c.topic}'.`,
-              commands: [`rcf blueprint supersede ${c.topic} --incoming ${sourceLabel}`, `rcf blueprint add ${sourceLabel}`],
+              commands: [`rcf define blueprint supersede ${c.topic} --incoming ${sourceLabel}`, `rcf define blueprint add ${sourceLabel}`],
             },
             {
               id: 'declareOnAdd',
               description: `Declare the resolution on the incoming add itself.`,
-              commands: [`rcf blueprint add ${sourceLabel} --resolve ${c.topic}=project:<ADR-id>`],
+              commands: [`rcf define blueprint add ${sourceLabel} --resolve ${c.topic}=project:<ADR-id>`],
             },
           ],
         };
@@ -310,7 +310,7 @@ export function conflictReportJson(conflicts) {
           {
             id: 'adoptIncoming',
             description: `Adopt the incoming blueprint (${c.incoming.slug}); remove the existing (${c.existing.slug}).`,
-            commands: [`rcf blueprint remove ${c.existing.slug}`],
+            commands: [`rcf define blueprint remove ${c.existing.slug}`],
           },
           {
             id: 'keepExisting',
@@ -343,7 +343,7 @@ function pruneAdrRef(side) {
   if (typeof side.title === 'string' && side.title.length > 0) out.title = side.title;
   if (typeof side.decision === 'string' && side.decision.length > 0) out.decision = side.decision;
   // Round-3: the incoming side may also carry `source` (the CLI arg
-  // to `rcf blueprint add SRC`); surface it on --json so agent-driven
+  // to `rcf define blueprint add SRC`); surface it on --json so agent-driven
   // composition has the same copy-paste-runnable command the terminal
   // renderer produces.
   if (typeof side.source === 'string' && side.source.length > 0) out.source = side.source;

package/src/blueprint/supersede.js

@@ -1,4 +1,4 @@
-// `rcf blueprint supersede <topic> [--incoming <source>]` implementation.
+// `rcf define blueprint supersede <topic> [--incoming <source>]` implementation.
 //
 // Scaffolds a project-level ADR at `rcf/adrs/adr-NNN-<kebab-topic>.json`
 // that supersedes the CONFLICT PAIR on the topic (one currently-applied
@@ -6,14 +6,14 @@
 // blueprint's scope:global ADR — Baz ruling, w-2026-08-19-008 round 3),
 // and appends a matching `manifest.resolutions[]` record so the conflict
 // detector honours the resolution when the operator re-runs
-// `rcf blueprint add <incoming source>`.
+// `rcf define blueprint add <incoming source>`.
 //
 // The `incomingSource` argument (mapped to `--incoming <source>` on the
 // CLI) is REQUIRED when the applied-blueprints count on the topic is
 // < 2, and silently accepted (informational) when it is already >= 2.
 // This is what makes option 3 as printed by the reshaped conflict
 // message executable VERBATIM from the refused-add state: the operator
-// runs `rcf blueprint supersede <topic> --incoming <source>` immediately
+// runs `rcf define blueprint supersede <topic> --incoming <source>` immediately
 // after the refused add, with zero prep; the verb loads the incoming
 // blueprint from disk, finds its scope:global ADR on <topic>, stamps
 // the id into the incoming blueprint's namespace, and uses that
@@ -85,7 +85,7 @@ export async function supersedeBlueprintTopic({ projectRoot, tree, topic, incomi
   if (typeof topic !== 'string' || topic.trim().length === 0) {
     // Schema minLength:1 accepts whitespace-only; the writer refuses
     // it up-front so a whitespace-only topic never lands on disk.
-    return rcfError({ kind: 'usage', message: `topic is required (e.g. rcf blueprint supersede errorEnvelope --incoming ./blueprints/rest)` });
+    return rcfError({ kind: 'usage', message: `topic is required (e.g. rcf define blueprint supersede errorEnvelope --incoming ./blueprints/rest)` });
   }
   // Topic is a LOOKUP KEY into applied ADR topics, not a slug (ADR-010).
   // Schema is minLength:1 with no character constraint and the schema
@@ -161,7 +161,7 @@ export async function supersedeBlueprintTopic({ projectRoot, tree, topic, incomi
   if (supersedes.length < 2) {
     return rcfError({
       kind: 'usage',
-      message: `topic '${topic}' has ${supersedes.length} scope:global ADR(s) across applied+incoming; at least two are required for a supersession record. If the incoming blueprint has not been named, add \`--incoming <source>\` (the same source you passed to \`rcf blueprint add\`).`,
+      message: `topic '${topic}' has ${supersedes.length} scope:global ADR(s) across applied+incoming; at least two are required for a supersession record. If the incoming blueprint has not been named, add \`--incoming <source>\` (the same source you passed to \`rcf define blueprint add\`).`,
     });
   }
 
@@ -198,7 +198,7 @@ export async function supersedeBlueprintTopic({ projectRoot, tree, topic, incomi
     title: `Project ruling on ${topic} (supersedes ${supersedes.length} blueprint ADR${supersedes.length === 1 ? '' : 's'})`,
     context: `Two or more applied blueprints each contributed a scope:global ADR on the '${topic}' topic: ${superseededSlugs}. Composition of these blueprints on one project needs a single project-level decision on ${topic}; the blueprint ADRs are retained on disk as superseded history.`,
     decision: `Adopt a project-level ruling on ${topic}. This ADR is the live decision; the blueprint ADRs listed under relatedAdrs are superseded and their content stands as historical context only.`,
-    consequences: `The blueprint conflict on topic '${topic}' is honoured via manifest.resolutions[]. Any future blueprint added with a scope:global ADR on '${topic}' must be listed on the resolution (or a fresh resolution must be recorded) before rcf blueprint add proceeds.`,
+    consequences: `The blueprint conflict on topic '${topic}' is honoured via manifest.resolutions[]. Any future blueprint added with a scope:global ADR on '${topic}' must be listed on the resolution (or a fresh resolution must be recorded) before rcf define blueprint add proceeds.`,
     ...(relatedAdrs.length > 0 ? { relatedAdrs } : {}),
     createdAt: isoNow,
     updatedAt: isoNow,

package/src/build/bundle.js

@@ -195,9 +195,9 @@ export function assembleBundle(tree, { fbsId }) {
 
   // Section 7 - completion contract (static, parameterised by fbsId).
   const completionContract = {
-    markInProgress: `rcf build ${fbsId} --mark inProgress`,
-    markComplete: `rcf build ${fbsId} --mark complete`,
-    finalise: `rcf finalise ${fbsId} --url <deploy-url>`,
+    markInProgress: `rcf build mark ${fbsId} inProgress`,
+    markComplete: `rcf build mark ${fbsId} complete`,
+    finalise: `rcf build finalise ${fbsId} --url <deploy-url>`,
   };
 
   const result = {

package/src/build/formatters/markdown.js

@@ -326,7 +326,7 @@ function pushArchitecturalContext(lines, bundle) {
 
 function pushTestSurface(lines, bundle) {
   lines.push(`## ${SECTION_NUMBERS.testSurface}. Existing test surface`, '');
-  lines.push('Presence reporting off the tree, not a coverage verdict (`rcf coverage` is the coverage surface).', '');
+  lines.push('Presence reporting off the tree, not a coverage verdict (`rcf audit coverage` is the coverage surface).', '');
   for (const entry of bundle.tests) {
     if (!entry.covered && entry.suites.length === 0) {
       lines.push(`- ${entry.acId}: no existing tests - test suite to be written for this AC`);
@@ -366,7 +366,7 @@ function pushRunbook(lines, bundle) {
   lines.push('architectural context above ARE the definition. Confirm your plan against');
   lines.push(`every in-scope acceptance criterion (${acIds}) in section 4 before writing`);
   lines.push('code, then mark pickup:', '');
-  lines.push(`    rcf build ${fbsId} --mark inProgress`, '');
+  lines.push(`    rcf build mark ${fbsId} inProgress`, '');
   lines.push('Commit any plan artefacts the driving workflow requires.', '');
 
   lines.push('### Stage 2 - Build', '');
@@ -374,14 +374,14 @@ function pushRunbook(lines, bundle) {
   lines.push('context in section 5. The bundle is the spec: deviation is escalation to');
   lines.push('the operator of the loop, not improvisation. As you implement, author or');
   lines.push('update Code Nodes for the source you write:', '');
-  lines.push('    rcf create cn --path <file>[#symbol] --acs <ac-ids>', '');
+  lines.push('    rcf define create cn --path <file>[#symbol] --acs <ac-ids>', '');
   lines.push('Do this now, not as an afterthought: comprehension of which symbols serve');
   lines.push('which acceptance criteria is cheapest to capture while you are writing the');
   lines.push('code, and Stage 5 refuses completion without it. Commit at stage end.', '');
 
   lines.push('### Stage 3 - Review', '');
   lines.push('Mechanical referee pass:', '');
-  lines.push('    rcf validate', '');
+  lines.push('    rcf define validate', '');
   lines.push('must come back clean; then re-read the diff against every in-scope');
   lines.push('acceptance criterion and document any deviations. Commit.', '');
 
@@ -389,18 +389,18 @@ function pushRunbook(lines, bundle) {
   lines.push('Exercise every in-scope acceptance criterion: write or extend the TS / TC');
   lines.push('documents (section 6 lists the existing surface and the flagged gaps) and');
   lines.push('the tests they point to, until:', '');
-  lines.push('    rcf coverage --strict', '');
+  lines.push('    rcf audit coverage --strict', '');
   lines.push('covers the in-scope acceptance criteria. Commit.', '');
 
   lines.push('### Stage 5 - Finalise', '');
   lines.push('CI green; PR raised and merged per the driving workflow\'s convention.');
   lines.push('After the merge:', '');
-  lines.push(`    rcf build ${fbsId} --mark complete`, '');
+  lines.push(`    rcf build mark ${fbsId} complete`, '');
   lines.push('This refuses (exit 3, missingCodeNodes) if any in-scope acceptance');
   lines.push('criterion still carries no Code Node - go back to Stage 2 and author it,');
   lines.push('or, for a genuinely no-code spec (docs-only, config-only), declare:', '');
-  lines.push(`    rcf build ${fbsId} --mark complete --no-code-nodes`, '');
-  lines.push('Then ship-gate the deployed app - an independent rcf-verify run that');
+  lines.push(`    rcf build mark ${fbsId} complete --no-code-nodes`, '');
+  lines.push('Then ship-gate the deployed app - an independent verify run that');
   lines.push('passes with ship authority promotes complete -> verified:', '');
-  lines.push(`    rcf finalise ${fbsId} --url <deploy-url>`);
+  lines.push(`    rcf build finalise ${fbsId} --url <deploy-url>`);
 }

package/src/build/mark.js

@@ -85,8 +85,8 @@ export function planMark(tree, { fbsId, status }) {
       noOp: false,
       refused: true,
       message: `build: refusing --mark verified on ${fbsId}; 'verified' is written only by the `
-        + `independent verify gate, not by --mark. Promote it with: rcf finalise ${fbsId} --url <deploy-url>. `
-        + `For a deliberate manual override (no verify run) use: rcf update ${fbsId} --set executionStatus=verified`,
+        + `independent verify gate, not by --mark. Promote it with: rcf build finalise ${fbsId} --url <deploy-url>. `
+        + `For a deliberate manual override (no verify run) use: rcf define update ${fbsId} --set executionStatus=verified`,
     };
   }
   const fromIndex = LIFECYCLE.indexOf(from);
@@ -102,7 +102,7 @@ export function planMark(tree, { fbsId, status }) {
       noOp: false,
       refused: true,
       message: `build: refusing backward transition ${from} -> ${status} on ${fbsId}; `
-        + `for a deliberate correction use: rcf update ${fbsId} --set executionStatus=${status}`,
+        + `for a deliberate correction use: rcf define update ${fbsId} --set executionStatus=${status}`,
     };
   }
   return { fbsId, from, to: status, noOp: false };

package/src/build/queue.js

@@ -134,7 +134,7 @@ function findCycleMembers(fbsById) {
  * any item whose chain reaches one, gets tier null (no defined chain
  * length) - the walk short-circuits there, so a cyclic graph can never
  * loop it. A dependency id that resolves to no FBS contributes chain
- * length 0 (same as the platform port; `rcf validate` is the
+ * length 0 (same as the platform port; `rcf define validate` is the
  * broken-reference surface).
  *
  * @param {Map<string, object>} fbsById

package/src/cli/blueprint.js

@@ -23,7 +23,7 @@ import {
 } from '../blueprint/index.js';
 import { conflictReportJson, renderConflictReport } from '../blueprint/conflicts.js';
 
-export const HELP = `Usage: rcf blueprint <verb> [options]
+export const HELP = `Usage: rcf define blueprint <verb> [options]
 
 Verbs:
   add <source>           Apply a blueprint from a source directory
@@ -43,7 +43,7 @@ Verbs:
                          --incoming <source>), and record a
                          manifest.resolutions[] entry so the conflict
                          detector honours the resolution when the
-                         operator re-runs \`rcf blueprint add <source>\`.
+                         operator re-runs \`rcf define blueprint add <source>\`.
                          --incoming is required when the topic has fewer
                          than two applied scope:global ADRs (the
                          refused-add state) and is silently accepted
@@ -82,7 +82,7 @@ Composition and namespacing:
   REQ / US / PRD / BS / TAD / TS: slug PREFIX (spa-REQ-001).
   ADR / TAC / FBS / CN: slug SUFFIX (ADR-005-spa).
   Two blueprints both contributing a scope:global ADR on the same topic
-  is a genuine conflict: rcf blueprint add refuses and prints both
+  is a genuine conflict: rcf define blueprint add refuses and prints both
   sides, plus four resolution paths (adopt incoming, keep existing,
   supersede via project ADR, or declare on the add itself via
   --resolve).

package/src/cli/browser-verify.js

@@ -43,7 +43,7 @@ const OPTION_SPEC = {
   help: { type: 'boolean' },
 };
 
-export const HELP = `Usage: rcf browser-verify <fbs-id> [options]
+export const HELP = `Usage: rcf verify browser <fbs-id> [options]
 
 Stage 5 browser-verification gate for a UI-bearing FBS. Writes a
 browserVerification record on the manifest; the finalise gate reads it.