30 lines
2.6 KiB
Plaintext
30 lines
2.6 KiB
Plaintext
✔ local draft preserves exact original ranges and duplicate source instances without inferring outputs or accepting facts (570.7936ms)
|
||
✔ review keeps unknown blocking, references distinct from output and boundaries distinct from compliance evidence (534.9067ms)
|
||
✔ draft adoption must account for every original range and does not fill paths from a reference (526.2201ms)
|
||
✔ source and requirement changes, other Tasks and tampered draft bytes are rejected without losing originals (932.4456ms)
|
||
✔ partial explicit source review leaves the other source unreviewed while old file evidence remains valid (999.7925ms)
|
||
✔ bounded draft does not claim full source coverage and cannot acknowledge an omitted remainder (537.4129ms)
|
||
✔ draft HTTP preserves its original artifact across restart and rejects stale scope and source versions (3997.3633ms)
|
||
✔ requirements HTTP binds selection, enforces optimistic revisions, restores original proofs and leaves provider history untouched (4535.6877ms)
|
||
✔ research evidence binds actual original bytes; model completion is not user acceptance (1063.4537ms)
|
||
✔ same text with distinct user source instances stays distinct; an appended requirement only invalidates its own revision (1346.1521ms)
|
||
✔ foreign project, old Task and fabricated evidence strings are rejected with preserved failed proofs (1928.3647ms)
|
||
✔ source changes invalidate prior proofs and cannot certify a read that was already stale at binding (1737.1758ms)
|
||
✔ missing or tampered artifacts never become evidence and original failures remain after recovery (1824.9299ms)
|
||
✔ checks omitted by explicit agreement are reported as not executed and never passed (588.9938ms)
|
||
✔ user confirmation stays separate from engineering evidence, is bounded to current inputs and cannot be silently converted (843.4112ms)
|
||
✔ existing multi-file results keep provenance and invalidate only evidence whose files changed (995.9659ms)
|
||
✔ unrelated additions preserve the checked file facts but remain visible as unreviewed user sources (901.4952ms)
|
||
✔ actual Git preview and publication recheck changed requirement bindings without touching HEAD or the owner index (7358.0279ms)
|
||
✔ no-test file application and manual completion keep pending user requirements for explicit review (1304.8995ms)
|
||
✔ revision races, forged source ranges, evidence fields and deletion cannot overwrite sealed requirements (626.2276ms)
|
||
✔ requirement binding prevents completion and Git acceptance after a review changes; legacy tasks stay explicit (1878.2394ms)
|
||
ℹ tests 21
|
||
ℹ suites 0
|
||
ℹ pass 21
|
||
ℹ fail 0
|
||
ℹ cancelled 0
|
||
ℹ skipped 0
|
||
ℹ todo 0
|
||
ℹ duration_ms 35423.321
|