create-snipara 1.3.30 → 1.3.31

package/README.md

@@ -50,7 +50,7 @@ The product surfaces remain:
 
 The default CLI path wires the local companion around those surfaces:
 
-- `snipara-companion` for local workflow commands and managed phase commits; legacy `rlm-hook` commands remain compatible
+- `snipara-companion` for local workflow commands and managed phase commits
 - `snipara-sandbox` for optional local code execution
 - `snipara-orchestrator` only when explicitly requested with `--with-orchestrator`
 - local config, env files, hook scripts, and a project companion pack
@@ -140,8 +140,7 @@ The interactive flow now asks for:
 - AI client
 
 By default, this uses the recommended `hosted-companion` setup: hosted MCP plus
-the local `snipara-companion` workflow helper. Legacy `rlm-hook` commands remain
-compatible. Add `--advanced` when you want profile selection, project id entry,
+the local `snipara-companion` workflow helper. Add `--advanced` when you want profile selection, project id entry,
 hook prompts, GitHub automation prompts, or sandbox provider prompts.
 Use `--with-orchestrator` only when you explicitly need the advanced production
 validation and htask package; it is not part of `full-stack` by default.
@@ -198,7 +197,7 @@ Writes `.snipara/companion/doctor.json` and validates:
 - Snipara Sandbox CLI presence
 - environment files
 - hosted MCP reachability when a live API key is available
-- exposed Hosted MCP tool aliases (`snipara_*`, with `rlm_*` reported as legacy)
+- exposed Hosted MCP tool aliases (`snipara_*`)
 - client-specific loading gaps that the terminal cannot prove
 
 For Claude-specific support, run:
@@ -322,7 +321,7 @@ The intended split is:
 
 - `create-snipara`: Context + Memory onboarding, auth, config, inspect, repair, and upgrade
 - `snipara-openclaw-install`: OpenClaw-only setup wrapper that remains narrower than `create-snipara`
-- `snipara-companion`: default local workflow helper; legacy `rlm-hook` commands remain compatible
+- `snipara-companion`: default local workflow helper
 - `snipara-mcp`: local stdio bridge, client-package development, compatibility, and testing
 - `snipara-sandbox`: optional local execution engine
 
@@ -414,9 +413,9 @@ Recommended explanation to users:
 
 ## API Key Requirements
 
-Existing manual API keys passed to `create-snipara --api-key` should start with `snp-`;
-legacy `rlm_` keys remain accepted for migration. When `create-snipara` provisions a
-new account through the browser flow, Snipara returns a new `snp-` key from the current hosted API.
+Existing manual API keys passed to `create-snipara --api-key` must start with `snp-`.
+When `create-snipara` provisions a new account through the browser flow, Snipara returns
+a new `snp-` key from the current hosted API.
 Prefer `SNIPARA_API_KEY` or the interactive prompt over `--api-key`; CLI
 arguments can be visible in shell history and process listings.
 

package/dist/index.js

@@ -13,7 +13,7 @@ import { homedir } from "os";
 // package.json
 var package_default = {
   name: "create-snipara",
-  version: "1.3.30",
+  version: "1.3.31",
   description: "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   main: "dist/index.js",
   type: "module",
@@ -88,7 +88,6 @@ var BASE_URL = "https://www.snipara.com";
 var API_URL = "https://api.snipara.com";
 var COMPANION_PACKAGE_NAME = "snipara-companion";
 var COMPANION_COMMAND_NAME = "snipara-companion";
-var LEGACY_COMPANION_COMMAND_NAME = "rlm-hook";
 var GITHUB_ANSWER_PACKS_LABEL = "GitHub PR Answer Packs";
 var MCP_PACKAGE_NAME = "snipara-mcp";
 var SANDBOX_PACKAGE_NAME = "snipara-sandbox[all]";
@@ -520,7 +519,7 @@ async function gatherConfiguration(options) {
         {
           title: "I have an API key",
           value: "api",
-          description: "Paste an API key that starts with snp- or legacy rlm_"
+          description: "Paste an API key that starts with snp-"
         },
         {
           title: "Create free Context + Memory account",
@@ -889,10 +888,10 @@ function sleep(ms) {
 }
 function isManualApiKey(value) {
   const trimmed = value.trim();
-  return trimmed.startsWith("snp-") || trimmed.startsWith("rlm_");
+  return trimmed.startsWith("snp-");
 }
 function manualApiKeyValidationMessage() {
-  return "API key should start with snp- or legacy rlm_";
+  return "API key should start with snp-";
 }
 function warnApiKeyCliExposure() {
   console.log(
@@ -911,9 +910,6 @@ function detectCompanionCommand() {
   if (commandExists(COMPANION_COMMAND_NAME)) {
     return COMPANION_COMMAND_NAME;
   }
-  if (commandExists(LEGACY_COMPANION_COMMAND_NAME)) {
-    return LEGACY_COMPANION_COMMAND_NAME;
-  }
   return null;
 }
 function detectSandboxCommand() {
@@ -1041,7 +1037,7 @@ async function installNodeCompanion(upgrade) {
         return;
       }
       failures.push(
-        `${packageManager}: command completed but ${COMPANION_COMMAND_NAME} is still not available on PATH (legacy ${LEGACY_COMPANION_COMMAND_NAME} is also accepted)`
+        `${packageManager}: command completed but ${COMPANION_COMMAND_NAME} is still not available on PATH`
       );
     } catch (error) {
       const detail = error instanceof Error && "message" in error ? error.message.split("\n")[0] : "unknown error";
@@ -1203,7 +1199,7 @@ This project uses Snipara Hosted MCP for project context and reviewed memory.
 - Endpoint: \`${buildHostedMcpEndpoint(answers)}\`
 - Auth: use \`SNIPARA_API_KEY\` from the environment. Never commit keys.
 - For Codex, expose the endpoint as a streamable HTTP MCP server and load the
-  key from an environment variable such as \`SNIPARA_API_KEY\` or \`RLM_API_KEY\`.
+  key from \`SNIPARA_API_KEY\`.
 - At the start of every new thread, validate hosted MCP with a tool-oriented
   call such as \`snipara_settings\`, \`tools/list\`, or a lightweight
   \`snipara_context_query\`. Do not treat empty MCP resources/templates as an
@@ -1233,14 +1229,13 @@ Agent task lifecycle:
    is installed, run \`snipara-companion workflow start --goal "<goal>" --plan-file
    <plan_file>\`, then use \`workflow phase-start\`, \`workflow phase-commit\`,
    \`workflow resume\`, and \`final-commit\` so compaction cannot lose the next
-   phase. Legacy \`rlm-hook\` commands remain compatible.
+   phase.
 10. Use local file reads, \`rg\`, git commands, and test commands for exact edits,
     current working-tree state, and verification.
 11. Treat every \`snipara_code_*\` response as indexed context: check indexed
     commit SHA, indexing time, included file sample, coverage, freshness warnings,
-    and sync guidance before relying on it. Legacy \`rlm_code_*\` tool IDs return
-    the same payloads. If \`git status --short\` is dirty, warn that the indexed
-    graph may not include local edits.
+    and sync guidance before relying on it. If \`git status --short\` is dirty,
+    warn that the indexed graph may not include local edits.
 12. Use Snipara Sandbox only when sandboxed execution, repeatable validation, or
     isolated transformations materially help.
 13. If a broad query is slow, retry once with a narrow keyword query before
@@ -1272,9 +1267,9 @@ Use Snipara Hosted MCP before answering project-specific questions.
 - When \`snipara_context_query\` returns \`answer_pack\`, use its facts, caveats, source map, and verification checklist before drafting claims.
 - Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for structural code questions.
 - On paid Context plans, use \`snipara_code_symbol_card\` before editing important symbols and \`snipara_code_impact\` before risky multi-file changes or PR reviews.
-- Check every \`snipara_code_*\` response for indexed commit SHA, indexing time, included files, coverage, and freshness warnings. Legacy \`rlm_code_*\` IDs return the same payloads.
+- Check every \`snipara_code_*\` response for indexed commit SHA, indexing time, included files, coverage, and freshness warnings.
 - Use local file reads, \`rg\`, \`git status --short\`, and tests for exact edits/current working tree; use Snipara for architecture and indexed code graph context.
-- When the plan is visible and \`snipara-companion\` is installed, use \`snipara-companion workflow start\`, \`phase-start\`, \`phase-commit\`, \`workflow resume\`, and \`final-commit\` to keep phase state durable across compaction. Legacy \`rlm-hook\` commands remain compatible.
+- When the plan is visible and \`snipara-companion\` is installed, use \`snipara-companion workflow start\`, \`phase-start\`, \`phase-commit\`, \`workflow resume\`, and \`final-commit\` to keep phase state durable across compaction.
 - If generated hooks are enabled, \`snipara-companion pre-tool\`, \`post-tool\`, and \`stuck-guard status\` provide runtime Rescue Pack checks when the agent loops on failures or empty searches.
 - Use Snipara Sandbox only when sandboxed execution or repeatable validation materially helps.
 - End substantial work with \`snipara_end_of_task_commit\` when available; for managed workflows, end every phase with \`snipara-companion workflow phase-commit\` and the task with \`snipara-companion final-commit\`.
@@ -1301,10 +1296,10 @@ This workspace uses Snipara Hosted MCP for current project context, business/cli
 - Use \`snipara_get_chunk\` before relying on exact cited wording from reference-based results.
 - Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for structural code questions.
 - On paid Context plans, use \`snipara_code_symbol_card\` before editing important symbols and \`snipara_code_impact\` before risky multi-file changes or PR reviews.
-- Check every \`snipara_code_*\` response for indexed commit SHA, indexing time, included files, coverage, and freshness warnings. Legacy \`rlm_code_*\` IDs return the same payloads.
+- Check every \`snipara_code_*\` response for indexed commit SHA, indexing time, included files, coverage, and freshness warnings.
 - Use \`snipara_plan\` or \`snipara_decompose\` only for complex work and only when available.
 - Use local file reads, \`rg\`, \`git status --short\`, and tests for exact code edits and current working-tree state.
-- When \`snipara-companion\` is installed and the LLM has a visible multi-phase plan, use \`snipara-companion workflow start\`, \`phase-start\`, \`phase-commit\`, \`workflow resume\`, and \`final-commit\` so the next phase survives compaction. Legacy \`rlm-hook\` commands remain compatible.
+- When \`snipara-companion\` is installed and the LLM has a visible multi-phase plan, use \`snipara-companion workflow start\`, \`phase-start\`, \`phase-commit\`, \`workflow resume\`, and \`final-commit\` so the next phase survives compaction.
 - Generated hooks can call \`snipara-companion pre-tool\`, \`post-tool\`, and \`stuck-guard status\` so Rescue Packs are runtime-triggered rather than relying only on instructions.
 - Use Snipara Sandbox only when sandboxed execution or repeatable validation materially helps.
 - End substantial work with \`snipara_end_of_task_commit\` when available; for managed workflows, end every phase with \`snipara-companion workflow phase-commit\` and the task with \`snipara-companion final-commit\`. Use \`snipara_remember_if_novel\` or \`snipara_remember\` only for narrow durable memories. Never store secrets.
@@ -1498,8 +1493,6 @@ ${answers.projectId ? `export SNIPARA_PROJECT_ID="${answers.projectId}"` : ""}
 SNIPARA_COMPANION_BIN=""
 if command -v ${COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
   SNIPARA_COMPANION_BIN="${COMPANION_COMMAND_NAME}"
-elif command -v ${LEGACY_COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
-  SNIPARA_COMPANION_BIN="${LEGACY_COMPANION_COMMAND_NAME}"
 fi
 
 if [ -n "$SNIPARA_COMPANION_BIN" ]; then
@@ -1518,8 +1511,6 @@ ${answers.projectId ? `export SNIPARA_PROJECT_ID="${answers.projectId}"` : ""}
 SNIPARA_COMPANION_BIN=""
 if command -v ${COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
   SNIPARA_COMPANION_BIN="${COMPANION_COMMAND_NAME}"
-elif command -v ${LEGACY_COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
-  SNIPARA_COMPANION_BIN="${LEGACY_COMPANION_COMMAND_NAME}"
 fi
 
 if [ -n "$SNIPARA_COMPANION_BIN" ]; then
@@ -1541,8 +1532,6 @@ ${answers.projectId ? `export SNIPARA_PROJECT_ID="${answers.projectId}"` : ""}
 SNIPARA_COMPANION_BIN=""
 if command -v ${COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
   SNIPARA_COMPANION_BIN="${COMPANION_COMMAND_NAME}"
-elif command -v ${LEGACY_COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
-  SNIPARA_COMPANION_BIN="${LEGACY_COMPANION_COMMAND_NAME}"
 fi
 
 if [ -n "$SNIPARA_COMPANION_BIN" ]; then
@@ -1561,8 +1550,6 @@ ${answers.projectId ? `export SNIPARA_PROJECT_ID="${answers.projectId}"` : ""}
 SNIPARA_COMPANION_BIN=""
 if command -v ${COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
   SNIPARA_COMPANION_BIN="${COMPANION_COMMAND_NAME}"
-elif command -v ${LEGACY_COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
-  SNIPARA_COMPANION_BIN="${LEGACY_COMPANION_COMMAND_NAME}"
 fi
 
 if [ -n "$SNIPARA_COMPANION_BIN" ]; then
@@ -2431,7 +2418,6 @@ async function testHostedConnection(answers) {
     spinner.succeed("Connected to Snipara Hosted MCP.");
     const toolNames = extractMcpToolNames(toolsResponse.data);
     const hasSniparaTools = toolNames.some((name) => name.startsWith("snipara_"));
-    const hasLegacyTools = toolNames.some((name) => name.startsWith("rlm_"));
     const checks = [
       {
         name: "hosted_connection",
@@ -2440,11 +2426,11 @@ async function testHostedConnection(answers) {
       },
       {
         name: "hosted_tool_aliases",
-        status: hasSniparaTools ? "pass" : hasLegacyTools ? "warn" : "warn",
-        detail: hasSniparaTools ? "snipara_* tools are exposed by Hosted MCP" : hasLegacyTools ? "Only legacy rlm_* tool aliases were detected; Hosted MCP is usable but naming is stale" : "tools/list succeeded, but expected snipara_* tools were not detected"
+        status: hasSniparaTools ? "pass" : "warn",
+        detail: hasSniparaTools ? "snipara_* tools are exposed by Hosted MCP" : "tools/list succeeded, but expected snipara_* tools were not detected"
       }
     ];
-    const settingsTool = hasSniparaTools ? "snipara_settings" : hasLegacyTools ? "rlm_settings" : "snipara_settings";
+    const settingsTool = "snipara_settings";
     const settingsResponse = await callHostedMcp(answers, "tools/call", {
       name: settingsTool,
       arguments: {}
@@ -2639,9 +2625,7 @@ function printSuccess(answers, report) {
   printNextStep("Open .snipara/companion/README.md for local commands and repair flow.");
   printNextStep("Run create-snipara doctor anytime you want a fresh local validation report.");
   if (answers.installCompanion) {
-    printNextStep(
-      `${COMPANION_COMMAND_NAME} is the primary companion command; legacy ${LEGACY_COMPANION_COMMAND_NAME} remains compatible.`
-    );
+    printNextStep(`${COMPANION_COMMAND_NAME} is the companion command for local workflow helpers.`);
     printNextStep(
       `Use ${COMPANION_COMMAND_NAME} query / plan / upload / task-commit for explicit local workflows.`
     );
@@ -2797,7 +2781,7 @@ function resolveMaintenanceProfile(detection, explicitProfile) {
 function readApiKeyFromEnvFiles() {
   const candidates = [".env.local", ".env"];
   for (const file of candidates) {
-    const value = readEnvValueFromFile(file, ["SNIPARA_API_KEY", "RLM_API_KEY"]);
+    const value = readEnvValueFromFile(file, ["SNIPARA_API_KEY"]);
     if (value) {
       return value;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-snipara",
-  "version": "1.3.30",
+  "version": "1.3.31",
   "description": "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   "main": "dist/index.js",
   "type": "module",