3 Commits

Include renames

Author	SHA1	Message	Date
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	48c5202de2	Validate plugin and bundled skills against the open spec (N2 WP4) ... Why: plugin skills were written to the skill root unvalidated and the bundled recipes carried no name — both now go through the library's spec validator (name required + kebab-case + equals dir, description required, known-keys whitelist). Evidence: go test -count=1 ./... green; TestV2InvalidSkillRejected pins the fail-closed path with plugin context + field location; Seed validates each SKILL.md before write (recipes dogfood-compliant); nested pins carry agent-native#28 (the validator). Impact: invalid plugin skills now abort the plugin load with a located error instead of landing silently; the architecture baseline gains backend/plugins→backend/skills. Refs: Agent-Native#28, Agent-Squad#32, N2 plan WP4	2026-10-07 13:57:17 +00:00
weichenandCursor	cd5b82186d	Add the public extension surface and platform services ... Why: Downstream products must extend the base through a public package and host API instead of editing internal code. Evidence: go test ./... passed, including plugin v2 assets, sidecar startup, migration v13, pending confirms, HITL timeout, hash embedder, command pairs, and the extension surface snapshot. Impact: apiVersion 2.0-experimental rejects empty network allowlists for declarative HTTP. Hash embeddings stay opt-in via models.embedding.provider=hash. Plugin secrets resolve per owner at execution time. Refs: docs/proposals/2026-10-01-plugin-contract-v2.md Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-01 10:35:02 +00:00