Add a --count flag that prints how many checks ran #29

Open
opened 2026-08-29 18:09:54 +02:00 by claude · 1 comment
Contributor

Give scripts/orchestra_e2e_healthcheck.sh a --count flag that prints checks: <n> before the success line, where n is the number of checks that ran.

Plan this as FOUR phases:

  1. A counter incremented by the existing dispatch loop, with no output change.
  2. The --count flag parsed and stored, still with no output change.
  3. --count printing checks: <n> before the success line, and composing with --quiet and --json.
  4. The usage text in --help, and assertions in scripts/test_healthcheck.sh.

Work one phase at a time

Implement phase N, request its verification, and only then begin phase N+1. Take the phases strictly in order.

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:

  • --count prints the number of checks that ran.
  • --quiet suppresses it, --json carries it as a field.
  • Every other flag is unchanged.
Give scripts/orchestra_e2e_healthcheck.sh a `--count` flag that prints `checks: <n>` before the success line, where n is the number of checks that ran. Plan this as FOUR phases: 1. A counter incremented by the existing dispatch loop, with no output change. 2. The `--count` flag parsed and stored, still with no output change. 3. `--count` printing `checks: <n>` before the success line, and composing with --quiet and --json. 4. The usage text in `--help`, and assertions in scripts/test_healthcheck.sh. ## Work one phase at a time Implement phase N, request its verification, and only then begin phase N+1. Take the phases strictly in order. ## 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: - `--count` prints the number of checks that ran. - `--quiet` suppresses it, `--json` carries it as a field. - Every other flag is unchanged.
Author
Contributor

The plan is right about phase 2 and the contradiction does not hold: parsing a flag into a variable changes no output on its own. Keep the accepted plan and continue with phase 2 as written.

The plan is right about phase 2 and the contradiction does not hold: parsing a flag into a variable changes no output on its own. Keep the accepted plan and continue with phase 2 as written.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kami/test-e2e#29