snipara-companion 3.2.30 → 3.2.31

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 Release notes for `snipara-companion`, newest first.
 
+## New In 3.2.31
+
+- Sends phase commits, final commits, and Team Sync handoffs to project-scoped
+  Why Capture with the existing goal, summary, files, verification commands,
+  session reference, and commit SHA.
+- Preserves reviewed-memory governance with an automatic read-only preview
+  followed by confirmation only when durable rationale candidates exist; filed
+  candidates remain `PENDING` in the review queue.
+- Keeps capture best-effort and observable in JSON receipts and the activity
+  timeline, so a Why Capture outage never rolls back a completed workflow or
+  handoff and never introduces a documentation prompt.
+
 ## New In 3.2.30
 
 - Persists an explicit `--ack-review-only` as a 15-minute, one-use

package/README.md

@@ -359,3 +359,9 @@ Launch assets, demo scripts, and post drafts live in
 [docs/launch/LAUNCH_KIT.md](./docs/launch/LAUNCH_KIT.md).
 
 Release notes live in [CHANGELOG.md](./CHANGELOG.md).
+When project auth is configured, `workflow phase-commit`, `final-commit`, and
+`team-sync handoff` also run reviewed Why Capture. The Companion first sends a
+read-only preview and confirms only when the server detects durable rationale.
+Confirmed candidates enter the pending review queue; capture failures remain
+visible but do not block the primary workflow command. No documentation prompt
+is shown.

package/dist/index.d.ts

@@ -441,6 +441,27 @@ interface SessionPersistResult {
     session_id: string;
     files_tracked: number;
 }
+type WhyCaptureSourceKind = "phase_commit" | "final_commit" | "handoff";
+interface WhyCaptureInput {
+    decision?: string;
+    why?: string;
+    rationale?: string;
+    sourceText?: string;
+    sourceKind: WhyCaptureSourceKind;
+    sourceSessionId?: string;
+    task?: string;
+    changedFiles?: string[];
+    commands?: string[];
+    commitSha?: string;
+    confirmed?: boolean;
+    previewOnly?: boolean;
+}
+interface WhyCaptureResult {
+    previewOnly: boolean;
+    confirmed: boolean;
+    candidateCount: number;
+    capturedCount?: number;
+}
 interface JournalAppendResult {
     success?: boolean;
     date?: string;
@@ -1273,6 +1294,7 @@ declare class RLMClient {
         payload?: Record<string, unknown>;
     }): Promise<EmitEventResult>;
     recordAdvisorInfluenceReceipt(input: RecordAdvisorInfluenceReceiptInput): Promise<RecordAdvisorInfluenceReceiptResult>;
+    captureWhy(input: WhyCaptureInput): Promise<WhyCaptureResult>;
     getAutomationEvents(args?: {
         sessionId?: string;
         limit?: number;