2.6 KiB
Task 06G4VF5HZW7Q4JBM3TTY7W1Y64
Add ten named checks to the healthcheck, in five phases
- Project: test-e2e
- Source: burnin/run18-implement-successor
- Priority: 0
Instructions
scripts/orchestra_e2e_healthcheck.sh currently runs a single check. Grow it to ten named checks, each implemented as its own shell function, each reported by name.
The ten checks, all read-only and all satisfiable inside this repository:
- repo_root_readable, 2. scripts_dir_present, 3. healthcheck_executable_bit, 4. selftest_present, 5. test_healthcheck_present, 6. readme_present, 7. no_crlf_line_endings, 8. no_tabs_in_scripts, 9. shebang_is_bash, 10. usage_text_mentions_every_flag.
Each check is a function named check_ that returns 0 for pass and 1 for fail, prints nothing on its own, and records its name and outcome in the existing results state.
Plan this as FIVE phases:
- Checks 1 to 3, with the dispatch loop that runs a list of check functions and records each outcome.
- Checks 4 to 6.
- Checks 7 to 8.
- Checks 9 to 10.
- Update the usage text in --help to list every check name, and extend scripts/test_healthcheck.sh with one assertion per check plus an assertion that all ten names appear in the output.
Work one phase at a time
This is a hard requirement. Implement phase N, request its verification, and only then begin phase N+1. Do not write the whole change first and verify the phases afterwards.
Behaviour that must not change
The existing success line, the --quiet, --json and --help flags, and the exit status all keep their current behaviour when every check passes.
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 add a manual check where a human should confirm the printed text.
Research first
Establish at least three findings with distinct confidence: at least one fact, one inference, one assumption.
Handoff behaviour
Behave normally throughout this task. If Orchestra asks you to write a handoff report, write it and stop.
Quality gate
bash -n scripts/*.sh && bash scripts/orchestra_e2e_healthcheck.sh
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.