47 lines
1.6 KiB
Markdown
47 lines
1.6 KiB
Markdown
# Task 06G4WDJ06G7FK00QF73Z9DDBT4
|
|
|
|
Sort the check names in --list-checks
|
|
|
|
- Project: test-e2e
|
|
- Source: gitea:test-e2e/27
|
|
- Priority: 0
|
|
|
|
## Instructions
|
|
|
|
`--list-checks` prints the ten check names in the order they run. Add a `--sorted` modifier that prints them in alphabetical order instead, leaving run order untouched.
|
|
|
|
Plan this as THREE phases:
|
|
|
|
1. A helper that returns the check names in alphabetical order, with no caller yet.
|
|
2. `--sorted` accepted alongside `--list-checks`, using that helper. Alone, `--sorted` changes nothing.
|
|
3. The usage text in `--help`, and assertions in scripts/test_healthcheck.sh for both orders.
|
|
|
|
## Work one phase at a time
|
|
|
|
Implement phase N, request its verification, and only then begin phase N+1.
|
|
|
|
## Verification policy for this project
|
|
|
|
Only two commands may appear on a run: line, exactly:
|
|
|
|
- ["bash", "-n", "<path>"]
|
|
- ["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:
|
|
- `--list-checks --sorted` prints the ten names alphabetically.
|
|
- `--list-checks` alone keeps run order.
|
|
- 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.
|