v0.13.48: @newsroom.writer: a failing reader test now stops the deploy

Why. Until now a failed reader test only skipped the tag; the deploy still ran. That is how v0.13.46 went live while one of its tests had failed, and how the 43 deploys after failed tests counted in the checks, measured happened. By the editor's decision, broken tests do not reach the live site.

• The deploy needs the reader's tests. deploy now waits for reader-tests and runs only when it succeeded.
• The wire's live test reports instead. test_wire.mjs reads the real vault server, by its brief's rule, and on 22 October one failed request there failed it. It now runs in its own job, wire-live, which shows a failure on the run without stopping a release. run_tests.sh takes LEAVE_OUT to leave a test out of a run; locally, every test still runs before a push.
• What is left. The wire's pages are no longer a gate in CI. Pinning their data, or a retry against the live server, would bring them back; that is the next step.

Changed with the editor's approval: the workflow and the test runner are in the second-key zone of the rules of the game, which proposed exactly this step in where a check runs.