4 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	6709325c38	Switch the R4 failure trigger to a sliding window ... Why: The consecutive-failure counter never fired in the live suite (0 reminders despite 20 failures) because real failures interleave with successes - each success reset the streak. The pattern to catch is "spinning overall", not "N in a row". Evidence: go test ./... green; the anchor test now covers scattered failures (3 in the last 6 outcomes escalates, 2 does not, once per run); the next live run must show the reminder actually appearing in the transcript. Impact: recentOutcomes ring (last 6) replaces consecToolFailures; the zero-hit search trigger keeps its own threshold (2); message wording matches the window semantics. Refs: Dev task feature/agent-e4-escalation-ledger (second fix-up).	2026-10-10 18:43:03 +00:00
weichen	03b4fdabaf	Restrict the source tag to material reads; never tag the model's own files ... Why: The first E4 live comparison regressed badly (toolFailures 10->24, toolCalls 63->166) and the instance transcript shows the loop: tagging kernel read_file/grep results put a trailing [src_N] line on the model's own workspace files, the model treated it as external tampering, and re-read/re-edit cycles cascaded into the read-before- write and file-changed guards. Why: The ledger only ever needed SOURCES - searches always, and workspace reads only under inputs/ (the upload material area). Grep cannot distinguish materials from self-produced files, so it stays untagged. Evidence: go test ./... green; new anchor TestEvidenceLedger OnlyTagsMaterialReads pins the inputs/-only rule; the re-run live comparison follows on the Dev side. Impact: evidenceTools loses read_file/grep; isEvidenceRead gates workspace reads to inputs/; everything else (search tags, escalation reminders, prompts) unchanged. Refs: Dev task feature/agent-e4-escalation-ledger (fix-up of #131).	2026-10-10 18:11:24 +00:00
weichen	21b8461525	Add R4 escalation reminders and the structured source-id evidence ledger (E4) ... Why: The plan's E4 remainder under the MiniMax-only constraint: the harness must detect the model going in circles and inject a change-of-strategy instruction (R4 - the model cannot be trusted to notice its own repeat-fail loop), and number sourcing needs addressable evidence: tool results carry [src_N|tool] tags so "found in materials" becomes "found in source src_N" for both the model and the fact-check notice. Why: Failure counting lives in one place (onEvent end, keyed by the slot status) because tool execution is parallel; the ledger and tag append are serialized by the same mutex, and escalation reminders fire once per condition streak - following the dual-speed nudge finding that MiniMax ignores vague reminders but follows concrete instructions. Evidence: go test ./... green; new anchors TestEscalationOnConsecutive ToolFailures, TestEscalationOnZeroHitSearches, TestEvidenceLedger TagsSource, TestEvidenceLedgerSkipsNonEvidenceTools. Live before/ after comparison runs on the Dev side per ruling 6. Impact: knowledge/web/tavily searches, fs_read_file and the workspace read_file/grep results now end with a source tag and enter the run ledger (2k-char head); two consecutive tool failures or two empty search results inject a concrete change-of-strategy reminder; base.deliverables v7 and agent-sub-research v3 explain the tags; fact-check notice points at src results. Non-evidence tools and failures are unchanged. Refs: proposal 2026-10-10-agent-delegation-routing-sandbox.md (E4, R4); Dev task feature/agent-e4-escalation-ledger.	2026-10-10 17:41:38 +00:00