Skip to content

testing: unattended soak evidence for the bare engine #263

Description

@mfw78

Run the bare engine unattended and record what happened.

Why

docs/production.md publishes a systemd unit, six alert rules and a poison-recovery runbook, and there is no evidence any of it has run unattended.
The only soak item reachable from this tracker was a cross-repo child pointing at shepherd, i.e. soak evidence for a different composition.

Two claims in the handbook are currently contradicted by the code and would be caught by one soak run: the drain path (#148, where the 10s drain against a 120s dispatch deadline exits 1 with an uncommitted cursor) and the readiness surface (#147, which does not exist).

Scope

Run the bare nexum engine against a real chain for a sustained period with at least one module holding a resumable subscription.
Exercise, and record: a clean SIGTERM drain, a restart with cursor resume, a provider outage and reconnect, a module trap and its restart, and a poison quarantine.
Capture the metric series across the run, so the alert rules in section 7 can be checked against real data rather than assumed.

Done when

There is a recorded run, its duration, what was exercised, and what the handbook got wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    testingTest coverage, harness, mocks, or test-infrastructure work

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions