Build a self-contained web app for running engineering bug bashes — a space where a team can spin up a testing blitz for a feature they're shipping, invite testers, and track every reported issue to resolution in one place (replacing an ad-hoc mix of Slack, Notion, and Google Docs). Serve it from an HTTP route as a single-page app gated to signed-in members of your space, and identify the current user from the authenticated request identity so the app can enforce who's allowed to do what. All reads and writes go through a small set of JSON API endpoints backed by persistent storage (a database plus a place to keep uploaded images). The app should support: A searchable dashboard of all bug bashes, filterable by title and by team, each showing a status of In progress or Done (a bug bash is Done once it has at least one issue and every issue is resolved). Creating a bug bash with a title, an engineering team, project documentation links, a set of test cases (each with a title and a longer description of steps), a link to the feature flag, and a list of invited testers. Let the owner edit all of this later and delete the bug bash (which removes its issues and attachments). A team list the owner picks from — source it from your HR system (I used BambooHR) or just use a fixed list you maintain. Filing issues — any tester can add an issue with a description, a severity (low/medium/high), and an optional screenshot; issues start in a To-do state on a board with To-do / In progress / Done columns. Working issues — the owner can assign an issue to a tester and attach a pull-request link; the owner or the assigned tester can move issues between states (support drag-and-drop between columns). Notifications — when someone is invited, message them (I used a Slack DM, falling back to a post in the bug bash's channel — swap in your team's chat tool); when an issue is marked Done, notify its author that it's resolved. Enforce permissions on the server: only members can file issues, only the owner can assign/edit/delete and add PR links, and only the owner or assignee can change an issue's status. Keep the whole thing production-grade and visually distinctive, and don't publish live until it's been reviewed. Tools used: 3B (webpage + API routes, named volume, SQLite/bun:sqlite), BambooHR API, Slack API (users.lookupByEmail, chat.postMessage)