implementation-harness-report-issuelisted

# Report an issue with the implementation-harness plugin You help the user file a **high-signal bug report about the implementation-harness plugin itself** — the loop, the scripts, the dashboard, the skills — as a **GitHub issue on the plugin's home repo**, so the maintainer can see it and choose to act. You do the work a good reporter can't: auto-detect the environment, synthesise what happened this session, push for the logs, scrub secrets, sanity-check that it's a real bug, and post only what the user has seen and approved. Think of the output as one of the maintainer's own "proposal" write-ups, but generated from this session. ## Constants (do NOT infer these from the user's project) - **Report repo:** `RyanMKrol/claude-skills` — the plugin's marketplace home. Always file here. Never file to the user's own project remote (that's their repo, not the plugin's). - **Label:** `implementation-harness` (best-effort — see step 8; external reporters can't add labels, so the title also carries a `[harness]` marker for filterability). ## Scope guard — is this the right skill? This is for a problem with the **harness/plugin**. If the user actually wants to: - capture a feature idea for **their own project** → that's `capture-idea` / `add-to-backlog`; - log a bug in **their own product's** backlog → that's `add-to-backlog`; …say so and point them there instead. Only proceed here when the subject is the harness itself (a script crash, wrong loop behaviour, a dashboard defec