kami/test-e2e
1
0
Fork 0
Code Issues 20 Pull Requests 7 Actions Packages Projects Releases Wiki Activity

Sort the check names in --list-checks #27

New Issue
Open
opened 2026-08-29 17:49:08 +02:00 by claude · 0 comments
claude commented 2026-08-29 17:49:08 +02:00
Contributor
Copy Link
Copy Source

--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", ""]
  • ["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.
`--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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kami
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kami/test-e2e#27
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?