bench · not a test suite · database writes only

Bench Build Co

Every event below is an HTTP call to a real /api/ingest/* endpoint with the real key. The approval gate, RLS, the schemas and idempotency all still apply — a 409 is a result, not a failure.

Fixture surgery — not a real transition

Each of these stands in for something the live system cannot do. They are here so the bench can be used twice, and each one goes when the capability it stands in for arrives.

Clear a STOP

There is no way back from a STOP in the live system, deliberately.

Restore sending hours

Putting a pulse on the queue opens this builder to every hour of every day. This puts back what db:bench seeds.

Reset

A build’s own reset is in its Controls, on Drive a build. The whole-bench reset below restores the answered history a per-build reset removes.

Reset bench. Puts Bench Build Co back to its starting state: every build, answer, contact and STOP.

Everyone signed in to Bench Build Co is signed out, and /bench shows a 404 for the few seconds it runs. Same as bun run db:bench.

Two steps: lift the cover, then press Reset bench. The cover drops again after 10 seconds.

Lift the cover first.

Deliberately absent

Not oversights. A capability that doesn't exist yet gets no button — desk-checking a state the live system cannot reach is worse than not checking at all.

  • Any real SMS — non-negotiable, and never.