Grooming pass (AI)

Description rewritten with investigation findings (see task description above). Original preserved here verbatim:

When the user uh uses the tool, sometimes they encounter an error and it shows like uh some information about the error text and then a refresh button. When this message is shown, I would like there to be a button enabling the user to report this error and this would create a text ex describing this the the situation the user is in um like the point in time, the version of the tool. Um the last action or something or like what the user was doing at that point the error message of course Maybe a comment from the user. And when the user clicks OK, it opens a fabricated task. Um, I think that's the same thing. Or maybe no, because maybe the user doesn't have a fabricator account, so it can either um post it on Fabricator or post it to my user chat My talk page. Um so basically it creates an error log, an error description, uh and room for the user to say a bit more what happened, when happened, or something if they want to it's uh uh up to them and then a publish to fabricator or a publish to uh my talk page And hopefully both can be just a button. If you click it, it goes to that page but everything pre-filled

Investigation notes

Existing error surfaces with "refresh" button (src/main.jsx):

• boot-error block in <Bootstrap> (line 209-218): "Couldn't start" + error message + Reload button. Triggered when profile fetch or other bootstrap throws.
• boot-error block in <ErrorBoundary> (line 273-281): "Something broke" + error.message + Reload button. Catches uncaught render errors anywhere in the tree.

Both share the same .boot-error CSS class (src/app.css:4091). The "Report this error" button should appear on both since they're the only "hard" error UIs the user sees (everything else is inline chips like chip--err for upload failures, which already have row-level context the user can act on).

Pre-fill URL verification (both return HTTP 200):

• Phabricator: https://phabricator.wikimedia.org/maniphest/task/edit/form/default/?projects=tool-upload-workbench&title=...&description=... — already used in the info modal as PHAB_NEW_TASK, but without title/description params yet.
• MediaWiki talk page: https://commons.wikimedia.org/w/index.php?title=User_talk:Daanvr&action=edit&section=new&preloadtitle=... accepts preloadtitle for the section heading. The preload parameter loads a wiki template page, not a literal string — so we can't reliably pre-fill the body via URL. Decision: ship the talk-page route with a clearly-labeled "Copy report to clipboard" button next to it, so the user pastes the body manually after the edit form loads.

Tool version source: __APP_VERSION__ Vite compile-time define (already wired up via vite.config.js:11, used in info-modal.jsx).

Last action: there is no existing action-history ring buffer. Adding one would require instrumenting many click handlers across app.jsx/table.jsx — high blast radius, low value for v1 of this feature. Decision: ship without "last action" tracking in v1. The error message + stack trace + URL is already a strong locator.

PII / privacy: Don't auto-include the username. The Phabricator task is signed by whoever submits it, and the talk-page edit is signed by the user's signature.

Scope

Add a "Report this error" button to the two boot-error panels (Bootstrap's "Couldn't start" + ErrorBoundary's "Something broke"). Clicking opens a new modal (src/ui/error-report-modal.jsx) showing:

• Read-only context: timestamp (ISO 8601), tool version (__APP_VERSION__ · __DEPLOY_TARGET__), error message, stack trace (collapsed by default), user-agent, current URL.
• Free-text comment field: "What were you doing when this happened? (optional)"
• Two submit buttons:
  1. Open Phabricator task — window.open to maniphest/task/edit/form/default/?projects=tool-upload-workbench&title=...&description=... with the body URL-encoded.
  2. Post to User talk:Daanvr — window.open to commons.wikimedia.org/w/index.php?title=User_talk:Daanvr&action=edit&section=new&preloadtitle=..., plus a "Copy report to clipboard" button.
• Cancel to dismiss without submitting.

No new OAuth scopes; window.open is user-action only.

Acceptance criteria

• When either of the two error panels (Couldn't start / Something broke) renders, a third button "Report this error" appears alongside Reload.
• Clicking it opens a modal with all the captured context visible. User can edit the body textarea (e.g. redact filenames) before submitting.
• "Open Phabricator task" opens a new tab to the Maniphest create-task form with title and description pre-filled.
• "Post to User talk:Daanvr" opens a new tab to the talk-page edit form with section title pre-filled, and offers a "Copy report" button next to it so the user can paste the body.
• No new OAuth scopes are required.
• npm run build passes (including the undefined-identifier scanner).
• CHANGELOG.md has an Unreleased entry under Added.

Out of scope

• "Last action" ring buffer / breadcrumb tracking (future task if maintainer wants more context capture).
• Surfacing this button on inline error chips (upload-error, save-error). Those are row-level and the user has direct repair options already.

MR: https://gitlab.wikimedia.org/daanvr/upload-workbench/-/merge_requests/47
Preview: https://upload-workbench.toolforge.org/mr-47/

MR: https://gitlab.wikimedia.org/daanvr/upload-workbench/-/merge_requests/47
Preview: https://upload-workbench.toolforge.org/mr-47/