Contract-suite scheduler rows (task suite-scheduler-rows): the determinism-posture extension in properties.rs's module doc (runner-driving rows admitted — spawned run_schedules(stop) tasks on a core StopToken against state outcomes only, elapsed-boundary-band tolerances, never timing-value assertions, never two-task race windows; ADR-017 §2 class 4) and three version-stamped rows: scheduler_boundary_fires (fired jobs are ordinary claimable work with ScheduleOpts over the plain-queue derived defaults 300/9/5/none + payload exact, clean-stop Ok(()), fired count inside the elapsed-boundary band — no double-fire per boundary while one leader runs; ADR-009 §3/§4, ADR-020 §3, ADR-019 §4), scheduler_bounded_catchup (runner-less downtime proves no fire without a runner, ≥3 elapsed boundaries replay boundary-by-boundary bounded below the 64-cap and inside the band; ADR-009 §4), scheduler_leadership_discipline (two spawned runners on one store: exactly one Ok(())/Err(LeadershipLost) pair by value, no duplicated fires inside the band; ADR-009 §1/§6, ADR-019 §4) — wired into both engines' suite targets (SQLite tests, pg harness_row!s), suite tokio dep added for the runner rows. Dispositions recorded in Notes: the beyond-cap skip-forward leg stays pinned engine-side (both engines' scheduler tests already backdate next_fire_at directly — catch_up_replays_up_to_the_cap_then_skips_forward twins), and the pg fire-wake parity gap is not demanded by these rows' shapes (claim-polling observation only; the one-call wake_tx disposition recorded for a later task). Verified: sqlite suite 16/16, pg suite 16/16 vs harness twice + solo re-runs of the three rows per engine (determinism), workspace build/test green, clippy -D warnings, fmt clean

alkstore-sqlite/tests/contract_suite.rs

@@ -71,7 +71,9 @@ mod rows {
         enqueue_opts_resolution, extent_clamp_semantics, in_tx_reads_see_own_writes,
         job_handle_validity_predicate, name_validation_rejects_empty_and_reserved,
         payload_round_trip_stores_exact_encoding, payload_too_large_never_produced_on_sqlite,
-        queue_depth_reclaim_and_dead_letter, receiver_close_and_save_arms, sweep_no_stranded_rows,
+        queue_depth_reclaim_and_dead_letter, receiver_close_and_save_arms,
+        scheduler_boundary_fires, scheduler_bounded_catchup, scheduler_leadership_discipline,
+        sweep_no_stranded_rows,
     };
 
     use super::SqliteFactory;
@@ -139,6 +141,21 @@ mod rows {
     async fn row_sweep_no_stranded_rows() {
         sweep_no_stranded_rows(&factory("row-sweep-stranded")).await;
     }
+
+    #[tokio::test(flavor = "multi_thread")]
+    async fn row_scheduler_boundary_fires() {
+        scheduler_boundary_fires(&factory("row-scheduler-boundary")).await;
+    }
+
+    #[tokio::test(flavor = "multi_thread")]
+    async fn row_scheduler_bounded_catchup() {
+        scheduler_bounded_catchup(&factory("row-scheduler-catchup")).await;
+    }
+
+    #[tokio::test(flavor = "multi_thread")]
+    async fn row_scheduler_leadership_discipline() {
+        scheduler_leadership_discipline(&factory("row-scheduler-leadership")).await;
+    }
 }
 
 mod factory_shape {