✔ local draft preserves exact original ranges and duplicate source instances without inferring outputs or accepting facts (468.4486ms) ✔ review keeps unknown blocking, references distinct from output and boundaries distinct from compliance evidence (484.8415ms) ✔ draft adoption must account for every original range and does not fill paths from a reference (516.5154ms) ✔ source and requirement changes, other Tasks and tampered draft bytes are rejected without losing originals (1013.6099ms) ✔ partial explicit source review leaves the other source unreviewed while old file evidence remains valid (991.4212ms) ✔ bounded draft does not claim full source coverage and cannot acknowledge an omitted remainder (612.533ms) ✖ draft HTTP preserves its original artifact across restart and rejects stale scope and source versions (2068.3835ms) ✔ requirements HTTP binds selection, enforces optimistic revisions, restores original proofs and leaves provider history untouched (4486.8271ms) ✔ research evidence binds actual original bytes; model completion is not user acceptance (1136.5702ms) ✔ same text with distinct user source instances stays distinct; an appended requirement only invalidates its own revision (1330.4142ms) ✔ foreign project, old Task and fabricated evidence strings are rejected with preserved failed proofs (1943.0843ms) ✔ source changes invalidate prior proofs and cannot certify a read that was already stale at binding (2138.4105ms) ✔ missing or tampered artifacts never become evidence and original failures remain after recovery (1089.038ms) ✔ checks omitted by explicit agreement are reported as not executed and never passed (569.5015ms) ✔ user confirmation stays separate from engineering evidence, is bounded to current inputs and cannot be silently converted (883.4522ms) ✔ existing multi-file results keep provenance and invalidate only evidence whose files changed (916.7001ms) ✔ unrelated additions preserve the checked file facts but remain visible as unreviewed user sources (1072.1152ms) ✔ actual Git preview and publication recheck changed requirement bindings without touching HEAD or the owner index (8602.9755ms) ✔ no-test file application and manual completion keep pending user requirements for explicit review (1309.4176ms) ✔ revision races, forged source ranges, evidence fields and deletion cannot overwrite sealed requirements (705.1709ms) ✔ requirement binding prevents completion and Git acceptance after a review changes; legacy tasks stay explicit (1897.7017ms) ℹ tests 21 ℹ suites 0 ℹ pass 20 ℹ fail 1 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 35081.7524 ✖ failing tests: test at tests\requirement-drafts.test.mjs:94:1 ✖ draft HTTP preserves its original artifact across restart and rejects stale scope and source versions (2068.3835ms) AssertionError [ERR_ASSERTION]: The input did not match the regular expression /原任务或运行/. Input: 'Error: 接口不存在。' at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async TestContext. (file:///D:/Ai-project/REA%E9%80%86%E5%90%91/Agent-Workbench/tests/requirement-drafts.test.mjs:99:3) at async Test.run (node:internal/test_runner/test:1409:7) at async Test.processPendingSubtests (node:internal/test_runner/test:974:7) { generatedMessage: true, code: 'ERR_ASSERTION', actual: Error: 接口不存在。 at Object.api (file:///D:/Ai-project/REA%E9%80%86%E5%90%91/Agent-Workbench/tests/helpers.mjs:107:43) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async waitForActual (node:assert:646:5) at async strict.rejects (node:assert:769:25) at async TestContext. (file:///D:/Ai-project/REA%E9%80%86%E5%90%91/Agent-Workbench/tests/requirement-drafts.test.mjs:99:3) at async Test.run (node:internal/test_runner/test:1409:7) at async Test.processPendingSubtests (node:internal/test_runner/test:974:7), expected: /原任务或运行/, operator: 'rejects', diff: 'simple' }