RUN  v3.2.7 /tmp/circe-round3-evidence

 × round3.test.ts > a late concurrent reconciliation cannot regress a terminal outcome 13ms
   → expected 'UNKNOWN' to be 'SUCCEEDED' // Object.is equality
 × round3.test.ts > interrupt during an invocation prevents the remaining pending effect from starting 4ms
   → expected 2 to be 1 // Object.is equality
 × round3.test.ts > ambiguous clarification cannot complete a pending request into execution 6ms
   → expected [ { …(7) } ] to have a length of +0 but got 1
 ✓ additional.test.ts > invalid revision during validation revokes the old authorization 6ms
 ✓ additional.test.ts > an ambiguous affirmative cannot authorize a pending effect 1ms
 ✓ additional.test.ts > completed command ids reject different content just like in-flight ids 2ms
 ✓ additional.test.ts > overlapping dispatch loops invoke each frozen effect only once 2ms
 ✓ additional.test.ts > semantic ingestion snapshots classifier output before awaiting validation 1ms
 ✓ additional.test.ts > a semantic turn cannot borrow versions from a different frame 7ms
 ✓ additional.test.ts > turn exclusions cover executable slot refs, not only proposition summary refs 2ms
 ✓ additional.test.ts > synthesized batch receipts retain the idempotency key actually sent 2ms
 ✓ additional.test.ts > a late RUNNING acknowledgement cannot overwrite an observed terminal outcome 1ms
 ✓ previous.test.ts > deduplicates the same proposal while the first delivery is in flight 4ms
 ✓ previous.test.ts > a new confirm id cannot refreeze a transaction with a RUNNING effect 1ms
 ✓ previous.test.ts > a confirm for an absent transaction must not confirm a different live transaction 0ms
 ✓ previous.test.ts > a cancelled transaction cannot be resurrected by a revision addressed to its id 1ms
 ✓ previous.test.ts > caller mutation during validation cannot retarget frozen effects 1ms
 ✓ previous.test.ts > different runtimes do not reuse the same external idempotency key 1ms
 ✓ previous.test.ts > an explicitly supplied but non-covering evidence set cannot fall back to current snapshots 1ms
 ✓ previous.test.ts > semantic proposals retain the exact frame version rather than rebinding to a new world version 4ms
 ✓ previous.test.ts > an inspect/query proposition does not become an executable proposal 0ms
 ✓ previous.test.ts > ambiguous classification with a capability does not invoke through ingest 1ms
 ✓ previous.test.ts > oversized mandatory context is explicitly reported as over budget 37ms
 ✓ previous.test.ts > frames differing in coverage metadata have different exact-input hashes 1ms
 ✓ previous.test.ts > late publication cannot attach a stale neighborhood judgment to the latest generation 1ms
 ✓ previous.test.ts > an obligation event invalidates a judgment over prior knowledge 0ms
 ✓ previous.test.ts > a reused spec id rejected at a later stage cannot leave an earlier accepted value 1ms
 ✓ previous.test.ts > required arity-one slot validation also applies to revisions 0ms
 ✓ previous.test.ts > journal contains enough command identity to recognize replayed typed proposals 1ms
 ✓ previous.test.ts > clear-selection without refs clears the UI selection 0ms

⎯⎯⎯⎯⎯⎯⎯ Failed Tests 3 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  round3.test.ts > a late concurrent reconciliation cannot regress a terminal outcome
AssertionError: expected 'UNKNOWN' to be 'SUCCEEDED' // Object.is equality

Expected: "SUCCEEDED"
Received: "UNKNOWN"

 ❯ round3.test.ts:38:52
     36|  if(releases[1])releases[1]({status:'UNKNOWN'});
     37|  await second;
     38|  expect(r.runtime.state().effects.get(id)?.status).toBe('SUCCEEDED');
       |                                                    ^
     39| });
     40| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/3]⎯

 FAIL  round3.test.ts > interrupt during an invocation prevents the remaining pending effect from starting
AssertionError: expected 2 to be 1 // Object.is equality

- Expected
+ Received

- 1
+ 2

 ❯ round3.test.ts:55:28
     53|  if(countBeforeResume>1)release({ok:true,status:'SUCCEEDED'});
     54|  await running;
     55|  expect(countBeforeResume).toBe(1);
       |                            ^
     56| });
     57| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/3]⎯

 FAIL  round3.test.ts > ambiguous clarification cannot complete a pending request into execution
AssertionError: expected [ { …(7) } ] to have a length of +0 but got 1

- Expected
+ Received

- 0
+ 1

 ❯ round3.test.ts:66:20
     64|  const initial=await r.runtime.ingest(utter('request'));expect(initial…
     65|  const answer=await r.runtime.ingest(utter('answer'));
     66|  expect(r.invokes).toHaveLength(0);
       |                    ^
     67|  expect(answer.reply?.kind).toBe('question');
     68| });

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/3]⎯


 Test Files  1 failed | 2 passed (3)
      Tests  3 failed | 27 passed (30)
   Start at  12:28:02
   Duration  590ms (transform 237ms, setup 0ms, collect 558ms, tests 107ms, environment 0ms, prepare 198ms)