relewise-setuplisted

# Relewise Setup When `../../scripts/relewise-agent` exists relative to this file, resolve it to an absolute path and use that executable. Otherwise, use `relewise-agent` from `PATH`. Never ask the user to paste a Personal Access Token into the conversation. Do not print, repeat, inspect, or place a token in command text, command arguments, output, logs, or repository files. ## Set up or repair authentication 1. Run `relewise-agent me` without changing the current configuration. 2. If it succeeds, explain that Relewise is already connected and make no changes. Include the accessible Dataset display names only when useful. 3. If it returns `authentication_error`, distinguish a missing token from a rejected, expired, or regenerated token using the error code and message. 4. Treat the initial ordinary invocation as the check for an existing `RELEWISE_AGENT_GATEWAY_TOKEN`; do not inspect or print the variable. If the token is missing, use this order: 1. If the AI client has access to a secure credential provider containing the user's Relewise Agent Gateway PAT, retrieve it and inject it only into the `relewise-agent` child process as `RELEWISE_AGENT_GATEWAY_TOKEN`. Use this route only when it can be repeated automatically for future Relewise invocations. 2. If no reusable credential-provider route is available, explain the two supported setup choices from [authentication setup](references/authentication-setup.md): configure such a provider, or configure a persistent use