# Task 06G4W2TMZ9MW9SEBM5MGTM5288

Describe each healthcheck check in one line

- Project: test-e2e
- Source: gitea:test-e2e/24
- Priority: 0

## Instructions

scripts/orchestra_e2e_healthcheck.sh now runs ten named checks. Give each one a one-line description, and print those descriptions where the names are already printed.

The descriptions, one per check:

- repo_root_readable: the repository root exists and is readable
- scripts_dir_present: the scripts directory exists
- healthcheck_executable_bit: this script is executable
- selftest_present: the selftest script is present
- test_healthcheck_present: the healthcheck test is present
- readme_present: README.md is present
- no_crlf_line_endings: no tracked text file uses CRLF endings
- no_tabs_in_scripts: no script indents with tabs
- shebang_is_bash: every script declares the bash shebang
- usage_text_mentions_every_flag: the usage text lists every flag

Where they appear:

- `--list-checks` prints `<name>: <description>`, one per line.
- `--help` prints the same description beside each name in its Checks section.
- `--summary` is unchanged and keeps printing `<name>: ok`.

Plan this as FIVE phases, two checks per phase, in the order listed above.

## Work one phase at a time

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.

## Every phase carries both kinds of check

This is a hard requirement of this task. Each phase must have at least one automated check from the policy below. Each phase must also have at least one manual check, confirmed by a human reading the printed output. Orchestra runs the automated ones. A human owns the manual ones, and the phase is not finished until that human signs it off.

## 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.

## Behaviour that must not change

Every existing flag keeps its current behaviour and exit status: --quiet, --json, --summary, --timing, --strict, --help. The success line is unchanged.

## Research first

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

## Handoff behaviour

Behave normally. If Orchestra asks you to write a handoff report, write it and stop.

Acceptance:
- Each of the ten checks has a one-line description in exactly one place in the script.
- --list-checks prints name and description for all ten.
- --help lists all ten names with their descriptions.
- --summary, --timing, --strict, --json and --quiet behave exactly as before.

## 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.