test(control): adversarial restart replay invariant suite

[hadamrd]

Parent: #163

Add tests that append interleaved frontier, memory, task, critic, and worker events, reopen the database, replay projections from zero, and compare them against stored projection cursors and BootContext. Include duplicate idempotency keys and out-of-order projection advancement attempts.

Acceptance evidence: wrong replay ordering or stale cursor advancement fails the suite.

Customer story

A maintainer deciding whether an autonomous patch is semantically trustworthy benefits because restart and replay behavior is tested against failure modes, not only the happy path.

Source

Generated by Forge brainstorm dry-run from repo-local product vision and axes.

[hadamrd]

forge-loop attempt — ⏳ PR OPEN (~439s)

PR: #187

Note: critic blocked merge: [sev2/tests] replay_projection is a new public function, but the tests only cover successful replay. Add an adversarial test where projection.apply() raises partway through r

fingerprint: 7f01a0f0512e

{
  "ts": "2026-06-03T01:18:37+00:00",
  "status": "open",
  "pr_url": "https://github.com/hadamrd/forge-loop/pull/187",
  "duration_s": 439.3,
  "note": "critic blocked merge: [sev2/tests] `replay_projection` is a new public function, but the tests only cover successful replay. Add an adversarial test where `projection.apply()` raises partway through r",
  "event_count": 0,
  "brief_fingerprint": "7f01a0f0512e1571ee597fdc1b1c6e4b966fb7df1273d209299906cc5f18a3c4"
}