gh-accountlisted

# gh-account — Cross-Account GitHub Token Resolver **Purpose:** Every operation in this suite that touches GitHub Projects or issues must begin here. This skill ensures the right PAT is loaded into `GH_TOKEN` for the duration of that single operation — without ever calling `gh auth switch`, which would corrupt the user's global `gh` CLI state. --- ## Default account: CSalcedoDataBI — always The default identity for all operations in this suite is **CSalcedoDataBI**, even when you are working inside a PAL-Devs-owned repository. The account only changes when the user explicitly says "use PAL-Devs" or you encounter a 403 on a PAL-owned board (see below). --- ## FIRST: are you inside a brake-armed run? (#550) Before anything else, check for `.agentic-board/brake-armed.json` in the current directory **or any directory above it**. If it is there, this is an autonomous run that has been braked, and the identity rule changes: ```powershell $t = [System.Environment]::GetEnvironmentVariable('GITHUB_TOKEN_AGENT', 'User') if (-not $t) { throw 'Run frenado y GITHUB_TOKEN_AGENT no existe. NO uses el token del dueno.' } $env:GH_TOKEN = $t ``` **Do NOT fall back to `GITHUB_TOKEN_PERSONAL` if the agent token is missing. Stop and say so.** Why this matters more than it looks: `main` requires a pull request, but the rule **exempts the repository admin role** — and the owner's PAT authenticates *as the owner*, so GitHub lets it push to `main` directly. Weaker permissions on one of his