Give the healthcheck a self-test and a machine-readable mode #9
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three pieces of work, in order. Plan them as exactly three phases in that order.
Phase 1 — a self-test for the healthcheck
New file
scripts/orchestra_e2e_selftest.sh, executable,#!/usr/bin/env bash.It runs
scripts/orchestra_e2e_healthcheck.sh, then asserts:OKOn failure it prints which assertion failed and exits 1. On success it prints
selftest: okand exits 0.Verification for this phase is automated only. The one check is:
Do not add a manual step to this phase.
Phase 2 —
--jsonon the healthcheckscripts/orchestra_e2e_healthcheck.sh --jsonprints exactly one line:and exits 0. Without
--jsonthe existing human output is unchanged, and--helpkeeps working.--jsonand--helptogether behave as--help.Verification for this phase must include both an automated check and a manual step. The JSON shape is a judgement a human confirms by reading it, so state the manual step as the exact command a human runs and the exact line they should see.
Phase 3 — teach the self-test about
--jsonExtend
scripts/orchestra_e2e_selftest.shto run the healthcheck twice: once plain and once with--json. Assert the plain run still containsOK, and assert the--jsonrun prints one line beginning with{"status":.Verification for this phase is automated only:
Constraints
The project's verification policy allows exactly two command shapes:
A
run:line outside those is refused when the plan seals, not later.Research first
Before planning, establish at least three findings and label their confidence honestly: at least one
fact, oneinference, and oneassumption. The plan must cite at least two of them in References.