26 lines
1.0 KiB
Markdown
26 lines
1.0 KiB
Markdown
# Task 06G4GWWJ8SWFREF06HDYEBAG0C
|
|
|
|
Route the healthcheck output through one helper
|
|
|
|
- Project: test-e2e
|
|
- Source: gitea:test-e2e/15
|
|
- Priority: 0
|
|
|
|
## Instructions
|
|
|
|
`scripts/orchestra_e2e_healthcheck.sh` prints its success line from more than one place. Centralise the output so every path goes through one helper, and give that helper an explicit format argument rather than reading a global.
|
|
|
|
Behaviour must not change. The plain run, `--quiet`, `--help` and `--json` all keep their current output and exit statuses, and `scripts/test_healthcheck.sh` keeps passing.
|
|
|
|
## Research first
|
|
|
|
Establish at least three findings with distinct confidence: at least one `fact`, one `inference`, one `assumption`.
|
|
|
|
|
|
## 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.
|