{"id":"assignee","title":"Task assignees with Assigned-to-me filter","part":"classic","group":"multi","kind":"feature","actions":["read","keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Tasks need an owner. Add an Assignee to tasks: it is picked from the team's members in the Edit dialog (an \"Assignee\" dropdown, which can also be left unassigned), and the task list shows the assignee's initials on each assigned task, with their full name on hover.","Bug from Priya: when someone is removed from the team in Settings, their tasks still show their initials. A task whose assignee is no longer a member should show as unassigned everywhere.","One more: add an \"Assigned to me\" filter next to All / Active / Done, with a count like the others."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A three-round feature. Assigns members through the Edit dialog's Assignee control and requires the row to show the member's initials with the full name on hover (title/aria-label, hover text or CSS tooltip) and the assignee saved in the mock API. The 'Assigned to me' filter must list exactly the current user's tasks with a count of (2); choosing Unassigned must clear the assignee in the API and on the row. After removing a member in Settings, their initials must disappear from the list (also after reload) and the Edit dialog must not show them as assignee.","reference":"references/assignee","audit_variants":{"should_fail":1,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"due-dates","title":"Due dates with Overdue and Due today","part":"classic","group":"multi","kind":"feature","actions":["read","look"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Add an optional due date to tasks, set in the Edit dialog (a \"Due date\" field). In the task list show it on each task that has one (e.g. \"Due Nov 12\"), and show tasks that are past their due date in red with the word \"Overdue\".","Follow-up from the team: a task due today should say \"Due today\" rather than Overdue — it isn't late until tomorrow. And the Board cards should show the due date, Due today and Overdue the same way the list does."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Sets due dates of yesterday, today and five days ahead in the Edit dialog. In both the task list and Board cards, yesterday's task must say 'Overdue' in a red colour (computed colour sampled as pixels), today's must say 'Due today' and not Overdue, the future one must show its date, and a task without a date must show none. A second browser context in the America/Los_Angeles time zone must show the same calendar day, and clearing the date in the Edit dialog must remove it after reload.","reference":"references/due-dates","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"bulk-actions","title":"Bulk select, mark done, delete with Undo","part":"classic","group":"multi","kind":"feature","actions":["read","dialog"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["People want to act on several tasks at once. Add a select checkbox to each row in the task list (separate from the completion checkbox), show how many tasks are selected (\"2 selected\"), and add a \"Mark selected done\" button.","Next: add \"Delete selected\" next to it, asking for confirmation first. And switching between All / Active / Done should clear the selection, so nobody acts on tasks they can't see.","Last one: after a bulk action, show a message such as \"2 tasks deleted\" or \"2 tasks marked done\" with an Undo button that reverses it."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A three-round feature. Selecting two rows (one already done) must show '2 selected'; Mark selected done must save both and show a message, and Undo must restore each task's previous state. Switching filters must clear the selection; cancelling the Delete selected confirmation (native or in-app) must delete nothing, confirming must remove both rows with a '2 tasks deleted' message and Undo must bring them back persistently after reload. A bulk delete without Undo must reach the mock API (hard or soft delete) within the undo window and stay gone after reload.","reference":"references/bulk-actions","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"comments","title":"Task comments with counts","part":"classic","group":"cross","kind":"feature","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Add comments to the task detail page: list the task's comments (author's name, date and text) and a \"Comment\" box with a \"Post\" button to add one; the API already has comments (see API.md). In the task list and on Board cards, show how many comments a task has (e.g. \"2 comments\"). The counts must be right straight after someone posts a comment and goes back to the list or the board."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"On a task's detail page, existing comments must be listed with author name, text and a date (text date or <time>). Posting a comment must show it, and without a reload the task list row must show '3 comments' (any phrasing that puts the number next to 'comment', or an aria-label/title), another row 1 comment, and the Board card 3 comments.","reference":"references/comments","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"shared-modal","title":"One shared accessible Modal component","part":"classic","group":"regression","kind":"refactor","actions":["keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["We have three different dialog implementations (the Edit task dialog, the Remove member confirmation in Settings, and the Invite dialog). Replace them with one shared Modal component. Every dialog must close on Escape and on a click outside it, keep keyboard focus inside it while it is open, and give focus back to the button that opened it when it closes. Nothing else about the dialogs should change (deleting a task keeps using the browser's own confirmation)."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"For the Edit task dialog, the Invite dialog and the Remove member confirmation, Escape and a click outside must each close the dialog and return focus to the opening button; on open, focus must be inside the dialog and 8 Tab and 8 Shift+Tab presses must not leave it (a native modal <dialog> counts). The dialogs must still work: editing saves the title, invite shows the API's validation error and then sends a valid invite, Remove deletes the member, and task deletion still uses the browser's native confirm and deletes the task.","reference":"references/shared-modal","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"task-status","title":"Replace done flag with three-state status","part":"classic","group":"regression","kind":"refactor","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Tasks need an \"In progress\" state. Replace the done flag with a status — To do, In progress or Done — stored as a `status` field (\"todo\" | \"in_progress\" | \"done\"); existing tasks that have done: true are Done and the rest are To do. The Board gets an In progress column between To do and Done, and the detail page gets a \"Status\" dropdown instead of the Completed checkbox. In the task list the checkbox still means Done (unticking a Done task makes it To do), and the All / Active / Done filters keep working: Active is everything that isn't Done."],"agent_scenario":"{}","judge_scenario":"{\"fail\":[{\"route\":\"PATCH /api/tasks/:id\",\"status\":500,\"when\":{\"id\":5}}]}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"With saving one specific task failing with HTTP 500, requires filter counts All (10) / Active (7) / Done (3) from existing data. Setting In progress on a task's detail page must save status 'in_progress' and, after in-app navigation without a reload, the Board must have To do / In progress / Done columns with the task in In progress, while the list shows it unchecked and under Active. Ticking and unticking list checkboxes must save 'done' and 'todo', a failed save must roll the checkbox back, and a newly added task must be saved as 'todo' and appear in the Board's To do column.","reference":"references/task-status","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"double-submit","title":"Prevent duplicate task creation","part":"classic","group":"async","kind":"bug fix","actions":["wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Support ticket: \"Sometimes when I add a task I get it twice. I think it happens when I click Add task (or press Enter) again because nothing seemed to happen — the server is slow some days.\" Please fix it so a task can't be created twice that way."],"agent_scenario":"{\"latency\":{\"default\":120,\"POST /api/tasks\":900}}","judge_scenario":"{\"latency\":{\"default\":80,\"POST /api/tasks\":900}}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: removes the in-flight guard and the disabled state from the add-task form's submit button.","seed_edits":2,"judge":"With task creation delayed 900ms in the mock API, a fast double click on Add task, pressing Enter twice, and a second click 0.5s later while the request is still in flight must each create exactly one task in the API. The title field must be cleared after adding and the list must show the task once.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"failed-toggle","title":"Failed done-toggle must roll back","part":"classic","group":"async","kind":"bug fix","actions":["wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug: on a flaky connection, marking a task done (in the list or with Mark done on the Board) looks like it worked, but after a refresh the task isn't done. Users can reproduce it with \"Release checklist\" and \"Reply to customer feedback\" today. When saving fails, the app must not pretend it worked: put the task back the way it was and tell the user it didn't save."],"agent_scenario":"{\"fail\":[{\"route\":\"PATCH /api/tasks/:id\",\"status\":503,\"when\":{\"id\":5}},{\"route\":\"PATCH /api/tasks/:id\",\"status\":503,\"when\":{\"id\":8}}]}","judge_scenario":"{\"fail\":[{\"route\":\"PATCH /api/tasks/:id\",\"status\":503,\"when\":{\"id\":5}},{\"route\":\"PATCH /api/tasks/:id\",\"status\":503,\"when\":{\"id\":8}}]}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the optimistic done-toggle no longer reverts or shows an error when the save fails.","seed_edits":1,"judge":"With saves for two specific tasks failing with HTTP 503, ticking one in the task list must leave the checkbox unticked after the failure and show an error message, while a normal tick still saves and shows done. On the Board, Mark done on the other failing task must leave the card in To do and show a new error message; done cards must keep Reopen and cards must not gain the list's checkbox.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"qa-header-shadow","title":"QA pass: header shadow blocks controls","part":"interaction","group":"qa","kind":"QA report","actions":["click-hit"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Do a QA pass on this app as a user would, before we ship it: the task list (adding, completing, editing, deleting, filtering, searching and sorting tasks), a task's detail page, the board, and the settings page (members and invites). Do NOT change any code. Write what you found to qa-report.md in the project root: one bullet per problem (what you did, what happened, what should happen), or \"No problems found\"."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: adds a 110px transparent gradient ::after 'shadow' under the sticky header without pointer-events: none, covering the add-task row and the filter/search/sort toolbar for mouse clicks (keyboard still works).","seed_edits":1,"judge":"The agent is asked to QA the app without changing code and write qa-report.md. The report is split into entries (top-level bullets or headings with their continuation lines) and matched by rule-based regular expressions, no LLM: some non-negated sentence must say a control can't be clicked/doesn't respond to the mouse while the entry names the add-task row, filters, search, sort or toolbar, or say the header/shadow/overlay covers or intercepts them. Sentences saying things work fine and 'No problems found' do not count.","reference":"references/qa-header-shadow","audit_variants":{"should_fail":3,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"qa-members-error","title":"QA pass: member list silently empty","part":"classic","group":"qa","kind":"QA report","actions":["wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Do a QA pass on this app as a user would, before we ship it: the task list (adding, completing, editing, deleting, filtering, searching and sorting tasks), a task's detail page, the board, and the settings page (members and invites). Do NOT change any code. Write what you found to qa-report.md in the project root: one bullet per problem (what you did, what happened, what should happen), or \"No problems found\"."],"agent_scenario":"{\"fail\":[{\"route\":\"GET /api/members\",\"status\":500}]}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the Settings page drops its error message for the member list, so when the members API fails it shows 'No members yet.' (the agent's backend returns HTTP 500 for the member list).","seed_edits":1,"judge":"The agent writes qa-report.md without changing code; the report is split into entries and matched with rule-based regular expressions, no LLM. A non-negated sentence must say 'No members yet', or say the member list is empty/blank/fails to load/returns 500/hides the error while referring to the members list; mentions of inviting or removing members and the header's 'N members' count are stripped before matching.","reference":"references/qa-members-error","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"url-state","title":"Task list view state in URL","part":"classic","group":"multi","kind":"feature","actions":["history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Make the task list's view shareable: the selected filter (All / Active / Done), the search text and the sort order should be kept in the page URL, so reloading the page or opening a copied link shows the same view.","The browser's Back button should undo the last change to the filter or the sort instead of leaving the page (typing in the search box shouldn't add a history entry per keystroke).","Last one: the Board should honour the search too — opening /board?q=rel shows only the cards whose title matches (case-insensitive, like the list's search), with a \"Clear search\" link that shows everything again."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A three-round feature. With Active, Priority sort and search 're' set, the URL must change and a reload must restore the same filter, search, sort and rows. Back must undo the last sort change and then the filter change one step at a time, and typing 'rel' letter by letter must not create one history entry per keystroke. /board?q=LEASE must show only the two cards matching case-insensitively mid-word, /board?q=rel exactly three, and a Clear search link must show all 10 cards.","reference":"references/url-state","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"inline-rename","title":"Inline rename in list and Board","part":"classic","group":"multi","kind":"feature","actions":["keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Let people rename a task right in the task list: a \"Rename\" button on each row turns the title into a text field in place (focused, with the current title); Enter saves, Escape cancels.","Two problems with renaming: an empty title must not be saved — keep the field open and say why — and leading or trailing spaces should be trimmed off.","Please add the same Rename button and behaviour to the cards on the Board."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A three-round feature tested on both list rows and Board cards. Rename must open a focused field holding the current title; Enter saves the new title to the mock API and shows it, Escape cancels. An all-spaces title must not be saved, the field must stay open and some reason must appear (new on-page text, a native dialog or a browser validation message); a padded title must be saved trimmed.","reference":"references/inline-rename","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"invite-admin","title":"Revoke invites, block duplicates, nav count","part":"classic","group":"multi","kind":"feature","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["In Settings, let people revoke a pending invite: a \"Revoke\" button on each pending invite, asking for confirmation first. The API supports DELETE /api/invites/:id (see API.md).","Inviting an email address that already belongs to a member, or that already has a pending invite, should be refused with a clear message. Ignore upper/lower case when comparing.","Show the number of pending invites on the Settings link in the top navigation, e.g. \"Settings (2)\" (just \"Settings\" when there are none), and keep it up to date as invites are sent and revoked."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A three-round feature. The Settings nav link must read just 'Settings' with no pending invites and 'Settings (2)' (or 'Settings 2') after sending two invites, also after reopening the app on another page. Revoke must ask for confirmation first (declining keeps the invite), then delete it in the mock API and update the count to 1. Inviting an existing member's or pending invitee's email in different letter case must show an 'already…' message and create no invite.","reference":"references/invite-admin","audit_variants":{"should_fail":4,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"checklist","title":"Task checklists with progress","part":"classic","group":"cross","kind":"feature","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Add a checklist to tasks. On the task detail page, people add checklist items (a \"New item\" field and an \"Add item\" button), tick them off and remove them; save the checklist on the task through the API. The task list rows and the Board cards show progress for tasks that have a checklist, e.g. \"2/5\"."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Adds three checklist items on a task's detail page, ticks one and removes another, and requires the checklist saved on the task in the mock API. Without a reload (in-app navigation), the list row and Board card must show '1/2' (or '1 of 2') and tasks without a checklist must show no progress; after a full reload the ticked item must still be ticked and the progress still shown.","reference":"references/checklist","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"related-tasks","title":"Two-way related task links","part":"classic","group":"cross","kind":"feature","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["On the task detail page, let people link related tasks: a \"Link a task\" picker lists the other tasks, and linked tasks appear under \"Related tasks\" as links that open that task. Links go both ways — if A is linked to B, B's page lists A too. Each related task has an \"Unlink\" button. Save links through the API."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"On a task's page, the 'Link a task' picker must not list the task itself; linking another task must list it under related tasks as a link that opens it. After clearing localStorage/sessionStorage and reloading (so only the mock API counts), the other task must list the first one; Unlink there must remove the link from both sides.","reference":"references/related-tasks","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"shared-task-card","title":"Shared task card for list and Board","part":"classic","group":"regression","kind":"refactor","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Task list rows and Board cards render the same task data with separate code. Make them share one component, and give Board cards the same Edit and Delete buttons the list rows have (same dialogs). Nothing else should change — in particular the Board keeps its Mark done / Reopen buttons and the list keeps its checkbox."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"List rows must still complete via checkbox, edit and save, keep Delete (with a confirmation that can be declined) and not gain Mark done/Reopen. Board cards must gain working Edit and Delete (Delete must confirm first), keep a working Star button, keep Reopen on done cards and Mark done that moves a card to Done, and must not gain the list's checkbox; all changes are verified in the mock API.","reference":"references/shared-task-card","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"settings-tabs","title":"Split Settings into Members/Invites tabs","part":"classic","group":"regression","kind":"refactor","actions":["history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Split Settings into two tabs with their own URLs: Members (/settings/members) and Invites (/settings/invites); /settings opens the Members tab. The Invite member button stays on the Members tab, and the Invites tab lists the pending invites. Everything that works in Settings today must keep working."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Opening Settings must show the Members tab at /settings/members (or /settings), where removing a member and sending an invite still work but pending invites are not listed. The Invites tab must be at /settings/invites, list the pending invite and not the members; both URLs must work when opened directly, and the main Settings nav link must be marked active (class or aria-current) on a tab.","reference":"references/settings-tabs","audit_variants":{"should_fail":2,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"load-retry","title":"Load error state with Retry","part":"classic","group":"async","kind":"bug fix","actions":["wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["When loading the tasks fails (the API has had short outages this week), the list shows an error but also says \"No tasks here.\", and the only way out is reloading the whole page. Don't say there are no tasks when loading failed, and add a \"Retry\" button that loads them again."],"agent_scenario":"{\"fail\":[{\"route\":\"GET /api/tasks\",\"status\":503,\"times\":6}]}","judge_scenario":"{\"fail\":[{\"route\":\"GET /api/tasks\",\"status\":503}]}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"With the mock API's task list failing with HTTP 503, requires an error message or Retry button and no 'no tasks' text. Clicking Retry while the API still fails must not reload the page and must keep showing the error without claiming there are no tasks; after the failure is lifted, Retry must load all 10 tasks without a page reload and the error must disappear.","reference":"references/load-retry","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"qa-board-count","title":"QA pass: wrong Board column counts","part":"classic","group":"qa","kind":"QA report","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Do a QA pass on this app as a user would, before we ship it: the task list (adding, completing, editing, deleting, filtering, searching and sorting tasks), a task's detail page, the board, and the settings page (members and invites). Do NOT change any code. Write what you found to qa-report.md in the project root: one bullet per problem (what you did, what happened, what should happen), or \"No problems found\"."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: each Board column header shows the total number of tasks instead of the number of cards in that column.","seed_edits":1,"judge":"The agent writes qa-report.md without changing code; the report is split into entries and matched with rule-based regular expressions, no LLM. An entry must mention the Board and a column/header, and a non-negated sentence must either pair the total (10/11) with the actual column card count (7/3/4), or state the header count is the total while the column figure appears in the same entry, or say the count is wrong/mismatched/the overall total/not updated.","reference":"references/qa-board-count","audit_variants":{"should_fail":3,"should_pass":4},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"qa-priority-ignored","title":"QA pass: new task priority ignored","part":"classic","group":"qa","kind":"QA report","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Do a QA pass on this app as a user would, before we ship it: the task list (adding, completing, editing, deleting, filtering, searching and sorting tasks), a task's detail page, the board, and the settings page (members and invites). Do NOT change any code. Write what you found to qa-report.md in the project root: one bullet per problem (what you did, what happened, what should happen), or \"No problems found\"."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: creating a task sends only the title to the mock API, so every new task is saved as medium priority regardless of the choice.","seed_edits":1,"judge":"The agent writes qa-report.md without changing code; the report is split into entries and matched with rule-based regular expressions, no LLM. An entry must mention creating/adding a new task and its priority (priority/high/low), and a non-negated sentence must say the result shows or is saved as medium, or that the chosen priority is ignored, not saved, has no effect or defaults/resets.","reference":"references/qa-priority-ignored","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"undo-delete","title":"Undo after deleting a task","part":"classic","group":"small","kind":"feature","actions":["wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["After deleting a task (from its row or its detail page), show a \"Task deleted\" message with an Undo button for a few seconds; Undo brings the task back."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Deleting a task from its row (accepting the native confirm) must remove it and show 'Task deleted' with Undo; Undo must restore it with the same priority, done state and description, persisting after reload. The same must work from the task's detail page. A delete without Undo must reach the mock API within 20 seconds, the message must disappear on its own, and the task must stay gone after reload.","reference":"references/undo-delete","audit_variants":{"should_fail":2,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"divider-lock","title":"Inbox resize divider locks the page","part":"interaction","group":"interaction","kind":"bug fix","actions":["drag","click-hit"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug report from Priya: \"In the Inbox, after I drag the bar between the task list and the task details to make the list wider, the whole page stops responding. I can't click any task or button, the cursor stays as the resize arrow everywhere, and the only way out is reloading the page.\" Please fix it."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the Inbox split divider listens for mouseup to end a drag while pointerdown calls preventDefault, so the drag never ends and a transparent drag overlay keeps covering the page.","seed_edits":1,"judge":"Opens the Inbox and drags the list/details divider 120px right with real mouse events, requiring the list width to grow by about 120px and stay fixed when the mouse moves after release. It then clicks a task title at its visible centre (hit-tested, no forced clicks) and requires the task to open and the resize cursor to be gone; a second drag 100px left must also resize the list and leave another task clickable.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"card-stretch","title":"Board card buttons open task instead","part":"interaction","group":"interaction","kind":"bug fix","actions":["click-hit"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug report: \"Since Board cards became clickable as a whole, I can't use the buttons on a card any more. Clicking the star, Mark done or the ✕ (delete) on a card just opens the task's page instead.\" Clicking anywhere else on a card should still open the task. Please fix it."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the card title's stretched-link ::after overlay gets z-index 1 and the rule lifting card buttons above it is removed, so Star, Mark done and Delete clicks land on the link.","seed_edits":3,"judge":"On the Board, clicks the star, Mark done and delete buttons on three cards at their visible centres and requires each to stay on the Board and change the task in the mock API (starred, done, deleted). As a control, clicking empty space in a card's footer and clicking a card's title must still open that task's page.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"loading-veil","title":"Inbox unclickable after slow load","part":"interaction","group":"interaction","kind":"bug fix","actions":["wait","click-hit"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug report from Mei (working from a train, slow connection): \"The Inbox loads, the list looks completely normal, but nothing in it reacts to the mouse — clicking a task doesn't open it, the ✓ / ☆ buttons don't show up when I hover a row, and ⋯ does nothing. Same after I switch the Status filter. On the office wifi it's all fine.\" Please fix it, and keep showing the spinner over the list while it's loading."],"agent_scenario":"{\"latency\":{\"GET /api/tasks\":1500}}","judge_scenario":"{\"latency\":{\"GET /api/tasks\":1200}}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the Inbox list's loading veil appears only after 300ms and, once loading ends, just fades to opacity 0 without being removed or made click-through, so it blocks the list on slow connections.","seed_edits":3,"judge":"Runs with the mock API's task-list endpoint delayed 1.2s. Requires a visible loading indicator over the list on first load and after changing the Status filter, and that it disappears; after each load, clicking a task title must open it, hovering a row must show its quick-action buttons, clicking the star must star the task in the mock API, and the row's more-actions button must open its menu.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"sticky-save","title":"Section links hide fields under sticky bar","part":"interaction","group":"interaction","kind":"bug fix","actions":["scroll","click-hit"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug report: \"On the 'Edit all fields' page of a long task (try Relocate staging database), the section links in the bar at the top (Basics / Planning / Repeat / Notes) don't really work. Say I'm at the bottom and click Basics: the page jumps, but the Title field ends up hidden behind that bar, and clicking where it is just hits the bar. Planning does the same on my laptop — its first row of fields is under the bar.\" Please fix it."],"agent_scenario":"{\"fixtures\":[\"long-task\"]}","judge_scenario":"{\"fixtures\":[\"long-task\"]}","judge_viewport":{"width":1200,"height":760},"seed":"Adds Basics / Planning / Repeat / Notes anchor links to the sticky toolbar of the task edit page, with no scroll offset for the sticky header, so jumped-to sections land underneath it.","seed_edits":6,"judge":"At a 1200x760 viewport with a long-task fixture, opens the edit page, scrolls to the bottom with the mouse wheel and checks the toolbar is still sticky. Clicking Basics, Planning and Repeat must leave each section heading and its first fields (Title, Status, Estimate, Repeats) uncovered at their visible centres; it then types into Title and Estimate, clicks Save at the bottom, and requires the saved title and estimate in the mock API.","reference":"references/sticky-save","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"hover-ghost","title":"Inbox task names not clickable","part":"interaction","group":"interaction","kind":"bug fix","actions":["hover","click-hit"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug report: \"In the Inbox I can't open a task by clicking its name any more — nothing happens, the row doesn't even highlight. The ✓ / ☆ buttons that show up when I hover a row work fine, and Tab + Enter on a task opens it.\" Please fix it."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the row hover-actions container is stretched across the whole row and hidden only with opacity 0 (still receiving clicks), so it covers task titles.","seed_edits":1,"judge":"Opens the Inbox and requires the quick-action buttons to be invisible on non-hovered rows. Clicking two task titles at their visible centres must open them; as a control, hovering a row must reveal its complete/star buttons, and clicking them must mark the task done or starred in the mock API without opening the task.","reference":"the app without the seed patch","audit_variants":{"should_fail":5,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"menu-clip","title":"Row menu clipped at list bottom","part":"interaction","group":"interaction","kind":"bug fix","actions":["click-hit","scroll"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug report: \"In the Inbox, the ⋯ menu on the last tasks in the list is cut off at the bottom of the list. I can see the top of it, but Move to Done and Delete are hidden, and when I scroll the list to get to them the menu closes.\" Please fix it."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":760},"seed":"Plants the bug: the Inbox row's more-actions menu is no longer portalled to the body with fixed positioning but absolutely positioned inside the scrolling list, so menus on the last rows are clipped.","seed_edits":5,"judge":"At a 1200x760 viewport, scrolls the Inbox list to the bottom with the mouse wheel, opens the last task's more-actions menu and clicks Move to Done and then Delete at their visible centres, requiring both changes in the mock API. As a control, the first task's menu must open next to its button and its Move to Done must work.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"narrow-nav","title":"Mobile navigation drawer behind Menu button","part":"extended","group":"layout","kind":"feature","actions":["resize","look"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["On my phone (about 390px wide) the app is a mess: the navigation sidebar keeps its full width on the left, the actual page gets squeezed into what's left, and the whole page scrolls sideways. On narrow screens, hide the navigation behind a Menu button in the header: tapping it opens the navigation over the page, picking a page takes me there and closes it. On a normal desktop window the sidebar should stay exactly as it is now."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":390,"height":844},"seed":"Removes the narrow-screen navigation drawer: the sidebar stays a fixed left column at every width and the header has no Menu button.","seed_edits":9,"judge":"At a 390x844 viewport, requires no horizontal page scroll on the Tasks, Board, Inbox and Settings pages, the task list to be at least 330px wide, and the navigation links hidden until a Menu button is pressed. After opening the menu, Tasks, Inbox, Board and Settings links must be fully visible and clickable; picking Board must navigate there and close the menu so the To do column is visible. At 1200px wide the sidebar must still show the links on the left without a menu and the Menu button must not appear.","reference":"the app without the seed patch","audit_variants":{"should_fail":4,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"dark-mode","title":"Dark mode follows system, persists, Inbox dark","part":"extended","group":"layout","kind":"feature","actions":["look","history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Two things about the Dark mode button in the header. 1) My laptop is set to dark mode but the app always opens light. Until I pick something with the button, the app should follow the system's light/dark setting. 2) Once I do pick light or dark, it should remember that: right now it goes back to light every time I reload or come back later.","Also, in dark mode the Inbox is still a white box with pale text on it — the task list and the open task are almost unreadable. Make the Inbox dark like the rest of the app, with readable text."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Reverts the theme to a session-only toggle: always opens light, ignores the system setting, does not save the choice, has no pre-paint theme script, and the Inbox is left out of the dark theme styles.","seed_edits":8,"judge":"Opens with the browser's colour scheme set to dark and requires the app to start dark (and a separate light-scheme context to start light), measuring the header's actual text and background luminance. Picking light via the page's theme control must survive a reload and a new tab; with the system switched to light, picking dark must persist across a visit. In dark mode on an open Inbox task, headings, list titles, description, comments and the Attachments heading must sit on a dark background with at least 4.5:1 contrast, and secondary text (priority badges, counts, labels, comment author/time, attachment size) at least 3:1.","reference":"the app without the seed patch","audit_variants":{"should_fail":4,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"scroll-tail","title":"Comment thread cuts off newest comment","part":"extended","group":"layout","kind":"bug fix","actions":["scroll"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["The comments in the Inbox: on a long thread (open \"Relocate staging database\") I can't get to the newest comment. The comment list scrolls, but it stops too early — the last comment is cut in half at the bottom of the box no matter how far I scroll, and when I post a new comment it ends up hidden down there too."],"agent_scenario":"{\"fixtures\":[\"long-thread\"]}","judge_scenario":"{\"fixtures\":[\"long-thread\"]}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: wraps the Inbox comment thread in a fixed 320px overflow-hidden box that also contains the heading, while the scrolling list is 100% tall, so its bottom ~30px is clipped.","seed_edits":2,"judge":"With a long-thread fixture, opens the long task in the Inbox and checks all expected comments exist. Scrolling the comment list down with the mouse wheel must leave the newest comment fully visible and uncovered, scrolling up must fully show the oldest; after posting a new comment it must be fully visible (directly or after wheel-scrolling down).","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"mention-trim","title":"Simplify @mention list rows","part":"extended","group":"ui","kind":"feature","actions":["look","keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Design tweak for the @mention list in the Inbox comment box: each row should show just the person — their avatar and name. Drop the email address and the \"ID m2\" bit, and let the name use the whole row, on one line (long names like \"Maximiliana Featherstonehaugh-Oyelaran Smythe\" get squeezed onto two lines right now; you can add a member with that name through the team API to try it). The keyboard keeps working as it does now: up/down to move, Enter or Tab to pick, Esc to close."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Adds a member with a very long name through the mock API, then types '@' in an Inbox comment box. The popup must list all team members with avatars, no email addresses or member IDs, and rows spanning the popup width; filtering to the long name must show it on one line, uncut and inside the popup. Keyboard behaviour must still work: ArrowDown/ArrowDown/ArrowUp+Enter inserts the second name, Tab picks the filtered match, and Escape closes the list while keeping focus in the comment box.","reference":"references/mention-trim","audit_variants":{"should_fail":4,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"type-scale","title":"Three-size type scale on Board and Inbox","part":"extended","group":"ui","kind":"feature","actions":["look"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Typography cleanup from design. The Board cards, the Inbox task list and the Inbox task pane use too many font sizes. Use exactly three there:\n- 14px: task titles (on cards and in the list) and reading text in the task pane — field values, the description, section headings (Attachments, Comments), attachment names, comment text and the comment box.\n- 13px: secondary text and actions — field labels (Status, Priority, …), attachment sizes and paths, comment authors, and buttons and links (Mark done, Attach file, Download, Post comment, the \"Add a comment\" label).\n- 12px: the smallest bits — priority badges, the \"Done\" marker in the list, comment timestamps.\nLeave everything else as it is: the initials in avatars, the column headings on the Board, the title bar of the task pane (task title, Edit, Copy link), the list's header and filters, and all other pages."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Reads computed font sizes. On Board cards and in Inbox rows and the task pane, every visible text must be exactly 14, 13 or 12px, with specific elements checked against the spec (titles, description, comment text 14px; labels, sizes, paths, authors, buttons and links 13px; priority badges, the Done marker and timestamps 12px). Elements that were to stay unchanged are checked too: avatar initials 11px, Board column headings 15px, the pane title 16px with 15px Edit/Copy link, the list's 15px filters, the 13px task count, and the Tasks page titles at 15px.","reference":"references/type-scale","audit_variants":{"should_fail":5,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"board-dnd","title":"Board drag-and-drop does not save; failed moves stick","part":"extended","group":"controls","kind":"bug fix","actions":["drag","wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Dragging cards on the Board is broken. I can pick a card up and carry it over to the other column (it follows the mouse fine), but when I let go it snaps back to where it was and nothing is saved. Same for every card, To do → Done and Done → To do.","Thanks! Mei found another one on the Board: when a move can't be saved — on this server \"Reply to customer feedback\" always fails to save right now — you get the \"Couldn't move … It's back where it was\" message, but the card stays in the column you dropped it in. Only a reload puts it back in To do. When a move fails, the card should go back where it was."],"agent_scenario":"{\"latency\":{\"PATCH /api/tasks/:id\":900},\"fail\":[{\"route\":\"PATCH /api/tasks/:id\",\"when\":{\"id\":8},\"status\":500,\"message\":\"internal error\"}]}","judge_scenario":"{\"latency\":{\"PATCH /api/tasks/:id\":600},\"fail\":[{\"route\":\"PATCH /api/tasks/:id\",\"when\":{\"id\":8},\"status\":500,\"message\":\"internal error\"}]}","judge_viewport":{"width":1200,"height":900},"seed":"Plants two bugs: the dragged card no longer has pointer-events disabled (so the drop lands on the card itself and snaps back), and a failed save never clears the card's pending state so it stays in the dropped column.","seed_edits":2,"judge":"With task saves delayed 600ms and saving one specific task always failing with HTTP 500, drags cards with real mouse events. Dropping on the same column must change nothing; To do -> Done and Done -> To do drags must persist in the mock API and show the card in the new column. A drag whose save fails must show an error and return the card to its original column without changing the API, after which the same card must drag successfully once the failure is lifted; a failing Done -> To do move must likewise revert, and clicking a card must still open the task.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"assignee-combo","title":"Searchable assignee combobox","part":"extended","group":"controls","kind":"feature","actions":["keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["The Assignee dropdown on a task's edit page (\"Edit all fields\") is a long plain list, and it's getting worse as the team grows. Make it a searchable picker: you type part of a person's name and the list narrows to the matches, the arrow keys move through them, Enter picks the highlighted one (without saving the whole form), and Escape closes the list without changing anything. Clicking a match should work too, and \"Unassigned\" must still be a choice. Keep it labelled Assignee and make it work for keyboard and screen-reader users like a standard combobox."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"On a task's edit page, requires the Assignee field to be a combobox rather than a native select. Typing part of a surname must narrow the options; arrow keys plus Enter must pick the highlighted option without submitting the form and close the list; Escape on a new search must close the list without changing the choice; Unassigned must be selectable. Saving must store the right assignee in the mock API, the highlighted option must be exposed to screen readers (aria-activedescendant, focus or aria-selected), arrow keys must actually move the highlight, and clicking an option must work.","reference":"references/assignee-combo","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"due-off-by-one","title":"Due date saved one day early","part":"extended","group":"controls","kind":"bug fix","actions":["read"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Due dates come out a day early. I opened \"Plan team offsite\", went to Edit all fields, picked November 20 as the due date and saved — the task now says it's due Nov 19, and the edit page shows the 19th too. Mei says one of hers slipped by two days because she edited the task twice. We have people in Shanghai, Berlin and Seattle: the due date has to be the day you picked, for everyone."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the edit page converts the picked due date through a local-midnight Date and toISOString(), shifting it back a day in time zones east of UTC.","seed_edits":2,"judge":"Runs in fresh browser contexts with the Asia/Shanghai and America/Los_Angeles time zones. In each, sets a due date on the edit page, requires the mock API to store that exact day, the task view to show that day (and not the neighbouring day), the edit page to show the same value when reopened, and re-saving after editing only Notes to leave the date unchanged.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"infinite-dup","title":"Inbox infinite scroll duplicates tasks","part":"extended","group":"controls","kind":"bug fix","actions":["scroll","wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["The Inbox shows some tasks twice. In our big workspace the Inbox loads more tasks as you scroll down, and each batch takes a second or so to arrive. If I scroll quickly — flick down to the bottom, back up a bit and down again while it's still loading — the same tasks show up two or even three times in the list. Every task should be in the list exactly once and in order, and scrolling all the way down should still get you every task."],"agent_scenario":"{\"fixtures\":[\"many-tasks\"],\"slow\":[{\"route\":\"GET /api/tasks\",\"when\":{\"page\":2},\"ms\":1200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":3},\"ms\":1200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":4},\"ms\":1200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":5},\"ms\":1200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":6},\"ms\":1200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":7},\"ms\":1200}]}","judge_scenario":"{\"fixtures\":[\"many-tasks\"],\"slow\":[{\"route\":\"GET /api/tasks\",\"when\":{\"page\":2},\"ms\":2200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":3},\"ms\":2200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":4},\"ms\":2200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":5},\"ms\":2200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":6},\"ms\":2200},{\"route\":\"GET /api/tasks\",\"when\":{\"page\":7},\"ms\":2200}]}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: removes the in-flight guard and de-duplication from the Inbox's paged loader, so fast scrolling requests the same page several times and appends it repeatedly.","seed_edits":5,"judge":"Uses a large many-tasks fixture with pages 2-7 of the task list delayed 2.2s (slower than the agent saw). Flicks the Inbox list down, back up and down with the mouse wheel until the end, then requires every task from the mock API listed exactly once and in API order. It then switches the Status filter to Done while a page is loading and back to All, scrolls to the end again and repeats the same check.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"row-actions-kbd","title":"Keyboard access to Inbox quick actions","part":"extended","group":"controls","kind":"bug fix","actions":["hover","keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Keyboard users can't use the quick actions in the Inbox. With a mouse, hovering a task shows its Complete and Star buttons at the end of the row. With the keyboard there's no way to get to them: Tab goes from the task straight to its ⋯ button and on to the next task, so you can't complete or star a task without a mouse. Make them reachable and usable with the keyboard, and visible while you're on them. Otherwise keep them hidden until you hover, as now — the designers want a calm list."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Removes keyboard access to the Inbox row quick actions: the Complete and Star buttons get tabIndex -1 and are shown only on hover, not on focus-within.","seed_edits":5,"judge":"Requires the quick actions to stay hidden without hover or focus and to appear on hover. Tabbing from a row's title link must reach its Complete and Star buttons within that row, each visibly shown and not covered while focused, with other rows' actions still hidden; Enter on Complete must mark the task done and Space on Star must star it in the mock API. After focus leaves and the mouse is away, the actions must be hidden again.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"draft-keep","title":"Keep unsent comment drafts per task","part":"extended","group":"browser","kind":"feature","actions":["history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["People keep losing half-written comments in the Inbox. If you start a comment on a task and then click another task, reload the page, or go back and forth in the browser, what you typed is gone. Keep unsent comments: each task keeps its own draft in this browser, and it's still there after a reload or when you come back to the task. Once the comment is posted, its draft is cleared."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"Types partial comments on two Inbox tasks and requires each task's draft to be independent and to survive switching tasks, a reload, and browser Back/Forward. Posting a restored draft must save it once in the mock API, clear the box and not bring the draft back after reload; an untouched task must show no draft, and the draft must also appear in a new tab of the same browser. Finally, with comment posting failing with HTTP 500, a failed post must leave the draft in place after a reload.","reference":"references/draft-keep","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"attach-upload","title":"Attachment preview and 1 MB limit","part":"extended","group":"browser","kind":"feature","actions":["upload","iframe"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Attachments need a preview. Right now the only way to see what's in a file attached to a task is to download it. In a task's Attachments (Inbox, task on the right), clicking a file's name should show the file right there in the task, under the list — the API serves a preview page for exactly this (see API.md). Clicking the name again hides it. A file you've just uploaded should open in the preview straight away.","Also: Diego tried to attach a 6 MB screen recording. It said \"Uploading…\" for ages and then failed. Files can be up to 1 MB — refuse bigger ones right away, before uploading anything, with a message that says the limit. Files under the limit upload as before."],"agent_scenario":"{\"slow\":[{\"route\":\"POST /api/tasks/:id/attachments\",\"ms\":2500}]}","judge_scenario":"{\"slow\":[{\"route\":\"POST /api/tasks/:id/attachments\",\"ms\":1500}]}","judge_viewport":{"width":1200,"height":900},"seed":"Removes the attachment preview (clickable file names and preview iframe) and the client-side 1 MB size check from the Inbox task's attachments.","seed_edits":9,"judge":"With uploads delayed 1.5s, clicking an attachment's name in an Inbox task must show the file's contents in an iframe and clicking again must hide it. A newly uploaded file must appear in the preview and be saved in the mock API, and a 700 KB file must upload. Picking a 1.5 MB file must immediately show a message stating the 1 MB limit, send no upload request and attach nothing, and the upload control must still work for a small file afterwards.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":3},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"back-keeps-place","title":"Back to Inbox keeps scroll and highlight","part":"extended","group":"nav","kind":"bug fix","actions":["scroll","history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["On a phone the Inbox loses my place. In a narrow window the Inbox shows either the list or one task. If I scroll down the list (often a few batches in), open a task and then go back — with the ← Inbox link or the browser's Back button — the list starts over from the top with only the first few tasks loaded, and I have to scroll down and hunt for where I was. Going back should leave the list exactly where it was, with the task I just looked at highlighted."],"agent_scenario":"{\"fixtures\":[\"many-tasks\"]}","judge_scenario":"{\"fixtures\":[\"many-tasks\"]}","judge_viewport":{"width":390,"height":844},"seed":"Plants the bug: returning from a task to the Inbox reloads and empties the paged list (losing the scroll position) and no longer highlights the last-viewed task.","seed_edits":5,"judge":"At a 390x844 viewport with a many-tasks fixture, scrolls the Inbox several batches down with the mouse wheel, opens a task and goes back with the browser's Back button, and later with the in-page Inbox link. Each time the previously opened row must be within 16px of its earlier position in the list and visibly highlighted (class/aria marker or distinct background), and only one row may stay highlighted.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"old-links","title":"Legacy task links: Back, deleted notice, Copy link","part":"extended","group":"nav","kind":"bug fix","actions":["history","clipboard"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Old task links — the /browse/TT-1002 kind from the old app, still all over our docs and chats — have two problems. First, they do take you to the task, but then the browser's Back button doesn't get you back to where you were: you land on the same task again, every time. Second, an old link to a task that has since been deleted says \"Task not found … the link may be mistyped\", so people think the link is broken. It should say clearly that the task was deleted (by whom, and when), like opening the deleted task's own address does.","One more: the Copy link buttons (on a task's page, on a task in the Inbox, and in a row's ⋯ menu) still hand out old-style /browse/TT-… links. For tasks created since the move those don't work at all — Diego got \"Task not found\" from one I sent him today. Copy link should copy the task's new address."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bugs: legacy /browse/TT-#### redirects push a history entry instead of replacing it, deleted tasks reached by a legacy link show a generic not-found message, and Copy link copies legacy /browse/TT-… addresses.","seed_edits":6,"judge":"Visiting a legacy link from the Board must land on the task's new address and Back must return to the Board. After deleting a task through the mock API, its legacy link must say it was deleted, name the task, the member who deleted it and a date, and not say not found; an unknown legacy link must say not found without claiming deletion. Copy link on a task page, in a newly created task's row menu and in the Inbox pane must put the task's new /tasks/<id> address on the clipboard, and that link must open the new task.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"login-return","title":"Return to deep link after sign-in","part":"extended","group":"auth","kind":"bug fix","actions":["history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Ticket from support: people keep getting task links in chat and email (like /tasks/4, or an inbox link such as /inbox/5?status=active). When they're signed out and open one, they get the sign-in page — fine — but after signing in they land on the task list instead of the task the link pointed to, and have to go find it again. After signing in, take people to the page the link was for, including its filters. (This team requires signing in; test accounts are the members' emails with the password `teamtasks`, e.g. alex@teamtasks.dev.)"],"agent_scenario":"{\"auth\":\"required\"}","judge_scenario":"{\"auth\":\"required\"}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the post-sign-in redirect only allows a fixed whitelist of top-level pages, so task and inbox deep links (with filters) fall back to the home page.","seed_edits":1,"judge":"With the mock API requiring sign-in, opens /tasks/4 signed out, signs in, and requires that task to show at /tasks/4; after signing out, an /inbox/5?status=active link must return to that path with the status filter kept and no sign-in form left. Opening /login?next=/tasks/2 while signed in must go straight to that task, and signing in with next set to a protocol-relative or absolute external URL must stay on the app's origin and open the app.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"viewer-role","title":"Read-only members offered edits; silent 403s","part":"extended","group":"auth","kind":"bug fix","actions":["read","wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["From Sam Carter, who is on the team as a read-only member (Viewer): \"The task list, the task pages and the Board all offer me the add-task box, Edit, Delete, Mark done and so on, as if I could change things. I tried deleting 'Plan team offsite' to see what happens: it vanished, then came back when I reloaded. I thought I'd broken something.\" Read-only members should not be offered changes anywhere. And whenever the server refuses a change (it answers 403 for read-only members — which can still happen to someone whose role was changed while they had the app open), the app must say so and leave things as they were instead of pretending it worked. (While you work on this, the app runs as Sam.)"],"agent_scenario":"{\"role\":\"viewer\"}","judge_scenario":"{\"role\":\"viewer\"}","judge_viewport":{"width":1200,"height":900},"seed":"Plants two bugs: the read-only check compares against lowercase 'viewer' while the API returns 'Viewer', so viewers see all edit controls; and delete becomes optimistic, removing the task even when the server refuses.","seed_edits":3,"judge":"With the mock API's current member set to the Viewer role, requires no add-task box, edit/delete/complete/star buttons, enabled checkboxes or editable fields on the task list, task page, Board and Inbox, and no delete/move items in the row menu. It then loads as Owner, switches the server to Viewer behind the app's back and clicks Delete: the task must remain in the mock API and in the list, and the user must be told of the refusal (new on-page text or an alert matching words like permission/forbidden/couldn't); a refused completion must not stay checked, and the task must still be there after reload.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"session-expiry","title":"Re-authenticate in place on session expiry","part":"extended","group":"auth","kind":"bug fix","actions":["wait","keys"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Complaint from Mei: \"I spent ten minutes filling in a task on its 'Edit all fields' page, pressed Save, and got thrown onto the sign-in page. After signing in I was back on the edit page, but everything I had typed was gone, and nothing had been saved.\" Sessions running out is expected, but when it happens the app must ask the person to sign in again right where they are, keep everything they typed, and then finish what they were doing (the save they pressed) without them having to do it again. The same goes for anything else that saves — the task page's description, posting a comment in the inbox, and so on. (This team requires signing in — test accounts are the members' emails with the password `teamtasks`, e.g. alex@teamtasks.dev — and on this test team a session only lasts two minutes, so it's easy to reproduce.)"],"agent_scenario":"{\"auth\":\"required\",\"sessionTtlMs\":120000}","judge_scenario":"{\"auth\":\"required\"}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: a 401 during a session now signs the user out to the sign-in page (discarding the form) instead of opening the in-place re-sign-in dialog and retrying the request.","seed_edits":1,"judge":"With sign-in required, fills Title and Notes on a task's edit page, expires all sessions in the mock API and clicks Save. A password prompt must appear while the typed values stay on the page; a wrong password must show an error and nothing must be saved yet; after the correct password the original save must complete automatically with both fields stored in the mock API, without landing on the sign-in page. The same flow for posting an Inbox comment must post it exactly once after re-sign-in and show it in the thread.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"checkout-return","title":"Checkout in new tab; cancel voids order","part":"extended","group":"payment","kind":"bug fix","actions":["tab","history"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Two problems with buying credits on the Credits page. 1) Checkout replaces our app in the same tab; it should open in a new tab, so the Credits page stays where it was. 2) If someone changes their mind on the checkout page and uses \"Cancel and return to Team Tasks\", they come back to \"Checkout cancelled\", but the order still sits in Orders as \"Awaiting payment\" — and can still be paid from that checkout link. An order abandoned that way must be cancelled, and show as Cancelled in the Orders list, both on the page they come back to and on the Credits page they left open. Paying must keep working as it does today."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants two bugs: checkout opens in the same tab instead of a new one, and returning via 'Cancel and return' only shows a notice without cancelling the pending order.","seed_edits":2,"judge":"On the Credits page, clicking Buy 100 credits must open the mock checkout page in a new tab while the original tab stays on Credits with no 'blocked' message, and a pending order must exist. Using 'Cancel and return' on the checkout tab must set the order to cancelled in the mock API and show it as Cancelled both on the returned tab (also after reload) and on the Credits tab left open. A second purchase paid on checkout must mark the order paid, raise credits to 750 and show Paid in both tabs.","reference":"the app without the seed patch","audit_variants":{"should_fail":3,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"balance-refresh","title":"Live credit balance after payment","part":"extended","group":"payment","kind":"bug fix","actions":["tab","wait"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Bug: on the Credits page, I buy credits, pay on the checkout tab and switch back to the tab with the Credits page — it still shows my old balance and the order as \"Awaiting payment\" until I reload. The \"Payment received\" notification also only shows up in the bell after a reload. The balance, the order and the bell should update by themselves as soon as the payment has gone through, without reloading — payments sometimes take a few seconds to go through, so it may complete after I've already switched back."],"agent_scenario":"{\"latency\":{\"default\":80,\"POST /pay/:id\":2500}}","judge_scenario":"{\"latency\":{\"default\":80,\"POST /pay/:id\":2500}}","judge_viewport":{"width":1200,"height":900},"seed":"Plants two bugs: the server-event client reads untyped onmessage messages while the mock API sends named events, so no live updates arrive; and the Credits page no longer refreshes on window focus or visibility change.","seed_edits":2,"judge":"With payments taking 2.5s in the mock API, buys credits from the Credits page, pays in the new checkout tab and immediately switches back. Without a reload, the balance must rise from 250 to 350, the order must show Paid and the notification bell's unread count must go from 2 to 3. After the mock API drops the live event connection, a second purchase must still update the balance to 850 and the bell to 4.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"white-screen","title":"Task page goes white after edit-save","part":"extended","group":"debug","kind":"bug fix","actions":["devtools"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Urgent: some tasks open as a completely white page — no header, no sidebar, nothing. Reloading doesn't help. It seems to start once someone saves the task on its \"Edit all fields\" page: e.g. open \"Plan team offsite\", Edit all fields, change anything, Save — the page goes white, and from then on that task always opens white. Other tasks are fine. Please find out what's going on and fix it."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the task page adds a 'Due' line guarded by \"'dueDate' in task\" and formats it unconditionally, so a task saved with a null due date throws and blanks the whole app.","seed_edits":2,"judge":"Records page errors. A task set to a null due date via the mock API must open with its heading; saving a title change on the edit page, reloading, setting and then clearing a due date, and saving a repeating task with an empty estimate must each leave the task page rendered (with Edit all fields and Delete task still present) and never show Invalid Date/NaN. Clearing the due date must actually clear it in the mock API and remove the old date from the page, the Inbox must render affected tasks, and no uncaught page error may occur.","reference":"the app without the seed patch","audit_variants":{"should_fail":5,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"wrong-param","title":"Inbox Status filter has no effect","part":"extended","group":"debug","kind":"bug fix","actions":["devtools"],"runs_per_side":3,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["In the Inbox, the Status filter doesn't seem to work: with \"Done\" picked I still see tasks that aren't done, \"Active\" shows finished ones, and the number of tasks next to the Inbox title stays the same whatever I pick. The All / Active / Done buttons on the task list page work fine. Can you look into it and fix it?"],"agent_scenario":"{\"fixtures\":[\"many-tasks\"]}","judge_scenario":"{\"fixtures\":[\"many-tasks\"]}","judge_viewport":{"width":1200,"height":900},"seed":"Plants the bug: the paged task request sends the status filter as 'state' instead of 'status', so the mock API ignores it and returns everything.","seed_edits":1,"judge":"With a many-tasks fixture, picks Done and then Active in the Inbox Status filter and requires the task count next to the title to equal the matching number in the mock API and every listed row to have the right done state; for Done it scrolls through all pages and requires exactly the done tasks, each once. After reloading with Active selected, no finished tasks may be listed and the count must match the active total.","reference":"the app without the seed patch","audit_variants":{"should_fail":2,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"activity-log","title":"Activity page filters, per-task view, delete, Load more","part":"extended","group":"long","kind":"feature","actions":["read","history","dialog"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["The Activity page needs filters. Add a \"Type\" filter (All activity, Tasks, Comments, Attachments, Orders) and a \"Person\" filter (Everyone, or one member of the team). Keep the filters in the page address, so a reload or a shared link shows the same view, and the browser's Back button undoes the last filter change. Newer / Older must page through the filtered entries, and changing a filter starts again from the first page. The API already supports filtering the activity log (see API.md).","On a task's page, add a \"View activity\" link that opens the Activity page showing only that task's entries. Make it clear on the Activity page that it is showing one task's activity (say which task), with a way to go back to all activity. The Type and Person filters still work on top of it.","Admins need to clean up the log: give each entry a Delete button. Ask first with the browser's own confirmation dialog (like deleting a task does), saying which entry will be deleted; nothing happens if they cancel. After deleting, stay on the same filters. Read-only members (Viewers) don't get Delete.","Change of plan from the design review: replace the Newer / Older paging with a \"Load more\" button under the list that adds the next 20 entries below the ones already shown, and goes away when there is nothing more to load. Filters work exactly as before; the address doesn't need a page number any more.","Bug from QA: with a couple of batches loaded with Load more, if you delete an entry and then press Load more, one entry is skipped and never shows up; and if something new happens in the team while you're on the page, the next Load more shows an entry twice. Load more must always continue right after the last entry shown — nothing skipped, nothing twice."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A five-round feature; the judge first adds 45 task-rename entries to the mock API's activity log, then compares the listed entries one by one with the expected log. It requires Type and Person filters kept in the URL (surviving reload, undone by Back/Forward), a Load more button adding 20 entries with the old Newer/Older paging gone, and per-entry Delete behind a native confirm dialog that names the entry (cancel deletes nothing, confirm deletes and keeps the filters). Load more must skip nothing after a delete and show nothing twice after new activity arrives; a task's View activity link must show only that task's entries, name the task, combine with Type and Person filters and allow returning to all activity; the Orders type must filter correctly, and Viewers must get no Delete buttons.","reference":"references/activity-log","audit_variants":{"should_fail":5,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"notify-center","title":"Notifications page with live counts and toasts","part":"extended","group":"long","kind":"feature","actions":["wait","read"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Add a Notifications page. A \"Notifications\" link in the sidebar, with the number of unread notifications next to it (e.g. \"Notifications 2\"), opens /notifications, which lists all notifications, newest first. Unread ones stand out and each has a \"Mark as read\" button; there's also a \"Mark all as read\". Clicking a notification that is about a task opens that task and marks the notification read. The bell, the sidebar count and the page must always agree with each other, and a new notification shows up in all of them right away, without reloading.","On the Notifications page, add two tabs: All and Unread. Keep the chosen tab in the page address, so a reload or the browser's Back keeps it. In Unread, a notification you mark as read stays in the list (dimmed) until you leave the page or reload, so the list doesn't jump under your mouse.","When a new notification arrives, also pop up a small message with its title, with a \"View\" button when it is about a task — except on the Notifications page itself, where it simply appears at the top of the list.","Change of plan: the pop-ups are too noisy. Only notifications about tasks assigned to me should pop up; everything else just goes to the bell and the Notifications page, as before. Also show the unread count in the browser tab's title, like \"(3) Team Tasks\" (just \"Team Tasks\" when nothing is unread).","When the live connection drops (a laptop wakes from sleep, the Wi-Fi blips), show \"Reconnecting…\" in the bell's panel and on the Notifications page until it is back. Once it's back, catch up with whatever arrived in the meantime — the counts and the list must be right without a reload."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A five-round feature driven by notifications pushed from the mock API. Requires a sidebar Notifications link whose unread count always matches the bell and the tab title '(n) Team Tasks', a newest-first /notifications page that receives new items live without a pop-up, persistent Mark as read and Mark all as read, and clicking a task notification to open the task and mark it read. All/Unread tabs must live in the URL (survive reload and Back), with items marked read in Unread staying until the page is left. Pop-ups must appear only for tasks assigned to the current user and include a working View button; after the mock API drops the live stream, 'Reconnecting…' must show in the bell panel and on the page, and once reconnected, notifications sent meanwhile must appear and all counts be correct.","reference":"references/notify-center","audit_variants":{"should_fail":4,"should_pass":2},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"recurring","title":"Recurring tasks: spawn next, scope edits, stop","part":"extended","group":"long","kind":"feature","actions":["read","keys","history"],"runs_per_side":5,"project":"Team Tasks (simulated, this repository: apps/team-tasks)","rounds":["Repeating tasks don't actually repeat yet. The edit page (\"Edit all fields\") lets you set \"Repeats\" and \"Every\", but marking such a task done does nothing special. Make it work: when a repeating task is marked done — with the checkbox in the task list, Mark done on the Board, the Completed box on the task page, or Status on the edit page — the next one is created right away: same title, priority, description, assignee and repeat rule, not done, due on the date moved on by the rule from the old due date (Every 2 weeks → 14 days later, Monthly → the same day next month). If it had no due date, count from today. The completed task stays done.","Make repeating tasks recognizable: on the task page and on the Board cards, show the repeat rule (\"Every week\", \"Every 2 weeks\", …) and the due date.","Editing a repeating task on the edit page: when you press Save, ask whether the change is for \"Only this task\" or \"This and future tasks\". Only this task: just this one changes, and the next one created when it's done is based on the series as it was. This and future tasks: this one and every not-done task of the series change, and so do the ones created after them. Cancelling the question (or pressing Escape) saves nothing and keeps your edits in the form.","Change of plan after a week of use: people complete repeating tasks late, and the next one is born overdue. For daily and weekly tasks, count the next due date from the day the task is actually completed when that is later than its due date. Monthly tasks keep their day of the month: the next one is due one month after the old due date, as before.","Two more things. If someone unticks a completed repeating task and ticks it again, we get a second copy of the next task — completing the same task again must not create another one. And add a \"Stop repeating\" button on the task page: it turns repeating off for that task and the not-done tasks of its series, so no new ones get created; nothing is deleted."],"agent_scenario":"{}","judge_scenario":"{}","judge_viewport":{"width":1200,"height":900},"seed":"none","seed_edits":0,"judge":"A five-round feature checked against the mock API's stored tasks. Completing a repeating task from the list checkbox, Board Mark done, the task page's Completed box or the edit page's Status must create exactly one next task with the same title, priority, description, assignee and rule, due per the rule (weekly/daily counted from completion when overdue, monthly from the old due date, no due date counted from today). The task page and Board cards must show the rule and due date; saving an edit must ask Only this task / This and future tasks (Escape saves nothing and keeps the form), with each scope applied correctly to the series. Unticking and re-ticking must not create a duplicate, Stop repeating must turn off the rule for all not-done tasks in the series without deleting anything, and the whole run must create exactly 7 new tasks.","reference":"references/recurring","audit_variants":{"should_fail":6,"should_pass":1},"license":null,"pr":null,"base_commit":null,"merge_commit":null,"fix_paths":null,"app_dir":null}
{"id":"excalidraw-12053","title":"Excalidraw menus don't close on outside click","part":"real","group":"excalidraw","kind":"bug fix","actions":["canvas","click-hit"],"runs_per_side":3,"project":"https://github.com/excalidraw/excalidraw","license":"MIT","pr":"https://github.com/excalidraw/excalidraw/pull/12053","base_commit":"f1a79b73df5b9883f940417861a4f5fb879a3f02","merge_commit":"2b1c2a9fbf62417168cdae041d00f38cc403f0a5","fix_paths":["packages/excalidraw/components/dropdownMenu/DropdownMenuContent.tsx"],"app_dir":"excalidraw-app","rounds":["This folder is the Excalidraw monorepo (the whiteboard app in excalidraw-app/, the editor in packages/excalidraw/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user: \"In the editor, if I open the main menu (the hamburger button at the top left) and then click somewhere on the canvas, the menu stays open. Same with the 'More tools' dropdown in the toolbar. Clicking outside a menu used to close it.\" Please fix it."],"seed":"none (the agent works in the real Excalidraw repository checked out just before the upstream fix, with git history removed)","judge":"Loads the Excalidraw app in headless Chrome at 1200x900 and uses real mouse clicks at screen coordinates. As a control, Escape must close the main (hamburger) menu; then the main menu, opened twice, and the toolbar's More tools dropdown must each close after a click on an empty canvas point (verified to be the canvas by hit-testing).","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"excalidraw-11922","title":"Excalidraw Save-as shortcut while editing text","part":"real","group":"excalidraw","kind":"bug fix","actions":["keys","canvas","download"],"runs_per_side":3,"project":"https://github.com/excalidraw/excalidraw","license":"MIT","pr":"https://github.com/excalidraw/excalidraw/pull/11922","base_commit":"d29d864884782305950122439f54f8dbb5c1bcb0","merge_commit":"afed9e6e27dd1cd5cc52857a405f7bea5312d813","fix_paths":["packages/excalidraw/wysiwyg/textWysiwyg.tsx"],"app_dir":"excalidraw-app","rounds":["This folder is the Excalidraw monorepo (the whiteboard app in excalidraw-app/, the editor in packages/excalidraw/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user: \"While I'm typing in a text element, Cmd/Ctrl+Shift+S (Save as) does nothing: the text editor stays open and nothing is saved. Plain Cmd/Ctrl+S works in the same situation.\" Please fix it."],"seed":"none (the agent works in the real Excalidraw repository checked out just before the upstream fix, with git history removed)","judge":"Stubs the browser's save-file picker to capture written files (a real download also counts). Double-clicks empty canvas, types 'hello' into a new text element and presses Cmd/Ctrl+Shift+S: within 3 seconds the text editor must close and a saved file must contain the text 'hello'. The same flow with plain Cmd/Ctrl+S is a control that must pass for the result to count.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"lexical-9752","title":"Lexical checklist click hijacks next Space","part":"real","group":"lexical","kind":"bug fix","actions":["keys","read"],"runs_per_side":3,"project":"https://github.com/facebook/lexical","license":"MIT","pr":"https://github.com/facebook/lexical/pull/9752","base_commit":"c1351ad29fc80efcb18e367c8681bc80963ce7e9","merge_commit":"150523f63f6768223bf689cd29e250045bc8b6b4","fix_paths":["packages/lexical-list/src/checkList.ts"],"app_dir":"packages/lexical-playground","rounds":["This folder is the Lexical monorepo (the editor packages in packages/, the playground app in packages/lexical-playground/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a writer using the playground: \"I had the caret at the end of a paragraph ('Owners sign off by Friday.') and clicked the check mark of a check list item below it, which checked the item. Then I kept typing ' Ping me': the first space unchecked the item again and never appeared in my paragraph, which now reads 'Friday.Ping me'.\" Please fix it."],"seed":"none (the agent works in the real Lexical repository checked out just before the upstream fix, with git history removed)","judge":"In the Lexical playground, types a paragraph followed by a check-list item, clicks at the end of the paragraph to place the caret, then clicks the item's check mark (it must become checked) and types ' Ping me'. The item must stay checked with text 'Task' and the paragraph must read 'Owners sign off by Friday. Ping me'. As a control, with the caret inside the item, clicking its check mark and pressing Space must still uncheck it.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"lexical-9346","title":"Lexical blank Vertical Align menu item","part":"real","group":"lexical","kind":"bug fix","actions":["resize","look"],"runs_per_side":3,"project":"https://github.com/facebook/lexical","license":"MIT","pr":"https://github.com/facebook/lexical/pull/9346","base_commit":"d487cb67288fca21115bc9b3a01c7b8b2cba44cc","merge_commit":"ea92147c95dae1fee80e25c14608bbc9587ed156","fix_paths":["packages/lexical-playground/src/index.css","packages/lexical-playground/src/plugins/TableActionMenuPlugin/index.tsx"],"app_dir":"packages/lexical-playground","rounds":["This folder is the Lexical monorepo (the editor packages in packages/, the playground app in packages/lexical-playground/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user of the playground: \"When my window is narrower than about 1100px, the 'Vertical Align' item in a table cell's actions menu (the small arrow button that appears in the selected cell) is blank — just an empty row with no text. On a wide window it looks fine.\" Please fix it."],"seed":"none (the agent works in the real Lexical repository checked out just before the upstream fix, with git history removed)","judge":"In the Lexical playground, inserts a 2x3 table through the toolbar, clicks a body cell and opens the cell's actions menu. At both 1000px and 1280px viewport widths, the 'Vertical Align' menu entry must render the visible text 'Vertical Align' (its label element must be visible, not hidden by narrow-width CSS).","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"tldraw-11115","title":"tldraw Escape during page drag closes menu","part":"real","group":"tldraw","kind":"bug fix","actions":["drag","keys"],"runs_per_side":3,"project":"https://github.com/tldraw/tldraw","license":"tldraw license (source-available)","pr":"https://github.com/tldraw/tldraw/pull/11115","base_commit":"1304f95496b7f27ccf47fa683020349f18bad116","merge_commit":"91a4718829a52aafcd7232c3a399456f712786f2","fix_paths":["packages/tldraw/src/lib/ui/components/PageMenu/DefaultPageMenu.tsx"],"app_dir":"apps/examples","rounds":["This folder is the tldraw monorepo (the SDK in packages/, the examples app in apps/examples/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user: \"In the page menu, if I start dragging a page to reorder it and press Escape before dropping it, the whole menu closes. When I open the menu again, the page I was dragging is stuck halfway and the rows move around when I hover over them. Escape should just cancel the drag.\" Please fix it."],"seed":"none (the agent works in the real tldraw repository checked out just before the upstream fix, with git history removed)","judge":"In the tldraw examples app with five pages, Escape without a drag must close the page menu (control). Dragging the second page row down two rows with the mouse held and pressing Escape must keep the menu open and return every row to its slot, not dragging; releasing must change neither page order nor current page. After reopening the menu, all rows must sit in their slots and must not move when the pointer hovers over them.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"tldraw-11253","title":"tldraw frame heading hit area when zoomed out","part":"real","group":"tldraw","kind":"bug fix","actions":["canvas","click-hit"],"runs_per_side":3,"project":"https://github.com/tldraw/tldraw","license":"tldraw license (source-available)","pr":"https://github.com/tldraw/tldraw/pull/11253","base_commit":"ccf6cccc22cdb8fbe768b11947c76f115ebe1990","merge_commit":"b456103d7d9086c622629b9731c2a8812fce0ad1","fix_paths":["packages/tldraw/src/lib/shapes/frame/FrameShapeUtil.tsx","packages/tldraw/src/lib/shapes/frame/components/FrameHeading.tsx","packages/tldraw/src/lib/shapes/frame/frameHelpers.ts"],"app_dir":"apps/examples","rounds":["This folder is the tldraw monorepo (the SDK in packages/, the examples app in apps/examples/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user: \"When I'm zoomed far out (around 10–20%), clicking in the empty canvas just above a frame's title selects the frame. The area above the title that grabs clicks is much taller than the title I can see. At 100% zoom it's fine.\" Please fix it."],"seed":"none (the agent works in the real tldraw repository checked out just before the upstream fix, with git history removed)","judge":"Creates a large frame in the tldraw examples app and sets the camera to 10%, 20% and 100% zoom. At each zoom, a real click on blank canvas 8 screen pixels above the visible frame heading must not select the frame, while clicking the heading itself must select it.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"react-admin-11406","title":"react-admin filters appear in order added","part":"real","group":"react-admin","kind":"bug fix","actions":["read"],"runs_per_side":3,"project":"https://github.com/marmelab/react-admin","license":"MIT","pr":"https://github.com/marmelab/react-admin/pull/11406","base_commit":"7e365e3e007853512ac2ebdfac215cb91eebae47","merge_commit":"181013cdd2ea4a59de9849c2534457d6cd570ba2","fix_paths":["packages/ra-ui-materialui/src/list/filter/FilterForm.tsx"],"app_dir":"examples/demo","rounds":["This folder is the react-admin monorepo (the library in packages/, the demo example app in examples/demo/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user of the demo: \"On the Orders list, when I add filters with the 'Add filter' button — say Min amount first, then Customer — the filter I added last shows up in the middle of the filter bar instead of after the ones I already added. The order seems arbitrary.\" Please fix it so filters appear in the order they were added."],"seed":"none (the agent works in the real react-admin repository checked out just before the upstream fix, with git history removed)","judge":"On the demo's Orders list, adds filters through the Add filter menu in two fresh browser contexts: Min amount then Customer, and Customer then Min amount. The visible filter fields, read top-to-bottom and left-to-right, must be the search box followed by the filters in the order they were added.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"react-admin-11342","title":"react-admin InPlaceEditor saves on focus loss","part":"real","group":"react-admin","kind":"bug fix","actions":["keys"],"runs_per_side":3,"project":"https://github.com/marmelab/react-admin","license":"MIT","pr":"https://github.com/marmelab/react-admin/pull/11342","base_commit":"a13cab504a42fb7888f9ede38cbc32a2e60ff69c","merge_commit":"a8b00f06eeaa1ee94a8b70288addb72258602930","fix_paths":["packages/ra-ui-materialui/src/input/InPlaceEditor/InPlaceEditor.tsx"],"app_dir":"examples/simple","rounds":["This folder is the react-admin monorepo (the library in packages/, the simple example app in examples/simple/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user of the simple example: \"On a post's show page, Miscellaneous tab, I click the Views value to edit it in place, type a new number and then press Tab (focus goes to the Clone button) or click another tab's header: the editor neither saves nor closes. If I click on plain text elsewhere instead, it saves.\" Please fix <InPlaceEditor> so moving focus away saves and closes it."],"seed":"none (the agent works in the real react-admin repository checked out just before the upstream fix, with git history removed)","judge":"On a post's show page in the simple example (Miscellaneous tab), clicks the Views in-place editor, types a new number and leaves it three ways: pressing Tab to the next button, clicking a tab header, and clicking plain text. Each time the editor must close and show the new value, and the value must still be shown after navigating to the list and back to the post. Then, on a blank page of the same dev server, mounts two in-place editors built from the app's own react-admin modules: a text editor, which must save and close when focus moves to a plain input, and a Select editor, where opening the dropdown must leave the editor open and the picked choice must be saved.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}
{"id":"react-admin-11310","title":"react-admin list page resets on reload","part":"real","group":"react-admin","kind":"bug fix","actions":["history","wait"],"runs_per_side":3,"project":"https://github.com/marmelab/react-admin","license":"MIT","pr":"https://github.com/marmelab/react-admin/pull/11310","base_commit":"7ee7217e6f6f758b3091d9ce2ff880fad4ffb666","merge_commit":"c0c23c5fbd180111d73184f1c82c75901420bbb7","fix_paths":["packages/ra-core/src/controller/list/useListController.ts","packages/ra-core/src/controller/list/useInfiniteListController.ts"],"app_dir":"examples/simple","rounds":["This folder is the react-admin monorepo (the library in packages/, the simple example app in examples/simple/). Dependencies are installed and the app's dev server is already running at <url> with hot reload. Do not start servers or install packages.\n\nBug report from a user of the simple example (it has an authProvider): \"I'm on page 2 of the Posts list and reload the page — the list jumps back to page 1 and the URL is rewritten to page=1. Opening a page-2 link in a new tab does the same. It used to keep the page.\" Please fix it."],"seed":"none (the agent works in the real react-admin repository checked out just before the upstream fix, with git history removed)","judge":"In the simple example (which has an auth provider), opens the Posts list, goes to page 2 with the pagination control, then reloads the tab and separately opens the same page-2 URL in a new tab. After each, once settled for 2 seconds, the list must show rows starting at 11 and the URL must still have page=2.","reference":"the upstream fix: git diff <base_commit> <merge_commit> -- <fix_paths>","audit_variants":{"should_fail":0,"should_pass":0},"agent_scenario":null,"judge_scenario":null,"judge_viewport":null,"seed_edits":0}