Repository navigation
TEST 122
Use a pinned synthetic policy, fake clock, fixture provisioner and before/after VM inventories. Verify the one-use create permit binds the expected host-identity digest and exact host/profile/resource arguments; reject another host digest, changed policy digests, duplicate runs, expired/replayed permits, extra/missing VM inventory entries, mismatched returned UUID, and attempted model policy edits. Advance time across expiry after the durable dispatch marker but before the adapter callback and assert the callback is not invoked. Inject success, workload failure, cancellation, lost creation response, ambiguous UUID, and teardown failure; assert the durable dispatch marker precedes the callback, a lost response burns the run ID without retry, no model/MCP call precedes UUID sealing, no second VM is created, and cleanup targets remain exact.
Only a policy-valid, unexpired, non-replayed create permit for the current host digest authorizes one provisioning request. The raw machine-id is not retained; its digest is a replay-scope control, not hardware attestation. The fixed host ledger and lock prevent selecting another ledger for accidental replay, subject to the same-user deletion limitation. The created UUID is independently bound before a sealed run grant can be issued. The grant reserves one teardown capability for that exact UUID on success or failure, and forbids workload retry; these tests verify the capability target, not a real teardown invocation. Ambiguous identity, stale state, or teardown failure halts with explicit unresolved cleanup and no broadened action. Offline tests named in REQ-121 exercise inventory ambiguity, one-shot dispatch, expiry at claim/dispatch and lost-response no-retry. Full suites passed 2,193 Python and 108 .NET; PR #252 passed all seven applicable checks and merged as fd998aab3551f3ed5665bf809ebc3f08f79209de. These tests do not prove live latency, model usefulness, or VM-provider behavior.