@ritualai/cli 0.7.11 → 0.7.13

package/dist/lib/stale-bundle-warning.js

@@ -0,0 +1,85 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.printStaleBundleWarning = printStaleBundleWarning;
+exports.shouldSkipWarning = shouldSkipWarning;
+exports.buildWarningLine = buildWarningLine;
+const skill_bundles_1 = require("./skill-bundles");
+const package_info_1 = require("./package-info");
+/**
+ * Pre-flight warning when the project's Ritual SKILL bundles drift
+ * from the installed CLI version.
+ *
+ * Why this exists (PR C, 2026-05-15): `ritual doctor` already reports
+ * drift, but users don't routinely run it. Eiman hit a CLI bug
+ * (#319 — dev URL leak in `/ritual init` output) that was already
+ * fixed in 0.7.11 — but her SKILL bundle on disk was older, so the
+ * fix only landed when she happened to re-run `ritual init`. A
+ * one-line stderr warning at every CLI entry catches the
+ * "upgraded the CLI, forgot to refresh skills" gap immediately.
+ *
+ * Design constraints:
+ *   - Best-effort: never throws, never blocks. Filesystem races,
+ *     unreadable manifests, missing dirs all silently no-op.
+ *   - Skip during `init` (the fix command itself) and `doctor`
+ *     (which already prints the same info, in more detail).
+ *   - Skip during `--version` / `-V` / `--help` / `-h` — those exit
+ *     immediately and a multi-line warning would feel out of place.
+ *   - Single line when one bundle drifts, single summary line when
+ *     multiple. Concise; the user doesn't need the doctor-style
+ *     per-provider breakdown to know what to do.
+ *   - Writes to stderr so it doesn't pollute scriptable stdout.
+ *
+ * The fix command is always `ritual init --skills-only` whether the
+ * bundle is stamped-and-drifted or pre-stamp-unknown — same code
+ * path, same outcome.
+ */
+function printStaleBundleWarning(argv) {
+    if (shouldSkipWarning(argv))
+        return;
+    let stale;
+    try {
+        const bundles = (0, skill_bundles_1.findLocalSkillBundles)(process.cwd(), (0, package_info_1.readPackageVersionSafe)());
+        stale = (0, skill_bundles_1.findStaleBundles)(bundles);
+    }
+    catch {
+        return;
+    }
+    if (stale.length === 0)
+        return;
+    const line = buildWarningLine(stale);
+    process.stderr.write(line);
+}
+const SKIP_COMMANDS = new Set(['init', 'doctor']);
+const SKIP_FLAGS = new Set(['--version', '-V', '--help', '-h']);
+/**
+ * Skip rules — kept narrow so any new command opts in automatically:
+ *   - `init` skips: the warning would print right before the user's
+ *     fix command runs.
+ *   - `doctor` skips: it already renders bundle drift in detail.
+ *   - `--version` / `--help` skips: short-circuit invocations.
+ *
+ * Note we look at the FIRST non-flag positional only — `ritual graph
+ * status` should still warn, since that's an arbitrary subcommand
+ * that has no special relationship to skill bundles.
+ */
+function shouldSkipWarning(argv) {
+    for (const a of argv) {
+        if (SKIP_FLAGS.has(a))
+            return true;
+    }
+    const firstPositional = argv.find((a) => !a.startsWith('-'));
+    if (firstPositional && SKIP_COMMANDS.has(firstPositional))
+        return true;
+    return false;
+}
+function buildWarningLine(stale) {
+    if (stale.length === 1) {
+        const s = stale[0];
+        const detail = s.drift.kind === 'drift'
+            ? `bundle ${s.drift.bundleVersion} vs CLI ${s.drift.cliVersion}`
+            : 'pre-0.7.11 bundle, no version stamp';
+        return `⚠ Ritual SKILL bundle is out of date (${detail}). Run \`ritual init --skills-only\` to refresh.\n\n`;
+    }
+    return `⚠ ${stale.length} Ritual SKILL bundles need refresh. Run \`ritual init --skills-only\`.\n\n`;
+}
+//# sourceMappingURL=stale-bundle-warning.js.map

package/dist/lib/stale-bundle-warning.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"stale-bundle-warning.js","sourceRoot":"","sources":["../../src/lib/stale-bundle-warning.ts"],"names":[],"mappings":";;AA+BA,0DAcC;AAgBD,8CAOC;AAED,4CAYC;AAlFD,mDAA0E;AAC1E,iDAAwD;AAExD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,SAAgB,uBAAuB,CAAC,IAAc;IACrD,IAAI,iBAAiB,CAAC,IAAI,CAAC;QAAE,OAAO;IAEpC,IAAI,KAAK,CAAC;IACV,IAAI,CAAC;QACJ,MAAM,OAAO,GAAG,IAAA,qCAAqB,EAAC,OAAO,CAAC,GAAG,EAAE,EAAE,IAAA,qCAAsB,GAAE,CAAC,CAAC;QAC/E,KAAK,GAAG,IAAA,gCAAgB,EAAC,OAAO,CAAC,CAAC;IACnC,CAAC;IAAC,MAAM,CAAC;QACR,OAAO;IACR,CAAC;IACD,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO;IAE/B,MAAM,IAAI,GAAG,gBAAgB,CAAC,KAAK,CAAC,CAAC;IACrC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;AAC5B,CAAC;AAED,MAAM,aAAa,GAAG,IAAI,GAAG,CAAC,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC,CAAC;AAClD,MAAM,UAAU,GAAG,IAAI,GAAG,CAAC,CAAC,WAAW,EAAE,IAAI,EAAE,QAAQ,EAAE,IAAI,CAAC,CAAC,CAAC;AAEhE;;;;;;;;;;GAUG;AACH,SAAgB,iBAAiB,CAAC,IAAc;IAC/C,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;QACtB,IAAI,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC;YAAE,OAAO,IAAI,CAAC;IACpC,CAAC;IACD,MAAM,eAAe,GAAG,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC;IAC7D,IAAI,eAAe,IAAI,aAAa,CAAC,GAAG,CAAC,eAAe,CAAC;QAAE,OAAO,IAAI,CAAC;IACvE,OAAO,KAAK,CAAC;AACd,CAAC;AAED,SAAgB,gBAAgB,CAC/B,KAA0C;IAE1C,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QACxB,MAAM,CAAC,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC;QACnB,MAAM,MAAM,GACX,CAAC,CAAC,KAAK,CAAC,IAAI,KAAK,OAAO;YACvB,CAAC,CAAC,UAAU,CAAC,CAAC,KAAK,CAAC,aAAa,WAAW,CAAC,CAAC,KAAK,CAAC,UAAU,EAAE;YAChE,CAAC,CAAC,qCAAqC,CAAC;QAC1C,OAAO,yCAAyC,MAAM,sDAAsD,CAAC;IAC9G,CAAC;IACD,OAAO,KAAK,KAAK,CAAC,MAAM,4EAA4E,CAAC;AACtG,CAAC"}

package/package.json

@@ -1,74 +1,75 @@
 {
-  "name": "@ritualai/cli",
-  "version": "0.7.11",
-  "description": "Ritual CLI — scaffold AI coding agent skills + register MCP servers. Connects Claude Code, Cursor, Windsurf, Kiro, Gemini CLI, VS Code/Copilot, and Codex to Ritual Cloud.",
-  "private": false,
-  "license": "Apache-2.0",
-  "homepage": "https://ritual.work/ritual-mcp/docs/",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/Ritual-Mobile/ritual-enterprise.git",
-    "directory": "apps/cli"
-  },
-  "author": "Ritual",
-  "publishConfig": {
-    "access": "public"
-  },
-  "bin": {
-    "ritual": "./dist/index.js"
-  },
-  "main": "./dist/index.js",
-  "files": [
-    "dist",
-    "skills",
-    "README.md"
-  ],
-  "dependencies": {
-    "commander": "^14.0.3",
-    "open": "^10.1.0"
-  },
-  "devDependencies": {
-    "@types/jest": "^29.5.0",
-    "@types/node": "^20.0.0",
-    "jest": "^29.7.0",
-    "ts-jest": "^29.1.0",
-    "tsx": "^4.19.0",
-    "typescript": "^5.0.0",
-    "@ritual/shared-types": "^1.0.0"
-  },
-  "engines": {
-    "node": ">=20.0.0"
-  },
-  "keywords": [
-    "ritual",
-    "mcp",
-    "ai-coding-agent",
-    "claude-code",
-    "cursor",
-    "windsurf",
-    "kiro",
-    "gemini-cli",
-    "copilot",
-    "codex"
-  ],
-  "jest": {
-    "preset": "ts-jest",
-    "testEnvironment": "node",
-    "roots": [
-      "<rootDir>/src",
-      "<rootDir>/test"
-    ],
-    "testMatch": [
-      "**/?(*.)+(spec|test).ts"
-    ]
-  },
-  "scripts": {
-    "build:skills": "node scripts/build-skills.js",
-    "build:ts": "tsc -p tsconfig.json",
-    "build": "pnpm run build:skills && pnpm run build:ts",
-    "dev": "tsx src/index.ts",
-    "clean": "rm -rf dist skills",
-    "typecheck": "tsc --noEmit -p tsconfig.json",
-    "test": "jest --passWithNoTests"
-  }
-}
+	"name": "@ritualai/cli",
+	"version": "0.7.13",
+	"description": "Ritual CLI — scaffold AI coding agent skills + register MCP servers. Connects Claude Code, Cursor, Windsurf, Kiro, Gemini CLI, VS Code/Copilot, and Codex to Ritual Cloud.",
+	"private": false,
+	"license": "Apache-2.0",
+	"homepage": "https://ritual.work/ritual-mcp/docs/",
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/Ritual-Mobile/ritual-enterprise.git",
+		"directory": "apps/cli"
+	},
+	"author": "Ritual",
+	"publishConfig": {
+		"access": "public"
+	},
+	"bin": {
+		"ritual": "./dist/index.js"
+	},
+	"main": "./dist/index.js",
+	"files": [
+		"dist",
+		"skills",
+		"README.md"
+	],
+	"scripts": {
+		"build:skills": "node scripts/build-skills.js",
+		"build:ts": "tsc -p tsconfig.json",
+		"build": "pnpm run build:skills && pnpm run build:ts",
+		"dev": "tsx src/index.ts",
+		"clean": "rm -rf dist skills",
+		"typecheck": "tsc --noEmit -p tsconfig.json",
+		"test": "jest --passWithNoTests",
+		"prepublishOnly": "pnpm run clean && pnpm run build"
+	},
+	"dependencies": {
+		"commander": "^14.0.3",
+		"open": "^10.1.0"
+	},
+	"devDependencies": {
+		"@ritual/shared-types": "workspace:^",
+		"@types/jest": "^29.5.0",
+		"@types/node": "^20.0.0",
+		"jest": "^29.7.0",
+		"ts-jest": "^29.1.0",
+		"tsx": "^4.19.0",
+		"typescript": "^5.0.0"
+	},
+	"engines": {
+		"node": ">=20.0.0"
+	},
+	"keywords": [
+		"ritual",
+		"mcp",
+		"ai-coding-agent",
+		"claude-code",
+		"cursor",
+		"windsurf",
+		"kiro",
+		"gemini-cli",
+		"copilot",
+		"codex"
+	],
+	"jest": {
+		"preset": "ts-jest",
+		"testEnvironment": "node",
+		"roots": [
+			"<rootDir>/src",
+			"<rootDir>/test"
+		],
+		"testMatch": [
+			"**/?(*.)+(spec|test).ts"
+		]
+	}
+}

package/skills/claude-code/ritual/.ritual-bundle.json

@@ -1,4 +1,4 @@
 {
-  "cliVersion": "0.7.11",
-  "builtAt": "2026-05-14T12:14:29.050Z"
+  "cliVersion": "0.7.13",
+  "builtAt": "2026-05-15T14:17:47.561Z"
 }

package/skills/claude-code/ritual/references/build-flow.md

@@ -197,7 +197,7 @@ Steps:
    >   - {state-specific call-to-action — see table below}
    >
    > Recommended: resume one if it matches this work.
-   > Reply with a number/name to resume, `suggest` to find high-leverage candidates from repo + workspace history, or `proceed` to start fresh.
+   > Reply with a number/name to resume, `suggest` to find high-leverage candidates from repo + workspace history, `delete N` to remove a duplicate/misfire, or `proceed` to start fresh.
 
    If `raw_input = null`, frame this as the user's no-arg start screen:
 
@@ -211,6 +211,7 @@ Steps:
    > Reply with:
    > - a number/name to resume
    > - `suggest` to have me look for high-leverage candidates from repo + workspace history
+   > - `delete N` to remove a duplicate/misfire from this list (soft-delete; recoverable)
    > - a feature/problem description to start fresh
    > - `none` to exit
 
@@ -285,6 +286,30 @@ Steps:
 
 6. **If the user picks "start fresh":** continue to Step 2 normally. The new exploration will sit alongside the existing ones; they're independent rows in the workspace.
 
+6a. **If the user picks `delete N` / "remove this from the list":**
+
+   This path handles duplicates and misfires that pollute the resume picker. Common shape: user accidentally created a near-duplicate exploration (started fresh thinking the original was unrecoverable), or a NOT_STARTED row from a typo / wrong-scope misfire that never converged. Eiman hit this in `nebula` on 2026-05-14 — two `Nerve-center /home dashboard` rows, no way to clear the unwanted one. This option fixes that.
+
+   Steps:
+
+   a. **Resolve `N` to an exploration_id.** The user replied `delete 2` referencing the numbered list rendered in step 3. Pick the exploration at that index. If they typed a name instead (`delete "Nerve-center duplicate"`), match by `name` (case-insensitive, exact or prefix).
+
+   b. **Show the target + ask for explicit confirmation** *(CLI Tenet #2 — single decisive proposal, not a 4-option menu)*:
+
+      > About to archive: **{name}** ({recommendationCount} rec{s}, {openDeferralsCount} open deferral{s}, last updated {relative time}).
+      >
+      > This soft-deletes the row — the full record (matters, questions, recs, attestations, decisions) is preserved for audit. The exploration disappears from this and future resume pickers. Restore is admin-only and not exposed in the CLI today.
+      >
+      > **(y/N)** — y to archive, anything else to cancel.
+
+   c. **[USER PAUSE]** — wait for `y` / `yes` (case-insensitive). Anything else = cancel back to the picker without calling the tool. Don't lecture; just say "Cancelled. Here's the picker again:" and re-render the menu.
+
+   d. **Call `mcp__ritual__archive_exploration(exploration_id)`.** On error (404 / 403 / 5xx), surface the failure and re-render the menu — don't silently swallow.
+
+   e. **Re-render the menu.** After successful archive, refresh the list (call `mcp__ritual__list_explorations` again) and show the updated picker. Lead with: "Archived **{name}**. Updated workspace:" — don't make the user re-derive what happened. Then return to step 4 ([USER PAUSE]) — the user can pick resume / suggest / fresh / `delete M` again.
+
+   f. **Anti-pattern**: do NOT auto-pick "start fresh" or "resume the survivor" after a delete. The user chose to clean up, not to commit to a next step.
+
 6b. **If the user picks `suggest` / "help me find the highest-leverage thing":**
 
    This path is for the "I have context but no concrete problem yet" case. The agent does a light workspace scan FIRST so suggestions land on real codebase and prior-deferral signals, not generic advice. This is **not** focused feature recon because no problem has been selected yet; focused recon still happens after the user picks a candidate.
@@ -1488,7 +1513,11 @@ For each question's loop:
 
 #### Step 9 — Review and accept recommendations (grouped, role-aware)
 
-Call `mcp__ritual__get_recommendations(exploration_id)`. Response is an array of recommendations. Each rec includes:
+**Use `mcp__ritual__get_recommendations_preview(exploration_id)` for the Step 9.1 landing screen.** It returns a server-rendered preview with `previewText` (terminal-formatted, hard-wrapped at 78 cols — print verbatim), `idMap` (`R1..RN` → uuid lookup for resolving `accept R3` / `detail R7`), `actions` (role-aware structured command list), `categoryGroups` (structured grouped list for non-terminal surfaces), `actionHint`, `scopeLine`, and `totalCount`. The server already handles role detection (admin vs collaborator) and filters out `approved`/`rejected` recs.
+
+Use `mcp__ritual__get_recommendations(exploration_id)` (the raw array) only when you need fields not in the preview — full `metadata.acceptance_criteria[]`, `metadata.explainability` rationale chain, `metadata.labels[]`, etc. The detail card in 9.3 (`detail R{N}`) loads from the raw tool keyed by the uuid you got from `idMap`.
+
+Each raw rec includes:
 
 - top-level: `id`, `title`, `content` (summary), `status`, `priority`, `points`, `confidence`
 - `metadata.category.name` — **the load-bearing grouping key** (one rec → one category)
@@ -1496,21 +1525,62 @@ Call `mcp__ritual__get_recommendations(exploration_id)`. Response is an array of
 - `metadata.explainability` — `rationale` (chained `→` arrow string), `faq_references[]`, `problem_alignment`, `inferred_elements`, optional `initial_input_analysis`
 - `metadata.labels[]` — secondary tags
 
-**Role model — load-bearing**: only **admins** can accept recommendations (call `accept_recommendations`). **Collaborators** can read, comment, and proceed to implement, but they cannot move recs from `draft`/`pending_review` to `approved`. Respect this so a collaborator running `/ritual build` doesn't hit a 403 mid-flow and lose context.
+**Role model — load-bearing**: only **admins** can accept recommendations (call `accept_recommendations`). **Collaborators** can read, comment, and proceed to implement, but they cannot move recs from `draft`/`pending_review` to `approved`. The preview API handles this automatically — the `actions` list and `actionHint` are gated on the caller's workspace role; admins see `accept recommended` while everyone else sees `request admin review` plus the optional `continue` (implement-ahead) path. Respect what the preview returns; don't substitute it.
 
 If you don't already know the user's role on this workspace, prefer the workspace member endpoint or cached role from `/ritual init`. When unavailable, ask plainly: *"Are you the workspace admin or a collaborator?"* Do not attempt acceptance blindly unless the user explicitly says to accept.
 
 **Vocabulary**: do NOT use "Reasoning chain" or "reasoning_chain" in user-facing copy. The user-visible label is **"Why this"** — a 4-line Problem / Discovery / Tradeoff / Recommendation breakdown derived from the rationale field. "Reasoning chain" sounds like internal model chain-of-thought; "Why this" is product-native.
 
-##### 9.1 — Landing screen: grouped category summary + compact scope
+##### 9.1 — Landing screen: server-rendered preview (primary path)
 
 The recommendations review is the most-read screen in the whole build flow.
 
+**Primary path — print the server preview verbatim:**
+
+```text
+1. Call mcp__ritual__get_recommendations_preview(exploration_id).
+
+2. Response shape:
+     {
+       terminalPreviewText: "...",   // present for surface=terminal (default)
+       uiPreview: {                   // always present
+         stage: "recommendations",
+         stageIndex: 4, stageCount: 6,
+         scopeLine, stats, categoryGroups,
+         idMap, actions
+       }
+     }
+
+3. Print response.terminalPreviewText VERBATIM. Do not re-render,
+   re-wrap, re-number, or add a leading "Here are your recommendations..."
+   line. The server already laid out the build rail, scope, grouped recs,
+   and role-aware action hint at 78-col wrap.
+
+4. Remember response.uiPreview.idMap so you can resolve user input — when
+   they reply `accept R3` or `detail R7`, look up `R{N}` → uuid in
+   idMap and use that uuid in the follow-up MCP call (accept_recommendations,
+   get_recommendations).
+
+5. response.uiPreview.actions is for mobile/web button rendering — terminal
+   flow ignores it (action hint copy is already inside terminalPreviewText).
+   Each action carries `style: "primary" | "secondary"` so a non-terminal
+   UI knows which is the call-to-action.
+```
+
+The server controls the rendering shape (category numbering, R-IDs, titles-only, 78-col wrap, role-aware action hint). Your job is to print and look up — not to invent labels, re-group, or add commentary.
+
+**Fallback path — if the preview tool is unavailable or returns a non-200**: render per the contract block below. The contract is the same shape the server uses, so a mismatch between server-rendered and agent-rendered output is unlikely. The fallback exists for older MCP servers that haven't deployed the preview endpoint yet.
+
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-STEP 9.1 RENDERING CONTRACT — non-negotiable
+STEP 9.1 RENDERING CONTRACT (FALLBACK) — non-negotiable
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
+Use this contract ONLY if get_recommendations_preview is unavailable
+(older MCP server) or returns an error. Otherwise, print the preview
+verbatim per the Primary path above.
+
+
 Landing view is for SELECTION, not reading. Full prose belongs in 9.3.
 
 ✓ DO:
@@ -2228,6 +2298,7 @@ This subcommand exclusively uses vNext MCP tools, in the order they appear:
 3. `mcp__ritual__list_explorations` (Step 1.5 — resume vs start, with state badges)
 4. `mcp__ritual__suggest_high_leverage_problems` (Step 1.5 step 6b — option 3, "help me find the highest-leverage thing")
 5. `mcp__ritual__check_exploration_overlap` (Step 1.5 step 8 — pre-creation overlap detection before "start fresh")
+5a. `mcp__ritual__archive_exploration` (Step 1.5 step 6a — soft-delete a duplicate/misfire when user picks `delete N` from the resume menu)
 6. `mcp__ritual__list_templates` (Step 2)
 7. `mcp__ritual__generate_considerations` (Step 4)
 8. `mcp__ritual__refine_considerations` (Step 4.2, iteration only)
@@ -2255,7 +2326,7 @@ This subcommand exclusively uses vNext MCP tools, in the order they appear:
 24c. `mcp__ritual__list_knowledge_sources` (used inline by Step 3.5 to show already-attached refs on resume; also called by `/ritual context-pulse` CP2 for Reference Grounding count)
 25. `mcp__ritual__sync_implementation` (Step 12)
 
-31 of the 40 vNext tools. The other 9 (`ping`, `get_exploration`, `list_agentic_runs`, `add_collaborator`, `check_anti_goals`, `query_knowledge_graph`, `get_workspace_overview`, `get_knowledge_source`, `remove_knowledge_source`) are situational, not part of the linear build flow.
+32 of the 43 vNext tools. The other 11 (`ping`, `get_exploration`, `list_agentic_runs`, `add_collaborator`, `check_anti_goals`, `query_knowledge_graph`, `get_workspace_overview`, `get_knowledge_source`, `remove_knowledge_source`, `get_recommendation_attestation`, `score_context_pulse`) are situational, not part of the linear build flow.
 
 ### After this subcommand
 

package/skills/codex/ritual/.ritual-bundle.json

@@ -1,4 +1,4 @@
 {
-  "cliVersion": "0.7.11",
-  "builtAt": "2026-05-14T12:14:29.050Z"
+  "cliVersion": "0.7.13",
+  "builtAt": "2026-05-15T14:17:47.561Z"
 }

package/skills/codex/ritual/references/build-flow.md

@@ -197,7 +197,7 @@ Steps:
    >   - {state-specific call-to-action — see table below}
    >
    > Recommended: resume one if it matches this work.
-   > Reply with a number/name to resume, `suggest` to find high-leverage candidates from repo + workspace history, or `proceed` to start fresh.
+   > Reply with a number/name to resume, `suggest` to find high-leverage candidates from repo + workspace history, `delete N` to remove a duplicate/misfire, or `proceed` to start fresh.
 
    If `raw_input = null`, frame this as the user's no-arg start screen:
 
@@ -211,6 +211,7 @@ Steps:
    > Reply with:
    > - a number/name to resume
    > - `suggest` to have me look for high-leverage candidates from repo + workspace history
+   > - `delete N` to remove a duplicate/misfire from this list (soft-delete; recoverable)
    > - a feature/problem description to start fresh
    > - `none` to exit
 
@@ -285,6 +286,30 @@ Steps:
 
 6. **If the user picks "start fresh":** continue to Step 2 normally. The new exploration will sit alongside the existing ones; they're independent rows in the workspace.
 
+6a. **If the user picks `delete N` / "remove this from the list":**
+
+   This path handles duplicates and misfires that pollute the resume picker. Common shape: user accidentally created a near-duplicate exploration (started fresh thinking the original was unrecoverable), or a NOT_STARTED row from a typo / wrong-scope misfire that never converged. Eiman hit this in `nebula` on 2026-05-14 — two `Nerve-center /home dashboard` rows, no way to clear the unwanted one. This option fixes that.
+
+   Steps:
+
+   a. **Resolve `N` to an exploration_id.** The user replied `delete 2` referencing the numbered list rendered in step 3. Pick the exploration at that index. If they typed a name instead (`delete "Nerve-center duplicate"`), match by `name` (case-insensitive, exact or prefix).
+
+   b. **Show the target + ask for explicit confirmation** *(CLI Tenet #2 — single decisive proposal, not a 4-option menu)*:
+
+      > About to archive: **{name}** ({recommendationCount} rec{s}, {openDeferralsCount} open deferral{s}, last updated {relative time}).
+      >
+      > This soft-deletes the row — the full record (matters, questions, recs, attestations, decisions) is preserved for audit. The exploration disappears from this and future resume pickers. Restore is admin-only and not exposed in the CLI today.
+      >
+      > **(y/N)** — y to archive, anything else to cancel.
+
+   c. **[USER PAUSE]** — wait for `y` / `yes` (case-insensitive). Anything else = cancel back to the picker without calling the tool. Don't lecture; just say "Cancelled. Here's the picker again:" and re-render the menu.
+
+   d. **Call `mcp__ritual__archive_exploration(exploration_id)`.** On error (404 / 403 / 5xx), surface the failure and re-render the menu — don't silently swallow.
+
+   e. **Re-render the menu.** After successful archive, refresh the list (call `mcp__ritual__list_explorations` again) and show the updated picker. Lead with: "Archived **{name}**. Updated workspace:" — don't make the user re-derive what happened. Then return to step 4 ([USER PAUSE]) — the user can pick resume / suggest / fresh / `delete M` again.
+
+   f. **Anti-pattern**: do NOT auto-pick "start fresh" or "resume the survivor" after a delete. The user chose to clean up, not to commit to a next step.
+
 6b. **If the user picks `suggest` / "help me find the highest-leverage thing":**
 
    This path is for the "I have context but no concrete problem yet" case. The agent does a light workspace scan FIRST so suggestions land on real codebase and prior-deferral signals, not generic advice. This is **not** focused feature recon because no problem has been selected yet; focused recon still happens after the user picks a candidate.
@@ -1488,7 +1513,11 @@ For each question's loop:
 
 #### Step 9 — Review and accept recommendations (grouped, role-aware)
 
-Call `mcp__ritual__get_recommendations(exploration_id)`. Response is an array of recommendations. Each rec includes:
+**Use `mcp__ritual__get_recommendations_preview(exploration_id)` for the Step 9.1 landing screen.** It returns a server-rendered preview with `previewText` (terminal-formatted, hard-wrapped at 78 cols — print verbatim), `idMap` (`R1..RN` → uuid lookup for resolving `accept R3` / `detail R7`), `actions` (role-aware structured command list), `categoryGroups` (structured grouped list for non-terminal surfaces), `actionHint`, `scopeLine`, and `totalCount`. The server already handles role detection (admin vs collaborator) and filters out `approved`/`rejected` recs.
+
+Use `mcp__ritual__get_recommendations(exploration_id)` (the raw array) only when you need fields not in the preview — full `metadata.acceptance_criteria[]`, `metadata.explainability` rationale chain, `metadata.labels[]`, etc. The detail card in 9.3 (`detail R{N}`) loads from the raw tool keyed by the uuid you got from `idMap`.
+
+Each raw rec includes:
 
 - top-level: `id`, `title`, `content` (summary), `status`, `priority`, `points`, `confidence`
 - `metadata.category.name` — **the load-bearing grouping key** (one rec → one category)
@@ -1496,21 +1525,62 @@ Call `mcp__ritual__get_recommendations(exploration_id)`. Response is an array of
 - `metadata.explainability` — `rationale` (chained `→` arrow string), `faq_references[]`, `problem_alignment`, `inferred_elements`, optional `initial_input_analysis`
 - `metadata.labels[]` — secondary tags
 
-**Role model — load-bearing**: only **admins** can accept recommendations (call `accept_recommendations`). **Collaborators** can read, comment, and proceed to implement, but they cannot move recs from `draft`/`pending_review` to `approved`. Respect this so a collaborator running `/ritual build` doesn't hit a 403 mid-flow and lose context.
+**Role model — load-bearing**: only **admins** can accept recommendations (call `accept_recommendations`). **Collaborators** can read, comment, and proceed to implement, but they cannot move recs from `draft`/`pending_review` to `approved`. The preview API handles this automatically — the `actions` list and `actionHint` are gated on the caller's workspace role; admins see `accept recommended` while everyone else sees `request admin review` plus the optional `continue` (implement-ahead) path. Respect what the preview returns; don't substitute it.
 
 If you don't already know the user's role on this workspace, prefer the workspace member endpoint or cached role from `/ritual init`. When unavailable, ask plainly: *"Are you the workspace admin or a collaborator?"* Do not attempt acceptance blindly unless the user explicitly says to accept.
 
 **Vocabulary**: do NOT use "Reasoning chain" or "reasoning_chain" in user-facing copy. The user-visible label is **"Why this"** — a 4-line Problem / Discovery / Tradeoff / Recommendation breakdown derived from the rationale field. "Reasoning chain" sounds like internal model chain-of-thought; "Why this" is product-native.
 
-##### 9.1 — Landing screen: grouped category summary + compact scope
+##### 9.1 — Landing screen: server-rendered preview (primary path)
 
 The recommendations review is the most-read screen in the whole build flow.
 
+**Primary path — print the server preview verbatim:**
+
+```text
+1. Call mcp__ritual__get_recommendations_preview(exploration_id).
+
+2. Response shape:
+     {
+       terminalPreviewText: "...",   // present for surface=terminal (default)
+       uiPreview: {                   // always present
+         stage: "recommendations",
+         stageIndex: 4, stageCount: 6,
+         scopeLine, stats, categoryGroups,
+         idMap, actions
+       }
+     }
+
+3. Print response.terminalPreviewText VERBATIM. Do not re-render,
+   re-wrap, re-number, or add a leading "Here are your recommendations..."
+   line. The server already laid out the build rail, scope, grouped recs,
+   and role-aware action hint at 78-col wrap.
+
+4. Remember response.uiPreview.idMap so you can resolve user input — when
+   they reply `accept R3` or `detail R7`, look up `R{N}` → uuid in
+   idMap and use that uuid in the follow-up MCP call (accept_recommendations,
+   get_recommendations).
+
+5. response.uiPreview.actions is for mobile/web button rendering — terminal
+   flow ignores it (action hint copy is already inside terminalPreviewText).
+   Each action carries `style: "primary" | "secondary"` so a non-terminal
+   UI knows which is the call-to-action.
+```
+
+The server controls the rendering shape (category numbering, R-IDs, titles-only, 78-col wrap, role-aware action hint). Your job is to print and look up — not to invent labels, re-group, or add commentary.
+
+**Fallback path — if the preview tool is unavailable or returns a non-200**: render per the contract block below. The contract is the same shape the server uses, so a mismatch between server-rendered and agent-rendered output is unlikely. The fallback exists for older MCP servers that haven't deployed the preview endpoint yet.
+
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-STEP 9.1 RENDERING CONTRACT — non-negotiable
+STEP 9.1 RENDERING CONTRACT (FALLBACK) — non-negotiable
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
+Use this contract ONLY if get_recommendations_preview is unavailable
+(older MCP server) or returns an error. Otherwise, print the preview
+verbatim per the Primary path above.
+
+
 Landing view is for SELECTION, not reading. Full prose belongs in 9.3.
 
 ✓ DO:
@@ -2228,6 +2298,7 @@ This subcommand exclusively uses vNext MCP tools, in the order they appear:
 3. `mcp__ritual__list_explorations` (Step 1.5 — resume vs start, with state badges)
 4. `mcp__ritual__suggest_high_leverage_problems` (Step 1.5 step 6b — option 3, "help me find the highest-leverage thing")
 5. `mcp__ritual__check_exploration_overlap` (Step 1.5 step 8 — pre-creation overlap detection before "start fresh")
+5a. `mcp__ritual__archive_exploration` (Step 1.5 step 6a — soft-delete a duplicate/misfire when user picks `delete N` from the resume menu)
 6. `mcp__ritual__list_templates` (Step 2)
 7. `mcp__ritual__generate_considerations` (Step 4)
 8. `mcp__ritual__refine_considerations` (Step 4.2, iteration only)
@@ -2255,7 +2326,7 @@ This subcommand exclusively uses vNext MCP tools, in the order they appear:
 24c. `mcp__ritual__list_knowledge_sources` (used inline by Step 3.5 to show already-attached refs on resume; also called by `/ritual context-pulse` CP2 for Reference Grounding count)
 25. `mcp__ritual__sync_implementation` (Step 12)
 
-31 of the 40 vNext tools. The other 9 (`ping`, `get_exploration`, `list_agentic_runs`, `add_collaborator`, `check_anti_goals`, `query_knowledge_graph`, `get_workspace_overview`, `get_knowledge_source`, `remove_knowledge_source`) are situational, not part of the linear build flow.
+32 of the 43 vNext tools. The other 11 (`ping`, `get_exploration`, `list_agentic_runs`, `add_collaborator`, `check_anti_goals`, `query_knowledge_graph`, `get_workspace_overview`, `get_knowledge_source`, `remove_knowledge_source`, `get_recommendation_attestation`, `score_context_pulse`) are situational, not part of the linear build flow.
 
 ### After this subcommand
 

package/skills/cursor/ritual/.ritual-bundle.json

@@ -1,4 +1,4 @@
 {
-  "cliVersion": "0.7.11",
-  "builtAt": "2026-05-14T12:14:29.050Z"
+  "cliVersion": "0.7.13",
+  "builtAt": "2026-05-15T14:17:47.561Z"
 }