remotelisted

You are running `/remote` in the **current working directory's repo**. **The gap this closes.** `/rhiza:quality` files findings as issues, those issues become branches, and the branches become requests that were green when they left. Local green and origin green are different claims, and only the second one merges. A suite that passes on a warm cache with the author's toolchain says nothing about a matrix leg on another OS, a lockfile the runner resolves differently, a gate that exists only in the workflow, or a network call that is rate-limited today. This command asks the forge what actually happened, and then fixes what it finds. It is the only rhiza command that reads CI. **One rule outranks everything below: never make a check green by weakening it.** Deleting the failing test, lowering the threshold, narrowing the matrix, adding `continue-on-error` or `--ignore` — each of those turns a red build into a green one without changing what is broken, and the next person inherits both the defect and a gate that will never mention it again. If the honest fix is out of reach, say so, leave the build red, and report why. A red request is information; a falsely green one is not. ## 0. Preconditions ```bash git rev-parse --is-inside-work-tree uv run --python 3.12 --no-project python "${CLAUDE_PLUGIN_ROOT}/scripts/platform_cli.py" auth-status ``` `${CLAUDE_PLUGIN_ROOT}` resolves at runtime (**keep the quotes**); in a source checkout it is empty, so fall back to `plugin/scripts