create-snipara 1.3.19 → 1.3.21

package/dist/index.js

@@ -9,7 +9,7 @@ import fs from "fs";
 import path from "path";
 import { execSync, spawn } from "child_process";
 import { homedir } from "os";
-var VERSION = "1.3.19";
+var VERSION = "1.3.20";
 var BASE_URL = "https://www.snipara.com";
 var API_URL = "https://api.snipara.com";
 var COMPANION_PACKAGE_NAME = "snipara-companion";
@@ -1033,26 +1033,59 @@ 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\`.
+- 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
+  outage because Snipara may be tool-only.
 
 Agent task lifecycle:
 
-1. Start substantial work with \`snipara_recall\` and a targeted \`snipara_context_query\`.
+1. Start every new thread by validating hosted MCP availability, then use
+   project-scoped \`snipara_recall\` and a targeted \`snipara_context_query\` before
+   falling back to local documentation search.
 2. Use \`snipara_context_query\` for docs, business context, client/project truth, architecture notes, runbooks, and narrative source material.
 3. When \`snipara_context_query\` returns \`answer_pack\`, treat it as the first-pass response plan: use its source facts, caveats, source map, and verification checklist before drafting claims.
 4. Use \`snipara_get_chunk\` to load cited source sections returned by reference-based queries before relying on precise wording.
-5. Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for structural code questions.
-6. On paid Context plans, use \`snipara_code_symbol_card\` for agent-ready symbol context and \`snipara_code_impact\` before risky multi-file changes or PR reviews.
-7. Use \`snipara_plan\` or \`snipara_decompose\` only for complex work and only when the hosted server exposes them.
-8. When the LLM has produced a visible multi-phase plan and \`snipara-companion\` 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.
-9. Use local file reads, \`rg\`, git commands, and test commands for exact edits, current working-tree state, and verification.
-10. Treat every \`snipara_code_*\` response as indexed context: check its 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.
-11. If \`git status --short\` is dirty, warn that Snipara's indexed code graph may not include local edits; use local reads/tests for exact edits and Snipara for architecture/code graph context.
-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 falling back to local search.
-14. When generated hooks are enabled, \`snipara-companion pre-tool\`, \`post-tool\`, and \`stuck-guard status\` provide runtime Rescue Pack checks for repeated failures, empty searches, and risky workflows.
-15. End each substantial phase with \`snipara_end_of_task_commit\` or \`snipara-companion workflow phase-commit\` when companion manages the plan. End the whole managed workflow with \`snipara-companion final-commit\`.
-16. Use \`snipara_remember_if_novel\` for one reusable memory while avoiding duplicates, and use \`snipara_remember\` for explicit direct memory writes.
-17. Do not store secrets, tokens, passwords, private keys, raw logs, transient command output, or unreviewed guesses in memory.
+5. For coding tasks, choose a workflow mode before editing: LITE for small
+   single-phase changes, FULL managed workflow for multi-file, risky,
+   release/deploy, architectural, compaction-prone, or future-maintainer-sensitive
+   work.
+6. Use whichever structural code graph tools are exposed in the current session
+   for callers, imports, neighbors, and path questions. Tool exposure can vary.
+7. On paid Context plans, use \`snipara_code_symbol_card\` for agent-ready symbol
+   context and \`snipara_code_impact\` before risky multi-file changes, PR
+   reviews, routes, services, jobs, auth, billing, deployment, schema, migrations,
+   or explicit "what is missing" assessments.
+8. Use \`snipara_plan\` or \`snipara_decompose\` only for FULL-mode work and only
+   when the hosted server exposes them.
+9. When the LLM has produced a visible multi-phase plan and \`snipara-companion\`
+   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.
+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.
+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
+    falling back to local search.
+14. When generated hooks are enabled, \`snipara-companion pre-tool\`, \`post-tool\`,
+    and \`stuck-guard status\` provide runtime Rescue Pack checks for repeated
+    failures, empty searches, and risky workflows.
+15. End each substantial phase with \`snipara_end_of_task_commit\` or
+    \`snipara-companion workflow phase-commit\` when companion manages the plan.
+    End the whole managed workflow with \`snipara-companion final-commit\`.
+16. Use \`snipara_remember_if_novel\` for one reusable memory while avoiding
+    duplicates, and use \`snipara_remember\` for explicit direct memory writes.
+17. Do not store secrets, tokens, passwords, private keys, raw logs, transient
+    command output, or unreviewed guesses in memory.
 `;
 }
 function buildClaudeMdTemplate(answers) {
@@ -2252,15 +2285,10 @@ function printSuccess(answers, report) {
 }
 function commandExists(command) {
   try {
-    execSync(`${command} --version`, { stdio: "ignore", shell: "/bin/sh", timeout: 2500 });
+    execSync(`command -v ${command}`, { stdio: "ignore", shell: "/bin/sh", timeout: 500 });
     return true;
   } catch {
-    try {
-      execSync(`command -v ${command}`, { stdio: "ignore", shell: "/bin/sh", timeout: 1e3 });
-      return true;
-    } catch {
-      return false;
-    }
+    return false;
   }
 }
 function detectEnvironment() {

package/package.json

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