feedback

# Superset Feedback Turn the user's feedback about Superset into a short, scannable report and submit it where they choose. Treat whatever they wrote after the command as the seed. The reader is a Superset engineer triaging dozens of reports. They should get the point from the title, the full picture from the summary bullets, and only read further when they need detail. Cut everything that doesn't help them reproduce or decide. ## 0. Is this a follow-up? Every private submission CCs the reporter, so they already have a copy in their inbox with a subject starting `[Feedback: ...]`. A reply to that email lands on the same thread; a new submission opens a new one and the team has to reconcile them by hand. If the seed reads like a continuation ("follow-up", "again", "still happening", "update on", "retraction", "root cause", "I already sent", "third time"), or the user filed something on this topic earlier in the session, ask whether they already sent a report about it. If they did, tell them to reply to that email with the new information and stop here. Only file fresh when they confirm it's a different issue. Never title a report "Follow-up:", "ROOT CAUSE:", or "RETRACTION"; those belong in a reply. ## 1. Gather context (best effort, never block) Run in parallel; skip anything that fails: - `superset --version` and `uname -sm` for the environment line - `superset auth whoami` for the signed-in user/org (private submissions only) - `superset status --json` for the host...