CLI tiers output hides exact-commit phase choices #550

What's the problem

Related: #546 / draft PR #547.

bench-ci tiers --repo rigforge --commit 0bbedc773adf073c43d6758032bcff437f57f18d succeeds but prints an empty selectable: value for tier4-e2e. The same exact-commit /tiers response discovers connect, control, and the other harness phases in selectable.phases, while selectable.targets is empty. The CLI's cmd_tiers renders only targets.

Expected: the discovery command shows the accepted phase choices. Actual: discovered phases are hidden, making supported workload selection appear unavailable. This is a CLI display defect; the API accepts the discovered phases. Authorized job 1888@0bbedc773adf073c43d6758032bcff437f57f18d uses phases=["connect","control"] and is pending; no product verdict is claimed from submission.

Please render discovered phases as well as targets (and other supported choices where appropriate). No worker or runner configuration was changed by hand.

Moved from p2pool-starter-stack/bench-ci#996 by the runner's triage: The issue asks for a RigForge CLI display fix in its product code; bench-ci’s API already discovers the phases, and the runner is unchanged. (recreated: GitHub cannot transfer out of a private repo).

what it impacts

Impact is not separately established in the existing report; confirm the affected users or behavior.

How I found it

Discovery details are not separately established in the existing report; preserve and verify the evidence already recorded.

how important is it

Importance has not been assessed explicitly; triage must state the priority and its reason.

acceptance criteria

Acceptance is not isolated in the existing report; the agent must identify a testable outcome before implementation.

possible solutions

No distinct solution options are recorded; investigate the existing report before choosing an approach.