rcf-lite 0.9.0 → 0.11.0

package/src/cli/validate.js

@@ -18,7 +18,7 @@ const OPTION_SPEC = {
   'no-code': { type: 'boolean' },
 };
 
-export const HELP = `Usage: rcf validate [options]
+export const HELP = `Usage: rcf define validate [options]
 
 Walk the rcf/ tree and report schema-validation and broken-reference
 issues. Exits 0 when clean, 3 on issues.
@@ -140,7 +140,7 @@ export async function main(argv, deps = {}) {
   }
   if (errors.length === 0) {
     if (!flags.quiet) {
-      stdout.write('rcf validate: tree is clean.\n');
+      stdout.write('rcf define validate: tree is clean.\n');
       // B4 (E2E matrix 2026-07-06-003): scaffold TODO placeholders were
       // surviving to otherwise-valid trees unflagged. Non-blocking notice
       // only - the exit code is unchanged.

package/src/cli/view.js

@@ -24,7 +24,7 @@ import { parsePersistUntil } from '../view-supervisor/persist-until.js';
 export const DEFAULT_PORT = 4373;
 export const SHUTDOWN_BUDGET_MS = 2000;
 
-export const HELP = `Usage: rcf view [subverb] [options]
+export const HELP = `Usage: rcf audit view [subverb] [options]
 
 Serve the on-disk RCF tree as a live HTML review surface. Runs a
 long-running HTTP + SSE server on 127.0.0.1 that watches rcf/ and pushes
@@ -32,10 +32,10 @@ tree updates to the connected browser tab. No on-disk output; no static
 files are written.
 
 Subverbs (spec §9.2):
-  rcf view                  Foreground server (default; lifetime tied to
+  rcf audit view            Foreground server (default; lifetime tied to
                             the invoking session). Backward-compatible
                             with pre-0.7.0 callers.
-  rcf view start [--detach|--foreground] [--persist-until <duration|iso>]
+  rcf audit view start [--detach|--foreground] [--persist-until <duration|iso>]
                             Start the server. --detach forks a supervised
                             background process that persists across the
                             parent session's death; the manifest carries
@@ -50,12 +50,14 @@ Subverbs (spec §9.2):
                             --detach; non-interactive callers keep
                             --foreground so a script does not orphan a
                             process.
-  rcf view status [--json]  Print the supervisor state:
+  rcf audit view status [--json]
+                            Print the supervisor state:
                             running | stale | not-started.
-  rcf view stop             Send SIGTERM to the supervised process, wait
+  rcf audit view stop       Send SIGTERM to the supervised process, wait
                             for a clean shutdown, and clear the manifest
                             record.
-  rcf view logs [--tail <n>] Print the supervisor log tail (default 200).
+  rcf audit view logs [--tail <n>]
+                            Print the supervisor log tail (default 200).
 
 Options:
   --port <n>        Bind the HTTP server on the given port.
@@ -83,7 +85,7 @@ Security posture:
 Shutdown:
   Ctrl-C (SIGINT) or SIGTERM triggers a clean shutdown: watcher
   closed, SSE connections drained with a shutdown event, port
-  released, 2s force-exit budget. Detached: rcf view stop sends
+  released, 2s force-exit budget. Detached: rcf audit view stop sends
   SIGTERM to the supervisor and waits for a clean unwind.
 
 Exit codes:
@@ -213,7 +215,7 @@ export function maybeAutoOpen({ target, noOpen, stream, env, stderr, spawnFn = s
 }
 
 /**
- * Main entry for the `rcf view` subcommand. Mirrors the shape of the
+ * Main entry for the `rcf audit view` subcommand. Mirrors the shape of the
  * old bin/rcf-view.js main().
  *
  * @param {string[]} argv - the argv slice *after* the "view" positional
@@ -278,7 +280,7 @@ export async function main(argv, deps = {}) {
     });
   } catch (err) {
     if (/** @type {NodeJS.ErrnoException} */ (err).code === 'EADDRINUSE') {
-      stderr.write(`[error] usage port ${resolvedPort} is in use (another rcf view process, or a different service).\n`);
+      stderr.write(`[error] usage port ${resolvedPort} is in use (another rcf audit view process, or a different service).\n`);
       stderr.write('Pass --port <n> or set RCF_VIEW_PORT to pick a free port.\n');
       return 2;
     }
@@ -286,7 +288,7 @@ export async function main(argv, deps = {}) {
     return 1;
   }
 
-  stdout.write(`rcf view server listening at ${server.url}\n`);
+  stdout.write(`rcf audit view server listening at ${server.url}\n`);
   stdout.write('watching rcf/ - Ctrl-C to shut down\n');
 
   maybeAutoOpen({

package/src/core/store/writer.js

@@ -1286,7 +1286,7 @@ export async function deleteDocument({ projectRoot, tree, id, options = {}, walk
   if (rootKinds.has(kind)) {
     return rcfError({
       kind: 'usage',
-      message: `delete: root singleton ${id} cannot be deleted via rcf delete`,
+      message: `delete: root singleton ${id} cannot be deleted via rcf define delete`,
       documentId: id,
     });
   }

package/src/design/writer.js

@@ -180,7 +180,7 @@ export async function writeMarkComplete({
     return rcfError({
       kind: 'usage',
       message: `design --mark-complete: refused - ${fbsId} designStage is missing: ${missing.join(', ')}. `
-        + 'Author the missing artefacts first via `rcf design ' + fbsId + ' journeys add ...`, `nav set ...`, or `theme-a11y set ...`.',
+        + 'Author the missing artefacts first via `rcf define design ' + fbsId + ' journeys add ...`, `nav set ...`, or `theme-a11y set ...`.',
       documentId: fbsId,
     });
   }
@@ -189,8 +189,8 @@ export async function writeMarkComplete({
     return rcfError({
       kind: 'usage',
       message: `design --mark-complete: refused - ${fbsId} designStage.${disagreement.designStagePath} = ${JSON.stringify(disagreement.designValue)} conflicts with uiBaseline.defaults.${disagreement.path} = ${JSON.stringify(disagreement.baselineValue)} and there is no operatorOptOuts entry. `
-        + 'Options: (1) change designStage to match, (2) rcf ui-baseline opt-out --field '
-        + disagreement.path + ' --reason "..." (project override), (3) rcf update '
+        + 'Options: (1) change designStage to match, (2) rcf discover ui-baseline opt-out --field '
+        + disagreement.path + ' --reason "..." (project override), (3) rcf define update '
         + fbsId + ' --set designStage.' + disagreement.designStagePath + '=... (per-FBS override).',
       documentId: fbsId,
     });

package/src/finalise/detect.js

@@ -1,36 +1,35 @@
-// rcf-verify install detection (spec §8.3, amendment 5 - install-together
-// posture). The finalise gate MUST detect whether `rcf-verify` is resolvable
-// and, when it is absent, prompt to install it - NEVER silently skip the ship
-// gate (the one behaviour §8.3 explicitly forbids).
+// rcf verify install detection (spec §8.3, amendment 5 - install-together
+// posture). The finalise gate MUST detect whether the `rcf` bin (which
+// carries the `verify` group) is resolvable and, when it is absent,
+// prompt to install rcf-lite - NEVER silently skip the ship gate (the
+// one behaviour §8.3 explicitly forbids).
 //
-// Two detection routes, in order, matching how the CLI is actually installed:
-//   1. The `rcf-verify` bin on PATH - the umbrella install exposes both `rcf`
-//      and `rcf-verify` as global bins (`npm i -g rcf-lite`).
-//   2. Package resolution from the project dir - the local-project install
-//      (`npm i rcf-lite` in a repo's node_modules). Two package specifiers
-//      are tried in order: the current umbrella `rcf-lite`, then the legacy
-//      `@stravica-ai/rcf-verify-lite` name (deprecated at 0.7.1 but still
-//      resolvable in lockfiles that pinned it). Either resolves to the same
-//      `bin/rcf-verify.js` entry point.
-// Either route yields a concrete invocation the finalise spawn (spawn.js)
-// uses verbatim. A miss returns { installed:false } and the caller enters
-// the prompt-or-explicit-flag path.
+// The 0.10.0 CLI reorganisation folded the standalone `rcf-verify` bin
+// into the umbrella `rcf` CLI as the `verify` group. Detection now
+// resolves the `rcf` bin exclusively; there is no legacy fallback.
+//
+// Two detection routes, in order:
+//   1. The `rcf` bin on PATH - the umbrella install exposes `rcf` as a
+//      global bin (`npm i -g rcf-lite`).
+//   2. Package resolution from the project dir - the local-project
+//      install (`npm i rcf-lite` in a repo's node_modules) resolves the
+//      `rcf-lite` package and its `bin/rcf.js` entry point.
+// Either route yields a concrete invocation the finalise spawn
+// (spawn.js) uses verbatim. A miss returns { installed:false } and the
+// caller enters the prompt-or-explicit-flag path.
 
 import { access, constants } from 'node:fs/promises';
 import { createRequire } from 'node:module';
 import { delimiter, dirname, join, resolve } from 'node:path';
 
-// VERIFY_PACKAGE is the current install target and the name shown to
-// operators in absent-verify messaging. VERIFY_PACKAGE_LEGACY is only used
-// as a resolution fallback for lockfiles still pinning the pre-0.7.1 scoped
-// name; it is never displayed as an install target.
+// VERIFY_PACKAGE is the install target and the name shown to operators
+// in absent-verify messaging.
 const VERIFY_PACKAGE = 'rcf-lite';
-const VERIFY_PACKAGE_LEGACY = '@stravica-ai/rcf-verify-lite';
-const VERIFY_PACKAGE_CANDIDATES = [VERIFY_PACKAGE, VERIFY_PACKAGE_LEGACY];
-const VERIFY_BIN = 'rcf-verify';
+const VERIFY_PACKAGE_CANDIDATES = [VERIFY_PACKAGE];
+const VERIFY_BIN = 'rcf';
 
 /**
- * The concrete way to launch rcf-verify as a fresh subprocess.
+ * The concrete way to launch the `rcf` bin as a fresh subprocess.
  *   - `{ command: '<abs-bin>', prefixArgs: [] }` for a PATH / shim bin
  *     (its own shebang runs it).
  *   - `{ command: process.execPath, prefixArgs: ['<abs-entry.js>'] }` for a
@@ -43,8 +42,8 @@ const VERIFY_BIN = 'rcf-verify';
  */
 
 /**
- * Scan PATH for an executable named `rcf-verify` (plus the Windows
- * `.cmd`/`.exe` shim variants). Returns the first absolute path that exists
+ * Scan PATH for an executable named `rcf` (plus the Windows `.cmd` /
+ * `.exe` shim variants). Returns the first absolute path that exists
  * and is executable, or null.
  *
  * @param {string} name
@@ -78,16 +77,11 @@ export async function findOnPath(name, { env = process.env } = {}) {
 }
 
 /**
- * Resolve the rcf-verify bin entry point from a starting directory, following
- * the normal node_modules resolution the caller's project sees. Returns the
- * absolute path to `bin/rcf-verify.js`, or null if no candidate package is
+ * Resolve the `rcf` bin entry point from a starting directory, following
+ * the normal node_modules resolution the caller's project sees. Returns
+ * the absolute path to `bin/rcf.js`, or null if the package is not
  * installed / resolvable from there.
  *
- * Candidates are tried in the order defined by VERIFY_PACKAGE_CANDIDATES: the
- * current umbrella (`rcf-lite`) first, then the deprecated scoped name
- * (`@stravica-ai/rcf-verify-lite`) as a fallback for lockfiles pinned to it.
- * The first candidate whose bin resolves and exists on disk wins.
- *
  * @param {string} fromDir - directory to resolve from (the project root / cwd)
  * @returns {Promise<string|null>}
  */
@@ -119,9 +113,9 @@ export async function resolvePackageBin(fromDir) {
 }
 
 /**
- * Detect whether rcf-verify is resolvable and, if so, how to launch it.
- * Deps are injectable so the finalise gate can be exercised without a real
- * rcf-verify on the test machine.
+ * Detect whether the `rcf` bin (carrying the `verify` group) is
+ * resolvable and, if so, how to launch it. Deps are injectable so the
+ * finalise gate can be exercised without a real installed rcf-lite.
  *
  * @param {object} [deps]
  * @param {string} [deps.cwd] - project dir to resolve a local install from
@@ -148,4 +142,4 @@ export async function detectVerify(deps = {}) {
   return { installed: false, invocation: null };
 }
 
-export { VERIFY_PACKAGE, VERIFY_PACKAGE_LEGACY, VERIFY_PACKAGE_CANDIDATES, VERIFY_BIN };
+export { VERIFY_PACKAGE, VERIFY_PACKAGE_CANDIDATES, VERIFY_BIN };

package/src/finalise/index.js

@@ -11,7 +11,6 @@ export {
   findOnPath,
   resolvePackageBin,
   VERIFY_PACKAGE,
-  VERIFY_PACKAGE_LEGACY,
   VERIFY_PACKAGE_CANDIDATES,
   VERIFY_BIN,
 } from './detect.js';

package/src/finalise/install.js

@@ -1,5 +1,6 @@
-// Absent-verify handling (spec §8.3, amendment 5). When `rcf-verify` is not
-// resolvable, the finalise gate MUST NOT silently skip - that recreates the
+// Absent-verify handling (spec §8.3, amendment 5). When the `rcf` bin
+// (which now carries the `verify` group post-0.10.0) is not resolvable,
+// the finalise gate MUST NOT silently skip - that recreates the
 // false-confidence failure the whole programme exists to prevent. The
 // sanctioned paths are exactly two, and nothing else:
 //   - interactive TTY  -> prompt the operator to install now (y/N);
@@ -35,8 +36,8 @@ export function promptYesNo(question, { input = process.stdin, output = process.
 }
 
 /**
- * Install rcf-verify globally (matches the install-together default of two
- * global bins). Streams npm's output to the operator. Returns the install
+ * Install rcf-lite globally so the `rcf verify` group becomes
+ * resolvable. Streams npm's output to the operator. Returns the install
  * process exit code.
  *
  * @param {object} [deps]
@@ -77,11 +78,11 @@ export async function resolveAbsentVerify({ installFlag, isTty }, io, deps = {})
   let wantsInstall = false;
   if (installFlag) {
     // Explicit flag: the sanctioned non-interactive install path.
-    io.stdout.write(`[finalise] rcf-verify not found; installing ${VERIFY_PACKAGE} (--install-verify)...\n`);
+    io.stdout.write(`[finalise] the rcf CLI (with verify) not found; installing ${VERIFY_PACKAGE} (--install-verify)...\n`);
     wantsInstall = true;
   } else if (isTty) {
     // Interactive: prompt. Declining aborts (never a silent skip).
-    io.stderr.write(`[finalise] rcf-verify is not installed. The ship gate cannot run without it.\n`);
+    io.stderr.write(`[finalise] rcf-lite is not installed. The ship gate cannot run without it.\n`);
     wantsInstall = await prompt(`Install ${VERIFY_PACKAGE} now? [y/N]`, {
       input: io.input, output: io.output,
     });
@@ -89,7 +90,7 @@ export async function resolveAbsentVerify({ installFlag, isTty }, io, deps = {})
       return {
         action: 'abort',
         code: 4,
-        reason: `finalise refused: rcf-verify is required and install was declined. `
+        reason: `finalise refused: rcf-lite is required and install was declined. `
           + `Install it (npm i -g ${VERIFY_PACKAGE}) or re-run with --install-verify. `
           + `The ship gate is never skipped.`,
       };
@@ -100,7 +101,7 @@ export async function resolveAbsentVerify({ installFlag, isTty }, io, deps = {})
     return {
       action: 'abort',
       code: 4,
-      reason: `finalise refused: rcf-verify is not installed and no TTY is available to prompt. `
+      reason: `finalise refused: rcf-lite is not installed and no TTY is available to prompt. `
         + `Install it (npm i -g ${VERIFY_PACKAGE}) or re-run with --install-verify. `
         + `The ship gate is never silently skipped.`,
     };

package/src/finalise/spawn.js

@@ -1,9 +1,10 @@
-// Fresh-subprocess invocation of `rcf-verify run` (spec §8.2). This is the
-// load-bearing independence guarantee: build-lite's finalise step launches
-// verify as a SEPARATE OS PROCESS with the isolation env - it MUST NOT import
-// verify's engine in-process, because the verifier agent must start from a
-// cold session with zero build context (§9). The subprocess exit code is the
-// gate; findings flow back via the --out report file, never stdout scraping.
+// Fresh-subprocess invocation of `rcf verify run` (spec §8.2). This is
+// the load-bearing independence guarantee: build-lite's finalise step
+// launches verify as a SEPARATE OS PROCESS with the isolation env - it
+// MUST NOT import verify's engine in-process, because the verifier
+// agent must start from a cold session with zero build context (§9).
+// The subprocess exit code is the gate; findings flow back via the
+// --out report file, never stdout scraping.
 //
 // The isolation env (core's ISOLATION_RECIPE, §7.3) is layered onto the child
 // env here so the recipe travels with the process boundary exactly as §8.2
@@ -14,9 +15,11 @@ import { spawn } from 'node:child_process';
 import { isolationEnv } from '#core/isolation';
 
 /**
- * Assemble the `rcf-verify run` argument vector from finalise options.
- * Deterministic and pure so it is directly unit-testable; the exact shape is
- * the §8.2 invocation contract.
+ * Assemble the `rcf verify run` argument vector from finalise options.
+ * Deterministic and pure so it is directly unit-testable; the exact
+ * shape is the §8.2 invocation contract. The 0.10.0 CLI reorganisation
+ * prepends the `verify` group token; the run-verb arguments below are
+ * otherwise unchanged.
  *
  * @param {object} opts
  * @param {string} opts.repo - RCF chain source (the project root)
@@ -32,6 +35,7 @@ import { isolationEnv } from '#core/isolation';
  */
 export function buildVerifyArgs(opts) {
   const args = [
+    'verify',
     'run',
     '--repo', opts.repo,
     '--profile', opts.profile,
@@ -47,7 +51,7 @@ export function buildVerifyArgs(opts) {
 }
 
 /**
- * Spawn rcf-verify as a fresh subprocess and resolve with its exit code.
+ * Spawn `rcf verify run` as a fresh subprocess and resolve with its exit code.
  * stdio is inherited by default so the operator sees verify's live progress
  * and its verdict line; the report artifact is read separately by the caller.
  *

package/src/mcp/tools.js

@@ -69,7 +69,7 @@ const ISSUE_SCHEMA = {
 // success branch stays the verbatim envelope transcription (D8/D9).
 const ERROR_PAYLOAD_SCHEMA = {
   type: 'object',
-  description: 'Tool execution error payload (accompanies isError: true): the same issue shape rcf validate --json ships',
+  description: 'Tool execution error payload (accompanies isError: true): the same issue shape rcf define validate --json ships',
   properties: {
     ok: { const: false },
     errors: { type: 'array', items: ISSUE_SCHEMA },

package/src/req-baseline/gate.js

@@ -73,7 +73,7 @@ export function formatStage1RefusalMessage({ fbsId, usId, reqId, openCandidates
     const short = shortDescription(c.canonicalText);
     lines.push(`          ${c.baselineKey}: ${short}`);
   }
-  lines.push(`        Resolve: rcf req-baseline sweep --req ${reqId}`);
+  lines.push(`        Resolve: rcf discover req-baseline sweep --req ${reqId}`);
   return lines.join('\n');
 }
 

package/src/ui-baseline/manifest-writer.js

@@ -210,14 +210,14 @@ export async function writeUiBaselineOptOut({
   if (!priorBaseline) {
     return rcfError({
       kind: 'usage',
-      message: 'ui-baseline opt-out: no uiBaseline record exists yet; run \'rcf ui-baseline init\' first.',
+      message: 'ui-baseline opt-out: no uiBaseline record exists yet; run \'rcf discover ui-baseline init\' first.',
     });
   }
   const normalisedField = String(field).startsWith('defaults.') ? String(field).slice('defaults.'.length) : String(field);
   if (typeof isKnownField === 'function' && !isKnownField(normalisedField)) {
     return rcfError({
       kind: 'usage',
-      message: `ui-baseline opt-out: unknown baseline field '${normalisedField}' (see 'rcf ui-baseline show' for the field list).`,
+      message: `ui-baseline opt-out: unknown baseline field '${normalisedField}' (see 'rcf discover ui-baseline show' for the field list).`,
     });
   }
   const isoNow = now.toISOString();

package/src/verify/cli/cleanup.js

@@ -9,7 +9,7 @@ import { formatError, isRcfError } from '#core/errors';
 
 import { readProvisionFile, cleanup } from '../provision/index.js';
 
-export const HELP = `Usage: rcf-verify cleanup --provision <file> [--url <app-url>]
+export const HELP = `Usage: rcf verify cleanup --provision <file> [--url <app-url>]
 
 Tear down artefacts recorded in the --provision file (all prefixed
 'zzverify-'). Reports what was removed and what could not be.

package/src/verify/cli/mcp.js

@@ -14,7 +14,7 @@ import { createToolRegistry } from '../mcp/tools.js';
 
 const here = dirname(fileURLToPath(import.meta.url));
 
-export const HELP = `Usage: rcf-verify mcp [options]
+export const HELP = `Usage: rcf verify mcp [options]
 
 Serve verify over the Model Context Protocol (local stdio). Exposes one tool,
 rcf_verify_run, over the same in-process engine the CLI uses. stdout carries

package/src/verify/cli/provision.js

@@ -11,7 +11,7 @@ import { formatError, isRcfError } from '#core/errors';
 import { readChain } from '../chain/index.js';
 import { runProvisioning } from '../provision/index.js';
 
-export const HELP = `Usage: rcf-verify provision --repo <path> --url <app-url> --provision <file>
+export const HELP = `Usage: rcf verify provision --repo <path> --url <app-url> --provision <file>
 
 Stand up prerequisite accounts / sandboxes / seed data for a later run.
 Credentials are written to the --provision FILE only, never echoed.

package/src/verify/cli/report.js

@@ -11,7 +11,7 @@ import { formatError, isRcfError } from '#core/errors';
 import { parseReport } from '../report/index.js';
 import { renderReport } from '../report/renderer.js';
 
-export const HELP = `Usage: rcf-verify report <report-path> [--json]
+export const HELP = `Usage: rcf verify report <report-path> [--json]
 
 Re-render a prior report artifact. Default output is the human-readable
 summary; --json re-emits the parsed artifact as JSON.

package/src/verify/cli/run.js

@@ -29,7 +29,7 @@ const OPTION_SPEC = {
   help: { type: 'boolean' },
 };
 
-export const HELP = `Usage: rcf-verify run [options]
+export const HELP = `Usage: rcf verify run [options]
 
 Launch a fresh-context adversarial verifier against a running app and emit a
 structured verdict stamped with the runtime it ran against.

package/src/view-supervisor/manifest-writer.js

@@ -19,13 +19,13 @@ export const DEFAULT_PID_PATH = '.rcf/view-server.pid';
  */
 export const viewServerGitignoreEntry = Object.freeze({
   path: '.rcf/view-server.pid',
-  owner: 'rcf view --detach (view-server pid file)',
+  owner: 'rcf audit view --detach (view-server pid file)',
   since: '0.7.0',
 });
 
 export const viewServerLogGitignoreEntry = Object.freeze({
   path: '.rcf/view-server.log',
-  owner: 'rcf view --detach (supervisor log)',
+  owner: 'rcf audit view --detach (supervisor log)',
   since: '0.7.0',
 });
 

package/bin/rcf-verify.js

@@ -1,122 +0,0 @@
-#!/usr/bin/env node
-// The `rcf-verify` alias bin. Post 0.7.1 packaging consolidation the
-// unified `rcf` CLI grew a `verify` subcommand that dispatches to the
-// same handlers this file wires up; `rcf-verify` remains as a
-// transition-grace alias (see docs/2026-08-06_packaging-consolidation-
-// proposal.md R3). When run directly (as `rcf-verify <verb>` rather
-// than through the routing `rcf verify <verb>`), the entrypoint emits
-// a one-line stderr deprecation notice; behaviour is otherwise
-// unchanged.
-//
-// Argv layout: `rcf-verify <subcommand> [args...]`. The first positional
-// selects the subcommand handler; global --version / --help short-circuit
-// before dispatch. The `main` export is also imported by bin/rcf.js as
-// the `verify` subcommand handler, so the dispatcher lives in one place.
-
-import { realpathSync } from 'node:fs';
-import { readFile } from 'node:fs/promises';
-import { dirname, resolve } from 'node:path';
-import process from 'node:process';
-import { fileURLToPath, pathToFileURL } from 'node:url';
-
-import { main as runMain } from '../src/verify/cli/run.js';
-import { main as reportMain } from '../src/verify/cli/report.js';
-import { main as provisionMain } from '../src/verify/cli/provision.js';
-import { main as cleanupMain } from '../src/verify/cli/cleanup.js';
-import { main as mcpMain } from '../src/verify/cli/mcp.js';
-import { main as helpMain, TOP_LEVEL_HELP } from '../src/verify/cli/help.js';
-
-const here = dirname(fileURLToPath(import.meta.url));
-
-const SUBCOMMANDS = {
-  run: runMain,
-  report: reportMain,
-  provision: provisionMain,
-  cleanup: cleanupMain,
-  mcp: mcpMain,
-  help: helpMain,
-};
-
-/**
- * @param {string[]} argv - argv minus node + script
- * @param {object} [deps]
- * @returns {Promise<number>}
- */
-export async function main(argv, deps = {}) {
-  const stdout = deps.stdout ?? process.stdout;
-  const stderr = deps.stderr ?? process.stderr;
-
-  if (argv.length === 0) {
-    stdout.write(TOP_LEVEL_HELP);
-    return 0;
-  }
-  const first = argv[0];
-  if (first === '--version' || first === '-v') {
-    stdout.write(`rcf-verify ${await readPackageVersion()}\n`);
-    return 0;
-  }
-  if (first === '--help' || first === '-h') {
-    stdout.write(TOP_LEVEL_HELP);
-    return 0;
-  }
-  const handler = SUBCOMMANDS[first];
-  if (!handler) {
-    stderr.write(`[error] usage unknown subcommand: ${first}\n`);
-    stderr.write(TOP_LEVEL_HELP);
-    return 2;
-  }
-  return await handler(argv.slice(1), deps);
-}
-
-async function readPackageVersion() {
-  try {
-    const pkgPath = resolve(here, '..', 'package.json');
-    const pkg = JSON.parse(await readFile(pkgPath, 'utf8'));
-    return pkg.version ?? '0.0.0';
-  } catch {
-    return '0.0.0';
-  }
-}
-
-/**
- * Symlink-safe entry-point compare (mirrors build's bin/rcf.js). macOS `/tmp`
- * is a symlink to `/private/tmp` and every `pnpm link` shim is a symlink;
- * without realpath the isMain gate breaks and main() never runs.
- *
- * @param {string} metaUrl
- * @param {string} argvPath
- * @returns {boolean}
- */
-export function isSameEntryPoint(metaUrl, argvPath) {
-  try {
-    const metaPath = fileURLToPath(metaUrl);
-    return realpathSync(metaPath) === realpathSync(argvPath);
-  } catch {
-    try {
-      return metaUrl === pathToFileURL(argvPath).href;
-    } catch {
-      return false;
-    }
-  }
-}
-
-const isMain = process.argv[1] && isSameEntryPoint(import.meta.url, process.argv[1]);
-if (isMain) {
-  // Transition-grace deprecation notice per proposal R3. Only fires when
-  // the alias bin is invoked directly (not when bin/rcf.js routes the
-  // `verify` subcommand through the exported `main`, since the isMain
-  // guard is false in that case). Suppressible via RCF_QUIET=1 for
-  // scripted callers who cannot tolerate stderr chatter.
-  if (!process.env.RCF_QUIET) {
-    process.stderr.write(
-      '[rcf-verify] deprecation: prefer `rcf verify` (the umbrella CLI subcommand). ' +
-      'The `rcf-verify` alias will be removed in a future major. Set RCF_QUIET=1 to silence.\n',
-    );
-  }
-  main(process.argv.slice(2))
-    .then((code) => process.exit(code))
-    .catch((err) => {
-      process.stderr.write(`[rcf-verify] unexpected failure: ${err.message}\n${err.stack}\n`);
-      process.exit(1);
-    });
-}

package/src/verify/cli/help.js

@@ -1,56 +0,0 @@
-// Top-level and per-subcommand help (mirrors build's cli/help.js). British
-// English, ASCII hyphens only.
-
-import { HELP as RUN_HELP } from './run.js';
-import { HELP as REPORT_HELP } from './report.js';
-import { HELP as PROVISION_HELP } from './provision.js';
-import { HELP as CLEANUP_HELP } from './cleanup.js';
-import { HELP as MCP_HELP } from './mcp.js';
-
-export const TOP_LEVEL_HELP = `Usage: rcf-verify <command> [options]
-
-A fresh-context adversarial verifier. Given an RCF chain (the acceptance
-contract) and a running app under a declared runtime profile, it launches an
-isolated verifier agent that walks real user journeys adversarially and emits a
-structured verdict stamped with the runtime it ran against.
-
-This is an independent ship-readiness signal, not a correctness guarantee.
-
-Commands:
-  run            Run adversarial verification and emit a report artifact
-  report <path>  Re-render a prior report artifact
-  provision      Stand up prerequisite accounts/sandboxes/data standalone
-  cleanup        Tear down provisioned artefacts (all prefixed 'zzverify-')
-  mcp            Serve verify over MCP (local stdio)
-  help [command] Print help for a command
-
-Options:
-  --version      Print the package version and exit
-  --help         Print this help and exit
-
-Run 'rcf-verify help <command>' for command-specific help.
-`;
-
-const SUB_HELP = {
-  run: RUN_HELP,
-  report: REPORT_HELP,
-  provision: PROVISION_HELP,
-  cleanup: CLEANUP_HELP,
-  mcp: MCP_HELP,
-};
-
-/**
- * @param {string[]} argv
- * @param {object} [deps]
- * @returns {Promise<number>}
- */
-export async function main(argv, deps = {}) {
-  const stdout = deps.stdout ?? process.stdout;
-  const topic = argv[0];
-  if (topic && SUB_HELP[topic]) {
-    stdout.write(SUB_HELP[topic]);
-    return 0;
-  }
-  stdout.write(TOP_LEVEL_HELP);
-  return 0;
-}