snipara-companion 3.6.21 → 3.6.22

package/CHANGELOG.md

@@ -4,6 +4,15 @@ Release notes for `snipara-companion`, newest first.
 
 ## Unreleased
 
+## New In 3.6.22 - 2026-09-12
+
+- Saves explicit session summaries and file checkpoints to the hosted journal,
+  requiring a journal entry id before reporting success or rotating the session.
+- Retains bounded, redacted local receipts and supports `session-end --retry`
+  after a failed write. Empty checkpoints are explicitly skipped.
+- Supports summary input through stdin and host session ids for Codex Stop hooks.
+  Reports telemetry delivery separately from journal persistence.
+
 ## New In 3.6.21 - 2026-08-31
 
 - Requires manual device-code entry and explicit all-project consent for the

package/README.md

@@ -664,6 +664,21 @@ 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).
+
+`session-end --summary "What was completed" --files src/example.ts` saves a
+session checkpoint to the hosted journal and prints a local receipt path.
+Hooks can pass the summary through `--summary-stdin` and use `--session-id` for
+the host task identity. Without a summary or files, the checkpoint is explicitly
+skipped. A failed write keeps the checkpoint and session id; retry the printed
+receipt with `session-end --retry <receipt.json>`. `session status` shows the last
+checkpoint status. Receipts live in `.snipara/companion/session-closeouts/` and
+contain a bounded, redacted summary; they are local artifacts, not source files.
+A journal entry id confirms persistence; automation event delivery is reported
+separately. A timeout can leave server acceptance uncertain, so a retry after an
+unconfirmed response may create a second journal entry. New Codex hook bundles
+forward the final assistant summary; older hooks need to be refreshed to do so.
+This checkpoint preserves session context; it does not generate product docs.
+
 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.

package/dist/index.d.ts

@@ -48,6 +48,12 @@ declare function saveConfig(config: Partial<RLMConfig>, options?: ConfigResoluti
  */
 declare function getConfigPath(options?: ConfigResolutionOptions): string;
 
+interface SessionCheckpoint {
+    sessionId: string;
+    summary: string;
+    files: string[];
+}
+
 interface ContextQueryResult {
     sections: Array<{
         title: string;
@@ -320,6 +326,9 @@ interface SessionPersistResult {
     success: boolean;
     session_id: string;
     files_tracked: number;
+    status: "saved" | "skipped";
+    entry_id?: string;
+    date?: string;
 }
 type WhyCaptureSourceKind = "commit" | "phase_commit" | "final_commit" | "handoff";
 interface WhyCaptureInput {
@@ -379,6 +388,7 @@ interface EndOfTaskCommitWhyInput {
 }
 interface JournalAppendResult {
     success?: boolean;
+    entry_id?: string;
     date?: string;
     message?: string;
 }
@@ -1185,9 +1195,10 @@ declare class RLMClient {
      */
     trackFiles(files: string[]): Promise<TrackFileResult>;
     /**
-     * Persist session context using snipara_remember
+     * Persist an explicit bounded checkpoint to the hosted journal. An event
+     * acknowledgement is not a persistence receipt.
      */
-    persistSession(): Promise<SessionPersistResult>;
+    persistSession(input?: Partial<SessionCheckpoint>): Promise<SessionPersistResult>;
     /**
      * Recall memories with optional lifecycle warnings.
      */