@winspan/claude-forge 8.54.4 → 9.12.0

package/dist/daemon/services/task-segmenter.d.ts

@@ -1,20 +1,249 @@
 import type { SQLiteStorage } from '../../core/storage/sqlite.js';
+/**
+ * decision f47c2c90 (二期B, spec 1711): conservative ack-title set for the
+ * parent_task_id linkage. A follow-up task's title matching one of these short
+ * tokens marks it as an approval/continue turn (gate 1 of the triple-gate, in
+ * tandem with the live isContinuationPrompt check on the prompt). Kept as a
+ * lowercase exact-match set because titles are short ack tokens, not free text.
+ * Passed verbatim to storage.getMostRecentUserTaskBefore so the segmenter is the
+ * single source of truth for "what counts as an ack title" (the boot backfill
+ * keeps its own mirror because it has no access to this daemon module).
+ */
+export declare const PARENT_LINK_ACK_TITLES: ReadonlyArray<string>;
+/**
+ * Task-tracking overhaul (2026-05-27 spec §3.3 / §R4).
+ *
+ * Bug 3 orphan recovery window. When linkEvent fires without an active
+ * task (e.g. Stop already closed it but sub-agent PostToolUse is still
+ * landing), we attach the event to the most recently completed task on
+ * the session IF it ended within this window. Default 5 min — short
+ * enough to avoid cross-task mis-attribution, long enough to absorb
+ * typical async sub-agent tool flushes (observed 1-4 min in production).
+ *
+ * Exported as `const` (not env-tunable) on purpose: changing it changes
+ * KPI semantics and should be a code review event. R4 mitigation: pure
+ * attachment, end_time is NOT updated by the fallback path (Q3).
+ */
+export declare const ORPHAN_RECOVERY_WINDOW_MS: number;
+/**
+ * decision 265f59d5: result of a boundary decision. When `ambiguous` is set,
+ * the sync path best-effort MERGED `prompt`'s event into `taskId`, but lexical
+ * signals were inconclusive — the daemon should hand this off to the async
+ * {@link TaskBoundaryClassifier} for a possible re-attribution. When undefined,
+ * the decision was unambiguous (clear ack / clear new-task / hard signal) and
+ * no LLM call is warranted.
+ */
+export interface BoundaryDecision {
+    /** The task id the synchronous path assigned the prompt to. */
+    taskId: string;
+    /**
+     * Present only when the prompt was MERGED into an already-active task via the
+     * ambiguous default (no ack token, no NEW_TASK_KEYWORD, no hard signal).
+     */
+    ambiguous?: {
+        sessionId: string;
+        mergedTaskId: string;
+        eventId: string;
+        prompt: string;
+        timestamp: string;
+    };
+}
 export declare class TaskSegmenter {
     private storage;
     private currentTasks;
     constructor(storage: SQLiteStorage);
     processPrompt(sessionId: string, prompt: string, timestamp: string, eventId?: string): string;
-    linkEvent(sessionId: string, eventId: string): void;
+    /**
+     * decision 265f59d5: same synchronous best-effort segmentation as
+     * {@link processPrompt}, but also reports whether the result was an AMBIGUOUS
+     * merge so the daemon can enqueue an async LLM re-attribution. The hot path is
+     * unchanged — this returns immediately; the LLM call (if any) is the caller's
+     * fire-and-forget responsibility.
+     */
+    processPromptWithBoundary(sessionId: string, prompt: string, timestamp: string, eventId?: string): BoundaryDecision;
+    /**
+     * Attach a non-prompt event (PostToolUse / PreToolUse / Stop / spawn …) to the
+     * session's currently-open task and refresh `lastTime`.
+     *
+     * Refreshing `lastTime` here is the critical part of the long-flow fix
+     * (2026-05-25): without it, `shouldStartNewTask` only sees the gap between
+     * user prompts, so a 20-minute background-agent run with hundreds of tool
+     * calls looks identical to the user walking away. The next prompt then trips
+     * `TASK_SWITCH_MINUTES` and the post-spawn work gets re-attributed to a
+     * brand-new task — exactly the symptom seen in task 36471706.
+     *
+     * `timestamp` is optional for backward compatibility; callers that already
+     * know the event timestamp should pass it (we trust hook timestamps more
+     * than wall-clock here because event delivery can be queued/replayed).
+     */
+    linkEvent(sessionId: string, eventId: string, timestamp?: string, opts?: {
+        hookType?: string;
+        toolName?: string;
+    }): void;
     /**
      * 从数据库恢复 session 的 active 任务到内存 Map。
      * 用于 daemon 重启后内存丢失场景的 lazy 恢复。
      * 找不到 active 任务时返回 null（不报错）。
+     *
+     * spec b1480935 (2026-06-01 Option A): only `task_kind='user'` tasks are
+     * eligible — callback / image / system rows MUST NOT be re-installed as
+     * the session's "current task" or every subsequent event would attach
+     * to an envelope row. The legacy `!is_noise` guard is preserved as a
+     * fallback for rows where backfill hasn't yet promoted task_kind.
+     *
+     * Orphan-event robustness fix (2026-06-01): switched from
+     * `queryTasks(limit:5).find(...)` to a DIRECT `getActiveUserTask()` SQL
+     * lookup. The old path took the most-recent 5 rows THEN filtered — on a
+     * high-task-count session a burst of newer agent-callback / completed rows
+     * pushed the active user task out of the top-5, so `.find()` returned null
+     * and every event after it orphaned. The direct query applies the predicate
+     * at the DB layer with no LIMIT truncation.
      */
     private recoverActiveTask;
+    /**
+     * Orphan-event robustness fix (2026-06-01): proactively re-populate the
+     * in-memory `currentTasks` map from the DB at daemon startup.
+     *
+     * Problem: after a daemon restart `currentTasks` is empty, so every event
+     * relies on per-event lazy `recoverActiveTask`. During the restart window a
+     * burst of buffered + replayed events arrives; any whose recovery heuristic
+     * doesn't fire (e.g. the orphan-recovery smart window finds no completed
+     * task) gets dropped. Hydrating up-front means those events hit the fast
+     * `currentTasks.get()` path instead.
+     *
+     * Idempotent + fault-tolerant: safe to call multiple times (it overwrites
+     * with the same DB-derived state) and never throws — a query failure logs
+     * and leaves the map untouched so the daemon still starts.
+     *
+     * @returns number of sessions hydrated (useful for the startup log line).
+     */
+    hydrateActiveTasks(): number;
+    /**
+     * decision c6613590 P0 缺陷 B: trusted map-hit accessor.
+     *
+     * The in-memory `currentTasks` map can hold a DANGLING pointer to a task the
+     * stale-task GC (daemon/index.ts `completeStaleActiveTasks`) already flipped
+     * to status='completed' in the DB. The old code trusted any map hit blindly,
+     * so a new prompt / late event would `linkEventToTask` onto that completed
+     * row — advancing its end_time and merging independent prompts into a stale
+     * task.
+     *
+     * Two defences run together (spec: "两个都修最稳"):
+     *   1. daemon evicts GC'd ids from the map (see {@link evictTasks}); but a
+     *      daemon that never restarts can still race the 5-min GC tick.
+     *   2. THIS guard PK-rechecks `status='active'` before trusting a map hit.
+     *      If the row is no longer active, we drop the stale entry and fall back
+     *      to `recoverActiveTask` (DB-authoritative). This makes the map a cache,
+     *      never an authority, for the active-task invariant.
+     */
+    private getTrustedCurrent;
+    /**
+     * decision c6613590 P0 缺陷 B: evict the given task ids from the in-memory
+     * `currentTasks` map. Called by the daemon's stale-task GC after it flips
+     * those tasks to 'completed' in the DB, so the map never keeps a dangling
+     * pointer that drags a closed task's end_time forward.
+     *
+     * Keyed by sessionId (the map's key), but we also verify the mapped task id
+     * matches before deleting — a session whose active task was already replaced
+     * by a newer one must NOT have its live entry evicted just because an older
+     * task on the same session was GC'd.
+     *
+     * @returns number of map entries actually evicted (for the daemon log line).
+     */
+    evictTasks(closed: Array<{
+        id: string;
+        session_id: string;
+    }>): number;
     getCurrentTaskId(sessionId: string): string | null;
     completeCurrentTask(sessionId: string, timestamp: string): void;
+    /**
+     * Boundary decision for the synchronous path.
+     *
+     * spec 1713 (2026-05-28) introduced the hard-signal boundary
+     * ({@link shouldStartNewTaskHard}); spec b1480935 (2026-06-01) kept the
+     * legacy keyword heuristic for the live daemon. We UNION the two so the
+     * decision is the strictly-more-eager of the pair: a new task starts if
+     * EITHER an explicit hard signal fires (5-min window / RESET_KEYWORDS /
+     * sub-agent return) OR the legacy keyword heuristic asks for it. This keeps
+     * every previously-passing keyword case green while satisfying the spec-1713
+     * hard-signal contract. The async classifier (when wired) corrects any
+     * over- or under-split after the fact.
+     */
     private shouldStartNewTask;
+    /**
+     * spec 1713 §10.2: the hard-signal boundary. Returns true when an OBJECTIVE
+     * marker says "new task":
+     *   1. a sub-agent just returned (agentJustReturned flag) → consumes the flag
+     *   2. gap > HARD_TIME_WINDOW_MIN (5 min)
+     *   3. an explicit RESET_KEYWORD appears in the prompt
+     *
+     * Pure of keyword *heuristics* (NEW_TASK_KEYWORDS) — those live in the legacy
+     * path. Mutates `current.agentJustReturned` (clears it) by design: the flag
+     * is a one-shot that only forces the immediately-following prompt.
+     */
+    private shouldStartNewTaskHard;
     private createTask;
     private extractTitle;
 }
+/**
+ * Task-tracking overhaul (2026-05-27 spec §3.2).
+ *
+ * Compute the is_noise flag for a freshly-extracted task title. Three
+ * heuristics, all conservative — the goal is to drop obvious envelope /
+ * sub-3-char / slash-command noise WITHOUT eating real user prompts:
+ *
+ *   • length(trim(title)) < 3 — sub-3-char titles ('好的'=2, 'ok'=2,
+ *     single CJK char). Note: spec §3.2 lists '好的' as expected-noise
+ *     and '推送吧'=3 as expected-real; this matches.
+ *   • title matches one of NOISE_PROMPT_PREFIXES (envelope tags emitted
+ *     by the framework on UserPromptSubmit).
+ *   • title is a single-word slash command (`/help`, `/login`, …) — the
+ *     user didn't actually start a new task, they fired a CC slash menu.
+ *
+ * What this DOES NOT flag (intentional — spec §3.2):
+ *   - Semantic acknowledgements like '批准' / 'approve' / 'ok' / '可以'.
+ *     Those titles should never reach createTask once SpecGate.handle
+ *     Approval is wired in Step 6. If they DO arrive in the meantime
+ *     (e.g. test seeds, legacy bug, race), Web shows them so the user
+ *     can spot the regression rather than silently dropping them.
+ *
+ * Exported for unit-test reuse; the production caller is
+ * TaskSegmenter.createTask above.
+ */
+export declare function computeIsNoise(title: string): boolean;
+/**
+ * True if the prompt is actually a tool-generated envelope (task-notification,
+ * system-reminder, image attachment, etc.) rather than a real human prompt.
+ *
+ * Thin wrapper over the canonical {@link isNoisePrompt} (core/utils). Kept
+ * as a named export so existing imports stay stable; each consumer's
+ * "what to do with noise" decision still lives at the call site (spec-gate
+ * skips auto-spec, here we skip task creation).
+ */
+export declare function isNoisePromptForSegmenter(prompt: string): boolean;
+/**
+ * True if the prompt is a genuine short continuation / acknowledgement
+ * ("继续" / "好的，这样可以" / "对对对" / "ok" / "批准" …) that should resume
+ * a recently-completed task via the B+ smart-window gate.
+ *
+ * decision c6613590 P0 缺陷 A — the old implementation (and the now-retired
+ * `CONTINUE_KEYWORDS` table) was `CONTINUE_KEYWORDS.some(kw => prompt.includes(kw))`,
+ * a pure SUBSTRING match.
+ * Because the keyword list contained '不是' / '这个' / '那个' / '它' / '不对',
+ * ordinary NEW questions were mis-classified as continuations and merged into
+ * a stale task:
+ *   • "现在全链路是不是都顺了?知识库、skill都正常了吗"  → '不是' matched
+ *   • "这个任务怎么又丢了?老是丢数据不行啊"            → '这个' matched
+ *
+ * The fix has two layers, BOTH must hold:
+ *   1. Length gate — the trimmed prompt must be ≤ ACK_MAX_LEN. A genuine ack
+ *      is short; a multi-clause question is not.
+ *   2. Ack-token presence — an ACK_CONTINUE_KEYWORD (collision-prone tokens
+ *      removed) must appear in the (short) prompt.
+ *
+ * This keeps every real ack a continuation ("继续"/"好的，这样可以"/"对对对"/
+ * "好的可以这样做") while the two real-world merge bugs above now return false
+ * and correctly start a new task. Exported for unit-test reuse.
+ */
+export declare function isContinuationPrompt(prompt: string): boolean;
 //# sourceMappingURL=task-segmenter.d.ts.map

package/dist/daemon/services/task-segmenter.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"task-segmenter.d.ts","sourceRoot":"","sources":["../../../src/daemon/services/task-segmenter.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAmBlE,qBAAa,aAAa;IAGZ,OAAO,CAAC,OAAO;IAF3B,OAAO,CAAC,YAAY,CAAuD;gBAEvD,OAAO,EAAE,aAAa;IAE1C,aAAa,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM;IAoB7F,SAAS,CAAC,SAAS,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,IAAI;IAOnD;;;;OAIG;IACH,OAAO,CAAC,iBAAiB;IAezB,gBAAgB,CAAC,SAAS,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI;IAIlD,mBAAmB,CAAC,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,IAAI;IAU/D,OAAO,CAAC,kBAAkB;IAW1B,OAAO,CAAC,UAAU;IAQlB,OAAO,CAAC,YAAY;CAMrB"}
+{"version":3,"file":"task-segmenter.d.ts","sourceRoot":"","sources":["../../../src/daemon/services/task-segmenter.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AA0ElE;;;;;;;;;GASG;AACH,eAAO,MAAM,sBAAsB,EAAE,aAAa,CAAC,MAAM,CAGxD,CAAC;AAEF;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,yBAAyB,QAAa,CAAC;AAEpD;;;;;;;GAOG;AACH,MAAM,WAAW,gBAAgB;IAC/B,+DAA+D;IAC/D,MAAM,EAAE,MAAM,CAAC;IACf;;;OAGG;IACH,SAAS,CAAC,EAAE;QACV,SAAS,EAAE,MAAM,CAAC;QAClB,YAAY,EAAE,MAAM,CAAC;QACrB,OAAO,EAAE,MAAM,CAAC;QAChB,MAAM,EAAE,MAAM,CAAC;QACf,SAAS,EAAE,MAAM,CAAC;KACnB,CAAC;CACH;AAED,qBAAa,aAAa;IAGZ,OAAO,CAAC,OAAO;IAF3B,OAAO,CAAC,YAAY,CAAoF;gBAEpF,OAAO,EAAE,aAAa;IAE1C,aAAa,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM;IAI7F;;;;;;OAMG;IACH,yBAAyB,CACvB,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,CAAC,EAAE,MAAM,GACf,gBAAgB;IAyInB;;;;;;;;;;;;;;OAcG;IACH,SAAS,CACP,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,MAAM,EACf,SAAS,CAAC,EAAE,MAAM,EAClB,IAAI,CAAC,EAAE;QAAE,QAAQ,CAAC,EAAE,MAAM,CAAC;QAAC,QAAQ,CAAC,EAAE,MAAM,CAAA;KAAE,GAC9C,IAAI;IAuDP;;;;;;;;;;;;;;;;;;OAkBG;IACH,OAAO,CAAC,iBAAiB;IAczB;;;;;;;;;;;;;;;;OAgBG;IACH,kBAAkB,IAAI,MAAM;IAsB5B;;;;;;;;;;;;;;;;;OAiBG;IACH,OAAO,CAAC,iBAAiB;IAgBzB;;;;;;;;;;;;OAYG;IACH,UAAU,CAAC,MAAM,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,MAAM,CAAA;KAAE,CAAC,GAAG,MAAM;IAYrE,gBAAgB,CAAC,SAAS,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI;IAIlD,mBAAmB,CAAC,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,IAAI;IAU/D;;;;;;;;;;;;OAYG;IACH,OAAO,CAAC,kBAAkB;IA4B1B;;;;;;;;;;OAUG;IACH,OAAO,CAAC,sBAAsB;IAe9B,OAAO,CAAC,UAAU;IAmClB,OAAO,CAAC,YAAY;CAMrB;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,wBAAgB,cAAc,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAUrD;AAED;;;;;;;;GAQG;AACH,wBAAgB,yBAAyB,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAEjE;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAK5D"}