reportlisted

# Reporting a suite finding upstream The inbox flow this mechanizes already exists: [`WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md)'s cross-project rule files every suite finding into the machine-local `WSS.BUG-REPORTS.md` and stops, and an adopter with no checkout has "an issue upstream" as their terminal step. This skill is that step made deterministic — and it is the durability move for the one file whose loss is unrecoverable: an inbox entry exists on one machine; an issue exists wherever GitHub does. The upstream repository is **`qupunto/wss`** — hardcoded, like the plugin-cache glob, because the plugin name is load-bearing; a fork files against itself by editing this line. ## The order is: local first, upstream second 1. **Append the entry to the inbox** — `$CLAUDE_CONFIG_DIR/WSS.BUG-REPORTS.md` (`~/.claude/WSS.BUG-REPORTS.md` unless that variable is set), in the format [`WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md#a-file-belonging-to-the-installation-is-never-edited-from-a-project-session) states. **Read that section before writing the entry** — the three template lines, where in the file they go, and which SHA the `Found:` line carries are all there, and this skill keeps no second copy of them on purpose. Filing locally is complete in itself. If everything after this step fails, the report exists and the doctor surfaces it; say the upstream half is owed rather than retrying into a wall. 2. **Compose the issue, redacte