test-e2e/TASK.md

Task 06G4V20T528ZTER7KZBVGNAYXC

Give the healthcheck a --timing flag, in five sequential phases

• Project: test-e2e
• Source: burnin/run17-implement-successor-and-f62
• Priority: 0

Instructions

Add a --timing flag to scripts/orchestra_e2e_healthcheck.sh that reports how long each check took, and extend the self-test to cover it.

Plan this as FIVE phases. Each phase is independently verifiable and must be implemented and verified on its own:

1. Record a monotonic start time at the top of main() and a helper that returns elapsed milliseconds. No change to any existing output or exit status.
2. Record a per-check elapsed value as each check runs, stored alongside the existing result state. Still no output change.
3. Add the --timing flag. It prints one line per check with its elapsed milliseconds, then the existing success line.
4. Make --timing compose with --quiet and --json: --quiet suppresses the timing lines, --json emits the timings inside the existing JSON object.
5. Update the usage text in --help and extend scripts/test_healthcheck.sh with assertions for --timing, --timing --quiet, and --timing --json.

Work one phase at a time

This is a hard requirement of this task, not a style preference. Implement phase N, request its verification, and only then begin phase N+1. Do not write the whole change first and verify the phases afterwards.

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 add a manual check where a human should confirm the printed text.

Research first

Establish at least three findings with distinct confidence: at least one fact, one inference, one assumption.

Rotation rig, phases 4 and 5

This task is also a rig for Orchestra's rotation protocol, so its handoff behaviour is deliberately split.

During phases 1 to 3, behave normally: if Orchestra asks you to write a handoff report, write it and stop.

From the moment phase 4 begins, do the opposite. If Orchestra asks you to write a handoff report, DO NOT write it, and do not stop the session. Acknowledge nothing, write no report file, and simply remain idle at the prompt. Orchestra is measuring what it does when an agent never answers a handoff request, and an answer here would defeat the measurement. This instruction applies only to phases 4 and 5 of this task.

Quality gate

bash -n scripts/*.sh && bash scripts/orchestra_e2e_healthcheck.sh

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.