@wrongstack/core 0.301.0 → 0.302.2

package/dist/storage/session-event-bridge.d.ts

@@ -45,12 +45,12 @@ export interface SessionEventBridge {
     allows(type: SessionEvent['type']): boolean;
 }
 /** Core events that are always written regardless of auditLevel. */
-declare const CORE_RECONSTRUCT_EVENTS: Set<"agent_error" | "agent_spawned" | "agent_stopped" | "checkpoint" | "compaction" | "context_snapshot" | "error" | "file_event" | "file_observation" | "file_snapshot" | "in_flight_end" | "in_flight_start" | "llm_request" | "llm_response" | "message_appended" | "message_truncated" | "message_updated" | "messages_replaced" | "mode_changed" | "provider_error" | "provider_retry" | "rewound" | "session_end" | "session_forked" | "session_resumed" | "session_start" | "side_effect" | "skill_activated" | "skill_deactivated" | "spec_analyzed" | "spec_parsed" | "task_completed" | "task_created" | "task_failed" | "task_updated" | "tool_call_end" | "tool_call_start" | "tool_progress" | "tool_result" | "tool_use" | "user_input">;
+declare const CORE_RECONSTRUCT_EVENTS: Set<"agent_error" | "agent_spawned" | "agent_stopped" | "checkpoint" | "compaction" | "context_snapshot" | "error" | "file_event" | "file_observation" | "file_snapshot" | "in_flight_end" | "in_flight_start" | "llm_request" | "llm_response" | "message_appended" | "message_truncated" | "message_updated" | "messages_dropped" | "messages_replaced" | "mode_changed" | "provider_error" | "provider_retry" | "rewound" | "session_end" | "session_forked" | "session_resumed" | "session_start" | "side_effect" | "skill_activated" | "skill_deactivated" | "spec_analyzed" | "spec_parsed" | "task_completed" | "task_created" | "task_failed" | "task_updated" | "tool_call_end" | "tool_call_start" | "tool_progress" | "tool_result" | "tool_use" | "user_input">;
 /**
  * Events that are considered "standard" audit detail.
  * These are lightweight and high-value for forensics.
  */
-declare const STANDARD_AUDIT_EVENTS: Set<"agent_error" | "agent_spawned" | "agent_stopped" | "checkpoint" | "compaction" | "context_snapshot" | "error" | "file_event" | "file_observation" | "file_snapshot" | "in_flight_end" | "in_flight_start" | "llm_request" | "llm_response" | "message_appended" | "message_truncated" | "message_updated" | "messages_replaced" | "mode_changed" | "provider_error" | "provider_retry" | "rewound" | "session_end" | "session_forked" | "session_resumed" | "session_start" | "side_effect" | "skill_activated" | "skill_deactivated" | "spec_analyzed" | "spec_parsed" | "task_completed" | "task_created" | "task_failed" | "task_updated" | "tool_call_end" | "tool_call_start" | "tool_progress" | "tool_result" | "tool_use" | "user_input">;
+declare const STANDARD_AUDIT_EVENTS: Set<"agent_error" | "agent_spawned" | "agent_stopped" | "checkpoint" | "compaction" | "context_snapshot" | "error" | "file_event" | "file_observation" | "file_snapshot" | "in_flight_end" | "in_flight_start" | "llm_request" | "llm_response" | "message_appended" | "message_truncated" | "message_updated" | "messages_dropped" | "messages_replaced" | "mode_changed" | "provider_error" | "provider_retry" | "rewound" | "session_end" | "session_forked" | "session_resumed" | "session_start" | "side_effect" | "skill_activated" | "skill_deactivated" | "spec_analyzed" | "spec_parsed" | "task_completed" | "task_created" | "task_failed" | "task_updated" | "tool_call_end" | "tool_call_start" | "tool_progress" | "tool_result" | "tool_use" | "user_input">;
 /**
  * Create a safe, audit-level-aware bridge around a SessionWriter.
  *

package/dist/storage/session-store.d.ts

@@ -11,6 +11,9 @@ export declare class DefaultSessionStore implements SessionStore {
     private readonly logger;
     private readonly onAppend?;
     private readonly onAppendBatch?;
+    /** Present in built production output; source-only tests retain the local compatibility path. */
+    private readonly catalogClient;
+    private readonly maintenanceHolderId;
     /**
      * In-memory cache for load() results, keyed by session ID. The cache is
      * invalidated when the file's mtimeMs or size changes (indicating the
@@ -38,6 +41,7 @@ export declare class DefaultSessionStore implements SessionStore {
      * the file has changed externally (e.g., another process wrote to it).
      */
     clearLoadCache(sessionId?: string): void;
+    dispose(): Promise<void>;
     /** Absolute path to the session index file. */
     private get indexFile();
     /** Join session ID to its absolute path within the store directory. */
@@ -131,6 +135,8 @@ export declare class DefaultSessionStore implements SessionStore {
     private appendToIndexStrict;
     /** Best-effort index append used by writer close. */
     private appendToIndex;
+    /** Final summary boundary: daemon is authoritative when available. */
+    private persistCatalogSummary;
     /** Append a tombstone entry for a deleted session. */
     private writeTombstone;
     /**

package/dist/tools/index.js

@@ -8352,22 +8352,27 @@ var OneShotOrchestrator = class {
    */
   resolveFallbackChain(input, config, target) {
     const mgr = this.opts.fallbackProfileManager;
+    let fromExplicitSource = false;
     let selected = mgr.resolveEffective({
       fallbackAuto: false,
       exclude: target
     });
     if (input.fallbackModels && input.fallbackModels.length > 0) {
-      selected = mgr.resolveEffective({
+      const resolved = mgr.resolveEffective({
         fallbackModels: input.fallbackModels,
         fallbackAuto: false,
         exclude: target
       });
+      selected = resolved;
+      fromExplicitSource = resolved.length > 0;
     } else if (config.fallbackModels && config.fallbackModels.length > 0) {
-      selected = mgr.resolveEffective({
+      const resolved = mgr.resolveEffective({
         fallbackModels: config.fallbackModels,
         fallbackAuto: false,
         exclude: target
       });
+      selected = resolved;
+      fromExplicitSource = resolved.length > 0;
     } else if (config.fallbackAuto !== false) {
       selected = mgr.resolveEffective({
         fallbackAuto: true,
@@ -8375,6 +8380,7 @@ var OneShotOrchestrator = class {
       });
     }
     if (config.fallbackAuto === false) return selected;
+    if (fromExplicitSource) return selected;
     const combined = [...selected, ...mgr.resolveAllConfigured(target)];
     const seen = /* @__PURE__ */ new Set();
     return Object.freeze(

package/dist/types/context-evidence.d.ts

@@ -54,6 +54,8 @@ export interface CompletedWorkEvidence {
 }
 export interface ContextEvidenceState {
     currentIntent?: ContextIntentEvidence | undefined;
+    /** Recent real human inputs, bounded and rendered as volatile continuity evidence. */
+    recentUserTurns?: ContextIntentEvidence[] | undefined;
     sessionGoals: string[];
     implicitFacts: string[];
     activeErrors: string[];

package/dist/types/messages.d.ts

@@ -3,6 +3,14 @@ export type MessageRole = 'user' | 'assistant' | 'system';
 export interface Message {
     role: MessageRole;
     content: string | ContentBlock[];
+    /**
+     * Local provenance used by context management. `user_input` is reserved for
+     * text the human actually submitted; provider adapters intentionally ignore
+     * this field. Keeping it on the journaled message lets resumed sessions
+     * distinguish real conversation turns from tool-result/runtime `user`
+     * messages without relying on brittle text heuristics.
+     */
+    origin?: 'user_input' | 'runtime' | undefined;
     /**
      * ISO-8601 timestamp from the originating SessionEvent.
      * Populated by SessionStore.replay() during session load/resume

package/dist/types/session.d.ts

@@ -137,6 +137,23 @@ export type SessionEvent = {
      * payload had on disk. Absent on freshly emitted events.
      */
     messagesOmitted?: number;
+} | {
+    /**
+     * The oldest `count` messages were evicted from the front of the history.
+     *
+     * A delta rather than a `messages_replaced` snapshot, because eviction is
+     * the one rewrite that repeats: once a long session reaches
+     * `Context.MAX_MESSAGES`, *every* subsequent append overflows by one and
+     * drops one. Emitting the surviving history each time made the journal
+     * quadratic in session length — measured at 2.1 GB for one session whose
+     * actual content was ~10 MB, and 17.9 GB across a 20 GB corpus. Replay
+     * splices the same prefix off, so the reconstructed conversation is
+     * identical to what the snapshot would have produced.
+     */
+    type: 'messages_dropped';
+    ts: string;
+    version: 1;
+    count: number;
 } | {
     /**
      * Exact post-rewrite conversation state. Replay replaces all messages
@@ -590,6 +607,8 @@ export interface SessionStore {
      * number of sessions indexed.
      */
     rebuildIndex?(): Promise<number>;
+    /** Release project-daemon connections owned by this store. */
+    dispose?(): Promise<void>;
     /**
      * Streaming event-level search. Walks the JSONL once without buffering
      * the whole file, calling `predicate(event, eventIndex, ts)` for each

package/dist/utils/context-evidence.d.ts

@@ -1,5 +1,5 @@
 import type { Context } from '../core/context.js';
-import type { TextBlock } from '../types/blocks.js';
+import { type TextBlock } from '../types/blocks.js';
 import type { CompactReport } from '../types/compactor.js';
 import type { CompletedWorkEvidence, CompletedWorkSource, ContextEvidenceState, ToolOutputMetadata } from '../types/context-evidence.js';
 export declare function createContextEvidenceState(): ContextEvidenceState;
@@ -14,6 +14,18 @@ export interface RecordToolOutputEvidenceInput {
     outputLines?: number | undefined;
 }
 export declare function recordUserIntentEvidence(ctx: Context, text: string): void;
+/** Runtime steering/status blocks must not displace real conversation turns. */
+export declare function isRuntimeContextInput(text: string): boolean;
+/**
+ * Keep the real conversation thread visible near the stable system prompt.
+ *
+ * Tool-heavy runs can place hundreds of protocol messages after one human
+ * instruction. Re-sending a small, replaceable tail of actual user inputs is
+ * cheaper and more reliable than retaining every intervening tool exchange.
+ * It is volatile provider evidence, so it never grows the durable chat log or
+ * invalidates the cached base prompt.
+ */
+export declare function buildConversationContinuityBlock(ctx: Pick<Context, 'contextEvidence' | 'messages'>): TextBlock | undefined;
 export declare function recordToolOutputEvidence(ctx: Context, input: RecordToolOutputEvidenceInput): ToolOutputMetadata;
 export declare function markAssistantReferencedEvidence(ctx: Context, text: string): void;
 export declare function buildContextEvidenceDigest(ctx: Context): string;

package/dist/utils/index.js

@@ -855,6 +855,9 @@ var MAX_TOOL_CALLS = 80;
 var MAX_FACTS = 40;
 var MAX_ERRORS = 20;
 var MAX_DIGEST_CHARS = 4e3;
+var MAX_RECENT_USER_TURNS = 8;
+var MAX_USER_TURN_CHARS = 700;
+var RUNTIME_CONTEXT_INPUT_PATTERN = /^\[(?:kanban todo update|fleet pulse|loop-detector|todo-reconciliation|mailbox|btw|system|context_state)\b/i;
 var RECENT_TOOL_CALL_SCAN_LIMIT = 20;
 var EXTRACT_CONTENT_CAP_CHARS = 1e4;
 var EXTRACT_ERROR_TAIL_LINES = 200;
@@ -862,6 +865,7 @@ var WRITE_TOOLS = /* @__PURE__ */ new Set(["edit", "write", "replace", "patch"])
 var READ_TOOLS = /* @__PURE__ */ new Set(["read", "grep", "glob", "ls", "tree"]);
 function createContextEvidenceState() {
   return {
+    recentUserTurns: [],
     sessionGoals: [],
     implicitFacts: [],
     activeErrors: [],
@@ -873,15 +877,25 @@ function createContextEvidenceState() {
   };
 }
 function recordUserIntentEvidence(ctx, text) {
-  const intent = normalizeWhitespace(text).slice(0, 700);
+  if (isRuntimeContextInput(text)) return;
+  const intent = normalizeWhitespace(text).slice(0, MAX_USER_TURN_CHARS);
   if (!intent) return;
   const state = ensureEvidence(ctx);
-  state.currentIntent = { text: intent, updatedAt: Date.now() };
+  const turn = { text: intent, updatedAt: Date.now() };
+  state.currentIntent = turn;
+  state.recentUserTurns ??= [];
+  state.recentUserTurns.push(turn);
+  if (state.recentUserTurns.length > MAX_RECENT_USER_TURNS) {
+    state.recentUserTurns.splice(0, state.recentUserTurns.length - MAX_RECENT_USER_TURNS);
+  }
   if (state.sessionGoals.length === 0 || isGoalish(intent)) {
     pushUniqueBounded(state.sessionGoals, intent, 8);
   }
   state.updatedAt = Date.now();
 }
+function isRuntimeContextInput(text) {
+  return RUNTIME_CONTEXT_INPUT_PATTERN.test(text.trim());
+}
 function recordToolOutputEvidence(ctx, input) {
   const state = ensureEvidence(ctx);
   const scanContent = input.content.length > EXTRACT_CONTENT_CAP_CHARS ? input.content.slice(0, EXTRACT_CONTENT_CAP_CHARS) : input.content;
@@ -949,6 +963,11 @@ function buildContextEvidenceDigest(ctx) {
   if (state.currentIntent?.text) {
     lines.push(`intent: ${state.currentIntent.text}`);
   }
+  const priorTurns = (state.recentUserTurns ?? []).slice(-6, -1);
+  if (priorTurns.length > 0) {
+    lines.push("recent_human_instructions:");
+    for (const turn of priorTurns) lines.push(`- ${turn.text}`);
+  }
   const goals = state.sessionGoals.slice(-3);
   if (goals.length > 0) {
     lines.push("session_goals:");
@@ -1003,6 +1022,7 @@ function ensureEvidence(ctx) {
     ctx.contextEvidence = createContextEvidenceState();
   }
   ctx.contextEvidence.completedWork ??= [];
+  ctx.contextEvidence.recentUserTurns ??= [];
   return ctx.contextEvidence;
 }
 var MAX_COMPLETED_WORK = 50;
@@ -1709,12 +1729,16 @@ function buildLiveNextStepsGateBlock(ctx) {
   });
   const omitted = openTodos.length - todoSnapshot.length;
   if (omitted > 0) todoSnapshot.push(`- \u2026and ${omitted} more open todo(s)`);
+  const todoReconciliation = ctx.tools?.some((tool) => tool.name === "todo") ? [
+    "Before ending the turn, you MUST call the `todo` tool with the complete current list to reconcile actual progress: finished items completed, exactly one actively worked item in_progress, and untouched items pending. A prose claim that work is done does not update the Todo/Kanban state."
+  ] : [];
   return {
     type: "text",
     text: [
       "[nextsteps_gate]",
       `Authoritative live state for this request: open todos = ${openTodos.length}.`,
       "You MUST omit <nextsteps> entirely while these todos remain open. Continue or finish the tracked work; do not propose unrelated follow-on work.",
+      ...todoReconciliation,
       "Open todo snapshot:",
       ...todoSnapshot,
       "[/nextsteps_gate]"

package/instructions/system-lite.md

@@ -28,8 +28,16 @@ The user is an experienced developer; accelerate them and stay focused.
 6. Report what changed, what was verified, and what remains unverified.
 
 <!--ws:if tool=todo-->
-Use a visible `todo` list for tasks with three or more steps.
-Keep its status truthful; do not mark work complete while verification is pending.
+## Todo status lifecycle
+
+Use a visible `todo` list for tasks with three or more steps. It is authoritative session/UI state; prose does not update it.
+
+1. Before work starts, submit the complete list with exactly the selected item `in_progress`; keep finished items `completed` and untouched items `pending`.
+2. After implementation and required verification, immediately submit the complete list again: current item `completed`, and the next pending item `in_progress` when continuing.
+3. Before a final response, reconcile every status. Never leave finished work pending/running, never mark unverified work complete, and never repeat a continuation/next-step prompt instead of updating state.
+4. Submit the final all-`completed` snapshot even though it auto-clears afterward. Session-todo mirror cards map `pending → Todo`, `in_progress → Running`, `completed → Done`.
+
+If blocked, keep the item truthful and report the blocker instead of advancing it as successful.
 <!--ws:end-->
 If verification fails twice for unclear reasons, stop and re-read the source instead of guessing.
 
@@ -54,6 +62,7 @@ These conditions are mandatory whenever a task belongs to a Kanban board. They a
 2. **Fully specify every card before advancing it.** Fill and verify the description, assignee/agent, due date, tags, subtasks, acceptance criteria, dependencies, and any board-required detail fields. An under-filled card must remain in Backlog.
 3. **Persist every completed action immediately.** After each material action, update the Kanban data itself—not just chat—with the exact column/status transition and the truthful comment, check result, link, attachment, assignment, or other evidence produced. Never fake, batch away, or skip intermediate updates.
 4. **Follow the lifecycle exactly.** Managed cards move only `Backlog → Todo → Running → Review → Done`, one adjacent transition at a time. Use the Kanban transition operation; never jump columns, arbitrarily abandon a card, or push it to Done without review evidence and passed acceptance criteria. Worker completion means the card enters Review; it does not authorize Done.
+5. **Close and advance immediately.** Persist the accepted card in Running before work. Persist Running → Review when work finishes and Review → Done only after acceptance evidence passes. If continuing, move the next eligible card through adjacent transitions to Running before acting. Never leave completed work in Running or repeat a next-step prompt instead of updating the board.
 
 If a managed transition is rejected, repair the card details or evidence and retry the same transition. Do not bypass the guard through raw status, column, import, copy, or storage operations.
 <!--ws:end-->

package/instructions/system-pro.md

@@ -107,6 +107,19 @@ Reasoning depth is a dial, not a constant. Match it to the blast radius of what
 10. **Leave the knowledge behind, not just the diff.** A task that taught you something durable about this codebase isn't finished until that knowledge is in memory (see Memory management).
 11. **Keep helper scripts temporary and contained.** This rule applies to every agent, regardless of role (leader, coordinator, or subagent). Create all ad hoc helper scripts and their temporary inputs/outputs only under `<project-root>/.temp_files/` — never in the repository root or source directories. Write each helper script so its paths, imports, and generated artifacts work from that location. Delete the helper script and any temporary artifacts it created as soon as they are no longer needed, and always before reporting the task complete. Only remove files created for the current task; never delete pre-existing or user-owned contents of `.temp_files/`. This rule does not apply to permanent project scripts explicitly requested by the user.
 
+<!--ws:if tool=todo-->
+## Todo status lifecycle
+
+The live `todo` list is authoritative session state shared by the active UI and session-owned Kanban mirror. Prose does not change status.
+
+1. Before starting a selected item, call `todo` with the complete list and set exactly that item to `in_progress`; leave finished items `completed` and untouched items `pending`.
+2. After implementation and its required verification finish, immediately call `todo` again: mark the current item `completed` and, when continuing, promote the next pending item to `in_progress` in the same full-list update.
+3. Before any final response, reconcile the complete list. Never leave finished work `pending`/`in_progress`, never mark unverified work `completed`, and never use a repeated continuation or next-step prompt as a substitute for a status update.
+4. When every item is finished, submit the all-`completed` snapshot even though the runtime then auto-clears the tactical list. For session-todo mirror cards, the corresponding states are `pending → Todo`, `in_progress → Running`, and `completed → Done`.
+
+If work is blocked, keep its status truthful, state the blocker, and do not silently advance as though it succeeded.
+<!--ws:end-->
+
 <!--ws:if tool=kanban-->
 ## Work planning with Kanban
 
@@ -145,6 +158,7 @@ These conditions are mandatory whenever a task belongs to a Kanban board. They a
    An under-filled card must remain in Backlog. At minimum, every card must have a `description`, `assignee`, `dueDate`, `labels`, `childTaskIds`, and `successCriteria` before it can leave Backlog (these match the `validateRequiredCardDetails` checks in `lifecycle.ts`). Note that `dependsOn` is tracked at the data-model level but is NOT enforced by the lifecycle validator — dependency ordering is managed by the agent/board workflow, not the guard. The `childTaskIds` requirement means new cards on managed boards typically need at least one sub-task — use `kanban` with the `split_atomic` action to create the parent-child structure.
 3. **Persist every completed action immediately.** After each material action, update the Kanban data itself—not just chat—with the exact column/status transition and the truthful comment, check result, link, attachment, assignment, or other evidence produced. Never fake, batch away, or skip intermediate updates.
 4. **Follow the lifecycle exactly.** Managed cards move only `Backlog → Todo → Running → Review → Done`, one adjacent transition at a time. Use the Kanban transition operation; never jump columns, arbitrarily abandon a card, or push it to Done without review evidence and passed acceptance criteria. Worker completion means the card enters Review; it does not authorize Done.
+5. **Close and advance immediately.** Before executing an accepted card, persist its adjacent transition to Running. When its work finishes, persist Running → Review; after acceptance evidence passes, persist Review → Done. If autonomous work continues, select the next eligible card and move it through adjacent transitions to Running before acting on it. Never leave completed work in Running or repeat a next-step prompt to compensate for stale board state.
 
 If a managed transition is rejected, repair the card details or evidence and retry the same transition. Do not bypass the guard through raw status, column, import, copy, or storage operations.
 

package/instructions/system.md

@@ -48,6 +48,19 @@ This parse is **internal reasoning**, not something you output. It keeps you anc
 8. **Stay focused.** Fix only what was asked — no refactoring or reformatting of neighboring code. Comment only to explain *why*, not *what*. Don't lecture about engineering principles unless asked.
 9. **Keep helper scripts temporary and contained.** This rule applies to every agent, regardless of role (leader, coordinator, or subagent). Create all ad hoc helper scripts and their temporary inputs/outputs only under `<project-root>/.temp_files/` — never in the repository root or source directories. Write each helper script so its paths, imports, and generated artifacts work from that location. Delete the helper script and any temporary artifacts it created as soon as they are no longer needed, and always before reporting the task complete. Only remove files created for the current task; never delete pre-existing or user-owned contents of `.temp_files/`. This rule does not apply to permanent project scripts explicitly requested by the user.
 
+<!--ws:if tool=todo-->
+## Todo status lifecycle
+
+The live `todo` list is authoritative session state shared by the active UI and session-owned Kanban mirror. Prose does not change status.
+
+1. Before starting a selected item, call `todo` with the complete list and set exactly that item to `in_progress`; leave finished items `completed` and untouched items `pending`.
+2. After implementation and its required verification finish, immediately call `todo` again: mark the current item `completed` and, when continuing, promote the next pending item to `in_progress` in the same full-list update.
+3. Before any final response, reconcile the complete list. Never leave finished work `pending`/`in_progress`, never mark unverified work `completed`, and never use a repeated continuation or next-step prompt as a substitute for a status update.
+4. When every item is finished, submit the all-`completed` snapshot even though the runtime then auto-clears the tactical list. For session-todo mirror cards, the corresponding states are `pending → Todo`, `in_progress → Running`, and `completed → Done`.
+
+If work is blocked, keep its status truthful, state the blocker, and do not silently advance as though it succeeded.
+<!--ws:end-->
+
 <!--ws:if tool=kanban-->
 ## Work planning with Kanban
 
@@ -84,6 +97,7 @@ These conditions are mandatory whenever a task belongs to a Kanban board. They a
    An under-filled card must remain in Backlog. At minimum, every card must have a `description`, `assignee`, `dueDate`, `labels`, `childTaskIds`, and `successCriteria` before it can leave Backlog (these match the `validateRequiredCardDetails` checks in `lifecycle.ts`). Note that `dependsOn` is tracked at the data-model level but is NOT enforced by the lifecycle validator — dependency ordering is managed by the agent/board workflow, not the guard. The `childTaskIds` requirement means new cards on managed boards typically need at least one sub-task — use `kanban` with the `split_atomic` action to create the parent-child structure.
 3. **Persist every completed action immediately.** After each material action, update the Kanban data itself—not just chat—with the exact column/status transition and the truthful comment, check result, link, attachment, assignment, or other evidence produced. Never fake, batch away, or skip intermediate updates.
 4. **Follow the lifecycle exactly.** Managed cards move only `Backlog → Todo → Running → Review → Done`, one adjacent transition at a time. Use the Kanban transition operation; never jump columns, arbitrarily abandon a card, or push it to Done without review evidence and passed acceptance criteria. Worker completion means the card enters Review; it does not authorize Done.
+5. **Close and advance immediately.** Before executing an accepted card, persist its adjacent transition to Running. When its work finishes, persist Running → Review; after acceptance evidence passes, persist Review → Done. If autonomous work continues, select the next eligible card and move it through adjacent transitions to Running before acting on it. Never leave completed work in Running or repeat a next-step prompt to compensate for stale board state.
 
 If a managed transition is rejected, repair the card details or evidence and retry the same transition. Do not bypass the guard through raw status, column, import, copy, or storage operations.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrongstack/core",
-  "version": "0.301.0",
+  "version": "0.302.2",
   "license": "MIT",
   "description": "WrongStack core: kernel, types, defaults, and shared utilities for the WrongStack CLI agent.",
   "repository": {
@@ -96,6 +96,10 @@
       "types": "./dist/storage/index.d.ts",
       "import": "./dist/storage/index.js"
     },
+    "./session-catalog": {
+      "types": "./dist/session-catalog/index.d.ts",
+      "import": "./dist/session-catalog/index.js"
+    },
     "./security": {
       "types": "./dist/security/index.d.ts",
       "import": "./dist/security/index.js"
@@ -173,8 +177,8 @@
   "wrongstackApiVersion": "0.1.10",
   "dependencies": {
     "zod": "4.4.3",
-    "@wrongstack/kanban": "0.301.0",
-    "@wrongstack/persistence": "0.301.0"
+    "@wrongstack/persistence": "0.302.2",
+    "@wrongstack/kanban": "0.302.2"
   },
   "devDependencies": {
     "@types/node": "^26.1.2",