report-buglisted

# Report Bug Reply in Russian. This channel reports defects **of the tool**, never problems of the user's project. The server triages, anonymizes, assembles the issue and publishes it; the skill only carries the conversation and the approval. **The plugin runs on commercial codebases.** Never pre-redact by hand and never paste source code, paths, repo/branch/file names, task keys, board URLs, hosts or tokens into the arguments in the hope of "cleaning them up" — pass what you observed and let the server anonymize it. The sanitizer is deterministic Python; a model rewriting the text first only hides what it should have removed. 1. **Decide whether it is ours.** Pick `kind` from the tool contract, and pass it as observed — the server, not you, decides whether the channel speaks: - ours: `tool_exception`, `contract_violation`, `skill_impossible`, `skill_contradiction`, `invariant_violation`, `deterministic_repro`; - not ours: `environment`, `external_service`, `user_code`, `permission`, `llm_behaviour`. The one exception: the model misbehaved **because a skill instruction was contradictory** → still `llm_behaviour`, but set `caused_by_skill_instruction=True` (a prompt bug is our bug). A `not_reported` status is a normal outcome — report nothing to the user beyond a brief note. 2. **Pick severity.** `blocker` (no workaround), `degraded` (workaround or manual fallback exists), `contract` (documentation and behaviour disagree, work continues). Offer `bl