Tell us what's working.

1. 1

   Press Give Feedback

   Hit the button in the top bar — or open /feedback for the standalone page. Page submits carry source: "page"; dialog submits carry the dialog source instead.
2. 2

   Pick who is reporting

   Choose Tracked (signed in, so admins can follow up), Anonymous (no name attached), or Guest (no account needed, optional name + email for follow-up). All three land in the same human queue.
3. 3

   Pick a rating

   Choose one: None, Good, Okay, or Bad (defaults to None). The rating is required - it is how admins sort the queue.
4. 4

   Write one critique

   A sentence is enough. Say what happened and what you expected instead.
5. 5

   Attach a screenshot (optional)

   Paste, drop, capture the current tab, then circle the problem with the micro-editor - see §4.
6. 6

   Submit

   Human feedback posts immediately and answers with a Report ID. Bot feedback goes through the same queue with its bot label attached.

• 👍 Positive critique protects. "Good" with a named detail stops a future redesign from deleting what you love.
• 👎 Negative critique repairs. "Bad" with expected-vs-actual gives the fixer a test case in one line.
• 🎯 One route, one point. The current route attaches automatically - don't spend words on where, spend them on what.

1. 1

   Paste or drop

   Copy any screenshot and paste it straight into the form, or drag a JPG, PNG, or WebP onto the dropzone. Anything else is refused with "Invalid screenshot (JPEG/PNG/WebP only)."
2. 2

   Capture this tab

   One click snapshots the page you are already on — no uploads, no file picker, no leaving the form. An empty capture is refused with "Invalid screenshot (empty)."
3. 3

   Annotate

   Draw arrows, circles, highlight boxes, or blur redactions over private text — each mark takes a short comment. The shapes travel with the screenshot as one feedback item.
4. 4

   Submit together

   The annotated shot posts with your rating and critique as one feedback item, plus source: "page" on page submits.

const res = await fetch("https://4weird.com/api/feedback", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "x-bot-key": process.env.FOURWEIRD_BOT_KEY
  },
  body: JSON.stringify({
    reporterType: "bot",
    rating: "bad",
    critique: "negative",
    text: "Lobby greeter repeats itself after rejoin; expected one greeting.",
    labels: ["lobby", "rejoin"],
    botExtras: { botId: "my-bot", runId: "r_abc123" }
  })
});
const { success, id } = await res.json(); // success panel shows 'Report ID: <id>'

1. 1

   Open unaddressed

   The admin view at /feedback/admin lists every item nobody has addressed yet, with rating, route, screenshot, and source badge (login + admin role required).
2. 2

   Filter the pile

   Slice by Good / Okay / Bad, by route, by source:page, by visibility (tracked / anonymous / guest), or humans-only / bots-only to batch related reports.
3. 3

   Address it

   Reply, link the fix, or leave a wont-fix note. Addressed items leave the queue and stay searchable.
4. 4

   Watch the trend

   Bad clusters on one route after a deploy is the ship-block signal - Okay drift is the polish backlog.

1. 1

   Apply the migrations in order

   Seven migrations build the feedback store layer by layer: 20261120000000 base (tables), 20261212000001 admin/events, 20261213000000 annotations/AI, 20261215000000 AI contract, 20261216000000 converge, 20261217000000 neutral, 20261218000000 repair. Skip one and the API degrades instead of writing.
2. 2

   Create the feedback-screenshots bucket

   Screenshot uploads need the feedback-screenshots storage bucket. No bucket means annotated shots fail while text-only feedback still posts.
3. 3

   Set the server key

   The API needs SUPABASE_SERVICE_ROLE_KEY as a server-only env var. It never ships to the browser — missing key means the server cannot write, and every submit answers 503.
4. 4

   Read the 503 per cause

   “feedback store not set up.” is one message with four causes: missing table (base migration not applied), missing column (a later migration skipped — extended fields stash instead), missing bucket (screenshots fail, text posts), missing key (nothing writes). Match the cause before re-running the checklist.
5. 5

   Trust graceful degradation

   When an extended column is absent the API stashes the extended fields with the report instead of rejecting it — nothing is lost, and the repair migration backfills the columns on next deploy.