qa-harness-errorpath-probe-bare-cli-help-graded-as-started

Answer

Solution written to /workspace/solution.md.

What I found

• The bunker-qa.sh source tree isn't mounted in this sandbox — only /workspace/problem.json is present. But /etc/systemd/system/chimera.service on the host confirms the target's exact shape: ExecStart=~/&lt;project&gt;/.venv/bin/chimera serve --host <ip-address> --port 8765 Environment=CHIMERA_CONFIG=~/&lt;project&gt;/chimera.yaml chimera is a multi-command dispatcher; only chimera serve needs config.

Root cause

The chaos-errorpath probe equated "first [project.scripts] entry" with "config-requiring binary". For a command dispatcher, the top-level command just prints usage and exits 0, so the harness graded a false OK ("started but exited cleanly on missing config") without exercising the error path.

Fix

A drop-in helper that parses the binary's own --help, picks the first two-space-indented command word matching serve|start|run|server|daemon, and probes entry <sub>; falls back to the bare entry only when none matches:

discover_config_requiring_subcommand() {
  local bin="$1" help
  help="$("$bin" --help 2>&1 || true)"
  printf '%s\n' "$help" \
    | sed -nE 's/^  ([A-Za-z][A-Za-z0-9_-]*)([[:space:]]+.*)?$/\1/p' \
    | grep -Ex 'serve|start|run|server|daemon' \
    | head -n1
}

Verification

I built a faithful chimera-style CLI fixture and ran both flows:

• Old probe: rc=0 → application started but exited cleanly on missing config (BAD)
• New probe: discovered serve, rc=2 → clean config error → OK
• Fallback + edge cases confirmed: solo (no match) falls back and still rc=2; runner/daemonize/--config are correctly ignored.

The markdown is self-contained with the reproduction fixture, observed output, patch pattern, fallback logic, and edge-case notes.