areev-run — the areev run driver

A host over Areev (governed-agents §4), peer of areev-mcp: executes OMS Workflow grains through the pure scheduler (areev-run-core), journaling every effect as content-addressed grains — intent before dispatch, result as a supersession re-stating identity and links — with checkpoints per superstep, resume from the file alone, HITL respond with separation of duties, budgets, cancel, and journal-consistent verify.

The replay contract (§5, stated honestly): the journal is exactly-once — a result-journaled effect is never re-executed or double-counted, across interrupts and across crashes. The external effect is at-most-once per attempt in normal operation and at-least-once across the dispatch-to-result crash window: a dangling intent re-delivers under the same idempotency key and the redelivery is journaled as an Observation — recorded, never silent.