create-snipara 1.3.15 → 1.3.16

package/dist/index.js

@@ -974,9 +974,10 @@ Agent task lifecycle:
 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. 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\`.
-15. Use \`snipara_remember_if_novel\` for one reusable memory while avoiding duplicates, and use \`snipara_remember\` for explicit direct memory writes.
-16. Do not store secrets, tokens, passwords, private keys, raw logs, transient command output, or unreviewed guesses in memory.
+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) {
@@ -997,6 +998,7 @@ Use Snipara Hosted MCP before answering project-specific questions.
 - 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.
 - 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.
+- 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\`.
 - Use \`snipara_remember_if_novel\` or \`snipara_remember\` only for narrow durable memories.
@@ -1026,6 +1028,7 @@ This workspace uses Snipara Hosted MCP for current project context, business/cli
 - 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.
+- 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.
 `;
@@ -1121,6 +1124,10 @@ async function installClaudeCodeHooks(answers) {
     fs.mkdirSync(hooksDir, { recursive: true });
   }
   const hooks = [
+    {
+      name: "snipara-stuck-guard.sh",
+      content: createStuckGuardHook(answers)
+    },
     {
       name: "snipara-startup.sh",
       content: createStartupHook(answers)
@@ -1152,6 +1159,11 @@ async function installClaudeCodeHooks(answers) {
   settings.hooks = settings.hooks || {};
   const hooksConfig = settings.hooks;
   const hookEntries = [
+    {
+      event: "PreToolUse",
+      script: path.join(hooksDir, "snipara-stuck-guard.sh"),
+      matcher: { tool_name: "Bash|Read|Grep|Glob|Edit|MultiEdit|Write" }
+    },
     {
       event: "PreToolUse",
       script: path.join(hooksDir, "snipara-startup.sh"),
@@ -1160,7 +1172,7 @@ async function installClaudeCodeHooks(answers) {
     {
       event: "PostToolUse",
       script: path.join(hooksDir, "snipara-session.sh"),
-      matcher: { tool_name: "Bash" }
+      matcher: { tool_name: "Bash|Read|Grep|Glob|Edit|MultiEdit|Write" }
     },
     {
       event: "PreCompact",
@@ -1180,6 +1192,26 @@ async function installClaudeCodeHooks(answers) {
   fs.writeFileSync(settingsPath, JSON.stringify(settings, null, 2) + "\n");
   console.log(chalk.green("   \u2713 Updated ~/.claude/settings.json"));
 }
+function createStuckGuardHook(answers) {
+  return `#!/usr/bin/env bash
+set -euo pipefail
+
+export SNIPARA_PROJECT_SLUG="${answers.projectSlug}"
+${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
+  INPUT=$(cat || true)
+  "$SNIPARA_COMPANION_BIN" pre-tool "$INPUT" || true
+fi
+`;
+}
 function createStartupHook(answers) {
   return `#!/usr/bin/env bash
 set -euo pipefail
@@ -1218,7 +1250,8 @@ elif command -v ${LEGACY_COMPANION_COMMAND_NAME} >/dev/null 2>&1; then
 fi
 
 if [ -n "$SNIPARA_COMPANION_BIN" ]; then
-  "$SNIPARA_COMPANION_BIN" emit-event --event-type tool_result --json '{"source":"claude-code-hook"}' || true
+  INPUT=$(cat || true)
+  "$SNIPARA_COMPANION_BIN" post-tool "$INPUT" || true
 fi
 `;
 }
@@ -1431,6 +1464,16 @@ function getCompanionCommands(answers) {
       command: `${COMPANION_COMMAND_NAME} session-bootstrap`,
       purpose: "Load durable decisions, learnings, and optional short-lived carryover at session start."
     },
+    {
+      title: "Check Stuck Guard status",
+      command: `${COMPANION_COMMAND_NAME} stuck-guard status`,
+      purpose: "Inspect whether recent tool failures, empty searches, or risky workflow signals should trigger a Rescue Pack."
+    },
+    {
+      title: "Simulate a Stuck Guard fixture",
+      command: `${COMPANION_COMMAND_NAME} stuck-guard simulate --fixture ./stuck-guard-fixture.json`,
+      purpose: "Replay canonical events against the hosted Stuck Guard decision API before enabling stricter modes."
+    },
     {
       title: "Ask memory about past decisions",
       command: `${COMPANION_COMMAND_NAME} recall --query "What did we decide about auth retries?" --type decision`,

package/package.json

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