1.7 KiB
Task 06G4WJ9T4F35NZC4Z8QQXM9Z6G
Add a --count flag that prints how many checks ran
- Project: test-e2e
- Source: gitea:test-e2e/29
- Priority: 0
Instructions
Give scripts/orchestra_e2e_healthcheck.sh a --count flag that prints checks: <n> before the success line, where n is the number of checks that ran.
Plan this as FOUR phases:
- A counter incremented by the existing dispatch loop, with no output change.
- The
--countflag parsed and stored, still with no output change. --countprintingchecks: <n>before the success line, and composing with --quiet and --json.- The usage text in
--help, and assertions in scripts/test_healthcheck.sh.
Work one phase at a time
Implement phase N, request its verification, and only then begin phase N+1. Take the phases strictly in order.
Verification policy for this project
Only two commands may appear on a run: line, exactly:
- ["bash", "-n", ""]
- ["bash", "scripts/orchestra_e2e_healthcheck.sh"]
Anything else is refused when you seal the plan. Give every phase at least one automated check from that list and at least one manual check.
Research first
Establish at least three findings with distinct confidence: at least one fact, one inference, one assumption.
Acceptance:
--countprints the number of checks that ran.--quietsuppresses it,--jsoncarries it as a field.- Every other flag is unchanged.
Completion
Run the configured quality gate. When the task is ready for the worker to verify and deliver, create .orchestra/done. Do not write a prose completion report.
This file is immutable for the lifetime of the task (§6.2) — its hash is carried in every handoff and re-verified on every pickup. Do not edit it.