4 Commits

Include renames

Author	SHA1	Message	Date
weichen	0e55875329	Admit intents with full slot validity and schema-typed slots ... Why: F09 - invalid slot information was dropped at the gate, the router saw only Start, and the command entrance passed untyped text, so invalid-slot recognitions could still reach business execution paths. Evidence: intentgate/route/server tests pass (verify-u6.json); admission regression cases added. Impact: invalid or missing slots never start executable actions; clarification flows unchanged; cmdbus confirmation untouched. Refs: feature/agent-stack-audit-remediation-b1 U6	2026-10-21 16:34:12 +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	517ae236b3	Project the command types through the intent gate surface ... Why: The boundary linter allows agent-intent imports only in the adapter layer; route and runmgr consume aliases from intentgate instead of importing the ecosystem library directly. Evidence: lint-boundaries passes below; backend suite green. Impact: intentgate re-exports Command/ActionRef and the kind constants; route drops the agent-intent import.	2026-10-07 07:58:05 +00:00
weichen	ff43c7c9aa	Unify intent routing behind the route package and enable NFKC ... Why: I1 WP3 - chat routing and the HITL free-text pivot now share one router consuming the library's command list, and both intent hosts fold compatibility-equivalent input. Evidence: go vet clean; go test ./... 30 packages ok, including the existing workflow-route and server e2e suites unchanged (behavior parity) and the new route package tests. Impact: new internal/route package (unique router with explicit priority rules); intentgate carries Commands and folds NFKC; server.go and runmgr.go route through it; nested pins at intent 2554b50 and squad 6b7a991. Blueprint actions resolve to a squad decision at the router level; per-run squad entry stays a recorded follow-up (no silent misrouting). Refs: Documents proposal 2026-10-07-agent-stack-n1q1i1-plans.md I1 WP3/WP4	2026-10-07 07:44:31 +00:00