/report-feedback

name: report-feedback
description: THE way a bug, feature request or feedback about Sutando, s.space or the desktop app reaches the AG2 team; the only path to the tracker (Slack #product-feedback, a GitHub issue, the master DB). Posting it in chat, a room or a DM, or asking another agent to log it, is not reporting it. Use when the owner says "report this bug", "report this issue", "report an issue", "report a bug", "file a bug", "log this bug", "submit feedback", "feature request", "tell the team this is broken", "something's broken, file it", in a DM, a room or by voice (not "report this on the PR" or "to <someone>": that is a comment or a message); or automatically (--auto) when the agent itself hits a Sutando/s.space bug. Files through the cloud /api/feedback API with diagnostic context and replies with the reference id. A non-owner asking is told to file it through their own report-feedback skill or the app's Report a bug button.

Report Feedback

When the user asks to **report a bug / issue / feature request / feedback about Sutando, s.space or the desktop app** — e.g. "report this bug", "report this issue", "report an issue", "file a bug", "log this bug", "submit feedback", "I have a feature request", "tell the team this is broken" — use this skill to file it, whether the ask comes in a DM, in a room or by voice. "Report this on the PR" or "report this to <someone>" asks for a PR comment or a message, not a report.

**This is the only path that reaches the AG2 team.** The report goes skill → `/api/feedback` → Slack #product-feedback, a GitHub issue on sonichi/sutando and the master feedback DB. A message in a room or a DM, a hand-opened GitHub issue, or asking another agent (another Sutando included) to "add a row" or pass it on never gets there; do not do those instead of filing. After filing, reply with the reference id the script prints.

It posts to the cloud `/api/feedback` route (the same one the desktop "Report an issue" form uses, which mirrors into GitHub issues) and auto-attaches diagnostic context (platform + a tail of recent workspace logs), so you don't need to gather logs yourself.

This is the **single reporting path for all surfaces** — chat, Discord, Telegram, and voice (which reaches it by delegating the task to the core agent). There is intentionally no separate voice tool, to avoid duplicating the same capability.

Usage

python3 skills/report-feedback/report-feedback.py \
  --title "<short one-line summary>" \
  [--body "<what happened, steps to reproduce, what was expected>"] \
  [--kind bug|feature|other] \
  [--severity low|medium|high|critical] \
  [--no-logs] [--auto]

• Ask the user for a short **title** and a **description** if they're not already clear from the conversation. Infer `kind` (default `bug`) and `severity` (default `medium`) from context.
• **Announce the log attachment before sending, then honor an opt-out.** Recent diagnostic logs are attached by default. Since there's no visible checkbox on voice/chat (unlike the desktop form), *say so first* — e.g. "I'll attach recent diagnostic logs to help debug, unless you'd rather I didn't." If the user declines, pass `--no-logs`. This makes it an informed opt-out rather than a silent default (especially important on voice, where the user can't see what's being sent). Log excerpts are redaction-scrubbed (Bearer tokens, `token=`/`api_key=`/`secret=` values, common key formats, and the home-dir username are masked) as a backstop, but announcing is still required.

Ask first (`--ask`, or `askFirst` in the owner's prefs)

The owner's approval step for automatic reports. Instead of filing, the report is parked as a draft under `<workspace>/state/feedback-drafts/<id>.json` and registered in the engine's HITL store (`src/hitl`) as a `HumanRequirement`: the gateway bridge projects it as the owner's card — **File this bug report · File without logs · Skip** — into its proactive room, and applies the click with the same stale-revision guard every other card gets. Nothing is posted by this script, so it needs no gateway env.

# ask (also what --auto does when feedback-prefs.json has "askFirst": true):
python3 skills/report-feedback/report-feedback.py --auto --title "..." --body "..."
# after the owner answers (the click is durable in the HITL store): run the clicked choices
python3 skills/report-feedback/report-feedback.py --apply
python3 skills/report-feedback/report-feedback.py --drafts        # pending drafts, oldest first
python3 skills/report-feedback/report-feedback.py --decide <draft-id> file|file_no_logs|skip   # by hand

• The click is applied **automatically, in the turn it causes**: the requirement is created with

`turn_on_action`, so the bridge records the click and then lets the same relay task through to the core (and re-forwards it if the relay redelivers the same click before that task was written, so a death in between cannot lose the turn); that task carries the header `hitl_click: true` and the card label as its body — it is a click already recorded, not an instruction: answer `[no-send]`, do not file by hand, and let the turn end — and the skill's `Stop` hook (`manifest.json` → `hooks/apply-clicks.py`, registered by `bash src/install-claude-hooks.sh` like every skill hook) runs `apply_clicks()` as that turn ends. `--apply` is the same routine by hand. It also registers any parked draft whose card was never created (a store write that failed at ask time exits 3 and keeps the draft).

• Filing is exactly-once by markers: before the post the draft becomes `<id>.posting`; a 2xx renames it

to `<id>.filed`, the card is resolved, the receipt removed; a 4xx (the server refused, nothing written) renames it back to a draft. A 5xx proves nothing (the write may have committed), so like no answer at all (a transport error, a death mid-request) it leaves `<id>.posting`, and `--apply` **holds** it — never re-posted on a guess. A held draft i