Heartbeat Deep Active Search Synthesis

過去レポートのView/ソース規律バックフィルで生成したView。

Generated: 2026-05-11T09:29:00+09:00

Safe local-only synthesis. No external sends, destructive actions, or production writes.

What changed

The active search loop no longer stops at “I saw candidates.” It now performs a second pass over conversation hits:

1. Classify owner messages into intent buckets.
2. Map each bucket to a durable ledger task.
3. Check whether that task is already done, open, or absent.
4. Promote absent/open gaps into ledger work once per run.
5. Write a report showing the buckets, task mapping, and promotions.

Evidence from the first deep run

python3 scripts/heartbeat_active_search.py --lane conversation_task_intake found:

• unmatched conversation candidates: 8
• deep intent buckets: 4
• promoted tasks:

- heartbeat-deep-active-search-synthesis

- heartbeat-schedule-alignment

Covered/done buckets were recognized instead of blindly reopening:

• heartbeat_watchdog_repair -> telegram-transport-watchdog-repair-loop status=done
• heartbeat_report_truthfulness -> heartbeat-report-truthfulness status=done

New open follow-up found by deeper search

• heartbeat-schedule-alignment: owner expected/asked about 8:00/8:15 behavior. Current heartbeat interval is anchored at :15/:45, not :00/:30. This needs a separate decision or safe implementation plan because changing cron schedule affects runtime behavior.

Guardrail

A bug in the first matching pattern treated “ほんとに根本的解決？…抜け漏れないか” as the “なんもない?” bucket. The pattern was tightened so “ほんとに何もないと思う?”-style challenges match, while generic “ほんとに根本解決?” review requests do not.