3 Commits

Include renames

Author	SHA1	Message	Date
weichen	f1302ed5b3	Enable canonical versioned Go module consumption ... Why: Allow consumers to download an immutable module revision without nested source checkouts or local path replacements. Evidence: SELF package tests and the prior canonical-path rejection are recorded in the Dev dependency-workspace task card; remote consumption is replayed against the committed candidate. Impact: Change the module identity and its Go imports while preserving API behavior. Existing historical submodule revisions remain buildable. Refs: Versioned dependencies U1/U3; feature/dependency-workspace	2026-10-13 15:47:16 +00:00
weichen	ef060d4ee5	Keep only hard facts in the blocking gate and add fact-consistency checks ... Why: User rulings 4/5 plus the P2-P4 live evidence. Keyword scoring dimensions (readability, actionability) kept failing valid documents - normal Chinese section headings flagged as column titles, loops of 4 corrections - because they grade writing preferences, not verifiable facts. Unverified numbers (~10-13 per run) remained the largest quality leak through every phase. And the verifier runs on the same model as the worker (lightweight falls back to chat), so "independent" verification was self-review. Separately, svc seeding after boot never registered the tavily tools until a restart because keys were snapshotted at startup. Changes: quality.HardFacts (lint actually ran + zero errors) replaces the full ScoreBytes projection in CheckArtifacts - keyword dimensions remain in ScoreBytes for eval visibility only. New fact-consistency check (runtime.factCheck, default on): extract percentages/dates/large numbers from deliverable text, trace each against the material corpus (attachment text + tool evidence); misses get exactly one correction round (fix, drop, or mark as target/estimate), never a loop. runVerifier skips same-source model verification unless runtime.verifierSameModel is set (hard facts + fact check still run). Search tools now register lazily, reading tavily keys per call (settings/seeding take effect immediately). Evidence: SELF - TestHardFactsIgnoresKeywordDimensions, TestHardFactsKeepsLintUnavailableBlocking, TestUnverifiedFactsAndNotice, TestFactCheckContinuationOnce (fact note fires, corrected run passes); go vet + go test ./... pass; live before/after on the golden task set recorded on the phase05 task card per the policy clause. Impact: Gate stops rejecting valid documents on stylistic grounds; invented figures get one forced correction round; same-model verification no longer pretends to be independent; tavily config is hot. No contract or storage changes.	2026-10-10 00:04:57 +00:00
weichen	0d55ebb948	Wire Tavily web search through the prompt-backed tool face ... Why: Agent-Native ships a Tavily integration (key-pool rotation, markdown output, fallback copy) that the backend never registered, so the catalog's WebSearch prompt had no carrier; wiring the tool gives it one and gives the agent live-web reach. Evidence: 4 new tool tests (registration, markdown formatting, empty query, failure fallback carried inside the error to match registry replay semantics); go test ./... 16 packages ok; live boot check - no keys means not registered, two keys log registration with both tools in /api/tools and 46 library modules in /api/prompts. Impact: tools.tavily.apiKeys/endpoint settings (restart effect; empty pool means the tool is absent, no silent degradation); tool.tavily_search and tool.web_search prompt modules inject citation discipline (cite sources, keep inference separate, fall back to workspace materials on failure); library floor raised to 46. Refs: feature/tavily-search-tool task card; guide disposition table in Documents.	2026-09-30 11:00:11 +00:00