47 lines
1.8 KiB
Markdown
47 lines
1.8 KiB
Markdown
# Task 06G4GBSQ2WRGD5HGYPYZZ4TYH0
|
|
|
|
Add a --strict mode to the healthcheck
|
|
|
|
- Project: test-e2e
|
|
- Source: gitea:test-e2e/13
|
|
- Priority: 0
|
|
|
|
## Instructions
|
|
|
|
Three phases, in this order.
|
|
|
|
## Phase 1 — `--strict` on the healthcheck
|
|
|
|
`scripts/orchestra_e2e_healthcheck.sh --strict` must reject an unrecognised flag: print `unknown flag: <flag>` on stderr and exit 2. Without `--strict` the current silent-ignore behaviour is unchanged, and `--help` still wins from any position.
|
|
|
|
## Phase 2 — cover `--strict` in the existing self-test
|
|
|
|
Extend `scripts/orchestra_e2e_selftest.sh`, which already asserts the plain and `--json` runs. Add assertions that `--strict --nonsense` exits 2 and that `--strict` alone exits 0. Keep its existing `fail()` helper and its existing assertions.
|
|
|
|
## Phase 3 — keep the pinned usage text honest
|
|
|
|
`scripts/test_healthcheck.sh` pins the healthcheck's exact `--help` output in a hardcoded `USAGE` variable. Phase 1 changes nothing about `--help`, so this phase only confirms the pin still holds.
|
|
|
|
Verify this phase by running the pinned test itself:
|
|
|
|
- run: ["bash", "scripts/test_healthcheck.sh"]
|
|
|
|
## Constraints
|
|
|
|
The project's verification policy allows exactly two command shapes:
|
|
|
|
["bash", "-n", "<one file>"]
|
|
["bash", "scripts/orchestra_e2e_healthcheck.sh"]
|
|
|
|
## Research first
|
|
|
|
Establish at least three findings with distinct confidence: at least one `fact`, one `inference`, one `assumption`. Cite at least two in References.
|
|
|
|
|
|
## 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.
|