Print the check count in the summary header #35

2026-08-29T20:10:31+02:00

kami commented

2026-08-29 20:10:31 +02:00

Goal

Print the check count in the summary header

--summary prints one line per check. Add a header line running <n> checks before those lines, where n is the number about to run. Plan this as THREE phases: 1. A helper that returns the number of checks that will run, with no output change. 2. The header line printed by --summary, using that helper. 3. 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. ## 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: - --summary prints the header before its per-check lines. - --quiet suppresses it, and every other flag is unchanged.

Acceptance

not stated in the task contract

Verification

bash -n scripts/*.sh && bash scripts/orchestra_e2e_healthcheck.sh exited 0
commit: e9e5a84a4c
independent review of e9e5a84a4c: pass
minor findings, not fixed: 1
accepted plan: 2edcbe9ef1cbe6c93f7a201942a0eb465a94d9bee5276a9e0c4bf5ed854cdd95

Behavioural changes

none reported

Deviations from plan

none reported

Remaining risks

none reported

Review hotspots

none reported

Reviewer findings

minor: scripts/test_healthcheck.sh:86 No automated assertion covers the --json guard on the new header, so a regression printing the header before the JSON line would still pass the test suite.

The sections above are derived from Orchestra state. The reported
changes, deviations, risks, and hotspots are the implementing agent's
own account and are not verified.

## Goal Print the check count in the summary header `--summary` prints one line per check. Add a header line `running <n> checks` before those lines, where n is the number about to run. Plan this as THREE phases: 1. A helper that returns the number of checks that will run, with no output change. 2. The header line printed by --summary, using that helper. 3. 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. ## 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: - --summary prints the header before its per-check lines. - --quiet suppresses it, and every other flag is unchanged. ## Acceptance - not stated in the task contract ## Verification - `bash -n scripts/*.sh && bash scripts/orchestra_e2e_healthcheck.sh` exited 0 - commit: e9e5a84a4c73be694b923ab8ad2d1308b43502dd - independent review of e9e5a84a4c73be694b923ab8ad2d1308b43502dd: pass - minor findings, not fixed: 1 - accepted plan: 2edcbe9ef1cbe6c93f7a201942a0eb465a94d9bee5276a9e0c4bf5ed854cdd95 ## Behavioural changes - none reported ## Deviations from plan - none reported ## Remaining risks - none reported ## Review hotspots - none reported ## Reviewer findings - minor: `scripts/test_healthcheck.sh:86` No automated assertion covers the --json guard on the new header, so a regression printing the header before the JSON line would still pass the test suite. The sections above are derived from Orchestra state. The reported changes, deviations, risks, and hotspots are the implementing agent's own account and are not verified.

kami added 3 commits 2026-08-29 20:10:32 +02:00

orchestra: TASK.md 7c24b6acea

orchestra: pre-release WIP snapshot (orchestra-06g4xafh1mbpc35vsjn7v3ns14-5ec6e9dc) 36bcf8a2e1

orchestra: pre-release WIP snapshot (orchestra-06g4xafh1mbpc35vsjn7v3ns14-5ec6e9dc) e9e5a84a4c

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin orchestra/06G4XAFH1MBPC35VSJN7V3NS14:orchestra/06G4XAFH1MBPC35VSJN7V3NS14

git checkout orchestra/06G4XAFH1MBPC35VSJN7V3NS14

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kami/test-e2e#35