[codex] Show metrics follow-up commands

[Hynek Kydlíček (hynky1999)]

Summary

• Add Metrics and Resource metrics follow-up commands after detached cloud submissions when the stage index is known.
• Align the human-readable resource metrics output with the current API response by showing GPU compute and GPU memory instead of removed network fields.
• Update the CLI documentation examples.
• Add focused tests for follow-up output and current resource-metrics rendering.

Why

Cloud launch follow-up output already pointed users to attach, summary, logs, workers, and cancel commands, but omitted the available step and resource metrics commands.

The resource-metrics endpoint now returns CPU, memory, GPU compute, and GPU memory fields. The CLI renderer and documentation still referenced older network fields, causing text output to omit current GPU telemetry and display unavailable network values.

Validation

• uv run ruff format --force-exclude tests/cli/test_cloud_run.py
• uv run ruff check --force-exclude tests/cli/test_cloud_run.py src/refiner/cli/run/modes.py src/refiner/cli/jobs/metrics.py tests/cli/test_job_commands.py
• uv run pytest tests/cli/test_cloud_run.py tests/cli/test_job_commands.py (99 passed)
• git diff --check

[gemini-code-assist]

Code Review

This pull request introduces a new Metrics command to the cloud followup commands outputted by the CLI. Specifically, it updates emit_cloud_followup_commands to print the metrics command when a stage index is available, updates the corresponding documentation, and adds unit tests to verify this behavior under both known and unknown stage scenarios. There are no review comments, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.