Commit History
-
[NOTICKET] planner: exhaustion refuses instead of crashing, + the dry-run findings log
Rifqi Hafizuddin +1: Claude Opus 5BUG 12 — retry exhaustion showed the user the validator's own words. Asked whether backlog relates to bad actor score, the planner burned all three attempts (cross-table select, then a join the schema does not declare) and the turn ended with Analysis failed: planner could not produce a usable plan after 3 attempts; last error: joins[0]: (...) is not a declared foreign key That is internal vocabulary about an internal contract, and it reads as a broken product rather than a limit of the data. The SAME question refused cleanly on the previous run, so this is reachable by chance, not by input. Two changes. On the final attempt the planner is now told that refusing is a valid outcome — until now the retry prompt only ever said "this plan was invalid, fix it", which pushes toward another plan even when none exists. And if it still exhausts, the service returns the infeasible sentinel instead of raising, reusing the path that already handles this well: the coordinator renders it…59715a0
-
[NOTICKET] docs: analytical-tools foundation — conventions, DEV_PLAN 0.9, status sync
Rifqi Hafizuddin +1: Claude Opus 5Documents the foundation shipped on pr/22 (ee1a76a, 535f173, 522e582, 4d76bd0). No code touched. New: docs/tools/ANALYTICAL_TOOLS_CONVENTIONS.md — the authoring guide, written against the shipped modules: the InputModel -> ToolSpec flow via spec_builder, build_description's three-part format, the auto-chart "charts" key convention, run_fit, the three registrations a tool needs, and the non-negotiable rules. Indexed as a new docs/ workstream section, mirroring docs/knowledge/. DEV_PLAN: new 0.9 sprint section with the 24-row task table and owners. Records the locked decision that the tool contract is FUNCTIONAL, not a base class -- BaseAnalysisTool/ToolResult/mcp_schema were designed and dropped because ToolSpec is already MCP-shaped, ACTIVE/DEFERRED already gates exposure, the chart envelope already existed, and a second output envelope would have collided with everything keying off ToolOutput.kind. Section 6: W3 re-open struck as RESOLVED -- superseded by the per-tool P1 decision ra…a7f0bca
-
/fix parsing and term extract (#21)
- [NOTICKET] fix: retire the fuzzy clustering pass; add E1c post-cluster recall (2cc21c92688d662c5cfdfeeb6784bb85b98575ca) - [NOTICKET] feat: parsing schema 0.4.0 — asset pointers for figures and tables (e662ac089b741c90e19b9f51f4933fb97a1225bc) - [NOTICKET] docs: sync REPO_STATUS / DEV_PLAN / contracts for pipeline v2 (c3c184d83bec4a4d42e9ad3f7265560802817e5b) - [NOTICKET] docs: close K15 with the paid v1-vs-v2 comparison (62782fed9292f67d7b376783920a07197d6776e9) - [NOTICKET] fix: test the caption hypothesis; ship the signal at weight 0.0 (36a166e1844d186d6cfb8fff9ea070f3dc69b220) - [NOTICKET] fix: cap key-parameter pre-emption in the review queue (Step 2) (4e3a6aefef7024db3ea4b7946fd7771a6c269601) - [NOTICKET] feat: assert on invariants, report a band, classify the genre (Steps 0 + 5) (f1d64b113db0289601806635a9b154201a6127fc) - [NOTICKET] fix: gate spend in cluster units and surface the estimate (Step 6) (cdb5fe82cc5f2893ccbb5e28282e8dc46a27e061) - [NOTICKET] fix: retire escalation…f07443e
-
/feat knowledge management (#20)
- [NOTICKET] docs: knowledge pipeline test integration — context, audited task checklist, DEV_PLAN §0.8 (8e69dc6c638509f4dd7b6775d520fb4aa4efbd3e) - [NOTICKET] docs: knowledge pipeline — reframe kex as prototype, not port target (7cce5ffc9ab88791ac139dbef8e88e124a3d049e) - [NOTICKET] feat(eval): knowledge-extraction gold set, scorer + frozen prototype baseline (60cf4a885ef31a8aa64916f5a70ac5a0e8062c5f) - [NOTICKET] chore: add missing planner and readiness eval results (bd6659b3bf523597e4482b04ab1fcff5e1284d25) - [NOTICKET] feat(knowledge_extraction): free stages — models, seam adapter, filters, cluster, ranking (024c30abd1189119d33508eded334fe5a3ed5011) - [NOTICKET] fix(knowledge_extraction): move runner into the package; fix two ranking defects (72605ff6876a7936ab685d417c766ce820f6214b) - [NOTICKET] feat(knowledge_extraction): span filter — E1 recall 0.8537, matches the frozen baseline (3a016343398753cf730d50548c0e92ff47c6716c) - [NOTICKET] feat(knowledge_extraction): paid extraction …b68816f
