@winspan/claude-forge 8.54.4 → 9.12.0

package/dist/daemon/services/loop-hint.d.ts

@@ -0,0 +1,139 @@
+/**
+ * LoopHint — formats the advisory `[LOOP HINT]` systemMessage the daemon emits
+ * when a prompt looks like one of the 3 whitelisted loop-suitable scenarios.
+ *
+ * decision e7d13697 (2026-06-11, Option C — approved):
+ *   The user wants the freshly-landed goal-convergence loop (`cf loop run`,
+ *   governance §10) SUGGESTED automatically in matching scenarios — but as an
+ *   ADVISORY hint only, never auto-run / never auto-spawn. This mirrors the
+ *   existing `[DECISION HINT]` advisory pattern (services/decision-hint.ts):
+ *   the daemon mints a systemMessage, the main thread still gates with a human
+ *   review before entering a loop.
+ *
+ * Why advisory-only (core-belief «daemon 永不对主线程加硬约束新智能»):
+ *   This service produces TEXT and (optionally) a telemetry row. It NEVER calls
+ *   `cf loop run`, never spawns an agent, never denies. The "should we loop?"
+ *   judgement stays with the main thread.
+ *
+ * Conservative-by-design (decision OQ2 hard constraint + fe6f98cd/KB
+ * low-adoption history): we only mint for prompts we are confident fall into a
+ * whitelisted scenario WITH a clean machine-judgeable PASS criterion. Open-ended
+ * tasks with no clean PASS are excluded — they would oscillate / loop forever.
+ * Better to under-mint than to spam.
+ *
+ * Fail-safe: every entry point catches its own errors and returns null; the
+ * UserPromptSubmit pipeline keeps running.
+ */
+import type { SQLiteStorage } from '../../core/storage/sqlite.js';
+/**
+ * forge_config key gating `[LOOP HINT]` minting. Default `true` (the user
+ * opted in via decision e7d13697). Set to `false` to suppress the hint without
+ * a code change (reversibility — decision Triage: all of A/B/C reversible).
+ *
+ * Seeded by `seedLoopConfig` (src/cli/commands/loop.ts) alongside the other
+ * `loop.*` keys, so a fresh install gets the default.
+ */
+export declare const LOOP_HINT_ENABLED_CONFIG_KEY = "loop.hint_enabled";
+/** Default when the key is absent (user opted in). */
+export declare const DEFAULT_LOOP_HINT_ENABLED = true;
+/**
+ * source_handler tag for the telemetry injection row (decision OQ5).
+ *
+ * Mirrors the KB-adoption precedent (decision 148f7a0a): KB injections are
+ * tagged `UserPromptSubmitHandler:kb` and stamped `adopted_at` when the session
+ * later actively uses the injected knowledge. We reuse the SAME `injections`
+ * table + `adopted_at` mechanism: a `[LOOP HINT]` mint writes one row with this
+ * tag; PostToolUse stamps `adopted_at` when the session later runs `cf loop run`
+ * (the observable "the hint was adopted" signal). See
+ * src/core/storage/injections.ts writeLoopHintAdoption / countLoopHintAdoption.
+ */
+export declare const LOOP_HINT_SOURCE_HANDLER = "UserPromptSubmitHandler:loop-hint";
+/** The 3 whitelisted scenarios (decision resolved scope). */
+export type LoopScenario = 'bug-fix' | 'test-lint-green' | 'spec-impl';
+/**
+ * Result of `classifyLoopScenario`. `null` when no whitelist scenario matched
+ * (the common case — most prompts are not loop-suitable).
+ */
+export interface LoopScenarioMatch {
+    scenario: LoopScenario;
+    /** Human-readable label for the hint body. */
+    label: string;
+}
+/**
+ * Conservative scenario classifier (decision OQ2).
+ *
+ * Returns the matched whitelist scenario, or `null` to mint nothing. Precision
+ * is favoured over recall: a prompt must clearly carry BOTH an action signal
+ * AND a subject/PASS signal for its scenario, and must NOT look open-ended.
+ *
+ * Order of checks:
+ *   0. Empty / system-generated / skip-decision → null (never classify).
+ *   1. Open-ended exclusion → null (vague tasks with no clean PASS).
+ *   2. Scenario-1 bug-fix.
+ *   3. Scenario-2 test/lint green.
+ *   4. Scenario-3 spec implementation (requires an explicit PASS-criterion or
+ *      spec reference so "implement a button" doesn't mint).
+ *
+ * Pure function (no I/O) so it is trivially unit-testable.
+ */
+export declare function classifyLoopScenario(prompt: string): LoopScenarioMatch | null;
+/**
+ * Resolve whether `[LOOP HINT]` minting is enabled from forge_config.
+ *
+ * Default `true` (user opted in). Any value other than the literal `'false'`
+ * (case-insensitive, trimmed) is treated as enabled, matching the lenient
+ * coercion used elsewhere (the key is seeded as the string `'false'`/`'true'`).
+ * Fail-silent: on any storage error, fall back to the default.
+ */
+export declare function resolveLoopHintEnabled(storage?: SQLiteStorage | null): boolean;
+/**
+ * Result returned by `emitLoopHintSimple` when a hint is generated.
+ */
+export interface LoopHintResult {
+    /** The `[LOOP HINT]` text to include in systemMessage. */
+    message: string;
+    /** The matched scenario (for logging / tests). */
+    scenario: LoopScenario;
+}
+/**
+ * Main entry point — decides whether to emit a `[LOOP HINT]` for this prompt
+ * and (when it does) writes the adoption-telemetry injection row.
+ *
+ * Guards (in order):
+ *   1. `loop.hint_enabled = false` → null (config gate, reversible).
+ *   2. scenario classifier returns null → null (not loop-suitable).
+ *
+ * When it mints:
+ *   • Writes ONE `injections` row tagged LOOP_HINT_SOURCE_HANDLER (fail-silent)
+ *     so adoption can later be measured (PostToolUse stamps `adopted_at` when
+ *     the session runs `cf loop run`). Without this landing point we could not
+ *     judge keep-vs-remove — the whole reason Option C was chosen over D.
+ *   • Returns `{ message, scenario }`. The handler pushes `message` into
+ *     systemParts; it is ADVISORY text with zero side effects beyond the row.
+ *
+ * Coexistence with `[DECISION HINT]` (decision guardrail): this is ADDITIVE and
+ * SECONDARY. A prompt can be both decision-worthy and loop-suitable; the loop
+ * hint is appended as its own section and never suppresses / replaces the
+ * decision hint. The decision hint stays the primary "spawn decision-maker"
+ * directive; the loop hint just additionally suggests the loop pattern.
+ *
+ * @param prompt - The raw user prompt text.
+ * @param storage - Optional SQLiteStorage (config gate + telemetry row).
+ * @param eventContext - Optional event fields for the telemetry row.
+ */
+export declare function emitLoopHintSimple(prompt: string, storage?: SQLiteStorage | null, eventContext?: {
+    session_id: string;
+    project_path: string;
+    event_id?: string;
+    timestamp?: string;
+} | null): LoopHintResult | null;
+/**
+ * Formats the `[LOOP HINT]` body. Kept separate for unit-test readability and
+ * to mirror `formatHintMessage` in decision-hint.ts.
+ *
+ * The body: names the matched scenario, suggests the loop-until-verify-PASS
+ * pattern (`cf loop run` / governance §10), and makes explicit that the main
+ * thread should still GATE at the start (human review — never auto-run).
+ */
+export declare function formatLoopHintMessage(match: LoopScenarioMatch, intentSummary: string): string;
+//# sourceMappingURL=loop-hint.d.ts.map

package/dist/daemon/services/loop-hint.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"loop-hint.d.ts","sourceRoot":"","sources":["../../../src/daemon/services/loop-hint.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAMlE;;;;;;;GAOG;AACH,eAAO,MAAM,4BAA4B,sBAAsB,CAAC;AAEhE,sDAAsD;AACtD,eAAO,MAAM,yBAAyB,OAAO,CAAC;AAE9C;;;;;;;;;;GAUG;AACH,eAAO,MAAM,wBAAwB,sCAAsC,CAAC;AAK5E,6DAA6D;AAC7D,MAAM,MAAM,YAAY,GAAG,SAAS,GAAG,iBAAiB,GAAG,WAAW,CAAC;AA8DvE;;;GAGG;AACH,MAAM,WAAW,iBAAiB;IAChC,QAAQ,EAAE,YAAY,CAAC;IACvB,8CAA8C;IAC9C,KAAK,EAAE,MAAM,CAAC;CACf;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,iBAAiB,GAAG,IAAI,CA2C7E;AAED;;;;;;;GAOG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,CAAC,EAAE,aAAa,GAAG,IAAI,GAAG,OAAO,CAS9E;AAED;;GAEG;AACH,MAAM,WAAW,cAAc;IAC7B,0DAA0D;IAC1D,OAAO,EAAE,MAAM,CAAC;IAChB,kDAAkD;IAClD,QAAQ,EAAE,YAAY,CAAC;CACxB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,kBAAkB,CAChC,MAAM,EAAE,MAAM,EACd,OAAO,CAAC,EAAE,aAAa,GAAG,IAAI,EAC9B,YAAY,CAAC,EAAE;IACb,UAAU,EAAE,MAAM,CAAC;IACnB,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB,GAAG,IAAI,GACP,cAAc,GAAG,IAAI,CAoCvB;AAED;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CACnC,KAAK,EAAE,iBAAiB,EACxB,aAAa,EAAE,MAAM,GACpB,MAAM,CAcR"}

package/dist/daemon/services/loop-hint.js

@@ -0,0 +1,272 @@
+/**
+ * LoopHint — formats the advisory `[LOOP HINT]` systemMessage the daemon emits
+ * when a prompt looks like one of the 3 whitelisted loop-suitable scenarios.
+ *
+ * decision e7d13697 (2026-06-11, Option C — approved):
+ *   The user wants the freshly-landed goal-convergence loop (`cf loop run`,
+ *   governance §10) SUGGESTED automatically in matching scenarios — but as an
+ *   ADVISORY hint only, never auto-run / never auto-spawn. This mirrors the
+ *   existing `[DECISION HINT]` advisory pattern (services/decision-hint.ts):
+ *   the daemon mints a systemMessage, the main thread still gates with a human
+ *   review before entering a loop.
+ *
+ * Why advisory-only (core-belief «daemon 永不对主线程加硬约束新智能»):
+ *   This service produces TEXT and (optionally) a telemetry row. It NEVER calls
+ *   `cf loop run`, never spawns an agent, never denies. The "should we loop?"
+ *   judgement stays with the main thread.
+ *
+ * Conservative-by-design (decision OQ2 hard constraint + fe6f98cd/KB
+ * low-adoption history): we only mint for prompts we are confident fall into a
+ * whitelisted scenario WITH a clean machine-judgeable PASS criterion. Open-ended
+ * tasks with no clean PASS are excluded — they would oscillate / loop forever.
+ * Better to under-mint than to spam.
+ *
+ * Fail-safe: every entry point catches its own errors and returns null; the
+ * UserPromptSubmit pipeline keeps running.
+ */
+import { isSystemGeneratedPrompt, isSkipDecisionKeyword, } from './decision-hint.js';
+/**
+ * forge_config key gating `[LOOP HINT]` minting. Default `true` (the user
+ * opted in via decision e7d13697). Set to `false` to suppress the hint without
+ * a code change (reversibility — decision Triage: all of A/B/C reversible).
+ *
+ * Seeded by `seedLoopConfig` (src/cli/commands/loop.ts) alongside the other
+ * `loop.*` keys, so a fresh install gets the default.
+ */
+export const LOOP_HINT_ENABLED_CONFIG_KEY = 'loop.hint_enabled';
+/** Default when the key is absent (user opted in). */
+export const DEFAULT_LOOP_HINT_ENABLED = true;
+/**
+ * source_handler tag for the telemetry injection row (decision OQ5).
+ *
+ * Mirrors the KB-adoption precedent (decision 148f7a0a): KB injections are
+ * tagged `UserPromptSubmitHandler:kb` and stamped `adopted_at` when the session
+ * later actively uses the injected knowledge. We reuse the SAME `injections`
+ * table + `adopted_at` mechanism: a `[LOOP HINT]` mint writes one row with this
+ * tag; PostToolUse stamps `adopted_at` when the session later runs `cf loop run`
+ * (the observable "the hint was adopted" signal). See
+ * src/core/storage/injections.ts writeLoopHintAdoption / countLoopHintAdoption.
+ */
+export const LOOP_HINT_SOURCE_HANDLER = 'UserPromptSubmitHandler:loop-hint';
+/** Max chars of the prompt echoed back into the hint body. */
+const LOOP_HINT_SUMMARY_MAX = 150;
+/**
+ * Human-readable scenario label used in the hint body.
+ */
+const SCENARIO_LABELS = {
+    'bug-fix': 'bug 修复（有明确 verify-PASS 判据）',
+    'test-lint-green': '测试 / lint「修到绿」（fix until green）',
+    'spec-impl': '明确 spec 的实现（verify 能判完成）',
+};
+/**
+ * Verbs / phrases that signal a machine-judgeable PASS criterion. A whitelist
+ * scenario REQUIRES at least one of these to be present (so we don't mint for
+ * open-ended "improve the architecture" style prompts that have no clean stop
+ * condition). This is the conservative gate referenced in decision OQ2.
+ */
+const PASS_CRITERION_RE = /(verify|pass|绿|green|通过|all\s+green|until\s+green|修到绿|跑通|build\s+success|构建成功|测试通过|全部通过|exit\s+0)/i;
+/**
+ * Scenario-1: bug-fix. Requires a fix-flavoured verb AND a bug/error noun.
+ * Conservative: "fix the typo in the README" matches "fix" but has no
+ * bug/error/failing noun, so it does NOT mint — which is the desired
+ * under-minting bias.
+ */
+const BUGFIX_ACTION_RE = /(fix|修复|修一?下|repair|resolve|解决|debug|排查)/i;
+const BUGFIX_SUBJECT_RE = /(bug|缺陷|错误|error|crash|崩溃|异常|exception|报错|failing|fail\b|失败|回归|regression|挂了|不工作|doesn'?t\s+work|broken)/i;
+/**
+ * Scenario-2: test/lint "fix until green". Requires a test/lint noun AND a
+ * make-green verb (fix / 修 / pass / 跑通 / green / 绿).
+ */
+// Note: `spec` is intentionally EXCLUDED here — in this codebase "spec" almost
+// always means a specification document (scenario-3), not a test spec. Treating
+// it as a test noun made "implement the spec and make verify pass" misclassify
+// as test-lint-green. Test specs are still caught via `vitest`/`jest`/`用例`/
+// `单测`/`test`.
+const TEST_LINT_SUBJECT_RE = /(test|测试|lint|eslint|tsc|typecheck|类型检查|ci\b|用例|单测|e2e|vitest|jest)/i;
+const MAKE_GREEN_RE = /(green|绿|pass|通过|跑通|fix|修复|修一?下|修到|until\s+green|all\s+pass|全部通过|fail|失败|红)/i;
+/**
+ * Scenario-3: implement an explicit spec where verify can judge done. Requires
+ * an implement verb AND a spec/decision reference.
+ */
+const IMPL_ACTION_RE = /(implement|实现|落地|按.*实现|实施|build\s+(?:the|a)\b|开发)/i;
+const SPEC_SUBJECT_RE = /(spec\b|规格|decision\b|决策|需求|requirement|design\s+doc|设计文档|acceptance|验收|按.*(?:spec|规格|决策|文档))/i;
+/**
+ * Open-ended exclusion guard. Prompts dominated by exploratory / vague verbs
+ * with no concrete PASS criterion must NOT mint even if they incidentally
+ * contain a whitelisted keyword. This is the "exclude open-ended tasks with no
+ * clean PASS criterion" requirement (they'd loop forever).
+ */
+const OPEN_ENDED_RE = /(explore|调研|research|brainstorm|头脑风暴|讨论|discuss|design\s+(?:from\s+scratch|a\s+new)|重新设计|想法|idea|方向|strategy|策略|optimize\s+(?:performance|the\s+architecture)|优化架构|提升性能|看看怎么|要不要|该不该|是否应该|whether\s+to|should\s+we)/i;
+/**
+ * Conservative scenario classifier (decision OQ2).
+ *
+ * Returns the matched whitelist scenario, or `null` to mint nothing. Precision
+ * is favoured over recall: a prompt must clearly carry BOTH an action signal
+ * AND a subject/PASS signal for its scenario, and must NOT look open-ended.
+ *
+ * Order of checks:
+ *   0. Empty / system-generated / skip-decision → null (never classify).
+ *   1. Open-ended exclusion → null (vague tasks with no clean PASS).
+ *   2. Scenario-1 bug-fix.
+ *   3. Scenario-2 test/lint green.
+ *   4. Scenario-3 spec implementation (requires an explicit PASS-criterion or
+ *      spec reference so "implement a button" doesn't mint).
+ *
+ * Pure function (no I/O) so it is trivially unit-testable.
+ */
+export function classifyLoopScenario(prompt) {
+    const text = (prompt ?? '').trim();
+    if (text.length === 0)
+        return null;
+    if (isSkipDecisionKeyword(text))
+        return null;
+    if (isSystemGeneratedPrompt(text))
+        return null;
+    // (1) Open-ended exclusion — bias hard toward under-minting.
+    if (OPEN_ENDED_RE.test(text))
+        return null;
+    // (2) test/lint "fix until green": test-noun AND make-green verb. Checked
+    //     BEFORE bug-fix because "fix the failing tests until green" carries both
+    //     a bug-flavoured noun ("failing") and a test noun — the test scenario is
+    //     the more specific intent, so it wins. A bug fix WITHOUT a test noun
+    //     ("fix the crash in the daemon") falls through to scenario-3 below.
+    if (TEST_LINT_SUBJECT_RE.test(text) && MAKE_GREEN_RE.test(text)) {
+        return {
+            scenario: 'test-lint-green',
+            label: SCENARIO_LABELS['test-lint-green'],
+        };
+    }
+    // (3) bug-fix: fix-verb AND bug-noun. The verify-PASS criterion is implicit
+    //     for bug fixes (verify-agent判 PASS), so we don't additionally require
+    //     PASS_CRITERION_RE here — the bug-noun is the concrete stop condition.
+    if (BUGFIX_ACTION_RE.test(text) && BUGFIX_SUBJECT_RE.test(text)) {
+        return { scenario: 'bug-fix', label: SCENARIO_LABELS['bug-fix'] };
+    }
+    // (4) spec implementation: implement-verb AND spec-noun, AND the prompt must
+    //     carry an explicit PASS criterion OR a spec/decision reference (the
+    //     spec-noun itself). Requiring SPEC_SUBJECT_RE already enforces this; we
+    //     additionally reject if it reads open-ended (handled above). This keeps
+    //     "implement a login page" (no spec, no PASS) from minting.
+    if (IMPL_ACTION_RE.test(text) && SPEC_SUBJECT_RE.test(text)) {
+        return { scenario: 'spec-impl', label: SCENARIO_LABELS['spec-impl'] };
+    }
+    // PASS_CRITERION_RE is intentionally NOT a standalone mint trigger — a lone
+    // "make it pass" with no scenario subject is too ambiguous. It is referenced
+    // in the doc as the conceptual gate the three subject checks encode.
+    void PASS_CRITERION_RE;
+    return null;
+}
+/**
+ * Resolve whether `[LOOP HINT]` minting is enabled from forge_config.
+ *
+ * Default `true` (user opted in). Any value other than the literal `'false'`
+ * (case-insensitive, trimmed) is treated as enabled, matching the lenient
+ * coercion used elsewhere (the key is seeded as the string `'false'`/`'true'`).
+ * Fail-silent: on any storage error, fall back to the default.
+ */
+export function resolveLoopHintEnabled(storage) {
+    if (!storage)
+        return DEFAULT_LOOP_HINT_ENABLED;
+    try {
+        const raw = storage.readConfig(LOOP_HINT_ENABLED_CONFIG_KEY);
+        if (raw === undefined || raw === null)
+            return DEFAULT_LOOP_HINT_ENABLED;
+        return raw.trim().toLowerCase() !== 'false';
+    }
+    catch {
+        return DEFAULT_LOOP_HINT_ENABLED;
+    }
+}
+/**
+ * Main entry point — decides whether to emit a `[LOOP HINT]` for this prompt
+ * and (when it does) writes the adoption-telemetry injection row.
+ *
+ * Guards (in order):
+ *   1. `loop.hint_enabled = false` → null (config gate, reversible).
+ *   2. scenario classifier returns null → null (not loop-suitable).
+ *
+ * When it mints:
+ *   • Writes ONE `injections` row tagged LOOP_HINT_SOURCE_HANDLER (fail-silent)
+ *     so adoption can later be measured (PostToolUse stamps `adopted_at` when
+ *     the session runs `cf loop run`). Without this landing point we could not
+ *     judge keep-vs-remove — the whole reason Option C was chosen over D.
+ *   • Returns `{ message, scenario }`. The handler pushes `message` into
+ *     systemParts; it is ADVISORY text with zero side effects beyond the row.
+ *
+ * Coexistence with `[DECISION HINT]` (decision guardrail): this is ADDITIVE and
+ * SECONDARY. A prompt can be both decision-worthy and loop-suitable; the loop
+ * hint is appended as its own section and never suppresses / replaces the
+ * decision hint. The decision hint stays the primary "spawn decision-maker"
+ * directive; the loop hint just additionally suggests the loop pattern.
+ *
+ * @param prompt - The raw user prompt text.
+ * @param storage - Optional SQLiteStorage (config gate + telemetry row).
+ * @param eventContext - Optional event fields for the telemetry row.
+ */
+export function emitLoopHintSimple(prompt, storage, eventContext) {
+    try {
+        // (1) Config gate — reversible kill switch.
+        if (!resolveLoopHintEnabled(storage))
+            return null;
+        // (2) Conservative scenario classification.
+        const match = classifyLoopScenario(prompt);
+        if (!match)
+            return null;
+        const message = formatLoopHintMessage(match, truncateSummary(prompt));
+        // (3) Adoption telemetry — write the mint row (fail-silent). Reuses the
+        //     KB-adoption `injections` + `adopted_at` mechanism (decision 148f7a0a).
+        if (storage && eventContext) {
+            try {
+                storage.writeInjection({
+                    event_id: eventContext.event_id,
+                    session_id: eventContext.session_id,
+                    timestamp: eventContext.timestamp ?? new Date().toISOString(),
+                    source_handler: LOOP_HINT_SOURCE_HANDLER,
+                    injection_type: 'systemMessage',
+                    content: message,
+                    metadata_json: JSON.stringify({
+                        scenario: match.scenario,
+                        project_path: eventContext.project_path,
+                    }),
+                });
+            }
+            catch {
+                // telemetry is observability, never a blocker.
+            }
+        }
+        return { message, scenario: match.scenario };
+    }
+    catch {
+        return null;
+    }
+}
+/**
+ * Formats the `[LOOP HINT]` body. Kept separate for unit-test readability and
+ * to mirror `formatHintMessage` in decision-hint.ts.
+ *
+ * The body: names the matched scenario, suggests the loop-until-verify-PASS
+ * pattern (`cf loop run` / governance §10), and makes explicit that the main
+ * thread should still GATE at the start (human review — never auto-run).
+ */
+export function formatLoopHintMessage(match, intentSummary) {
+    return [
+        '[LOOP HINT]',
+        '',
+        `daemon 判定本任务疑似适合 goal-convergence loop（场景：${match.label}）。`,
+        `这是**建议**，不是约束——主线程进 loop 前仍须人审 gate，daemon 绝不自动起 loop。`,
+        '',
+        `若确认适合，可用 loop-until-verify-PASS 模式（governance §10）：`,
+        `  cf loop enable && cf loop run    # 每轮 coder→verify-agent，PASS/SKIP 收敛、FAIL 续迭代`,
+        `  （或交互形态 cf loop run --interactive / 原生 /loop，迭代间人盯）`,
+        '',
+        `任务摘要："${intentSummary}"`,
+        `如不适合（开放式 / 无干净 PASS 判据）或已有计划，忽略本提示即可。`,
+    ].join('\n');
+}
+function truncateSummary(text) {
+    const oneLine = (text ?? '').replace(/\s+/g, ' ').trim();
+    if (oneLine.length <= LOOP_HINT_SUMMARY_MAX)
+        return oneLine;
+    return oneLine.slice(0, LOOP_HINT_SUMMARY_MAX - 1) + '…';
+}
+//# sourceMappingURL=loop-hint.js.map

package/dist/daemon/services/loop-hint.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"loop-hint.js","sourceRoot":"","sources":["../../../src/daemon/services/loop-hint.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAGH,OAAO,EACL,uBAAuB,EACvB,qBAAqB,GACtB,MAAM,oBAAoB,CAAC;AAE5B;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,4BAA4B,GAAG,mBAAmB,CAAC;AAEhE,sDAAsD;AACtD,MAAM,CAAC,MAAM,yBAAyB,GAAG,IAAI,CAAC;AAE9C;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,mCAAmC,CAAC;AAE5E,8DAA8D;AAC9D,MAAM,qBAAqB,GAAG,GAAG,CAAC;AAKlC;;GAEG;AACH,MAAM,eAAe,GAAiC;IACpD,SAAS,EAAE,4BAA4B;IACvC,iBAAiB,EAAE,iCAAiC;IACpD,WAAW,EAAE,0BAA0B;CACxC,CAAC;AAEF;;;;;GAKG;AACH,MAAM,iBAAiB,GACrB,oGAAoG,CAAC;AAEvG;;;;;GAKG;AACH,MAAM,gBAAgB,GAAG,2CAA2C,CAAC;AACrE,MAAM,iBAAiB,GACrB,2GAA2G,CAAC;AAE9G;;;GAGG;AACH,+EAA+E;AAC/E,gFAAgF;AAChF,+EAA+E;AAC/E,4EAA4E;AAC5E,eAAe;AACf,MAAM,oBAAoB,GACxB,sEAAsE,CAAC;AACzE,MAAM,aAAa,GACjB,8EAA8E,CAAC;AAEjF;;;GAGG;AACH,MAAM,cAAc,GAClB,oDAAoD,CAAC;AACvD,MAAM,eAAe,GACnB,gGAAgG,CAAC;AAEnG;;;;;GAKG;AACH,MAAM,aAAa,GACjB,sNAAsN,CAAC;AAYzN;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,oBAAoB,CAAC,MAAc;IACjD,MAAM,IAAI,GAAG,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC;IACnC,IAAI,IAAI,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IACnC,IAAI,qBAAqB,CAAC,IAAI,CAAC;QAAE,OAAO,IAAI,CAAC;IAC7C,IAAI,uBAAuB,CAAC,IAAI,CAAC;QAAE,OAAO,IAAI,CAAC;IAE/C,6DAA6D;IAC7D,IAAI,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC;QAAE,OAAO,IAAI,CAAC;IAE1C,0EAA0E;IAC1E,8EAA8E;IAC9E,8EAA8E;IAC9E,0EAA0E;IAC1E,yEAAyE;IACzE,IAAI,oBAAoB,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;QAChE,OAAO;YACL,QAAQ,EAAE,iBAAiB;YAC3B,KAAK,EAAE,eAAe,CAAC,iBAAiB,CAAC;SAC1C,CAAC;IACJ,CAAC;IAED,4EAA4E;IAC5E,2EAA2E;IAC3E,4EAA4E;IAC5E,IAAI,gBAAgB,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,iBAAiB,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;QAChE,OAAO,EAAE,QAAQ,EAAE,SAAS,EAAE,KAAK,EAAE,eAAe,CAAC,SAAS,CAAC,EAAE,CAAC;IACpE,CAAC;IAED,6EAA6E;IAC7E,yEAAyE;IACzE,6EAA6E;IAC7E,6EAA6E;IAC7E,gEAAgE;IAChE,IAAI,cAAc,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,eAAe,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;QAC5D,OAAO,EAAE,QAAQ,EAAE,WAAW,EAAE,KAAK,EAAE,eAAe,CAAC,WAAW,CAAC,EAAE,CAAC;IACxE,CAAC;IAED,4EAA4E;IAC5E,6EAA6E;IAC7E,qEAAqE;IACrE,KAAK,iBAAiB,CAAC;IAEvB,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,sBAAsB,CAAC,OAA8B;IACnE,IAAI,CAAC,OAAO;QAAE,OAAO,yBAAyB,CAAC;IAC/C,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,OAAO,CAAC,UAAU,CAAC,4BAA4B,CAAC,CAAC;QAC7D,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI;YAAE,OAAO,yBAAyB,CAAC;QACxE,OAAO,GAAG,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,KAAK,OAAO,CAAC;IAC9C,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,yBAAyB,CAAC;IACnC,CAAC;AACH,CAAC;AAYD;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,UAAU,kBAAkB,CAChC,MAAc,EACd,OAA8B,EAC9B,YAKQ;IAER,IAAI,CAAC;QACH,4CAA4C;QAC5C,IAAI,CAAC,sBAAsB,CAAC,OAAO,CAAC;YAAE,OAAO,IAAI,CAAC;QAElD,4CAA4C;QAC5C,MAAM,KAAK,GAAG,oBAAoB,CAAC,MAAM,CAAC,CAAC;QAC3C,IAAI,CAAC,KAAK;YAAE,OAAO,IAAI,CAAC;QAExB,MAAM,OAAO,GAAG,qBAAqB,CAAC,KAAK,EAAE,eAAe,CAAC,MAAM,CAAC,CAAC,CAAC;QAEtE,wEAAwE;QACxE,6EAA6E;QAC7E,IAAI,OAAO,IAAI,YAAY,EAAE,CAAC;YAC5B,IAAI,CAAC;gBACH,OAAO,CAAC,cAAc,CAAC;oBACrB,QAAQ,EAAE,YAAY,CAAC,QAAQ;oBAC/B,UAAU,EAAE,YAAY,CAAC,UAAU;oBACnC,SAAS,EAAE,YAAY,CAAC,SAAS,IAAI,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;oBAC7D,cAAc,EAAE,wBAAwB;oBACxC,cAAc,EAAE,eAAe;oBAC/B,OAAO,EAAE,OAAO;oBAChB,aAAa,EAAE,IAAI,CAAC,SAAS,CAAC;wBAC5B,QAAQ,EAAE,KAAK,CAAC,QAAQ;wBACxB,YAAY,EAAE,YAAY,CAAC,YAAY;qBACxC,CAAC;iBACH,CAAC,CAAC;YACL,CAAC;YAAC,MAAM,CAAC;gBACP,+CAA+C;YACjD,CAAC;QACH,CAAC;QAED,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,KAAK,CAAC,QAAQ,EAAE,CAAC;IAC/C,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,IAAI,CAAC;IACd,CAAC;AACH,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,qBAAqB,CACnC,KAAwB,EACxB,aAAqB;IAErB,OAAO;QACL,aAAa;QACb,EAAE;QACF,6CAA6C,KAAK,CAAC,KAAK,IAAI;QAC5D,wDAAwD;QACxD,EAAE;QACF,qDAAqD;QACrD,kFAAkF;QAClF,sDAAsD;QACtD,EAAE;QACF,SAAS,aAAa,GAAG;QACzB,uCAAuC;KACxC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACf,CAAC;AAED,SAAS,eAAe,CAAC,IAAY;IACnC,MAAM,OAAO,GAAG,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC,OAAO,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,IAAI,EAAE,CAAC;IACzD,IAAI,OAAO,CAAC,MAAM,IAAI,qBAAqB;QAAE,OAAO,OAAO,CAAC;IAC5D,OAAO,OAAO,CAAC,KAAK,CAAC,CAAC,EAAE,qBAAqB,GAAG,CAAC,CAAC,GAAG,GAAG,CAAC;AAC3D,CAAC"}

package/dist/daemon/services/outcome-classification-service.d.ts

@@ -0,0 +1,49 @@
+/**
+ * OutcomeClassificationService — Stop-time outcome instrumentation.
+ *
+ * Extracted from `StopHandler` (D-3) so the orchestrator stays thin.
+ * Single responsibility: gather signals + run `classifyOutcome` + persist
+ * outcome columns on `sessions` + `tasks`, plus the Phase 2 metrics rollup
+ * back-fill.
+ *
+ * Lifecycle: owned by `StopHandler` (constructed per-daemon, called per-event).
+ * Stateless — no per-call construction deps; each method receives storage +
+ * taskSegmenter explicitly so the service is trivially injectable in tests.
+ *
+ * Failure mode: every public method is fire-and-forget. Never throws; logs at
+ * debug level when storage / git subprocess hiccups.
+ */
+import type { StopEvent } from '../../core/types.js';
+import type { SQLiteStorage } from '../../core/storage/sqlite.js';
+import type { TaskSegmenter } from './task-segmenter.js';
+export declare class OutcomeClassificationService {
+    /**
+     * Classify the session's outcome at Stop time and persist to both
+     * `sessions` and the most recent task row. Also rolls up Phase 2 metrics
+     * (intercept_count / kb_inject_count / skill_match_count).
+     *
+     * Fire-and-forget; never throws (debug-logs on error).
+     */
+    classifySession(event: StopEvent, storage: SQLiteStorage, taskSegmenter: TaskSegmenter | null): Promise<void>;
+    /**
+     * Backfill outcome on all unclassified completed/abandoned tasks for the
+     * session. Without this, TaskSegmenter-completed tasks (the ones closed by a
+     * new-prompt switch) stay outcome=NULL forever.
+     *
+     * spec 1100 v2: classification is pure edit-intent — NO git subprocess per
+     * task. Gated to MAX_IDLE_TASKS_PER_RUN to bound the per-task edit-intent
+     * queries. Fire-and-forget; never throws.
+     */
+    classifyIdleTasks(event: StopEvent, storage: SQLiteStorage): Promise<void>;
+    /**
+     * Count a single task's Edit/Write intent events. Best-effort: 0 on error so
+     * classification never throws because of a storage hiccup.
+     */
+    private safeTaskEditIntent;
+    /**
+     * Session-level edit intent = COUNT of Edit/Write events across the session
+     * (tool_name only; gzip-safe). Best-effort, 0 on error.
+     */
+    private safeSessionEditIntent;
+}
+//# sourceMappingURL=outcome-classification-service.d.ts.map

package/dist/daemon/services/outcome-classification-service.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"outcome-classification-service.d.ts","sourceRoot":"","sources":["../../../src/daemon/services/outcome-classification-service.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AACrD,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAClE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAczD,qBAAa,4BAA4B;IACvC;;;;;;OAMG;IACG,eAAe,CACnB,KAAK,EAAE,SAAS,EAChB,OAAO,EAAE,aAAa,EACtB,aAAa,EAAE,aAAa,GAAG,IAAI,GAClC,OAAO,CAAC,IAAI,CAAC;IAwHhB;;;;;;;;OAQG;IACG,iBAAiB,CAAC,KAAK,EAAE,SAAS,EAAE,OAAO,EAAE,aAAa,GAAG,OAAO,CAAC,IAAI,CAAC;IA8ChF;;;OAGG;IACH,OAAO,CAAC,kBAAkB;IAS1B;;;OAGG;IACH,OAAO,CAAC,qBAAqB;CAQ9B"}