snipara-companion 1.3.6 → 1.3.7

package/README.md

@@ -59,6 +59,19 @@ yarn global add snipara-companion
 snipara-companion
 ```
 
+## New In 1.3.7
+
+- Hardens `memory-guard check` with `--confirmed-by-user "<confirmation>"`
+  for explicit, auditable overrides after the user has reviewed destructive or
+  contradictory signals.
+- Adds stable guard exit codes in strict mode: `20` for confirmation required,
+  `21` for unavailable memory/context guidance, and `22` for invalid guard
+  options.
+- Validates destructive checks before hosted calls so vague commands such as
+  `--destructive` without `--intent` or `--command` fail fast.
+- Extends `snipara-companion init --with-hooks` so it also installs local code
+  overlay Git hooks (`post-commit` sync and `pre-push` promotion/reindex).
+
 ## New In 1.3.6
 
 - Adds `snipara-companion memory audit` for a read-only memory hygiene pass that
@@ -661,6 +674,11 @@ snipara-companion memory-guard check \
   --intent "npm publish snipara-companion" \
   --destructive \
   --strict
+snipara-companion memory-guard check \
+  --intent "npm publish snipara-companion" \
+  --destructive \
+  --strict \
+  --confirmed-by-user "User confirmed npm publish after reviewing guard output"
 ```
 
 When memory or source context contradicts the requested action, the JSON output
@@ -668,6 +686,13 @@ sets `requiresConfirmation=true`, includes `contradictions`, and provides a
 `confirmationPrompt`. In `--strict` mode the command exits non-zero until the
 operator has explicitly confirmed the override.
 
+Strict mode exit codes:
+
+- `20`: confirmation is required before continuing.
+- `21`: memory/context guidance was unavailable for a triggered guard.
+- `22`: guard options were invalid, for example `--destructive` without a
+  specific `--intent` or `--command`.
+
 ### Commit Memory Policy
 
 Companion separates two concepts:

package/dist/index.d.ts

@@ -1000,6 +1000,7 @@ interface MemoryGuardFinding {
     code: "recent_failure" | "release_surface" | "manual" | "destructive_intent" | "contradiction";
     message: string;
 }
+type MemoryGuardBlockReason = "confirmation_required" | "guidance_unavailable";
 interface MemoryGuardContradiction {
     source: "memory" | "context";
     reason: string;
@@ -1020,6 +1021,7 @@ interface MemoryGuardCheckOptions {
     status?: string;
     destructive?: boolean;
     requireConfirmation?: boolean;
+    confirmedByUser?: string;
     strict?: boolean;
     json?: boolean;
     limit?: number;
@@ -1027,9 +1029,18 @@ interface MemoryGuardCheckOptions {
     includeContext?: boolean;
     recentFailures?: boolean;
 }
+interface MemoryGuardConfirmation {
+    required: boolean;
+    confirmed: boolean;
+    note?: string;
+    overridesDestructive: boolean;
+    overridesContradictions: boolean;
+}
 interface MemoryGuardCheckResult {
     triggered: boolean;
     shouldBlock: boolean;
+    blockReason?: MemoryGuardBlockReason;
+    exitCode: number;
     trigger: MemoryGuardTrigger;
     findings: MemoryGuardFinding[];
     files: string[];
@@ -1047,6 +1058,7 @@ interface MemoryGuardCheckResult {
     destructive: boolean;
     contradictions: MemoryGuardContradiction[];
     requiresConfirmation: boolean;
+    confirmation: MemoryGuardConfirmation;
     confirmationPrompt?: string;
     memoryAvailable: boolean;
     contextAvailable: boolean;