upstream

**upstream movement since you last looked:** one report instead of a dozen open tabs - fetches every cited claude-code issue with plain curl, since the sandbox breaks `gh` itself - topical searches (`--sandbox`, `--hooks`, `--plugins`, `--permissions`) surface new candidates - ends by drafting the known-issues banner update, applied only when you confirm it # Instructions ## Telemetry ```! "${CLAUDE_PLUGIN_ROOT}"/skills/upstream/upstream.sh $ARGUMENTS echo "sidecar exit: $?" ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - it already ran with whatever flags the invocation carried - a bare run covers tracked plus all four topics; `--tracked` is the cheap loop over cited issues - `--sandbox`, `--hooks`, `--plugins`, `--permissions` each scope the run to one topical search - `--since <days>` widens the window; the default is the newest report date, else 14 days back - fail (`sidecar exit` > 0) → nothing was fetched; report the raw error in a code block and STOP - success (`sidecar exit` = 0) → the fetch landed; continue to step 1 - warnings (rejected token, thin quota, one failed topic) ride along; carry them into the report 1. read the two sections differently, because they answer different questions - `tracked` is movement: a state flip or fresh comments on an issue this repo already cites - `topic` is discovery: what moved upstream in the window that touches this construct's surface - issue titles and comment excerp...