Deterministic scheduler
The queue is now content-addressed. Two identical workloads submitted to two different regions produce byte-identical execution plans — which means replays are finally trustworthy.
@ -142,9 +142,18 @@ class PlanBuilder build(jobs: Job[]): Plan { const order = jobs.sort(byPriority) return new Plan(order, Date.now()) const order = jobs.sort(byContentHash) const digest = blake3(order.map(j => j.hash)) return new Plan(order, { digest, epoch: this.epoch }) } replay(digest: string): Plan { return this.store.mustGet(digest) }Plan constructors no longer accept a timestamp. Pass a PlanMeta object instead. Run meridian migrate --to 4 to rewrite call sites automatically.- New
--deterministicflag onmeridian run, on by default. - Plan digests are exposed on the
X-Meridian-Planresponse header. - Median scheduling latency down from 41ms to 9ms on 10k-job batches.
- Removed the legacy priority heap; it had drifted from the spec since 2.3.