[Phase 2.1] Integration tests: provisioning on-mesh with unstable pointer #42

Closed
opened 2026-03-16 19:07:52 +00:00 by Mark · 0 comments
Owner

Test Scenario

End-to-end provisioning flow using unstable.tail018ac4.ts.net as node pointer:

Setup

  • Node A: local mesh node
  • Node B: unstable.tail018ac4.ts.net

Test Flow

  1. Emit boundary.found on mesh
  2. Mesh emits provision_worker intent
  3. Provisioning capability claims under contract
  4. Placement selects unstable.tail018ac4.ts.net
  5. Worker instance spawned on unstable
  6. Worker claims intent, executes, commits result
  7. Worker exits
  8. Ledger shows complete lifecycle

Edge Cases

  • Duplicate intent with same idempotency key (should not double-spawn)
  • Spawn failure (should retry with backoff)
  • Deadline exceeded (should mark failed, forfeit bond)
  • Worker crash mid-execution (should mark failed, allow retry)

Acceptance

  • Entire flow uses core intent protocol only
  • No custom provisioning channel dependency
  • Provisioning bone enforces deterministic correctness
  • Test runs in CI with memory backplane + mocked node pointers
## Test Scenario End-to-end provisioning flow using `unstable.tail018ac4.ts.net` as node pointer: ### Setup - Node A: local mesh node - Node B: `unstable.tail018ac4.ts.net` ### Test Flow 1. Emit `boundary.found` on mesh 2. Mesh emits `provision_worker` intent 3. Provisioning capability claims under contract 4. Placement selects `unstable.tail018ac4.ts.net` 5. Worker instance spawned on unstable 6. Worker claims intent, executes, commits result 7. Worker exits 8. Ledger shows complete lifecycle ### Edge Cases - [ ] Duplicate intent with same idempotency key (should not double-spawn) - [ ] Spawn failure (should retry with backoff) - [ ] Deadline exceeded (should mark failed, forfeit bond) - [ ] Worker crash mid-execution (should mark failed, allow retry) ## Acceptance - [ ] Entire flow uses core intent protocol only - [ ] No custom provisioning channel dependency - [ ] Provisioning bone enforces deterministic correctness - [ ] Test runs in CI with memory backplane + mocked node pointers
Mark 2026-05-28 00:29:46 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#42
No description provided.