relay-configlisted

## Inputs - Env: optional `RELAY_SKILL_ROOT` defaults to `skills`; writes go to `${RELAY_HOME:-~/.relay}/routes.json`; legacy `~/.relay/policy.json`, repo `.relay/policy.json`, and `~/.relay/executors.json` are read fallback only when routes.json is absent; optional `RELAY_CONFIG_MODEL_PROBE_TIMEOUT_MS` defaults model-list probes to `20000` ms. - Files: effective relay routes, optional repo `.relay/routes.json`, legacy fallback files listed above. - Sibling scripts: `${RELAY_SKILL_ROOT:-skills}/relay-config/scripts/relay-config.js`, `${RELAY_SKILL_ROOT:-skills}/relay-dispatch/scripts/relay-config.js`. # Relay Config Set up relay routes interactively. The user should not have to memorize command flags. ## Use when - The user asks to set up or configure relay - The user wants company-safe strict mode, personal open mode, OpenCode/Pi opt-in, or advisory-review routing - The user asks whether a provider/model route such as `example/opencode-model-*` or `openai/*` is available - The user asks to resolve a short model name such as `glm-5.2` for a known actor - The user asks whether model catalog entries are fresh or stale - The user asks to create, show, or remove a route preset such as `light`, `diverse`, or `hardened` - The user asks to run relay doctor/check ## Do not use when - Dispatching implementation work - use `relay-dispatch` - Reviewing PRs - use `relay-review` - Coordinating parallel implementation leaves - use `relay-fleet` ## Workflow ### 1. Inspect current st