=== the CONCURRENT double-use race: two processes, one approval ======
    Two guarded runs started with the SAME token at the same instant.
    Exactly one wins the O_EXCL consumption marker and executes; the
    other is refused because the request id is already consumed.
    Which real process finishes first is not a fact a lesson can
    quote, so the winner signals when its last receipt is on disk
    and the loser waits for that signal before attempting. Both are
    launched together and both stay alive; only the moment the loser
    attempts is ordered, and it is still refused by the real O_EXCL
    marker. That also fixes the order of the two runs appends to
    this one hash-chained receipt file.

--- process A (no artificial delay - the winner) ----------------------
guarded run RUN-RACE-01  agent=meridian-ops-agent  target=fielddesk-api/control  transport=local
  clock 2026-08-18T15:56:00Z  policy envelope/meridian-ops@2026-08-29.2  request REQ-165143C1DE
  STEP 0 prereq       no handoff declared for this envelope: meridian-ops-agent is an ops automation account, not a registered AI system on Meridian's register, so it has no AI Assurance handoff to read.
  STEP 1 envelope     ASK   roll_deploy  class=reversible  zone=it-data  (version matches ^1\.14\.[0-9]{1,2}$)
        budget: 0/6 actions, 0/3 mutating used in RUN-RACE-01
  STEP 2 pre-state    captured dbf3098bde64c1db  pool_max=32 version=1.14.3 backups=3
  STEP 3 dry-run      version 1.14.3 -> 1.14.3
        plan hash dbf3098bde64c1db - this is what an approver signs
  STEP 4 approval     1 of 1 valid  p.velasquez  keys a  binding 3ada44f7008f  expires 2026-08-18T16:11:00Z
  STEP 5 execute      version 1.14.3 -> 1.14.3
  STEP 6 verify       PASS  version == '1.14.3'
  STEP 7 compensate   not needed
  STEP 8 receipt      seq 1  6930c2a369ffa938  prev GENESIS
RESULT verified  exit 0

--- process B (waits for A's done-signal - the loser) ------------------
guarded run RUN-RACE-01  agent=meridian-ops-agent  target=fielddesk-api/control  transport=local
  clock 2026-08-18T15:56:00Z  policy envelope/meridian-ops@2026-08-29.2  request REQ-165143C1DE
  STEP 0 prereq       no handoff declared for this envelope: meridian-ops-agent is an ops automation account, not a registered AI system on Meridian's register, so it has no AI Assurance handoff to read.
  STEP 1 envelope     ASK   roll_deploy  class=reversible  zone=it-data  (version matches ^1\.14\.[0-9]{1,2}$)
        budget: 1/6 actions, 1/3 mutating used in RUN-RACE-01
  STEP 2 pre-state    captured dbf3098bde64c1db  pool_max=32 version=1.14.3 backups=3
  STEP 3 dry-run      version 1.14.3 -> 1.14.3
        plan hash dbf3098bde64c1db - this is what an approver signs
  STEP - DENY         approval for request REQ-165143C1DE was already used by receipt AR-A0D99E817DDF at 2026-08-18T15:56:00Z - approvals are single-use, and a short expiry never prevented a replay
  STEP 8 receipt      seq 2  e12929bfd12f716a  prev 6930c2a369ffa938
RESULT denied  exit 4

exit codes: A=0  B=4
