{"case_id": "sweeper-001", "slug": "abantecart", "repo": "https://github.com/AbanteCart/abantecart-src", "base_commit": "b19852ecd16915f87c66faf46a9f1da04866f8c5", "reference_commit": "0afa04f80d87841b14acf5be34821b9ac7152c69", "task_scoped": "Find and fix issues in AbanteCart’s storefront account profile editor.", "task_specified": "Fix AbanteCart account edit file upload: CustomerFrm file fields are not processed with processFileUploads and the form never gets multipart enctype, so a profile file upload is not saved. Uploading a file on Edit Account should persist and show the saved filename link after reopen.", "pr": 1840, "issue": null, "workflows": "workflows:\n- id: target-account-edit-file-upload-persist\n category: target\n purpose: 'Uploading an ID photo on Edit Account must persist. On the buggy build Continue leaves no uploaded-file link after reopen; on the fixed build reopening Edit Account shows a visible id-photo.txt link under ID Photo.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/index.php?rt=account/login and wait until the storefront login form is visible (login name/email and password fields).\n - Type exactly wrenHolt into the login name / email field.\n - Type exactly peat8noll into the password field.\n - Click Login / Continue and wait until an authenticated My Account page loads.\n - Open exactly http://127.0.0.1:13200/index.php?rt=account/edit and wait until the Edit Account form is visible, including a file input labeled ID Photo (name id_photo).\n - Create a small local text file named exactly id-photo.txt with any short text content, then use the page file input for ID Photo / id_photo to select that file (page-context setInputFiles is allowed only to attach this file to the repo-native form control).\n - Click the Continue / submit button on the Edit Account form and wait for navigation or a success state (My Account or Edit Account with success).\n - Open exactly http://127.0.0.1:13200/index.php?rt=account/edit again and wait until the Edit Account form reloads with the ID Photo control.\n - 'Look only at the visible ID Photo area. Decide: (A) a link or filename text id-photo.txt is visible under/near ID Photo (saved upload shown), OR (B) no id-photo.txt link/filename is shown for the saved upload.'\n - 'Final verdict — PASS only if outcome (A): after upload+Continue, reopening Edit Account visibly shows id-photo.txt for ID Photo. FAIL only if outcome (B): id-photo.txt is not shown after reopen. Do not FAIL for slow loads; use uncertain only if login or account/edit cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.'\n- id: preservation-account-edit-name-save\n category: preservation\n purpose: 'Editing First Name on the same Edit Account form without a file upload must still persist after reopen (adjacent profile save path must not regress).\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/index.php?rt=account/login and wait until the login form is visible.\n - Type exactly wrenHolt into the login name / email field.\n - Type exactly peat8noll into the password field.\n - Click Login and wait until My Account loads.\n - Open exactly http://127.0.0.1:13200/index.php?rt=account/edit and wait until the Edit Account form is visible.\n - Clear the First Name field and type exactly Maren into First Name.\n - Click Continue / submit and wait for success or My Account.\n - Open exactly http://127.0.0.1:13200/index.php?rt=account/edit again and wait for the form to reload.\n - Final verdict — PASS only if First Name visibly shows Maren after reopen. FAIL if the first name did not save. Do not FAIL for slow loads; use uncertain only if login or account/edit cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-002", "slug": "actual", "repo": "https://github.com/actualbudget/actual", "base_commit": "9dbee1078a099cff633b16fd6da978d36dc5cd65", "reference_commit": "f803a918adf42897aa26f39daa227d1a0771cf85", "task_scoped": "Find and fix issues in Actual Budget’s budget import tools.", "task_specified": "Fix Actual Budget nYNAB import so payees that are linked to a transfer account are not created as unused literal payees. Importing a nYNAB JSON budget that contains transfer payees should create a single budget without those spaced transfer payee names in the Payees list while still importing ordinary payees.", "pr": 8424, "issue": null, "workflows": "workflows:\n- id: target-ynab5-import-skips-transfer-payees\n category: target\n purpose: 'After importing a nYNAB JSON budget, literal YNAB transfer payees with a spaced Transfer : prefix must not appear in the Payees list.'\n steps:\n - Open http://127.0.0.1:13200/\n - If the page asks where the server is, click the button \"Don't use a server\" and wait until the welcome / get-started screen shows \"Import my budget\".\n - Click \"Import my budget\", then click the button \"nYNAB The newer web app\", then click \"Select file...\".\n - 'Use the browser page context / evaluate JavaScript to inject the import file without using upload_file. After clicking Select file..., find `#open-file-dialog-input` (it may be temporarily present in the DOM). Create a File from this exact JSON text named `minimal.json` with type `application/json`, assign it via DataTransfer to the input''s files, then dispatch a bubbling `change` event so Actual''s openFileDialog handler runs. JSON payload follows exactly between the markers:\n\n <<>>\n\n {\"name\":\"MinimalTransferTest\",\"accounts\":[{\"id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"name\":\"Checking\",\"type\":\"checking\",\"on_budget\":true,\"closed\":false,\"deleted\":false,\"note\":null},{\"id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"name\":\"Saving\",\"type\":\"savings\",\"on_budget\":true,\"closed\":false,\"deleted\":false,\"note\":null}],\"payees\":[{\"id\":\"eeeeeeee-5555-5555-5555-555555555555\",\"name\":\"Starting Balance\",\"transfer_account_id\":null,\"deleted\":false},{\"id\":\"aaaaaaaa-1111-1111-1111-111111111111\",\"name\":\"Salary\",\"transfer_account_id\":null,\"deleted\":false},{\"id\":\"bbbbbbbb-2222-2222-2222-222222222222\",\"name\":\"Store\",\"transfer_account_id\":null,\"deleted\":false},{\"id\":\"cccccccc-3333-3333-3333-333333333333\",\"name\":\"Transfer : Checking\",\"transfer_account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"deleted\":false},{\"id\":\"dddddddd-4444-4444-4444-444444444444\",\"name\":\"Transfer : Saving\",\"transfer_account_id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"deleted\":false}],\"category_groups\":[{\"id\":\"88888888-8888-8888-8888-888888888888\",\"name\":\"Immediate Obligations\",\"hidden\":false,\"deleted\":false}],\"categories\":[{\"id\":\"ffffffff-6666-6666-6666-666666666666\",\"category_group_id\":\"88888888-8888-8888-8888-888888888888\",\"name\":\"Income\",\"hidden\":false,\"deleted\":false},{\"id\":\"99999999-7777-7777-7777-777777777777\",\"category_group_id\":\"88888888-8888-8888-8888-888888888888\",\"name\":\"Food\",\"hidden\":false,\"deleted\":false}],\"months\":[],\"transactions\":[{\"id\":\"t1\",\"date\":\"2026-01-01\",\"amount\":1000000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"payee_id\":\"aaaaaaaa-1111-1111-1111-111111111111\",\"category_id\":\"ffffffff-6666-6666-6666-666666666666\",\"transfer_account_id\":null,\"transfer_transaction_id\":null,\"deleted\":false},{\"id\":\"t2\",\"date\":\"2026-01-02\",\"amount\":-25000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"payee_id\":\"bbbbbbbb-2222-2222-2222-222222222222\",\"category_id\":\"99999999-7777-7777-7777-777777777777\",\"transfer_account_id\":null,\"transfer_transaction_id\":null,\"deleted\":false},{\"id\":\"t3\",\"date\":\"2026-01-03\",\"amount\":-100000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"payee_id\":\"dddddddd-4444-4444-4444-444444444444\",\"category_id\":null,\"transfer_account_id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"transfer_transaction_id\":\"t4\",\"deleted\":false},{\"id\":\"t4\",\"date\":\"2026-01-03\",\"amount\":100000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"payee_id\":\"cccccccc-3333-3333-3333-333333333333\",\"category_id\":null,\"transfer_account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"transfer_transaction_id\":\"t3\",\"deleted\":false}],\"subtransactions\":[],\"scheduled_transactions\":[],\"scheduled_subtransactions\":[],\"payee_locations\":[]}\n\n <<>>\n\n Wait until the imported budget UI loads with accounts Checking and Saving.'\n - Open http://127.0.0.1:13200/payees and wait until the Payees page heading and payee name list are visible. If a control like \"Show unused payees\" is present, expand it so unused payees are listed too.\n - 'Final verdict — PASS only if the Payees list does NOT contain the exact literal name `Transfer : Checking` and does NOT contain the exact literal name `Transfer : Saving` (spaces around the colon). Actual''s own transfer payees written as `Transfer: Checking` / `Transfer: Saving` without spaces around the colon must be ignored for this check. FAIL only if the Payees page loaded after a successful nYNAB import and at least one of the spaced names `Transfer : Checking` or `Transfer : Saving` is visible in the payee list.'\n- id: preservation-ynab5-import-keeps-normal-payees\n category: preservation\n purpose: Importing a nYNAB JSON budget should still create ordinary non-transfer payees such as Salary and Store.\n steps:\n - Open http://127.0.0.1:13200/\n - If the page asks where the server is, click the button \"Don't use a server\" and wait until the welcome / get-started screen shows \"Import my budget\".\n - Click \"Import my budget\", then click the button \"nYNAB The newer web app\", then click \"Select file...\".\n - 'Use the browser page context / evaluate JavaScript to inject the import file without using upload_file. After clicking Select file..., find `#open-file-dialog-input` (it may be temporarily present in the DOM). Create a File from this exact JSON text named `minimal.json` with type `application/json`, assign it via DataTransfer to the input''s files, then dispatch a bubbling `change` event so Actual''s openFileDialog handler runs. JSON payload follows exactly between the markers:\n\n <<>>\n\n {\"name\":\"MinimalTransferTest\",\"accounts\":[{\"id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"name\":\"Checking\",\"type\":\"checking\",\"on_budget\":true,\"closed\":false,\"deleted\":false,\"note\":null},{\"id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"name\":\"Saving\",\"type\":\"savings\",\"on_budget\":true,\"closed\":false,\"deleted\":false,\"note\":null}],\"payees\":[{\"id\":\"eeeeeeee-5555-5555-5555-555555555555\",\"name\":\"Starting Balance\",\"transfer_account_id\":null,\"deleted\":false},{\"id\":\"aaaaaaaa-1111-1111-1111-111111111111\",\"name\":\"Salary\",\"transfer_account_id\":null,\"deleted\":false},{\"id\":\"bbbbbbbb-2222-2222-2222-222222222222\",\"name\":\"Store\",\"transfer_account_id\":null,\"deleted\":false},{\"id\":\"cccccccc-3333-3333-3333-333333333333\",\"name\":\"Transfer : Checking\",\"transfer_account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"deleted\":false},{\"id\":\"dddddddd-4444-4444-4444-444444444444\",\"name\":\"Transfer : Saving\",\"transfer_account_id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"deleted\":false}],\"category_groups\":[{\"id\":\"88888888-8888-8888-8888-888888888888\",\"name\":\"Immediate Obligations\",\"hidden\":false,\"deleted\":false}],\"categories\":[{\"id\":\"ffffffff-6666-6666-6666-666666666666\",\"category_group_id\":\"88888888-8888-8888-8888-888888888888\",\"name\":\"Income\",\"hidden\":false,\"deleted\":false},{\"id\":\"99999999-7777-7777-7777-777777777777\",\"category_group_id\":\"88888888-8888-8888-8888-888888888888\",\"name\":\"Food\",\"hidden\":false,\"deleted\":false}],\"months\":[],\"transactions\":[{\"id\":\"t1\",\"date\":\"2026-01-01\",\"amount\":1000000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"payee_id\":\"aaaaaaaa-1111-1111-1111-111111111111\",\"category_id\":\"ffffffff-6666-6666-6666-666666666666\",\"transfer_account_id\":null,\"transfer_transaction_id\":null,\"deleted\":false},{\"id\":\"t2\",\"date\":\"2026-01-02\",\"amount\":-25000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"payee_id\":\"bbbbbbbb-2222-2222-2222-222222222222\",\"category_id\":\"99999999-7777-7777-7777-777777777777\",\"transfer_account_id\":null,\"transfer_transaction_id\":null,\"deleted\":false},{\"id\":\"t3\",\"date\":\"2026-01-03\",\"amount\":-100000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"payee_id\":\"dddddddd-4444-4444-4444-444444444444\",\"category_id\":null,\"transfer_account_id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"transfer_transaction_id\":\"t4\",\"deleted\":false},{\"id\":\"t4\",\"date\":\"2026-01-03\",\"amount\":100000,\"memo\":null,\"cleared\":\"cleared\",\"approved\":true,\"account_id\":\"125f339b-2a63-481e-84c0-f04d898905d2\",\"payee_id\":\"cccccccc-3333-3333-3333-333333333333\",\"category_id\":null,\"transfer_account_id\":\"bc1d862f-bab0-41c3-bd1e-6cee8c688e32\",\"transfer_transaction_id\":\"t3\",\"deleted\":false}],\"subtransactions\":[],\"scheduled_transactions\":[],\"scheduled_subtransactions\":[],\"payee_locations\":[]}\n\n <<>>\n\n Wait until the imported budget UI loads with accounts Checking and Saving.'\n - Open http://127.0.0.1:13200/payees and wait until the Payees page heading and payee name list are visible. If a control like \"Show unused payees\" is present, expand it so unused payees are listed too.\n - Final verdict — PASS only if both `Salary` and `Store` are visible as payee names on the Payees page after the nYNAB import. FAIL if the Payees page loaded after import but either `Salary` or `Store` is missing from the payee list.\n"} {"case_id": "sweeper-003", "slug": "adminer", "repo": "https://github.com/vrana/adminer", "base_commit": "37d0febb7569794beee05bb1c1afd495262e4b67", "reference_commit": "9db3a5ad4711a33de5adba774334bf1e12d949d4", "task_scoped": "Find and fix issues in Adminer Editor’s data browsing and search.", "task_specified": "Fix Adminer Editor database overview search: Search data in tables dies with a PHP TypeError. Searching from the overview should list matching tables without a TypeError.", "pr": null, "issue": 992, "workflows": "workflows:\n- id: target-editor-search-all-tables\n category: target\n purpose: Adminer Editor database overview \"Search data in tables\" must run without a PHP TypeError. On the buggy build, searchColumns() passes a null $_GET[\"select\"] into foreignKeyOptions(string $table), so searching from the overview fatals before results. After the fix, searching a known product name lists matching tables (e.g. Products) as visible links.\n steps:\n - Open exactly http://127.0.0.1:13200/ and wait until the Adminer Editor login form is visible (Username and Password fields and a Login button). Prefer English UI if a language choice appears.\n - Type exactly nella-quist into the Username field.\n - Type exactly oak9-twine into the Password field.\n - Click the Login button and wait until you leave the login form and see the Editor database/table overview (heading/chrome for Editor, and a table list and/or Search data in tables control).\n - Confirm the overview shows Search data in tables (a search input next to a Search submit control) and that a Products table entry is listed.\n - Type exactly Alpha into the Search data in tables search input, then click the Search submit button next to it. Wait for the page to finish responding.\n - 'Observe the visible page after that search: either (A) a normal Editor result for the search (for example a list/link mentioning Products / Alpha, or a clear No tables message without a PHP fatal), or (B) a PHP fatal/TypeError/error page (e.g. TypeError mentioning foreignKeyOptions or Argument #1 must be of type string) or an otherwise broken blank/error page with no usable search results UI.'\n - Final verdict — PASS only if (a) you are logged into Editor, AND (b) after searching Alpha the page remains a usable Editor response without TypeError/fatal and shows a Products-related search hit/link (or other clear non-fatal search result UI for that query). FAIL only if (a) is true and the search response shows a PHP TypeError/fatal (especially foreignKeyOptions / must be of type string) or otherwise dies with no usable search results. Do not FAIL for login/setup problems; use uncertain only if login or the Search data in tables control cannot be observed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-editor-table-select\n category: preservation\n purpose: Opening a single table select/browse view from Editor must still list seeded product rows (adjacent path unaffected by searchColumns overview guard).\n steps:\n - Open exactly http://127.0.0.1:13200/ and wait until the Adminer Editor login form is visible.\n - Type exactly nella-quist into Username and oak9-twine into Password, then click Login.\n - Confirm you are in the Editor overview with a Products table link/entry visible.\n - Click the Products table link to open its select/browse view. Do not use Search data in tables in this workflow.\n - Wait until the Products select/browse page shows row data.\n - Final verdict — PASS only if signed into Editor and the Products select/browse view visibly lists at least one seeded row such as Alpha Widget. FAIL if signed in but Products select is blank/broken or shows a PHP fatal. Do not FAIL for login/setup problems; use uncertain only if Products cannot be opened after retries. Do not use fetch/XHR/API/database reads for this judgment.\n"} {"case_id": "sweeper-004", "slug": "adminerevo", "repo": "https://github.com/adminerevo/adminerevo", "base_commit": "91aff545e9d35a1179ad81700512b18e8296d8e1", "reference_commit": "da507f6181b54cfef75491ab6b98e26aea954429", "task_scoped": "Find and fix issues in AdminerEvo’s row editing forms.", "task_specified": "Fix AdminerEvo multi-row edit for nullable ENUM columns: the field dropdown defaults to NULL instead of original. Multi-row Edit of a nullable ENUM should select original so an unchanged Save keeps existing values.", "pr": 209, "issue": 172, "workflows": "workflows:\n- id: multi-edit-nullable-enum-keeps-original\n category: target\n purpose: Multi-row Edit of a nullable ENUM must default the field dropdown to \"original\", not \"NULL\", so an unchanged Save does not wipe existing values.\n steps:\n - Navigate to http://127.0.0.1:13200/\n - Wait until the Adminer login form is visible (System/Server/Username/Password fields, and a Login button). Prefer English UI if a language choice is offered.\n - Leave System as MySQL (default). Leave the Server field blank/empty (localhost) unless login fails, in which case try \"127.0.0.1\".\n - Type \"dale.quist\" into the Username field.\n - Type \"ironKettle3!\" into the Password field.\n - Type \"wickbin\" into the Database field on the login form.\n - Click the Login button and wait until you are inside Adminer (database/table navigation appears; not the login form).\n - If you are not already in database wickbin, open/select the \"wickbin\" database.\n - Open the \"listings\" table select/browse view (click the listings table so row data is listed).\n - Wait until the listings table listing shows at least two data rows (e.g. Linen Apron / Clay Mug) with checkboxes.\n - Check/select the checkboxes for two existing data rows (Linen Apron and Clay Mug).\n - Click the Edit submit button that edits the selected rows (labeled \"Edit\", usually near Clone/Delete under the result table). Do not click a single-row edit link for only one row.\n - Wait until the multi-row Edit form loads (Save button visible; fields for editing selected rows).\n - Locate the form control for the \"status\" column (nullable ENUM). Inspect which option is currently selected in that dropdown/select.\n - Final verdict: PASS only if the status dropdown's currently selected visible option is \"original\" (keeping existing values). FAIL only if the currently selected visible option is \"NULL\" (or clearly defaults to NULL instead of original) on this multi-row Edit form. Do not use fetch/XHR/API/network/DevTools/database as evidence—only the visible selected option text in the Adminer edit form. If login, table browse, or opening multi-row Edit fails before you can see the status dropdown, treat as setup failure rather than product PASS/FAIL.\n- id: preserve-single-row-enum-edit-value\n category: preservation\n purpose: Single-row Edit of a listings row must still open with the row's actual status enum value selected (e.g. active or pending), not collapse to a broken blank form.\n steps:\n - Navigate to http://127.0.0.1:13200/\n - Wait until the Adminer login form is visible.\n - Leave System as MySQL. Leave Server blank/empty (localhost) unless login fails, then try \"127.0.0.1\".\n - Type \"dale.quist\" into the Username field.\n - Type \"ironKettle3!\" into the Password field.\n - Type \"wickbin\" into the Database field.\n - Click Login and wait until Adminer is open.\n - Open database \"wickbin\" if needed, then open the \"listings\" table select/browse view.\n - Wait until at least one data row such as \"Linen Apron\" is visible.\n - Open single-row Edit for the \"Linen Apron\" row (use that row's edit link/icon, not multi-select Edit).\n - Wait until the Edit form loads with a Save button.\n - Locate the \"status\" field dropdown on the form.\n - Final verdict: PASS only if the status dropdown shows a real enum value selected that matches the row (for Linen Apron this should be \"active\"), as a normal Adminer edit form. FAIL if the edit form is missing/broken, or status is not shown as the row's actual value \"active\". Do not perform multi-row Edit in this workflow. Do not use fetch/XHR/API/network/DevTools/database as evidence—only visible page content. If login or opening the single-row editor fails, treat as setup failure rather than product PASS.\n"} {"case_id": "sweeper-005", "slug": "akaunting", "repo": "https://github.com/akaunting/akaunting", "base_commit": "482f3a6da11842c0d8559e276bbbd9774ff5b394", "reference_commit": "016bd89bf620fb5c3d35e2973d729b19e72d51a4", "task_scoped": "Find and fix issues in Akaunting’s item catalog editor.", "task_specified": "Fix Akaunting item sale price parsing so localized amounts with three or more thousand separators are not truncated when saved. Saving that sale price should store and display the full amount.", "pr": 3372, "issue": 1618, "workflows": "workflows:\n- id: target-item-sale-price-keeps-multi-thousand-separators\n category: target\n purpose: Localized item sale prices with three or more thousand separators must be stored and shown in full, not truncated.\n steps:\n - 'Open http://127.0.0.1:13200/auth/login and wait until the Akaunting login page is visible with the green Akaunting logo, login background styling, Email and Password fields (not a bare unstyled text shell).\n\n '\n - 'Sign in with email sofia.brandt@mail.com and password cedarPorch8!. Wait until login succeeds and you are inside the signed-in company app (URL contains /1 or the admin navigation is visible).\n\n '\n - 'Open http://127.0.0.1:13200/1/common/items/create and wait until the New Item form is visible with Name, Sale Price, and Purchase Price fields (both price fields show a required red *).\n\n '\n - Set Type to product if it is not already selected.\n - In Name, enter exactly: Ceramic Table Lamp\n - 'In Sale Price, clear any existing value and type exactly: 1.234.567,89\n\n '\n - In Purchase Price, clear any existing value and type exactly: 100\n - Click Save and wait until the request finishes and you land on the items list or the saved item view.\n - 'Open the items list at http://127.0.0.1:13200/1/common/items if you are not already there, and locate the row for Ceramic Table Lamp.\n\n '\n - 'Final verdict — FAIL only if that row clearly shows a truncated sale price around one thousand dollars such as $1,234.57 or $1,234.56, proving the multi-separator amount was not preserved.\n\n '\n - 'Final verdict — PASS only if that same row clearly shows the full amount $1,234,567.89 (or an equivalent full-amount rendering that includes 1,234,567 and not merely 1,234.xx).\n\n '\n - 'Do not PASS on the create form alone. Do not FAIL for login/setup/network problems; only FAIL when Ceramic Table Lamp is visible with the truncated ~$1,234.57-class amount.\n\n '\n- id: preservation-item-sale-price-two-separator-amount-still-works\n category: preservation\n purpose: A normal two-separator localized sale price such as 1.234,56 must still save and display correctly.\n steps:\n - 'Open http://127.0.0.1:13200/auth/login and wait until the Akaunting login page is visible with Email and Password fields.\n\n '\n - 'If not already signed in, sign in with email sofia.brandt@mail.com and password cedarPorch8! and wait until the signed-in app is available.\n\n '\n - Open http://127.0.0.1:13200/1/common/items/create and wait until the New Item form is visible.\n - Set Type to product if needed.\n - In Name, enter exactly: Linen Throw Pillow\n - 'In Sale Price, clear any existing value and type exactly: 1.234,56\n\n '\n - In Purchase Price, clear any existing value and type exactly: 100\n - Click Save and wait until the item is saved.\n - Open http://127.0.0.1:13200/1/common/items if needed and locate Linen Throw Pillow.\n - 'Final verdict — PASS only if that row shows sale price $1,234.56 (or an equivalent rendering of 1234.56).\n\n '\n - 'Final verdict — FAIL if the item is missing, the save fails, or the shown sale price is clearly not 1234.56 / $1,234.56.\n\n '\n"} {"case_id": "sweeper-006", "slug": "alist", "repo": "https://github.com/AlistGo/alist", "base_commit": "68922bd05b9d014b2b4afc15967350a44115cc20", "reference_commit": "79c96c0490714f53ad7ead1587131da4d76db8be", "task_scoped": "Find and fix issues in AList’s guest file access.", "task_specified": "Fix AList guest base-path joining: When a guest confined to a base path opens a subfolder from the guest root, absolute subfolder paths are resolved against the real root instead of that base path, so the folder fails to load. Opening a subfolder under the guest root should list that folder's files under the guest base path.", "pr": 9601, "issue": 9600, "workflows": "workflows:\n- id: target-guest-base-path-subfolder-navigation\n category: target\n purpose: As the enabled guest confined to base path /public, opening a subfolder under the guest root must list that folder's contents; baseline fails because JoinBasePath ignores the base path for absolute subpaths so the subfolder request misses /public and errors.\n steps:\n - Open http://127.0.0.1:13200/ in a fresh browser context (no admin login). Confirm the AList file browser UI loads with normal styling/logo (not a bare-text/error-only page).\n - Stay signed out / use the default guest session. Do not log in as admin.\n - Confirm the guest file list for the virtual root is visible and includes a folder named exactly `docs` (seeded under the guest base path /public). If a login wall blocks guest browsing, treat that as setup failure (not a product PASS/FAIL for this bug).\n - Click / open the `docs` folder using the normal AList file-browser UI (row click or equivalent folder open control). Wait for the list request to finish.\n - Observe whether the UI successfully shows the contents of `docs`, specifically a file named exactly `hello.txt`, with no permission/load failure for this navigation.\n - 'Final verdict (tighten): FAIL only if BOTH are true: (1) you opened the guest file browser and clicked into the `docs` folder under the guest root, and (2) that navigation fails with a clear bug-specific UI outcome — AList shows a load/permission/error state for this folder (for example a visible error toast/dialog/message such as failed to load / permission denied / object not found / 403/500 wording) AND the `hello.txt` file is NOT listed inside `docs`. Do not FAIL for admin login mistakes, missing seed folder `docs`, or unrelated chrome/tooling issues. PASS only if BOTH are true: (1) after opening `docs` as guest you remain in the file browser showing that folder, and (2) `hello.txt` is visibly listed as a file inside `docs` with no error toast/dialog blocking the listing. Do not PASS if the folder open fails or `hello.txt` is absent.\n\n '\n- id: preservation-admin-public-docs-navigation\n category: preservation\n purpose: An admin user with unrestricted base path must still be able to open /public/docs and see hello.txt after the base-path join fix.\n steps:\n - Open http://127.0.0.1:13200/@login (the dedicated sign-in page — do NOT open /@manage first while still a guest; /@manage is the admin shell and will show errors such as User invalid / not an admin without a prior admin login). Confirm the styled login form is visible with username and password fields.\n - Sign in with username exactly `admin` and password exactly `CloudShelf8!`. Wait until the authenticated admin UI is available (redirect away from the login form into manage dashboard or the main file browser).\n - Only after this successful admin login, open the file browser / homepage listing (leave manage and go to the main file list if needed) so storages under `/` are visible, including `public`.\n - Open the `public` storage/folder, then open the `docs` folder inside it. Wait for the listing to finish.\n - Confirm a file named exactly `hello.txt` is listed inside `/public/docs`.\n - 'Final verdict (tighten): PASS only if BOTH are true: (1) admin login with `admin` / `CloudShelf8!` succeeded via /@login, and (2) navigating `public` → `docs` shows `hello.txt` listed with no permission/load error for this path. FAIL only if this admin navigation into `/public/docs` clearly fails in the UI (login rejected for these credentials, or `docs`/`hello.txt` cannot be opened/listed after a correct admin session). Do not FAIL for guest-path issues unrelated to this admin check.\n\n '\n"} {"case_id": "sweeper-007", "slug": "ampache", "repo": "https://github.com/ampache/ampache", "base_commit": "aa3484e07322ea486109510752b11bf595f2e841", "reference_commit": "7dab6a3fc99e6a213deb1930628cfa13f4766270", "task_scoped": "Find and fix issues in Ampache’s Smart Playlist management.", "task_specified": "Fix Ampache Smart Playlist rename via the web Edit dialog so the new name persists after Save. Baseline fails because the playlist id from the form is passed as a string into a constructor that requires an int under strict_types, causing a TypeError that prevents the rename from sticking; after the fix the renamed title remains in the Smart Playlists list.", "pr": 4426, "issue": null, "workflows": "workflows:\n- id: target-smart-playlist-rename-via-edit-dialog\n category: target\n purpose: 'Renaming a Smart Playlist through the Ampache web edit dialog must persist after the EditObjectAction int-cast fix.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/login.php and wait until the real Ampache login page is visible (Ampache logo/branding and styled login form — not a bare PHP error or empty page). Sign in with username priya-shah and password VinylGate8!maple using only normal UI typing and clicks (no page-context fetch/XHR/API shortcuts). Wait until the signed-in Ampache UI appears (sidebar navigation visible).\n\n '\n - 'In the left sidebar, expand/open the Playlists section if needed, then click the \"Smart Playlists\" link (sidebar id sb_home_playlist_smartPlaylist, URL browse.php?action=smartplaylist). Wait until the Smart Playlists browse table/list is visible and contains the seeded list named exactly \"Rename Me Smart\".\n\n '\n - 'On the \"Rename Me Smart\" row, click the Edit control (edit icon / link whose onclick opens showEditDialog for type search_row; title \"Smart Playlist Edit\"). Wait until the modal dialog \"Smart Playlist Edit\" appears with a Name text input (form field name=\"name\").\n\n '\n - 'Clear the Name field and type the unique new name: Renamed Smart Core4426. Click the dialog Save button (not Cancel). Wait for the dialog to close and the Smart Playlists list/row to refresh.\n\n '\n - 'Final verdict — PASS only if the Smart Playlists list clearly shows the new name \"Renamed Smart Core4426\" (the rename stuck). Final verdict — FAIL if after Save the list still shows only \"Rename Me Smart\", OR the name did not update, OR a PHP TypeError / fatal / error page appeared instead of a successful rename. Do not FAIL for unrelated login/asset issues if the rename itself clearly succeeded.\n\n '\n- id: preservation-save-as-smart-playlist-from-search\n category: preservation\n purpose: 'Saving a search as a new Smart Playlist (save_as_smartplaylist path, not the edit dialog) must keep working.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/login.php and wait for the Ampache login UI. Sign in with username priya-shah and password VinylGate8!maple using only normal UI actions (no page-context fetch/XHR/API shortcuts). Wait for the signed-in main UI with sidebar.\n\n '\n - 'In the sidebar Search section, open Song search (link to search.php?type=song, e.g. sb_home_search_song). Wait until the \"Search Ampache...\" form is visible with the \"Save as Smart Playlist\" button (id savesearchbutton).\n\n '\n - 'Click \"Save as Smart Playlist\". Wait for a confirmation page/message that a Smart Playlist was saved (wording like \"Your search has been saved as a Smart Playlist\" / \"No Problem\").\n\n '\n - 'Optionally follow the confirmation link or navigate via sidebar to Smart Playlists (browse.php?action=smartplaylist) and confirm a newly created Smart Playlist appears (auto-named, typically including the username \"priya-shah\").\n\n '\n - 'Final verdict — PASS if Save as Smart Playlist succeeded (confirmation shown and/or a new Smart Playlist is listed). Final verdict — FAIL only if that Save as Smart Playlist action completed and Ampache showed a clear failure / fatal error with no new Smart Playlist created. Do not FAIL for unrelated login or asset issues.\n\n '\n"} {"case_id": "sweeper-008", "slug": "anchor-cms", "repo": "https://github.com/anchorcms/anchor-cms", "base_commit": "7ddb50a9066a97c3f49caa86f3ab4272b8c3bcec", "reference_commit": "a3dff725240d25911b46099652e9176731089f5f", "task_scoped": "Find and fix issues in Anchor CMS’s custom site variable management.", "task_specified": "Fix Anchor CMS custom site variable editing: Changing the value of an existing custom variable and saving does not persist the new value. Saving a new value for a custom variable should keep that value when the variable is reopened.", "pr": 1266, "issue": 1259, "workflows": "workflows:\n- id: custom-variable-value-persists-on-edit\n category: target\n purpose: Editing an existing custom site variable value must persist after save and reopen.\n steps:\n - Navigate to http://127.0.0.1:13200/index.php/admin/login\n - Wait until the Anchor CMS admin login form is visible with Username and Password fields and styled admin chrome (CSS/logo loaded, not a bare text shell).\n - Type \"petra.shaw\" into the Username field.\n - Type \"limeGrove6!\" into the Password field.\n - Click the Login button and wait until the admin UI loads (admin top nav with Posts / Pages / Extend, URL leaves /admin/login).\n - Open http://127.0.0.1:13200/index.php/admin/extend/variables and wait until the Site Variables list is visible.\n - Confirm the list shows the seeded variable named \"greeting\" with value text \"Hello Anchor\".\n - Open the greeting variable for editing (click the greeting row/link so the URL is /index.php/admin/extend/variables/edit/custom_greeting).\n - Wait until the edit form shows Name \"greeting\" and Value \"Hello Anchor\".\n - Clear the Value textarea and type exactly \"Hello Quillmere\".\n - Keep the Name field as \"greeting\" (do not rename).\n - Click the Update button and wait for the response (variables list or success flash such as \"Your variable was updated\").\n - Re-open http://127.0.0.1:13200/index.php/admin/extend/variables/edit/custom_greeting and wait until the edit form is visible again.\n - Final verdict. FAIL only if the edit form is open for greeting AND the Value field still shows \"Hello Anchor\" (the new value did not persist). PASS only if the same edit form shows Value exactly \"Hello Quillmere\" (and not \"Hello Anchor\"). If login failed, the variables list/edit form never opened, or the result is ambiguous, do not guess—treat as setup failure rather than product PASS/FAIL. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preserve-create-custom-variable\n category: preservation\n purpose: Creating a new custom site variable must still succeed and appear in the variables list.\n steps:\n - Navigate to http://127.0.0.1:13200/index.php/admin/login\n - Wait until the Anchor CMS admin login form is visible with Username and Password fields.\n - Type \"petra.shaw\" into the Username field.\n - Type \"limeGrove6!\" into the Password field.\n - Click the Login button and wait until the admin UI loads.\n - Open http://127.0.0.1:13200/index.php/admin/extend/variables/add and wait until the Create Variable form is visible with Name and Value fields.\n - Type \"hoursnote\" into the Name field.\n - Type \"Desk hours\" into the Value textarea.\n - Click the Save button and wait for the response.\n - Open http://127.0.0.1:13200/index.php/admin/extend/variables and wait until the variables list loads.\n - Final verdict. PASS only if the variables list visibly includes a variable named \"hoursnote\" with value text \"Desk hours\" (or the success flash \"Your variable was created\" plus that list entry). FAIL if the create form was submitted while signed in but hoursnote/Desk hours never appears in the list. If login or the create form cannot be reached, treat as setup failure rather than product PASS. Do not use fetch/XHR/API/database reads for this judgment.\n"} {"case_id": "sweeper-009", "slug": "answer", "repo": "https://github.com/apache/answer", "base_commit": "682811f769f4db6d24a0d1749901d95c2d93a7eb", "reference_commit": "43a91313d8b323b5f79a0e5e69b69a244a2468f3", "task_scoped": "Find and fix issues in Apache Answer’s answer management.", "task_specified": "Fix Apache Answer so accepting an answer works when short-id permalinks are enabled. On a question opened via a short /questions/ URL, clicking Accept must mark the answer Accepted and must not show Answer do not found. Accepting an answer under long-id permalinks must still work.", "pr": 1544, "issue": 1541, "workflows": "workflows:\n- id: target-accept-answer-with-short-permalinks\n category: target\n purpose: With short-id permalinks enabled, accepting an answer on a question must succeed and mark the answer Accepted instead of showing Answer do not found.\n steps:\n - Open http://127.0.0.1:13200/users/login and wait until the Apache Answer email/password login form is visible. If already signed in, open http://127.0.0.1:13200/users/logout first, then return to the login page.\n - Type email `siteadmin@communityanswers.local` and password `SiteAdmin#2024` into the login fields using normal keyboard input (do not use page-context fetch/XHR/API shortcuts). Click the Log in / Login button and wait until a logged-in Answer page appears (home/questions chrome with the admin account available).\n - Open http://127.0.0.1:13200/admin/seo and wait for the Admin SEO settings form with a Permalink select control.\n - In the Permalink select, choose the short-id option whose label/value is `/questions/D1D1` (permalink value 4). Submit/save the SEO form with the visible save/update button and wait for a success toast or confirmation that settings were updated.\n - Open http://127.0.0.1:13200/ and wait for the question list. Find and open the seeded question titled exactly `What is a tag?` (click its title link). Wait until the question detail page shows the question title and at least one answer body.\n - Confirm the URL path uses a short question id form under `/questions/` (short alphanumeric id, not a long numeric id like `10010000000000001`). Locate the answer under the question and find the green Accept control (button/label text `Accept`, not already `Accepted`).\n - Click the Accept button for that answer using a normal UI click and wait for the page response (toast/modal and/or button state update).\n - 'Final verdict — PASS only if BOTH are true: (1) no visible error toast/modal contains the exact text `Answer do not found`, and (2) the Accept control for that answer now shows `Accepted` (accepted state). FAIL if a visible error toast/modal contains `Answer do not found`, OR the answer remains unaccepted with the Accept button still showing `Accept` after the click, OR a server/error page blocks the accept action.'\n- id: preservation-accept-answer-with-long-permalinks\n category: preservation\n purpose: After switching SEO permalinks back to long question ids, accepting an answer must still succeed and mark the answer Accepted.\n steps:\n - Open http://127.0.0.1:13200/users/login if needed and sign in with email `siteadmin@communityanswers.local` and password `SiteAdmin#2024` using normal UI input. Wait until logged in.\n - Open http://127.0.0.1:13200/admin/seo and wait for the Admin SEO settings form with a Permalink select control.\n - In the Permalink select, choose the long-id option whose label/value is `/questions/10010000000000001` (permalink value 2). Submit/save the SEO form with the visible save/update button and wait for a success toast or confirmation that settings were updated.\n - Open http://127.0.0.1:13200/ and open the seeded question titled exactly `What is reputation and how do I earn them?`. Wait until the question detail page shows that title and an answer body. If the answer is already labeled `Accepted` and there is no Accept button, do not fail — that is already the success state.\n - If an Accept button is visible, click it using a normal UI click and wait for the page response.\n - Final verdict — PASS if no visible error contains `Answer do not found` AND the answer shows `Accepted` (including when it was already Accepted before you clicked). FAIL if `Answer do not found` appears, if a 500/server error appears, or if an Accept button was clicked and the answer stays unaccepted. Do not FAIL only because a leftover run already accepted the answer.\n"} {"case_id": "sweeper-010", "slug": "audiobookshelf", "repo": "https://github.com/advplyr/audiobookshelf", "base_commit": "325469c5a5700ff1b65b35f7169e233518e574b3", "reference_commit": "c009db9f2889d8ccec4437c50ab357c5183226dd", "task_scoped": "Find and fix issues in Audiobookshelf’s library author management.", "task_specified": "Fix Audiobookshelf author rename/merge: Renaming an author onto an existing author name that already shares books must not crash the server on duplicate bookAuthor rows. The merge should succeed (duplicates ignored), show Author merged in the UI, and keep the server available.", "pr": 5256, "issue": 5247, "workflows": "workflows:\n- id: preservation-author-description-update\n category: preservation\n purpose: Editing an author's description (without renaming onto another author) still saves successfully and keeps the server available.\n steps:\n - Open http://127.0.0.1:13200/login and wait until the Audiobookshelf login UI is visible with normal product styling (dark themed form, not a bare unstyled text shell). Confirm the Audiobookshelf logo/icon image is present near the brand text audiobookshelf.\n - Sign in with username exactly NolanVoss and password exactly emberLane#41. Wait until the authenticated library UI loads (bookshelf / library content area visible).\n - 'Open the Authors view for the current library: use the Authors control in the left side rail or bookshelf toolbar (route ends with /bookshelf/authors). Wait until author cards/rows are listed.'\n - Confirm both authors Branderson and Brandon Sanderson are visible in the Authors list (seeded merge scenario must still be intact).\n - Open the edit UI for author Branderson (click the author card / edit control so the author edit modal/form appears with a Name field showing Branderson).\n - Change only the Description field to exactly preservation-author-desc-ok. Do NOT change the Name field. Click Save.\n - Wait a few seconds for a success toast. The usual text is exactly Author updated (not Author merged). If the toast is missed, reopen Branderson and confirm Description shows preservation-author-desc-ok.\n - 'Confirm the app is still reachable: reload or revisit the Authors view and verify author cards still render (including Branderson).'\n - Final verdict — PASS if the Branderson description save kept the Authors UI usable AND you either saw Author updated or reopened Branderson and the Description is preservation-author-desc-ok. FAIL only if an error toast appears, or the Authors/library UI becomes unreachable. If the toast was missed and you cannot reopen Branderson to confirm the description, judge uncertain — do not fail. Do not FAIL for slow UI alone; wait/retry first. Do not change the author name in this workflow.\n- id: target-author-rename-merge-no-crash\n category: target\n purpose: Renaming author Branderson onto existing author Brandon Sanderson must merge successfully without crashing the server.\n steps:\n - Open http://127.0.0.1:13200/login and wait until the Audiobookshelf login UI is visible with normal product styling and the Audiobookshelf logo/icon present (not a bare unstyled text shell).\n - Sign in with username exactly NolanVoss and password exactly emberLane#41. Wait until the authenticated library UI loads.\n - Open the Authors view (/bookshelf/authors via side rail or toolbar). Wait until author cards/rows are listed.\n - Confirm Branderson and Brandon Sanderson are both visible before the rename.\n - Open the edit UI for author Branderson (author edit modal/form with Name field).\n - Change the Name field from Branderson to exactly Brandon Sanderson (matching the existing author). Leave other fields alone. Click Save.\n - Wait several seconds for either a success toast or a clear failure/crash symptom (connection error, page becomes unreachable, login/library no longer loads).\n - 'Reload the Authors view after Save (even if the toast was missed): Branderson should be gone and Brandon Sanderson should remain if the merge worked.'\n - Final verdict — PASS if after this Save the Authors view still loads with Brandon Sanderson present and Branderson absent (merge succeeded; server alive). The Author merged toast confirms that, but do not FAIL only because that exact toast was missed when the list already shows the merge. FAIL if the UI becomes unreachable / connection fails / server no longer serves pages, OR the Save shows Failed to update / Socket disconnected, OR both authors are still present. Do not PASS merely because a toast appeared with a different message. Do not FAIL for slow UI alone before checking the Authors list; retry reload once.\n"} {"case_id": "sweeper-011", "slug": "automad", "repo": "https://github.com/marcantondahmen/automad", "base_commit": "537879321d98c208c3cca38dcaeaf18bb7443a7e", "reference_commit": "ce97894725bf17a46586f45e2f1f9b1e43198057", "task_scoped": "Find and fix issues in Automad’s dashboard search and replace.", "task_specified": "Fix Automad shared-data search and replace: Selecting a Shared search hit and running Replace Selected leaves the Shared field unchanged. Replacing a Shared match should update shared data so the new value appears in search results and Shared settings.", "pr": null, "issue": null, "workflows": "workflows:\n- id: shared-search-replace-updates-sitename\n category: target\n purpose: 'Selecting a Shared / Global Data search hit and running Replace selected must update the shared sitename so a later Search shows the replacement text on that Shared result.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/dashboard/login\n - 'Confirm the Automad dashboard Sign in form is visible (Username or email and Password fields, Sign in control). Confirm dashboard CSS/JS assets load (styled login card, not a bare unstyled HTML shell). If the page is unreachable or shows a PHP fatal error, stop as setup failure (not a product pass/fail).\n\n '\n - 'Sign in with username \"mira-park\" and password \"leafTrail8!\". Submit via the Sign in control until an authenticated dashboard UI loads (sidebar / home navigation). If a first-run Setup Wizard appears, click Finish / dismiss it until the normal dashboard is visible. If login fails, stop as setup failure.\n\n '\n - Navigate to http://127.0.0.1:13200/dashboard/search\n - 'Confirm the Search UI is visible: a Search text input, a Replace text input, and a \"Replace selected\" control. Use only normal UI actions — no DevTools, no fetch/XHR/API calls from the page console.\n\n '\n - 'In the Search input, type exactly: New Project Wait until search results render. Confirm a result card labeled \"Global Data and Files\" is visible and that its field badge/context shows the sitename match for \"New Project\" (highlighted mark or plain text). If that Shared result never appears, search exactly CedarCoveSite and/or open Shared settings. If sitename is already CedarCoveSite (leftover from an earlier replace), do not stop as setup failure — that is already the success state. If neither New Project nor CedarCoveSite appears as the shared sitename, then stop as setup failure.\n\n '\n - 'If sitename is still New Project, check only the checkbox on that \"Global Data and Files\" result card (do not use Select all if other page results are also listed). In the Replace input, type exactly: CedarCoveSite Click \"Replace selected\". Wait for the results list to refresh after the replace request. If sitename is already CedarCoveSite, skip Replace selected.\n\n '\n - 'Clear the Search input, then type exactly: CedarCoveSite Wait for results. Observe whether a \"Global Data and Files\" result shows the marker in the sitename field context.\n\n '\n - 'Optionally open http://127.0.0.1:13200/dashboard/shared and read the visible Sitename field value in Global Data (draft/shared settings form) as supporting UI evidence.\n\n '\n - 'Final verdict: PASS if login and Search UI worked AND the shared sitename is CedarCoveSite (Global Data and Files search hit or Shared settings Sitename). A leftover already showing CedarCoveSite is PASS — do not require seeing New Project first. FAIL only if ALL are true: (1) the Global Data and Files hit for \"New Project\" was visible and its checkbox was checked; (2) Replace selected was clicked with replace text CedarCoveSite; (3) afterward, Search for CedarCoveSite shows no Global Data and Files hit containing that marker, and/or Shared settings Sitename still shows \"New Project\" without the marker (Shared replace did not persist — target bug: shared search result uses a null/empty path so the selected Shared file is omitted from the replace payload). If login or Search UI fails, or neither New Project nor CedarCoveSite is the shared sitename, report setup/environment failure rather than PASS/FAIL on the bug.\n\n '\n- id: page-search-replace-updates-home-title\n category: preservation\n purpose: 'Preserve that Search → Replace selected still updates a normal page hit (homepage title \"Make it Yours\"), proving adjacent non-Shared replace remains intact.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/dashboard/login\n - 'Confirm the Automad Sign in form is visible. If unreachable, stop as setup failure.\n\n '\n - 'Sign in with username \"mira-park\" and password \"leafTrail8!\" until the authenticated dashboard loads. If a Setup Wizard appears, finish/dismiss it. If already signed in from a prior workflow in this phase, continue. If login fails, stop as setup failure.\n\n '\n - Navigate to http://127.0.0.1:13200/dashboard/search\n - 'Confirm Search and Replace inputs and \"Replace selected\" are visible.\n\n '\n - 'In the Search input, type exactly: Make it Yours Wait for results. Confirm a page result card for the homepage (URL \"/\" or title context containing \"Make it Yours\") is visible — not only Global Data and Files. If that page result never appears, stop as setup failure.\n\n '\n - 'Check only the checkbox on that homepage/page result card (not Global Data and Files). In the Replace input, type exactly: LanternHomeTitle Click \"Replace selected\". Wait for the results list to refresh.\n\n '\n - 'Clear the Search input, then type exactly: LanternHomeTitle Wait for results and observe whether a page result (homepage \"/\") shows that marker in title/content context.\n\n '\n - 'Final verdict: PASS only if ALL are true: (1) login/Search UI worked; (2) a homepage page hit for \"Make it Yours\" was selected; (3) after Replace selected, searching for LanternHomeTitle shows a page result whose visible context includes LanternHomeTitle. FAIL only if the page hit was selected and Replace selected was clicked, but a later Search for LanternHomeTitle shows no page hit containing that marker (normal page replace broke). Setup/login/missing initial hit failures are not product FAIL for this preservation check.\n\n '\n"} {"case_id": "sweeper-012", "slug": "babybuddy", "repo": "https://github.com/babybuddy/babybuddy", "base_commit": "6ce518f3612ae1ee8d49de3434aacf48e15c0724", "reference_commit": "b307200149ae92d0d95dfde82e320d5401148dcf", "task_scoped": "Find and fix issues in Baby Buddy’s feeding log management.", "task_specified": "Fix Baby Buddy bottle feeding form validation: Logging a past bottle feeding can fail with a false period-intersection error when a later feeding already exists, because the end time is still treated as now during validation. A bottle feeding with only a past start time should set end equal to start before validation so it saves successfully while normal non-overlapping bottle feedings still work.", "pr": 1017, "issue": 806, "workflows": "workflows:\n- id: target-bottle-feeding-past-start-no-false-overlap\n category: target\n purpose: Logging a past bottle feeding should not fail with a false period-intersection error against a later feeding.\n steps:\n - Open `http://127.0.0.1:13200/login/` and log in with username `NoahBerg` and password `leftSock2`.\n - Open `http://127.0.0.1:13200/feedings/add/` and wait for the feeding form to load. The child should already be selected when only one child exists.\n - 'Create a recent breast feeding that will sit later than the bottle feeding: set Start time to about 30 minutes ago, End time to about 15 minutes ago, choose type `Breast milk` and method `Left breast`, then submit/save the form. Confirm the feeding is added successfully. Remember that breast Start time — the next bottle Start must be earlier than it.'\n - Open `http://127.0.0.1:13200/feedings/bottle/add/` and wait for the bottle feeding form to load.\n - 'Add a bottle feeding that starts before that breast feeding: set Start time to about 60 minutes ago (earlier than the breast Start you just saved), choose type `Formula`, enter amount `4`, then submit/save. Do not put the bottle Start after the breast feeding.'\n - Final verdict - PASS only if that earlier-start bottle feeding is saved successfully and the page shows a success message that a Feeding entry was added (for example containing `Feeding entry` and `added`). FAIL if the page shows `Another entry intersects the specified time period` or any period-intersection validation error, or if the bottle feeding is not added. If the bottle Start you submitted is later than the breast Start, redo the times — do not PASS a save that never crossed the earlier feeding.\n- id: preservation-bottle-feeding-current-still-works\n category: preservation\n purpose: A normal current bottle feeding with no overlapping conflict should still save successfully.\n steps:\n - Open `http://127.0.0.1:13200/login/` and log in with username `NoahBerg` and password `leftSock2`.\n - Open `http://127.0.0.1:13200/feedings/bottle/add/` and wait for the bottle feeding form to load.\n - Leave Start time at the default value already shown on the form (approximately now). Choose type `Formula`, enter amount `3`, then submit/save. Do not edit Start into any past time window.\n - Final verdict - PASS only if the bottle feeding is saved successfully and the page shows a success message that a Feeding entry was added. FAIL if save fails, if a period-intersection error appears, or if no success confirmation is visible.\n"} {"case_id": "sweeper-013", "slug": "bagisto", "repo": "https://github.com/bagisto/bagisto", "base_commit": "6276c3776b15ef8d91ae009bac7c3b873270225b", "reference_commit": "7292d2fa10d43bc5617ce3c15ca6d5a4ef26c83a", "task_scoped": "Find and fix issues in Bagisto’s Admin Data Transfer module.", "task_specified": "Fix Bagisto Admin Data Transfer import file validation: creating an import with a real browser CSV upload fails with a file type validation error. Creating an import with a CSV upload should succeed and open the import detail instead of showing a file type validation error.", "pr": 11045, "issue": 10899, "workflows": "workflows:\n- id: data-transfer-csv-import-accepts-browser-csv\n category: target\n purpose: Admin Data Transfer must accept a real browser CSV upload (text/plain or text/csv) and create the import instead of showing a file validation error.\n steps:\n - Open http://127.0.0.1:13200/admin/login\n - Confirm the Bagisto admin login page is styled (Bagisto logo/theme CSS under /themes or /admin assets present, not a bare PHP error) with email and password fields.\n - Log in with email miraHolt@test.com and password peat6quill using the native login form, then submit.\n - Wait until the authenticated admin UI loads (sidebar/nav such as Dashboard / Catalog / Settings), not the login form.\n - Navigate to http://127.0.0.1:13200/admin/settings/data-transfer/imports/create\n - Wait for the Create Import form with Type, File upload, Action, Validation Strategy, Allowed Errors, and Field Separator controls.\n - Set Type to Tax Rates (or the tax-rates importer option).\n - Leave Action as Create/Update (append) and Validation Strategy as Stop on Errors if already selected; ensure Allowed Errors is a number such as 10 and Field Separator is a comma \",\".\n - 'Using only the native file input (page-context may attach a File to the input; do not call business APIs), upload a CSV named willow_tax_rates.csv with MIME type text/plain and exactly these two lines: identifier,is_zip_range,zip_code,zip_from,zip_to,state,country,tax_rate WILLOW-TX-CA-1,0,*,\"\",\"\",CA,US,8.25'\n - Submit the form using the native Save/Create Import button (not via fetch/XHR).\n - Wait for the post-submit UI: either a success flash and import detail/validate page, or a visible validation error on the file field / form.\n - Do not use fetch, XHR, or page-context HTTP APIs for login, form submit, navigation, or pass/fail judgment. Native file-input attachment only is allowed for the CSV.\n - 'Final verdict: result=fail only if, after successful admin login and submitting the Create Import form with willow_tax_rates.csv (text/plain), the UI still shows a file/format validation error and does not create/open an import record (no success flash / import detail for the new import). result=pass only if that same submit succeeds with a success message and/or navigates to the import detail/validate page for the new import without a file MIME/extension validation error. Do not fail for unrelated login/timeout/selector issues without reaching the create-import submit result. Do not pass merely because the create form rendered if submit still shows a file validation error. Forbidden to use fetch/XHR/page-context HTTP for triggering or judging.'\n- id: admin-catalog-products-list-still-works\n category: preservation\n purpose: Admin Catalog Products listing still loads after login (unrelated to Data Transfer CSV MIME validation).\n steps:\n - Open http://127.0.0.1:13200/admin/login\n - Confirm the Bagisto admin login page is styled with email/password fields.\n - Log in with email miraHolt@test.com and password peat6quill using the native login form, then submit.\n - Wait until the authenticated admin UI loads.\n - Navigate to http://127.0.0.1:13200/admin/catalog/products\n - Wait for the Products listing/datagrid UI (table or empty-state for catalog products), not a 500/login redirect.\n - Confirm the page shows product catalog management chrome (title/breadcrumb such as Products) without a fatal error.\n - Do not use fetch, XHR, or page-context HTTP APIs for login, navigation, or pass/fail judgment.\n - 'Final verdict: result=pass only if, after successful admin login, the Catalog Products page loads with visible products UI (datagrid/empty state/product management chrome). result=fail if login fails, the page is a 500/exception, or the products listing never appears. Forbidden to use fetch/XHR/page-context HTTP for triggering or judging.'\n"} {"case_id": "sweeper-014", "slug": "bolt", "repo": "https://github.com/bolt/core", "base_commit": "e75391eb701dee42c0e6a8e4cb061353868dd8f0", "reference_commit": "690695af093b8ef66e3a02a73d257527428d3b13", "task_scoped": "Find and fix issues in Bolt’s password recovery workflow.", "task_specified": "Fix Bolt reset password: submitting Forgot Password for an existing user fatals with TypeError/500 instead of the check-email page. After the fix, submitting an email must show the Password Reset Email Sent success page.", "pr": 3732, "issue": null, "workflows": "workflows:\n- id: target-reset-password-existing-user-shows-check-email\n category: target\n purpose: Submitting the forgotten-password form for an existing seeded user must show the check-email success page instead of a TypeError/500 from buildResetEmail's array type hint.\n steps:\n - Open http://127.0.0.1:13200/bolt/login and wait until the Bolt login page loads with Username/Password fields and a \"Forgot Password\" control (repo-native Bolt admin login UI, not a blank/error page).\n - Click \"Forgot Password\" (or open http://127.0.0.1:13200/bolt/reset-password). Wait for the Reset Password request form with an email field and a Submit button.\n - Enter email `cleo@test.com` into the email field and click Submit. Wait for the next page to finish loading.\n - Observe the resulting page. Expected fixed behavior is the success page titled/headed around \"Password Reset Email Sent\" / \"Reset Password\" with text that an email was sent containing a reset link. Broken behavior is an HTTP 500 / TypeError / Exception page mentioning DeepCollection, array, or buildResetEmail, or any generic server-error page instead of the check-email success content.\n - 'Final verdict: FAIL only if after submitting the email the UI shows a server error / TypeError / 500 (or otherwise never reaches the Password Reset Email Sent / check-email success page). PASS only if the check-email success page is clearly shown (Password Reset Email Sent / email-sent confirmation text). Do not FAIL for unrelated login dashboard issues. Do not use fetch/XHR/API/Network/DB as the oracle — decide only from visible page content.'\n- id: preservation-bolt-login-still-works\n category: preservation\n purpose: Normal Bolt admin login with seeded credentials remains available.\n steps:\n - Open http://127.0.0.1:13200/bolt/login and wait for the styled Bolt login form (Username and Password fields).\n - Sign in with username `cleoVann` and password `ridge7plow`. Confirm the Bolt backend/admin UI loads after login (dashboard or admin chrome with navigation / content, not stuck on the login form and not a 500 error page).\n - 'Final verdict: PASS only if cleoVann login succeeds and the Bolt admin UI is visible after sign-in. FAIL if login rejects the seeded credentials or the admin UI does not load. Do not FAIL based on password-reset behavior (that is the core bug). Do not use fetch/XHR/API/Network/DB as the oracle.'\n"} {"case_id": "sweeper-015", "slug": "bookstack", "repo": "https://github.com/BookStackApp/BookStack", "base_commit": "92d15d9cf2ab767732434187b7a42ac581dc9490", "reference_commit": "f4f243585608346de614b0ec177be549e976c4bf", "task_scoped": "Find and fix issues in BookStack’s content import tools.", "task_specified": "Fix BookStack ZIP import run: When a ZIP import fails because the user lacks create permissions, the session is cleared and the user is logged out. The user should remain signed in and see the import permission errors.", "pr": null, "issue": 5754, "workflows": "workflows:\n- id: target-zip-import-permission-error-keeps-session\n category: target\n purpose: A permission-denied ZIP import run must keep the user signed in and show import errors instead of logging them out.\n steps:\n - 'Open http://127.0.0.1:13200/login. Log in with email rita.nguyen@importer.com and password importBay3!. Wait until you leave the login page and the signed-in BookStack UI is visible (for example Books in the navigation, and the page is not the Log in form).\n\n '\n - 'Open http://127.0.0.1:13200/import and wait until the Import page shows a file input for a ZIP and a Validate / upload control. Confirm you are still signed in as RitaNguyen (not on the Log in page).\n\n '\n - 'Use the browser page context to submit the same ZIP import upload path as the Import form: read the CSRF token from the page (input[name=\"_token\"] or meta csrf-token), build a File named core-import-book.zip whose bytes are a ZIP archive containing a single entry data.json with exact UTF-8 text {\"book\":{\"name\":\"Core Import Book\"}}, then POST multipart form-data to http://127.0.0.1:13200/import with credentials included, field _token set to that CSRF token, and field file set to that File. Follow the redirect to the Continue Import page for the uploaded pending import (URL like /import/).\n\n '\n - 'On the Continue Import page, confirm the pending import details mention Core Import Book and a Run Import button is visible. Click Run Import and wait for the navigation / page update to finish.\n\n '\n - 'Final verdict - PASS only if both are true after Run Import: (1) you remain signed in on the Continue Import page (or the same /import/ page) and are NOT redirected to the Log in page / login form, AND (2) the page visibly shows Import Errors including the text \"You are lacking the required permissions to create books.\" FAIL if after Run Import the browser shows the Log in page / login form (session cleared) — that is the permission-error logout bug. FAIL if you cannot reach Run Import or cannot tell whether the session survived.\n\n '\n- id: preservation-admin-zip-import-still-creates-book\n category: preservation\n purpose: An admin ZIP import of a book should still succeed and open the created book.\n steps:\n - 'Open http://127.0.0.1:13200/login. If not already signed in as OwenBlake, log in with email owen.blake@admin.com and password cedarQuill7!. Wait until the signed-in BookStack UI is visible (not the Log in form).\n\n '\n - 'Open http://127.0.0.1:13200/import. Use the browser page context to upload a ZIP the same way as the Import form: read the CSRF token, build a File named preserve-import-book.zip that is a ZIP containing data.json with exact UTF-8 text {\"book\":{\"name\":\"Preservation Admin Book\",\"pages\":[{\"name\":\"Hello Page\",\"html\":\"

Hello from import

\"}]}}, then POST multipart form-data to http://127.0.0.1:13200/import with credentials included, field _token and field file. Follow the redirect to the Continue Import page.\n\n '\n - 'On Continue Import, click Run Import and wait for the result page to load.\n\n '\n - 'Final verdict - PASS only if after Run Import you remain signed in and the UI shows the created book named Preservation Admin Book (for example the book page title/heading or Books list entry). FAIL if you are logged out, or if the book Preservation Admin Book is not visibly created/opened after a successful-looking run.\n\n '\n"} {"case_id": "sweeper-016", "slug": "bugsink", "repo": "https://github.com/bugsink/bugsink", "base_commit": "2328a35e201117ccf1f721ccc71051cc7cc16619", "reference_commit": "e00ebce32c0e5d1d7b56fcabb75b301eb6fc4cd8", "task_scoped": "Find and fix issues in Bugsink’s Auth Tokens management.", "task_specified": "Fix Bugsink auth token description editing: Saving a description on the first of multiple tokens blanks that token because the server reads the last row's description field. Saving a description on the first token should persist that token's own text on the first row.", "pr": 424, "issue": null, "workflows": "workflows:\n- id: target-auth-token-first-description-persists\n category: target\n purpose: On the Auth Tokens page with two tokens, saving a description on the first token must persist that token's own text instead of blanking it from the last row's empty description field.\n steps:\n - 'Open http://127.0.0.1:13200/accounts/login/ and wait until the styled Bugsink login page is fully loaded (cyan/branded background, Bugsink logo image, Login button). Using only normal keyboard/mouse UI actions, sign in with username nora.klein@tokenyard.test and password TokenMark8!willow. Confirm login succeeds and you leave the login form (home or another authenticated Bugsink page with navigation is visible).\n\n '\n - 'Using only normal UI navigation (sidebar/menu link labeled Tokens, or open http://127.0.0.1:13200/bsmain/auth_tokens/ directly), open the Auth Tokens page. Wait until the page shows the heading Auth Tokens, an Add Token button, and exactly two token rows. Each row should currently show an Add description control (empty descriptions). Do not use fetch/XHR/ page-context API calls.\n\n '\n - 'On the first token row only (the top row), click Add description so the inline description editor appears for that row. Clear the description input if needed, then type exactly: First Token Unique Desc Click that same first row''s Save button (the submit control next to the first-row description input). Wait for the page to reload/return to the Auth Tokens list.\n\n '\n - 'Final verdict PASS only if ALL are true on the Auth Tokens list after that save: (1) the first/top token row visibly shows the description text First Token Unique Desc, AND (2) that first row no longer shows Add description as its only description control (it shows the saved text, optionally with Edit). Final verdict FAIL only if that two-token Auth Tokens scene was reached and the first-row save was submitted, AND after reload the first token row does NOT show First Token Unique Desc (for example it still shows only Add description / blank description because the server applied the last row''s empty description value). Do not FAIL for login failure, missing CSS/logo, inability to open Tokens, or wrong-row clicks.\n\n '\n- id: preservation-auth-token-last-description-persists\n category: preservation\n purpose: On the Auth Tokens page with two tokens, saving a description on the last token must still persist that last token's text.\n steps:\n - 'Open http://127.0.0.1:13200/accounts/login/ and wait until the styled Bugsink login page loads (logo + Login). Sign in with username nora.klein@tokenyard.test and password TokenMark8!willow using normal UI actions.\n\n '\n - 'Open the Auth Tokens page via the Tokens navigation link or http://127.0.0.1:13200/bsmain/auth_tokens/. Confirm the Auth Tokens heading and two token rows are visible.\n\n '\n - 'On the last/bottom token row only, click Add description (or Edit if a description already exists). Type exactly: Last Token Unique Desc into that last row''s description input. Click that same last row''s Save button. Wait for the Auth Tokens list to reload.\n\n '\n - 'Final verdict PASS only if the last/bottom token row visibly shows the description text Last Token Unique Desc after save. Final verdict FAIL only if the two-token Auth Tokens scene was reached, the last-row save was submitted, and that last row does not show Last Token Unique Desc. Do not FAIL for login/navigation/asset problems.\n\n '\n"} {"case_id": "sweeper-017", "slug": "cacti", "repo": "https://github.com/Cacti/cacti", "base_commit": "5686785fc4c5c8f604cc0d3d41741a70c0965363", "reference_commit": "0d0fbe6e60335182b9b95c7ce24bb724b420ede4", "task_scoped": "Find and fix issues in Cacti’s device configuration interface.", "task_specified": "Fix Cacti device debug toggle: after clicking Enable Device Debug on the Localhost device edit page, the page still shows Enable Device Debug. After enabling debug, the same page should show Disable Device Debug.", "pr": 6186, "issue": 6187, "workflows": "workflows:\n- id: target-device-debug-enable-toggle\n category: target\n purpose: 'After clicking Enable Device Debug on the Localhost device edit page, the page must show Disable Device Debug. On the buggy build, strict in_array type mismatch leaves the control stuck on Enable Device Debug even though the setting was written.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Open exactly http://127.0.0.1:13200/index.php and wait until the Cacti Login page is visible (Username and Password fields, Login button, and modern theme styles/logo).\n - Type exactly rowanPike into the Username field.\n - Type exactly creek4noll into the Password field.\n - Click the Login button and wait until the authenticated Console UI loads (Console tab visible).\n - 'Open exactly http://127.0.0.1:13200/host.php?action=edit&id=1 and wait until the Device edit page for Localhost is visible (form field Description with value Localhost, and a toolbar action titled Enable Device Debug or Disable Device Debug). The Description text may not be an associated HTML label: identify the visible input by its displayed Localhost value and the Device [edit: Localhost] heading; do not repeatedly use a locator that matches no element.'\n - Confirm the Localhost device edit toolbar currently shows an action titled Enable Device Debug (bug icon / enableDebug). If it already shows Disable Device Debug, refresh the page once; if still Disable, treat as setup contamination and stop with uncertain.\n - 'Execute the Enable Device Debug click as a separate browser action, with no potentially failing preliminary reads in the same command. Confirm that the click call completed successfully. If it throws or an earlier command aborts before the click, the action has NOT happened: correct the locator and actually perform it, or return uncertain. Then wait for the Localhost edit page to settle before inspecting the toolbar; a wait for the same URL alone does not establish a completed transition.'\n - 'On the Localhost device edit page after that click, look only at the Device Debug toolbar control title/class: (A) it now shows Disable Device Debug (class disableDebug), OR (B) it still shows Enable Device Debug (class enableDebug).'\n - 'Final verdict — PASS only if after clicking Enable Device Debug on Localhost the same edit page visibly shows Disable Device Debug (disableDebug). FAIL only if after that click the page still shows Enable Device Debug (enableDebug) while still on Device [edit: Localhost]. Do not FAIL for slow loads or toast text alone. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.'\n- id: preservation-localhost-device-edit-form\n category: preservation\n purpose: 'Editing the seeded Localhost device must still show the Description field with Localhost and adjacent toolbar actions such as Create New Graphs.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Open exactly http://127.0.0.1:13200/index.php and wait until the Cacti Login page is visible.\n - Type exactly rowanPike into the Username field.\n - Type exactly creek4noll into the Password field.\n - Click the Login button and wait until the authenticated Console UI loads.\n - 'Open exactly http://127.0.0.1:13200/host.php?action=edit&id=1 and wait until the Device edit page for Localhost is visible. Confirm identity with the visible Device [edit: Localhost] heading and the input displaying Localhost; a missing HTML label association is a locator problem, not a missing form.'\n - Look at the Description field value and the device toolbar actions (Create New Graphs / Re-Index Device).\n - Final verdict — PASS only if the Description field visibly contains Localhost and at least one of Create New Graphs or Re-Index Device is visible in the device toolbar. FAIL if the Localhost edit form is missing or Description is not Localhost. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-018", "slug": "calibre-web", "repo": "https://github.com/janeczku/calibre-web", "base_commit": "e3dd77d34f0401f8944b065ae82193278bac4205", "reference_commit": "0e83d01bee17b6837cee6c25e5f2c03bdca506dc", "task_scoped": "Find and fix issues in Calibre-Web’s book metadata editor.", "task_specified": "Fix Calibre-Web book tag editing so saving tags that differ only by letter case does not fail with a database UNIQUE constraint error. Saving case-insensitive duplicate tags should keep a single tag and succeed, while distinct tags should still save normally.", "pr": 3670, "issue": null, "workflows": "workflows:\n- id: target-case-insensitive-duplicate-tags-save\n category: target\n purpose: Saving a book with tags that differ only by letter case must succeed without a database UNIQUE error.\n steps:\n - 'Open http://127.0.0.1:13200/login. Log in with username elena-vasquez and password harbourMist9!. Wait until you leave the login form and the signed-in Calibre-Web UI is visible (for example the navbar brand Calibre-Web, and a book list that includes No Signposts in the Sea).\n\n '\n - 'Open http://127.0.0.1:13200/admin/book/1 (Edit metadata for No Signposts in the Sea). Confirm the edit form shows Title No Signposts in the Sea and a Tags text input with id tags.\n\n '\n - 'Clear the Tags field and type exactly: Java, java Then submit/save the edit form (the primary save/submit control on the edit page). Wait for the response page to finish loading.\n\n '\n - 'Final verdict — PASS only if both are true after save: (1) the page does NOT show a danger flash/alert containing Database Error or UNIQUE constraint failed related to tags, AND (2) the book still opens successfully (for example /book/1 or the edit form) with a Tags value that includes Java (case-insensitive duplicates may be collapsed to a single tag). FAIL only if after this save path you clearly see a user-visible database error such as \"Oops! Database Error: UNIQUE constraint failed: tags.name\" (or the same UNIQUE/tags failure in a danger alert). Do not FAIL for unrelated UI chrome or for a successful save that keeps only one of Java/java.\n\n '\n- id: preservation-distinct-tags-still-save\n category: preservation\n purpose: Saving a book with two distinct tags must still persist both tags after reopen.\n steps:\n - 'Open http://127.0.0.1:13200/login. Log in with username elena-vasquez and password harbourMist9! if not already signed in. Confirm the signed-in Calibre-Web UI is visible.\n\n '\n - 'Open http://127.0.0.1:13200/admin/book/1. Clear the Tags field and type exactly: Alpha, Beta Then submit/save the edit form and wait for the response.\n\n '\n - 'Re-open http://127.0.0.1:13200/admin/book/1 and read the Tags field value.\n\n '\n - 'Final verdict — PASS only if both are true: (1) the save did not show a Database Error / UNIQUE constraint failed danger alert, AND (2) the Tags field on reopen contains both Alpha and Beta (order may vary; comma separation is fine). FAIL if either tag is missing after reopen, or if a database UNIQUE/tags error appears for this distinct-tag save.\n\n '\n"} {"case_id": "sweeper-019", "slug": "castopod", "repo": "https://github.com/ad-aures/castopod", "base_commit": "63c763f941195b3758c4b91acd8c350a5e7bb9c2", "reference_commit": "732d42923d0d7a66ff1ebd5841458e4205060560", "task_scoped": "Find and fix issues in Castopod’s episode editing and preview workflow.", "task_specified": "Fix Castopod draft episode Preview: after saving a new episode title, the official Preview page still shows the old title. Preview must show the title you just saved so you can check the episode before publishing.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-episode-preview-shows-saved-title\n category: target\n purpose: After saving a new draft episode title, the official Preview page must show the updated title instead of the stale cached title.\n steps:\n - Open http://127.0.0.1:13200/cp-auth/login and wait until the official Castopod login page is visible, including the Castopod branding/logo and Email plus Password fields. If already signed in, continue.\n - Log in with email remy@test.com and password Pewter9latch using the Email and Password fields, then submit the Login button. Wait until the official Castopod Admin dashboard or another authenticated admin page loads. If login never succeeds, this is setup/evaluation failure, not a product FAIL.\n - Open http://127.0.0.1:13200/cp-admin/podcasts/1/episodes/1/edit and wait until the official Edit episode page is visible. Confirm the Title input value is exactly Original Draft Title ALPHA, the heading Edit is visible, and a Preview link is visible in the draft-mode banner.\n - Click the Preview link in the draft-mode banner and wait until the official episode preview page loads. Confirm the visible episode heading is exactly Original Draft Title ALPHA and the page still shows it is a preview / not published. This first preview visit is setup and must succeed on both baseline and reference.\n - Return to http://127.0.0.1:13200/cp-admin/podcasts/1/episodes/1/edit. In the Title field, replace the value with exactly Corrected Draft Title OMEGA. Do not change the permalink/slug. Click the Save episode button and wait until the edit page finishes reloading with the success message Episode has been successfully updated!\n - Click the Preview link in the draft-mode banner again (full navigation to the official preview page, not a stale tab). Wait until the official episode preview page is visible, including the large episode heading and the preview banner.\n - Final verdict — decide only from the official Castopod episode preview page. Do not use fetch, XHR, page-context HTTP, DevTools, Network, API JSON, logs, or the database. PASS only if the visible episode heading is exactly Corrected Draft Title OMEGA and Original Draft Title ALPHA is not shown as the episode title. FAIL only if the preview page loaded successfully and the visible episode heading is still Original Draft Title ALPHA (the saved title was not shown). If login, the edit form, Save episode, or the preview page never appeared, this is setup/evaluation failure, not a product FAIL.\n- id: preservation-episode-edit-persists-title\n category: preservation\n purpose: Saving a draft episode title through the official Edit episode form still persists on the edit form after reload.\n steps:\n - Open http://127.0.0.1:13200/cp-auth/login and wait until the official Castopod login page is visible, including the Castopod branding/logo. If already signed in, continue.\n - Log in with email remy@test.com and password Pewter9latch using the Email and Password fields, then submit. Wait until an authenticated Castopod Admin page loads.\n - Open http://127.0.0.1:13200/cp-admin/podcasts/1/episodes/2/edit and wait until Edit and the Title field are visible. The seeded Title is Original List Title DELTA. If it already shows Preserved List Title SIGMA (leftover from an earlier try), do not treat that as setup failure — that is already the saved title. Do not open episodes/1 — that draft is for target only.\n - If Title is still Original List Title DELTA, replace it with exactly Preserved List Title SIGMA, click Save episode, and wait for the page to finish reloading. If Title is already Preserved List Title SIGMA, leave it (optional Save is fine). Do not change the permalink/slug.\n - Final verdict — decide only from the official Edit episode UI. Do not use fetch, XHR, page-context HTTP, DevTools, Network, API JSON, logs, or the database. PASS if the Title input value is exactly Preserved List Title SIGMA (including when it was already SIGMA before this visit). The Episode has been successfully updated! toast confirms a fresh save, but do not FAIL or use uncertain only because that toast was missed when Title is already SIGMA. FAIL only if after a save the Title is still Original List Title DELTA (or any value other than SIGMA). If login or the editor never loaded, this is setup/evaluation failure, not a product FAIL.\n"} {"case_id": "sweeper-020", "slug": "changedetection.io", "repo": "https://github.com/dgtlmoon/changedetection.io", "base_commit": "a27265450c34617c107a52d39f14310beb1b4a51", "reference_commit": "b74b76c9f9c8fbbe62ff1c9f571b40b68c543976", "task_scoped": "Find and fix issues in changedetection.io’s watch configuration.", "task_specified": "Fix changedetection.io watch recheck interval editing so a custom interval with all time fields empty or zero is rejected by the server. Saving a watch with Use global settings for time between check turned off and Weeks/Days/Hours/Minutes/Seconds all empty or zero should show a visible validation error that at least one time interval must be specified, and should not update the watch.", "pr": 3427, "issue": 843, "workflows": "workflows:\n- id: target-custom-recheck-interval-requires-time-value\n category: target\n purpose: Saving a watch with custom recheck interval but all time fields empty/zero must show a validation error instead of updating the watch.\n steps:\n - ? Open http://127.0.0.1:13200 and wait until the changedetection.io watch list page is visible with the \"Add a new web page change detection watch\" form. Confirm styled UI (not a bare-text page)\n : CSS-styled header/menu and the add-watch form are present.\n - In the add-watch URL field, enter exactly `https://example.com/core-recheck-interval` and click the Watch / submit control that adds the watch without opening edit first. Wait until the watch list shows a row containing `example.com/core-recheck-interval` (or a truncated form of that URL).\n - Open the Edit page for that newly added watch (click its Edit link). Wait until the watch edit form is visible, including the checkbox labeled like `Use global settings for time between check` and the Weeks/Days/Hours/Minutes/Seconds interval fields.\n - Uncheck `Use global settings for time between check` so the watch uses a custom interval. Clear or set Weeks, Days, Hours, Minutes, and Seconds all to empty or `0`. Do not leave any positive interval value.\n - Click the Save button on the edit form and wait for the page to finish navigating or re-rendering.\n - 'Final verdict — PASS only if all of the following are true after Save: (1) the UI still shows the watch edit form for this watch (or clearly remains on the edit flow), (2) a visible validation error appears whose text includes `At least one time interval`, and (3) there is no success flash/message saying the watch was updated (for example `Updated watch.`). FAIL if Save succeeds with an `Updated watch` (or equivalent success) message, if the app returns to the watch list without that validation error, or if the empty/zero custom interval is accepted.'\n- id: preservation-custom-recheck-interval-with-minutes-still-saves\n category: preservation\n purpose: A custom recheck interval with a valid Minutes value must still save successfully.\n steps:\n - Open http://127.0.0.1:13200 and wait until the changedetection.io watch list page is visible with the add-watch form.\n - In the add-watch URL field, enter exactly `https://example.com/preserve-recheck-interval` and click the Watch / submit control that adds the watch. Wait until the watch list shows that URL.\n - Open the Edit page for that newly added watch. Wait until the edit form shows the `Use global settings for time between check` checkbox and the interval fields.\n - Uncheck `Use global settings for time between check`. Set Minutes to exactly `5`, and set Weeks/Days/Hours/Seconds to `0` or empty.\n - Click Save and wait for the result.\n - Final verdict — PASS only if Save succeeds with a visible success confirmation such as `Updated watch.` and the app does not show the validation error `At least one time interval`. FAIL if saving a valid custom Minutes=5 interval is rejected, shows that validation error, or otherwise fails to update the watch.\n"} {"case_id": "sweeper-021", "slug": "chevereto", "repo": "https://github.com/chevereto/chevereto", "base_commit": "6364b152c0a9d8786d621189c7401d2bd3d1fd6e", "reference_commit": "e0f06f36eba9b031b95f90f406f8967567621612", "task_scoped": "Find and fix issues in Chevereto’s image viewer and image actions.", "task_specified": "Fix Chevereto image delete URL: opening the official delete link shows a server error and the image remains. The delete URL should remove the image so the viewer no longer shows it.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-delete-url-removes-image\n category: target\n purpose: 'After a guest upload, the official Embed-codes Delete link must actually delete the image instead of showing a server error while the viewer still displays the file.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/upload and wait until the official Chevereto Peafowl upload UI is visible: the styled top bar with the Chevereto logo (not a bare unstyled text shell), the Upload nav item, and the anywhere-upload box with the heading Drag and drop or paste files here to upload plus a big accent Upload button. If this page is missing, unstyled, or a PHP fatal, stop and treat that as a setup problem, not a product pass/fail.'\n - 'Using only the native file input id anywhere-upload-input (it may be visually hidden), attach a tiny PNG named exactly lobby-badge.png. Page-context may attach a File to that existing input and dispatch its change event so the official queue appears — do not call /json, /api, or any other business endpoint via fetch/XHR, and do not write the database. A minimal 1x1 PNG base64 payload is: iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8z8BQDwAEhQGAhKmMIQAAAABJRU5ErkJggg== Wait until the upload queue shows lobby-badge.png and the Upload button is ready.'\n - If the guest checkbox I agree to the terms and privacy policy (id upload-tos) is visible, click it so it is checked. Then click the big accent Upload button (data-action=upload). Wait until the official result shows the heading Upload complete and the Embed codes dropdown (select id uploaded-embed-toggle) is visible. If upload never completes, stop and treat that as a setup problem.\n - In the Embed codes select, choose Viewer link. Read the filled textarea and record that exact viewer URL (it looks like http://127.0.0.1:13200/image/…). Then choose Delete link. Read the filled textarea and record that exact delete URL — it must contain /delete/ after the image id (for example http://127.0.0.1:13200/image/lq/delete/). Keep both URLs.\n - Open the recorded Delete link URL in the same browser. Wait until the page finishes loading. Note whether you see Chevereto's error page with the heading Something went wrong (and Why am I seeing this? / For security reasons) or a post-delete page such as That page doesn't exist / The content has been deleted.\n - Then open the recorded Viewer link URL. Wait until that page finishes loading. Note whether the uploaded image is still shown (title such as lobby badge / lobby-badge, or the image viewer chrome for that file) or the official 404 That page doesn't exist.\n - 'Final verdict — FAIL only if ALL are true: (1) Upload complete and both embed URLs were obtained from the official Embed codes UI; (2) opening the Delete link shows the Chevereto error page Something went wrong (Why am I seeing this? is also typical); AND (3) the Viewer link still shows the uploaded image instead of That page doesn''t exist. That leftover image after a failed delete URL is the bug. PASS only if ALL are true: (1) the same upload + Delete-link path was used; (2) the Delete link does not remain on Something went wrong; AND (3) the Viewer link no longer shows the uploaded image (That page doesn''t exist and/or The content has been deleted). Do not PASS just because upload succeeded. Do not FAIL because the uploader, TOS, or embed dropdown never appeared. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.'\n- id: preservation-upload-viewer-still-works\n category: preservation\n purpose: 'Guest upload and the official image viewer must still work for a file that is not deleted.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/upload and wait until the official Chevereto Peafowl upload UI is visible: styled top bar with the Chevereto logo, the anywhere-upload box (Drag and drop or paste files here to upload), and the accent Upload button. If this page is missing or unstyled, stop and treat that as a setup problem.'\n - 'Using only the native file input id anywhere-upload-input, attach a tiny PNG named exactly window-sill.png. Page-context may attach a File to that existing input only — do not call /json or /api via fetch/XHR. A minimal 1x1 PNG base64 payload (different bytes from lobby-badge.png, so Chevereto will not reject it as Duplicated upload) is: iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR4nGOQi9ryHwAD8gIsFe8/lwAAAABJRU5ErkJggg== Wait until the queue shows window-sill.png.'\n - If the guest checkbox I agree to the terms and privacy policy is visible, check it. Click the accent Upload button. Wait until Upload complete and the Embed codes dropdown are visible.\n - In Embed codes, choose Viewer link. Record that viewer URL, then open it. Wait until the official image viewer loads.\n - Final verdict — PASS only if the viewer page shows the uploaded image (title/name such as window sill / window-sill) with Chevereto Peafowl chrome, and is not a Something went wrong error page and not That page doesn't exist. FAIL only if upload completed and the Viewer link opens a 500 Something went wrong page, a blank/fatal page, or a 404 That page doesn't exist instead of the image. Do not open or use any Delete link in this workflow. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-022", "slug": "chyrp-lite", "repo": "https://github.com/xenocrat/chyrp-lite", "base_commit": "5bcb4261091d904ec2285d28ddf67868f10878f8", "reference_commit": "2cf5d5d80b09b3237b09dfb3603f345cfb8f6648", "task_scoped": "Find and fix issues in Chyrp Lite’s Inject module.", "task_specified": "Fix Chyrp Lite Inject post-filter markers: when a post contains two distinct inject markers, every marker is replaced with the first matched injector payload. Each inject marker should render its own injector payload.", "pr": 345, "issue": null, "workflows": "workflows:\n- id: multi-inject-markers-render-distinct-payloads\n category: target\n purpose: A public post with two distinct Post-filter inject markers must render each injector payload, not replace every marker with the first payload.\n steps:\n - Open http://127.0.0.1:13200/?action=view&url=morning-light-quay\n - Wait until the page finishes loading. Confirm this is the Chyrp Lite blossom-themed blog post page titled \"Morning light on the quay\" (styled page with sidebar, not a bare PHP fatal or installer).\n - Read the main article body text in the post content area. Ignore sidebar navigation link titles.\n - 'Final verdict (tighten): FAIL only if ALL are true — (1) the main article body contains \"Closing notes before the cafes opened for the day.\"; (2) the main article body contains \"The ferry timetable is posted by the gate.\"; (3) the main article body does NOT contain \"Gulls circle the pier posts at noon.\". PASS only if ALL are true — (1) the main article body contains \"Closing notes before the cafes opened for the day.\"; (2) the main article body contains \"The ferry timetable is posted by the gate.\"; (3) the main article body contains \"Gulls circle the pier posts at noon.\". Do not treat sidebar/prev/next link text as evidence. If the page is unreachable, is the installer, or the article body cannot be read, treat as setup failure rather than a product PASS/FAIL on the bug.'\n- id: single-inject-marker-still-renders\n category: preservation\n purpose: A public post with a single Post-filter inject marker must continue to render that injector payload after the inject-marker fix.\n steps:\n - Open http://127.0.0.1:13200/?action=view&url=walk-after-rain\n - Wait until the page finishes loading. Confirm this is the Chyrp Lite blossom-themed blog post page titled \"A short walk after rain\".\n - Read the main article body text in the post content area.\n - 'Final verdict (tighten): PASS only if ALL are true — (1) the main article body contains \"Back home before the streetlamps warmed up.\"; (2) the main article body contains \"Steam rises from a paper cup.\"; (3) the main article body does NOT contain \"The ferry timetable is posted by the gate.\"; (4) the main article body does NOT contain \"Gulls circle the pier posts at noon.\". FAIL if this is the walk-after-rain post page but the expected closing line or steam sentence is missing, or a quay-post inject sentence appears. If the page is unreachable or not the expected post page, treat as setup failure rather than a preservation FAIL tied to the fix.'\n"} {"case_id": "sweeper-023", "slug": "cloudreve", "repo": "https://github.com/cloudreve/Cloudreve", "base_commit": "edd50147e78c29dc6deadd060a695974e558aabf", "reference_commit": "762811d50f41a464ccf84705c4a3a84f71e2c239", "task_scoped": "Find and fix issues in Cloudreve’s file sharing.", "task_specified": "Fix Cloudreve My Shares list: After a shared file is moved to the trash bin, the share still appears as available. A share for a file in the trash bin should be marked as expired.", "pr": null, "issue": 2347, "workflows": "workflows:\n- id: preservation-share-stays-available-while-file-not-trashed\n category: preservation\n purpose: 'While vendor-quote.txt remains in My Files (not in trash), Shared by me must still show that share as available rather than expired.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/session and wait until the official Cloudreve sign-in page is visible with styled UI (logo/branding/theme CSS loaded, not a bare-text shell). The first step is an Email field.\n\n '\n - 'Type exactly nell.briggs@test.com into the Email field. Click the Next / Continue button (login continue). Do not use fetch, XHR, or API shortcuts.\n\n '\n - 'Wait until the Password field appears (title like \"Enter password\"). Type exactly pineLatch5! into the Password field and click Sign in. Wait until you leave the login form and the official file manager or navigation chrome is visible.\n\n '\n - 'Navigate to http://127.0.0.1:13200/shares and wait until the official Shared by me page (maybe in Chinese) lists share cards. Confirm a card named vendor-quote.txt is visible. Do not open site-survey.txt. Do not delete any share from this page.\n\n '\n - 'Look only at the vendor-quote.txt share card on this official Shared by me page. Do not open DevTools, Network, or call APIs.\n\n '\n - 'Final verdict — PASS only if you are on Shared by me after a successful UI login, a vendor-quote.txt card is visible, AND that card does not show Expired (maybe in Chinese) or unavailable status text. This file was not moved to trash in this workflow.\n\n '\n - 'FAIL only if vendor-quote.txt is missing from Shared by me, or if that card shows Expired (maybe in Chinese) or unavailable while the file was not put in trash. Do not FAIL because site-survey.txt was later moved to trash. Do not FAIL for login/setup problems alone. Do not use fetch/XHR for setup, triggering, or scoring.\n\n '\n- id: target-trashed-file-share-marked-expired\n category: target\n purpose: 'After site-survey.txt is moved to the trash bin through the official file manager, Shared by me must mark that file''s share as expired.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/session and wait until the official Cloudreve sign-in page is visible with styled UI (logo/branding/theme CSS loaded, not a bare-text shell).\n\n '\n - 'Type exactly nell.briggs@test.com into the Email field. Click Next / Continue. Then type exactly pineLatch5! into the Password field and click Sign in. Wait until you are signed in. Do not use fetch, XHR, or API shortcuts at any point.\n\n '\n - 'Navigate to http://127.0.0.1:13200/home and wait until the official My Files file manager lists site-survey.txt. Confirm file-manager styling is loaded. This setup step must succeed before judging the share status. Do not open http://127.0.0.1:13200/shares yet. Do not delete a share from Shared by me.\n\n '\n - 'Select the file named exactly site-survey.txt in My Files (single click so it is the selected item). Open its context menu with a normal right-click on that file row (or the official toolbar Delete control / Delete keyboard shortcut). Click Delete (maybe in Chinese). Do not choose any permanent-delete option. Do not delete vendor-quote.txt.\n\n '\n - 'Wait for the official delete dialog titled like Delete objects (maybe in Chinese). The description should say the file will be moved to the trash bin (for example \"Are you sure to move site-survey.txt to trash bin?\"). Leave Permanently delete (maybe in Chinese) unchecked. Click OK to confirm the trash move. Wait until the dialog closes and site-survey.txt is no longer listed in My Files.\n\n '\n - 'Navigate to http://127.0.0.1:13200/shares and wait until the official Shared by me page (maybe in Chinese) lists share cards. After the trash move, the leftover card for that file may still be titled site-survey.txt, or it may show a UUID-like trash name instead (the unfixed product renames the file in trash; the original name is only in restore metadata). Identify that leftover card: it is the share that is not named vendor-quote.txt. Stay on this Shared by me list. Do not open / click through that leftover card (opening it can show a different \"share does not exist or has expired\" message). Refresh the page once if the list looks stale. Judge only whether that leftover list card shows the official Expired badge (English Expired, or Chinese 已失效). Do not treat an empty list as a product fail if the share was removed from Shared by me instead of the file being trash-moved from My Files.\n\n '\n - 'Final verdict — PASS only if site-survey.txt was trash-moved from My Files with Permanently delete unchecked, a leftover share card for that file is still listed on Shared by me (titled site-survey.txt or a UUID-like trash name, not vendor-quote.txt), AND that list card itself shows the official Expired badge (Expired or 已失效) next to the name. FAIL only if that same trash-then-shares path was followed and the leftover list card has no Expired / 已失效 badge. Do not treat the visit/error text \"share does not exist or has expired\" (Chinese 分享不存在或已过期 / 分享不存在或已過期) as the Expired badge; that text appears after opening the share, not as the list-card status. Do not FAIL for login/setup problems, deleting the share from Shared by me, permanently deleting the file, or opening the wrong page. Do not FAIL because vendor-quote.txt still looks available. Do not FAIL because the leftover card title changed from site-survey.txt to a UUID-like trash name. Do not use fetch/XHR for setup, triggering, or scoring.\n\n '\n"} {"case_id": "sweeper-024", "slug": "cmsimple-xh", "repo": "https://github.com/cmsimple-xh/cmsimple-xh", "base_commit": "de14036bbb0230961e68391d1ab87fb99de08a41", "reference_commit": "e7d4390fe4b8978a2b4640935b46a7033fa8d850", "task_scoped": "Find and fix issues in CMSimple_XH’s account recovery.", "task_specified": "Fix CMSimple_XH password forgotten reset so completing a valid reset link saves the new password instead of fatalling with a PHP TypeError from XH_writeFile when no session exists. Completing the reset link should show the password-reset success message and persist the new password.", "pr": 664, "issue": null, "workflows": "workflows:\n- id: password-forgotten-request-email\n category: preservation\n purpose: Submitting the configured security email on the password-forgotten form still shows the reminder-email-sent confirmation without completing the reset link.\n steps:\n - Open http://127.0.0.1:13200/?&function=forgotten\n - Confirm the Password forgotten request form is visible with the email field (xh_email) and Send Reminder (or equivalent) submit control. Do not open any xh_code reset URL in this workflow.\n - Type exactly elsa.quinn@test.com into the email field and submit the form.\n - Observe the resulting Password forgotten page.\n - 'Return Final verdict as compact JSON only: {\"result\":\"pass\"|\"fail\",\"substeps\":[...]}.'\n - Final verdict (tight): result=pass only if the page shows the reminder confirmation that an email with a reset link was sent (valid for 1-2 hours), and there is no PHP TypeError / fatal. result=fail if the form remains without that confirmation, a TypeError/fatal appears, or the page instead shows the later \"password has been reset\" success (that means a reset link was completed — out of scope for this preservation check).\n- id: password-forgotten-reset-save\n category: target\n purpose: Completing the password-forgotten reset link must save a new password and show the reset success message instead of a PHP TypeError from XH_writeFile.\n steps:\n - Open http://127.0.0.1:13200/?&function=forgotten\n - Confirm the Password forgotten page is visible with an email input (name xh_email) and a submit control such as \"Send Reminder\".\n - Type exactly elsa.quinn@test.com into the email field and submit the form.\n - Confirm the page shows that an email with a reset link was sent (text about an email sent / link valid for 1-2 hours). If the form is still shown with no sent confirmation, treat as setup failure (not the target bug).\n - Open http://127.0.0.1:13200/userfiles/last-reset-link.txt in the browser. This is the product-served plain-text reset URL written by the local mail path after the reminder was sent. Read the full http://127.0.0.1:13200/...xh_code=... URL from the page body.\n - Navigate to that exact reset URL (same tab is fine).\n - Observe the resulting page after the reset request finishes.\n - 'Return Final verdict as compact JSON only: {\"result\":\"fail\"|\"pass\",\"substeps\":[...]}.'\n - Final verdict (tight): result=fail only if the reset response shows a PHP TypeError / array_key_exists Argument\n"} {"case_id": "sweeper-025", "slug": "cockpit", "repo": "https://github.com/agentejo/cockpit", "base_commit": "f2fdb59e1cff1fea23d533aef09f3b99ad347289", "reference_commit": "5f01f55a32b68b98d9067b4ab107750abc287194", "task_scoped": "Find and fix issues in Cockpit’s singleton management.", "task_specified": "Fix Cockpit singleton deletion so removing a singleton also clears its persisted data key in storage. After deleting a singleton that had saved field values and recreating a singleton with the same name and fields, the form should open with empty values instead of showing the previous data.", "pr": 1460, "issue": null, "workflows": "workflows:\n- id: singleton-delete-clears-persisted-data\n category: target\n purpose: 'Deleting a Cockpit singleton must also clear its persisted data key so recreating the same singleton name does not reopen with stale field values.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Navigate to http://127.0.0.1:13200/auth/login\n - Wait until the Cockpit login page is fully styled (style.css / logo-plain background / favicon) and shows Username, Password, and the Authenticate button — not a bare unstyled text shell or PHP fatal.\n - Log in with username admin and password admin using the normal login form, then wait until the authenticated Cockpit admin shell is visible (top/side navigation including Modules / Singletons, not the login form).\n - Open Singletons from the Modules menu (or navigate to http://127.0.0.1:13200/singletons). Wait until the Singletons list shows the seeded entry labeled Site Settings (name sitesettings).\n - Open the Site Settings form (click the Site Settings card/label or the Form action) and wait until the Title text field is visible.\n - Confirm the Title field currently contains the exact seeded value STALE_TITLE_MARKER. If that marker is missing, treat as setup/seed failure rather than a product PASS/FAIL for this bug.\n - Go back to the Singletons list (http://127.0.0.1:13200/singletons). Open the Site Settings row menu / dropdown and choose Delete. Confirm the Are you sure? dialog. Wait until a Singleton removed success notification appears and Site Settings is gone from the list (empty state / No singletons is OK).\n - Click Add Singleton. Enter Name exactly sitesettings and Label exactly Site Settings. Add a Text field with field name exactly title and field Label exactly Title. After the final input edit, move focus away and wait at least 500 ms BEFORE clicking Save so the form binding settles. Wait for Saving successful. Reopen the singleton schema through its UI and verify the saved Name sitesettings, field name title, field Label Title, and Text type. If any differ, correct the schema through the UI, blur and wait before Save again. Do not judge the stale-data bug using an unidentified blank input.\n - Open the form for the verified sitesettings singleton using Show form or Form. Handle a visible existing-editor lock using UNLOCK if required. Wait until the specifically labeled Title field is visible. A blank unlabeled text box is not sufficient proof that the required title field was recreated.\n - 'Final verdict — FAIL only if ALL of the following bug-specific evidence are true on this delete → recreate → reopen path: (1) the Title input visibly contains STALE_TITLE_MARKER again; AND (2) the scene is the recreated sitesettings form after a successful delete (not login failure, and not the pre-delete form skipped). PASS only if ALL of the following fix-specific evidence are true: (1) the Title input is empty / blank (no STALE_TITLE_MARKER text); AND (2) the form is clearly the recreated sitesettings singleton with a Title field. If login, Singletons navigation, delete confirmation, recreate/save, or the final form cannot be completed, treat as setup/navigation failure rather than a product PASS or FAIL for the stale-data bug.\n\n '\n- id: singleton-form-save-reopen-persists\n category: preservation\n purpose: 'Saving a non-empty Title on a singleton form must still persist when the form is reopened (adjacent singleton data path must keep working).\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Navigate to http://127.0.0.1:13200/auth/login\n - Wait until the styled Cockpit login page is visible. If already authenticated, continue; otherwise log in with username admin and password admin and wait for the admin shell.\n - Open Singletons and create a separate preservation singleton named preserve_title_settings (Label Preserve Title Settings) with a Text field named title and Label Title. Do not reuse sitesettings, which the target workflow deletes and recreates. If this preservation fixture already exists from a prior attempt, verify its schema through the UI. After the final schema edit, blur and wait at least 500 ms BEFORE Save, then reopen the schema to verify the saved names/type.\n - Open the Preserve Title Settings / preserve_title_settings form and wait for the labeled Title field. Resolve a visible existing-editor lock through UNLOCK if needed.\n - Change the Title field to exactly PRESERVE_TITLE_OK using normal UI input. Move focus away, wait at least 500 ms BEFORE clicking Save, and confirm the field still contains the desired value. Then click Save and wait for Saving successful. An immediate DOM input value or a wait only after Save does not establish that the form binding was ready before submission.\n - Navigate away to the Singletons list, then reopen that same preserve_title_settings form so its Title is loaded anew. Wait for the labeled field before reading it.\n - 'Final verdict — PASS only if after reopen the Title input shows exactly PRESERVE_TITLE_OK. FAIL if Title reverts to a previous value, is empty, or still shows only STALE_TITLE_MARKER instead of PRESERVE_TITLE_OK after this save+reopen path. If login, Singletons, or the form cannot be reached/saved, treat as setup/navigation failure rather than a product PASS.\n\n '\n"} {"case_id": "sweeper-026", "slug": "concretecms", "repo": "https://github.com/concretecms/concretecms", "base_commit": "d482717affefc770bffc5eefe7b264c5917dee09", "reference_commit": "3926e2925554964b6a505ab67d8077324ecc52c2", "task_scoped": "Find and fix issues in Concrete CMS’s page type composer configuration.", "task_specified": "Fix Concrete CMS page type composer form controls: Adding a control that already exists on the page type silently creates a duplicate. The form editor should reject the duplicate add so a second identical control row is not created.", "pr": 12916, "issue": 12917, "workflows": "workflows:\n- id: duplicate-page-type-composer-control\n category: target\n purpose: 'Verify that adding the same Page Type Composer form control twice is rejected in the Form editor UI instead of silently creating a duplicate row.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/index.php/login\n - 'Confirm the Concrete CMS login page loads with styled Atomik/Concrete UI (username and password fields, not a bare PHP error or install wizard). If unreachable or broken, stop as setup failure (not product pass/fail).\n\n '\n - 'Sign in with username elenaVoss and password quillBay6! (use the username field value \"elenaVoss\", not the email address). Submit the login form via Sign In.\n\n '\n - 'Confirm you reach an authenticated site with the Concrete toolbar and/or Dashboard access. If login fails, stop as setup failure.\n\n '\n - 'Open Dashboard → Pages & Themes → Page Types (http://127.0.0.1:13200/index.php/dashboard/pages/types). Confirm the list includes a page type named Page.\n\n '\n - 'Open Form for the Page page type (link/button labeled Form / Edit Form; URL contains /dashboard/pages/types/form). Confirm the composer form editor shows sets such as Basics and Content, and that Basics already lists Page Name (Name core page property). Count how many Page Name rows exist across Basics and Content before the next step.\n\n '\n - 'In the Basics set, click the plus (+) Add Form Control control to open the Add Form Control dialog.\n\n '\n - 'In the dialog, open the Built-In Property tab and click Name (shown as Page Name) — the same control already present in Basics — to attempt creating a duplicate. Wait for the UI to settle after the click (loader may appear; dialog may stay open or an error dialog/alert may appear).\n\n '\n - 'Observe the visible result: whether a new Page Name row was added, whether the Add Form Control dialog closed as a successful add, and whether any error text such as \"This control has already been added to this page type.\" is shown.\n\n '\n - 'Final verdict (require both scene and bug-specific evidence). FAIL only if ALL are true: (1) you are on the Page page-type Form editor; (2) a second Add Form Control of the existing Name/Page Name built-in property was attempted; AND (3) the duplicate add is visibly accepted — a new additional Page Name/Name control row appears in Basics or Content compared with the pre-attempt count (dialog closing as a successful add without keeping the row count unchanged also counts as acceptance). PASS only if ALL are true: (1) same Form editor scene; (2) the second Name add was attempted; AND (3) the duplicate is visibly rejected — no additional Page Name/Name row is created after the attempt (Add Form Control dialog may remain open without appending a row, and/or an error/alert containing \"This control has already been added to this page type.\" may appear). Do not PASS merely because a click seemed to do nothing if you never opened the Built-In Property list and clicked Page Name. If login, navigation, or opening Add Form Control fails before the duplicate attempt can be observed, report setup/environment failure rather than PASS/FAIL.\n\n '\n- id: add-distinct-composer-control\n category: preservation\n purpose: 'Preserve that a distinct unused Page Type Composer form control can still be added successfully to a page type form set.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/index.php/login\n - Confirm the Concrete CMS login page loads. If unreachable, stop as setup failure.\n - 'Sign in with username elenaVoss and password quillBay6! (use username \"elenaVoss\", not the email). Confirm an authenticated dashboard UI. If login fails, stop as setup failure.\n\n '\n - 'Open Dashboard → Pages & Themes → Page Types → Form for the Page page type. Confirm the composer form editor with the Basics set.\n\n '\n - 'Click plus (+) Add Form Control on Basics. Add a Built-In Property that is not already listed in Basics or Content — prefer User, otherwise Date/Time or Version Comment. Complete the add (dialog should close and a new row appear).\n\n '\n - 'Confirm the newly chosen distinct control appears as a row in the form set table and there is no rejection that blocks this unused control.\n\n '\n - 'Final verdict. PASS only if the unused distinct built-in property was added and is visibly listed in a form set. FAIL only if adding that unused distinct control is blocked or the new row never appears after a completed add attempt. Setup/login/navigation failures are not product FAIL for this preservation check.\n\n '\n"} {"case_id": "sweeper-027", "slug": "cotonti", "repo": "https://github.com/Cotonti/Cotonti", "base_commit": "351f7c31ea6d6e9afe40c204d40825c8230998e0", "reference_commit": "4e665fb5b523f1552a338d079af84dc74817e017", "task_scoped": "Find and fix issues in Cotonti’s page comments interface.", "task_specified": "Fix Cotonti ajax comments pagination Last link: clicking Last (>>) on a multi-page comments list loads the next page instead of the final page. Clicking Last should show the last page of comments rather than the next page.", "pr": null, "issue": 1878, "workflows": "workflows:\n- id: target-comments-last-page\n category: target\n purpose: 'On the Welcome page comments list with ajax pagination, Last (>>) must jump to the final comments page showing LASTPAGE_ONLY_MARKER. On the buggy build Last acts like Next and shows PAGE2_ONLY_MARKER instead.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/login.php and wait until the Cotonti login form is visible (username and password fields).\n - Type exactly ida-crowe into the username field (name rusername).\n - Type exactly amber7silt into the password field (name rpassword).\n - Click the Login button and wait until an authenticated page loads (site header showing ida-crowe or an Administration link).\n - Open exactly http://127.0.0.1:13200/index.php?e=page&c=news&id=1 and wait until the Welcome page content and the comments section are visible.\n - Scroll to the comments section (comments-container / Comments). Confirm the first comments page shows PAGE1_ONLY_MARKER in at least one comment body.\n - 'In the comments pagination area, >> and > are different controls — do not mix them up. Last is the double-arrow >> inside span.pagenav_last (often titled Last). Next is the single-arrow > inside span.pagenav_next (often titled Next). They sit next to each other and look similar. Identify the control by its span class or title, not by guessing from arrow length. Do not click a page number (2, 3, 4, 5) and do not click the single >. Click only span.pagenav_last >>. Wait until the comments list finishes updating via ajax.\n\n '\n - 'Look only at the visible comment body text after that Last (>>) click. If you see LASTPAGE_ONLY_MARKER, the click was Last. If you see PAGE2_ONLY_MARKER and no LASTPAGE_ONLY_MARKER, Last behaved like Next (the bug). If you instead still see only PAGE1_ONLY_MARKER, the list did not change — click span.pagenav_last >> again, not >.\n\n '\n - 'Final verdict — PASS only if after clicking Last (>>) the comments list visibly shows LASTPAGE_ONLY_MARKER. FAIL only if that Last (>>) click was the double-arrow control and the list shows PAGE2_ONLY_MARKER without LASTPAGE_ONLY_MARKER. If you realize you clicked > or a page number, do not score: reload the Welcome page so PAGE1_ONLY_MARKER is visible again, then click span.pagenav_last >> and score from that click. Do not FAIL for slow loads; use uncertain only if Login or the Welcome comments section cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n- id: preservation-comments-next-page\n category: preservation\n purpose: 'From the first Welcome comments page, Next (>) must still advance to page 2 and show PAGE2_ONLY_MARKER (adjacent pagination must not regress).\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/login.php and wait until the Cotonti login form is visible.\n - Type exactly ida-crowe into the username field (name rusername).\n - Type exactly amber7silt into the password field (name rpassword).\n - Click the Login button and wait until an authenticated page loads.\n - Open exactly http://127.0.0.1:13200/index.php?e=page&c=news&id=1 and wait until the Welcome page and comments section are visible.\n - 'In the comments pagination area, > and >> are different controls — do not mix them up. This check needs Next only: the single-arrow > inside span.pagenav_next (often titled Next). Last is the double-arrow >> inside span.pagenav_last. They sit next to each other and look similar. Identify the control by its span class or title, not by guessing from arrow length. Do not click >> and do not click a page number (2, 3, 4, 5). Click only span.pagenav_next >. Wait until the comments list finishes updating.\n\n '\n - 'Look only at the visible comment body text after that Next (>) click. PAGE2_ONLY_MARKER means Next was correct. LASTPAGE_ONLY_MARKER means you clicked >> by mistake — do not score, do not FAIL. Reload the Welcome page so PAGE1_ONLY_MARKER is visible again, then click span.pagenav_next > (not >>) and read again.\n\n '\n - 'Final verdict — PASS only if after clicking Next (>) the comments list visibly shows PAGE2_ONLY_MARKER. FAIL if PAGE2_ONLY_MARKER is absent after a confirmed Next (>) click (the single-arrow control, not >> and not a page number). If the last click was >> or a page number, reload and click span.pagenav_next > before scoring. Do not FAIL for slow loads; use uncertain only if Login or the Welcome comments section cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n"} {"case_id": "sweeper-028", "slug": "cpg1.6.x", "repo": "https://github.com/coppermine-gallery/cpg1.6.x", "base_commit": "dcacf7ac26f0b58f7cc4a767ed3ec0d331417e14", "reference_commit": "b2d184ea070aa1a2610efd606867c881b3a31778", "task_scoped": "Find and fix issues in Coppermine’s album access control.", "task_specified": "Fix Coppermine private album visibility for guests: get_private_album_set frees the result after the first private album, so only that album is hidden and other private albums remain visible. Guests should not see any Administrators-only private albums on the gallery index.", "pr": 13, "issue": null, "workflows": "workflows:\n- id: guest-hides-all-private-albums\n category: target\n purpose: After an admin logs in and then logs out, guests must not see any Administrators-only private albums on the gallery index.\n steps:\n - Navigate to http://127.0.0.1:13200/login.php\n - Wait until the Coppermine login form is visible (Username and Password fields, and an OK / Login submit control).\n - Type \"Micah-Sol\" into the Username field.\n - Type \"quiltFern4!\" into the Password field.\n - Click the OK / Login submit control and wait until you are signed in (Logout is visible in the menu; the login form is gone). If a brief welcome/redirect page appears, wait until the gallery loads.\n - Navigate to http://127.0.0.1:13200/index.php if you are not already on the gallery home.\n - Confirm the signed-in gallery index shows the public album \"River Walk Prints\" and the administrator-only albums \"Client Proofs\", \"Family Prints\", and \"Darkroom Holds\".\n - Click the Logout link in the site menu (the control whose label contains Logout). Do not open logout.php by typing a URL. Wait until you are a guest again (Login is visible; Logout is gone).\n - Navigate to http://127.0.0.1:13200/index.php as that unauthenticated guest.\n - Wait until the gallery index album listings are visible.\n - Confirm \"River Walk Prints\" is still visible. Inspect the visible album titles for \"Client Proofs\", \"Family Prints\", or \"Darkroom Holds\".\n - Final verdict: FAIL only if the guest index shows \"Family Prints\" or \"Darkroom Holds\" (or both) as a visible album title—that is the private-album forbid-set truncation leak. PASS only if none of \"Client Proofs\", \"Family Prints\", and \"Darkroom Holds\" appear as visible album titles for the guest, while the page still shows \"River Walk Prints\". Do not use fetch/XHR/API/network/DevTools/database as evidence—only album titles visible in the gallery UI. If login, logout, or the gallery index never loads, or River Walk Prints is missing after logout, treat as setup failure rather than product PASS/FAIL.\n- id: preserve-public-album-visible-to-guest\n category: preservation\n purpose: After an admin logs in and logs out, the public album must remain listed for guests on the gallery index.\n steps:\n - Navigate to http://127.0.0.1:13200/login.php\n - Wait until the Coppermine login form is visible.\n - Type \"Micah-Sol\" into the Username field.\n - Type \"quiltFern4!\" into the Password field.\n - Click the OK / Login submit control and wait until you are signed in (Logout visible). If a welcome/redirect page appears, wait until the gallery loads.\n - Navigate to http://127.0.0.1:13200/index.php if you are not already on the gallery home.\n - Confirm the signed-in gallery index shows the public album \"River Walk Prints\".\n - Click the Logout link in the site menu (label contains Logout). Do not type a logout URL. Wait until you are a guest again (Login visible).\n - Navigate to http://127.0.0.1:13200/index.php as that unauthenticated guest.\n - Wait until the Coppermine gallery index page loads.\n - Look for the album titled \"River Walk Prints\" in the visible album list.\n - Final verdict: PASS only if \"River Walk Prints\" is clearly visible as an album title on the guest gallery index. FAIL if that public album title is missing from the page. Do not use fetch/XHR/API/network/DevTools/database as evidence—only visible page content. If login, logout, or the index page fails to load, treat as setup failure rather than product PASS.\n"} {"case_id": "sweeper-029", "slug": "craftcms", "repo": "https://github.com/craftcms/cms", "base_commit": "aa048c29bd8c8a4ec15f2e8d57b85e620e14d348", "reference_commit": "1a3de71bc1f75ee23782e9ff51dcd9cc6148728f", "task_scoped": "Find and fix issues in Craft CMS’s custom field setup and editing interface.", "task_specified": "Fix Content Block field saving in Craft CMS: Saving a Content Block field that has no nested fields selected a second time causes a TypeError and takes down the control panel. Saving an empty Content Block field should succeed and keep the administrator on the field editor.", "pr": null, "issue": 17829, "workflows": "workflows:\n- id: preservation-plain-text-field-save\n category: preservation\n purpose: 'Creating and saving a normal Plain Text field in Settings → Fields must still succeed and remain visible in the official Fields index.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/admin/login and wait until the official Craft CMS Sign In page is visible: title Sign In - Harbor Quill Press, Username or Email, Password, Sign in, and the Powered by Craft CMS logo with styled cp.css. If already signed in to the Dashboard, skip login.\n\n '\n - 'If the Sign In form is showing, type exactly wynnCalder into Username or Email and exactly thatch9quay into Password, then click Sign in. Wait until Dashboard - Harbor Quill Press. If login fails, stop and treat that as a setup problem.\n\n '\n - 'Open exactly http://127.0.0.1:13200/admin/settings/fields and wait until the Fields index is visible (heading Fields, New field button).\n\n '\n - 'If the Fields table already lists a field named exactly Site Tagline, click that name to open its editor. Otherwise click New field and wait until Create a new field is visible. Type exactly Site Tagline into Name. Leave Field Type as Plain Text (the default). Do not switch to Content Block, Matrix, or any other type.\n\n '\n - 'Click the primary Save button. Wait until the save finishes.\n\n '\n - 'Open exactly http://127.0.0.1:13200/admin/settings/fields and wait until the Fields index is visible.\n\n '\n - 'Final verdict — judge only whether the Plain Text field Site Tagline was saved and is listed on the official Fields index. PASS only if Site Tagline appears in the Fields table with type Plain Text (or the editor showed Field saved and reopening the Fields index still lists Site Tagline). FAIL only if saving that Plain Text field shows a TypeError / exception page, or Site Tagline is missing from the Fields index after a successful-looking save. Do not FAIL because Empty Content Block is also listed. Do not FAIL for login problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n- id: target-empty-content-block-second-save\n category: target\n purpose: 'Saving a Content Block field that has no nested fields a second time must not TypeError. The second save should succeed and keep the administrator on the official field editor.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/admin/login and wait until the official Craft CMS Sign In page is visible: title Sign In - Harbor Quill Press, labels Username or Email and Password, a Sign in submit button, the Powered by Craft CMS wordmark/logo, and styled cp.css (not a bare unstyled text shell, not a cookies-must-be-enabled message, and not a JavaScript-must-be-enabled message). If the page is already the signed-in Dashboard, skip login.\n\n '\n - 'If the Sign In form is showing, type exactly wynnCalder into Username or Email and exactly thatch9quay into Password, then click Sign in. Wait until the signed-in Control Panel Dashboard loads (title Dashboard - Harbor Quill Press). If login fails, stop and treat that as a setup problem, not this bug.\n\n '\n - 'Open exactly http://127.0.0.1:13200/admin/settings/fields and wait until the official Fields index is visible (title Fields - Harbor Quill Press, heading Fields, a New field button). Do not use GraphQL, the plugin store, or any other settings screen.\n\n '\n - 'If the Fields table already lists a field named exactly Empty Content Block, click that field name to open its editor and skip the create steps. Otherwise click New field and wait until Create a new field is visible (title Create a new field - Harbor Quill Press). Confirm the Name and Handle inputs and the Field Type control (default Plain Text) are present. If the new-field form never appears, stop and treat that as a setup problem.\n\n '\n - 'If this is a new field (heading Create a new field): type exactly Empty Content Block into Name and wait until Handle is filled (emptyContentBlock or similar). Open the Field Type control (the Field Type menubtn / custom-select labeled Field Type — What type of field is this?) and choose exactly Content Block. Wait until the Content Block settings appear: Field Layout designer and View Mode (Grouped / In a pane / Inline). Do not add any nested fields to the Field Layout. Do not change View Mode. Do not click Save yet.\n\n '\n - 'If this is a new field, open the More actions disclosure next to the primary Save button (aria-label More actions) and click Save and continue editing. Wait until the first save succeeds: a Field saved notification and the editor for Empty Content Block (URL contains settings/fields/edit/, heading is Empty Content Block or Edit Field). The Control Panel must still be usable. If the first save already shows a TypeError / Yii exception / createLayout error, stop and treat that as a setup problem — the first save of an empty Content Block is supposed to succeed.\n\n '\n - 'On the Empty Content Block field editor, click the primary Save button (the submit button labeled Save in the header action-buttons — not Save and add another, not Cancel). Wait until the second save finishes or the Control Panel is replaced by an error page.\n\n '\n - 'Final verdict — judge only the result of that second Save of the empty Content Block field Empty Content Block, after Field Type was Content Block and no nested fields were added. FAIL only if the Control Panel is taken down or the second save shows a PHP TypeError / Yii exception whose message includes createLayout or must be of type array, null given (the empty fieldLayouts config is passed as null). PASS only if the second save succeeds in the official CP: a Field saved notification and the administrator remains on the Empty Content Block editor or the Fields index, with no TypeError and no exception page. Do not PASS merely because the first save worked. Do not FAIL because Handle auto-generated, View Mode stayed Grouped, or the Fields table was empty before creating the field. Do not FAIL for login or a missing New field button — those are setup problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n"} {"case_id": "sweeper-030", "slug": "crater", "repo": "https://github.com/crater-invoice-inc/crater", "base_commit": "c07e44520a97c2bed54918996f61fa7b402c426e", "reference_commit": "2cadcad48565961eb42b0d3bc4d871cafecb1ef8", "task_scoped": "Find and fix issues in Crater’s company settings.", "task_specified": "Fix Crater company settings update so saving notification settings without a currency change is not blocked when the company already has transactions. Changing Send Notifications to a new email on Settings → Notifications and saving must persist that email after a hard reload.", "pr": 821, "issue": null, "workflows": "workflows:\n- id: target-notification-email-persists-without-currency\n category: target\n purpose: Saving Notifications email without changing currency must persist after reload when the company already has transactions.\n steps:\n - Open http://127.0.0.1:13200/login and wait until the Crater login page is fully styled (theme CSS loaded, favicon/branding present, Email and Password fields and a Login button). Do not continue on a bare unstyled text shell.\n - Sign in with email tessa-quinn@test.com and password riverMoss9!. Wait until you reach the signed-in admin app (URL under /admin or dashboard/navigation is visible).\n - Open http://127.0.0.1:13200/admin/settings/notifications and wait until the Notifications settings card is visible with title \"Notifications\", the email field labeled \"Send Notifications to\", and a Save button.\n - Confirm the \"Send Notifications to\" field currently shows exactly notify@example.com. If it does not, treat this as a setup problem (not a product FAIL/PASS for the bug).\n - Clear the email field and type exactly: changed@example.com\n - Click the Save button for the notification email form and wait until the save request finishes (loading ends; a toast may appear).\n - Hard-reload the Notifications settings page: navigate again to http://127.0.0.1:13200/admin/settings/notifications (or full browser refresh) and wait until the \"Send Notifications to\" field is visible again with a loaded value. Do not judge from the in-form value before this reload.\n - Final verdict — FAIL only if after that hard reload the \"Send Notifications to\" field still shows notify@example.com (the new email did not persist). A server/error toast mentioning currency (for example \"Undefined array key \\\"currency\\\"\" or \"Cannot update company currency\") may appear as supporting evidence, but persistence failure after reload is required for FAIL.\n - Final verdict — PASS only if after that hard reload the \"Send Notifications to\" field shows exactly changed@example.com.\n - Do not PASS based only on a success toast before reload. Do not FAIL for login/setup/network/UI-loading problems; only FAIL when the reloaded field clearly remains notify@example.com after saving changed@example.com.\n- id: preservation-preferences-timezone-still-saves\n category: preservation\n purpose: Preferences settings that include the existing company currency must still save and persist when the company already has transactions.\n steps:\n - Open http://127.0.0.1:13200/login and wait until the Crater login page is visible with Email and Password fields.\n - If not already signed in, sign in with email tessa-quinn@test.com and password riverMoss9! and wait until the signed-in admin app is available.\n - Open http://127.0.0.1:13200/admin/settings/preferences and wait until the Preferences settings card is visible with Currency, Default Language, and Time Zone fields, and a Save button in the general preferences form.\n - Confirm Time Zone currently shows Asia/Kolkata (seeded default). Do not change Currency.\n - Using the Time Zone multiselect, change Time Zone to UTC (search/select UTC). Leave other fields unchanged.\n - Click the Save button for the general preferences form (the Save near Currency / Default Language / Time Zone) and wait until the save request finishes.\n - Hard-reload Preferences: open http://127.0.0.1:13200/admin/settings/preferences again (or full refresh) and wait until Time Zone is visible with a loaded value.\n - Final verdict — PASS only if after that hard reload Time Zone shows UTC.\n - Final verdict — FAIL if after reload Time Zone is still Asia/Kolkata, the save clearly failed, or Preferences cannot be saved despite using the seeded admin account.\n"} {"case_id": "sweeper-031", "slug": "cubecart", "repo": "https://github.com/cubecart/v6", "base_commit": "b8302cd4a170d7001d066909c60bffe29aa8fbdd", "reference_commit": "c14eea53739bf5e9e7dc287a3ca1e56fd75cf24a", "task_scoped": "Find and fix issues in CubeCart’s extension configuration interface.", "task_specified": "Fix CubeCart admin module settings so a missing module template does not blank the whole admin page. Opening Extensions → Manage Extensions → Print Order Form (gateway) should keep the admin chrome visible instead of dying with Unable to load template templates/main.php.", "pr": 4230, "issue": 4229, "workflows": "workflows:\n- id: target-print-order-form-admin-not-blank\n category: target\n purpose: Opening the stock Print Order Form gateway module settings must render the CubeCart admin chrome. When Module::fetch() fails to find admin/index.tpl under the module skin, the buggy early return leaves Smarty pointed at the module skin so templates/main.php cannot load and the admin page shows Unable to load template / dies without admin chrome.\n steps:\n - Open exactly http://127.0.0.1:13200/admin.php?_g=login and wait until the CubeCart admin login screen is visible with styled chrome (login box and logo/CSS loaded, not a bare unstyled text shell).\n - Type exactly IvoPell into the username field and mossLatch2! into the password field. Wait at least two seconds, then click the Log In submit button.\n - Confirm you are signed into the admin backend (leave the login form; admin sidebar/header or dashboard chrome is visible). If a welcome/tour popup appears, close/dismiss it with its X or Skip/Close control, then continue.\n - In the admin sidebar, open the Extensions group and click Manage Extensions. Wait until the extensions page is visible (cards and/or marketplace chrome). The marketplace list may take a short time to finish loading; do not leave this page for a different URL. Do not install, buy, or delete any extension.\n - On the Manage Extensions page, find the installed extension card whose name is Print Order Form (use the page search/filter if needed). Click that card's Configure control (cog / title Configure). Wait for the resulting module settings page.\n - 'On the Print Order Form settings page that opened from Configure, observe the visible page: either (A) CubeCart admin chrome with sidebar/header and module context such as the text Print Order Form and/or a General tab, or (B) a page without admin chrome that shows Unable to load template / templates/main.php (possibly inside a debug panel) or is otherwise blank of admin UI.'\n - Final verdict — PASS only if (a) you are signed into admin, AND (b) the Print Order Form settings page opened via Configure shows CubeCart admin chrome including Print Order Form and/or General. FAIL only if (a) is true and that settings page shows Unable to load template / templates/main.php without admin chrome, or otherwise has no admin chrome. Do not FAIL for login/setup problems; use uncertain only if login, Manage Extensions, or the Configure click cannot be completed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail. Do not pass by typing the module settings URL into the address bar.\n- id: preservation-manage-extensions-shows-print-order-form\n category: preservation\n purpose: After login, Manage Extensions must still list the installed Print Order Form card (the extensions list itself, not the module settings page).\n steps:\n - Open exactly http://127.0.0.1:13200/admin.php?_g=login and wait until the CubeCart admin login screen is visible.\n - Type exactly IvoPell into the username field and mossLatch2! into the password field. Wait at least two seconds, then click Log In.\n - Confirm you are signed into the admin backend. Dismiss any welcome/tour popup if present.\n - In the admin sidebar, open the Extensions group and click Manage Extensions. Wait until the extensions page is visible (cards and/or marketplace chrome). The marketplace list may take a short time to finish loading. Do not install, buy, or delete any extension. Do not click Configure / the cog on Print Order Form.\n - Final verdict — PASS only if signed into admin and the Manage Extensions page visibly shows an installed extension card named Print Order Form. FAIL if signed in and Manage Extensions loaded but that card name is missing. Do not FAIL for login/setup problems; use uncertain only if login or Manage Extensions cannot be reached after retries. Do not click through to the Print Order Form settings page. Do not use fetch/XHR/API/database reads for this judgment.\n"} {"case_id": "sweeper-032", "slug": "cypht", "repo": "https://github.com/cypht-org/cypht", "base_commit": "d4a9c43b109d019577b364fa89852264377ca03a", "reference_commit": "9e893732171cdb62176f1156b04bf1ad739774d0", "task_scoped": "Find and fix issues in Cypht’s mail composition preferences.", "task_specified": "Fix Enable exclude auto BCC in Cypht Settings: Saving Settings while the checkbox is checked leaves the setting disabled after reload. Enable exclude auto BCC should remain enabled after Save when the checkbox was checked.", "pr": 2016, "issue": null, "workflows": "workflows:\n- id: target-exclude-auto-bcc-stays-enabled\n category: target\n purpose: Saving Settings while Enable exclude auto BCC is checked must keep that checkbox enabled after reload; baseline posts value 0 and leaves it disabled.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the Cypht login UI is fully styled (Bootstrap layout, Cypht logo/app branding, Username and Password fields — not a bare unstyled text shell).\n\n '\n - 'Using only the native login form (no page-context fetch/XHR/API), enter username `MiraHolt` and password `bayNote7!`, then click Login. Wait until you are signed in (main Cypht chrome with navigation such as Settings / Save / folder menu is visible).\n\n '\n - 'Open Settings via the UI navigation or go to http://127.0.0.1:13200/?page=settings and wait until the Settings page shows general setting rows. Locate the checkbox labeled \"Enable exclude auto BCC\". Confirm it is currently checked (default enabled). If it is unchecked before any Save in this session, treat as setup failure and do not judge the product bug yet — reload Settings once and re-check; only proceed when it starts checked.\n\n '\n - 'Leave \"Enable exclude auto BCC\" checked. Using only a normal click on the Settings page Save button (name/action save_settings), submit Save. Wait until a visible \"Settings updated\" (or equivalent) confirmation appears or the settings form finishes processing.\n\n '\n - 'Open Settings again (navigate away if needed, then http://127.0.0.1:13200/?page=settings). Wait for the Settings page to fully render, then read the checked/unchecked state of \"Enable exclude auto BCC\".\n\n '\n - 'Final verdict — FAIL only if all of the following are true: (1) you were signed in and reached Settings; (2) Enable exclude auto BCC started checked; (3) you clicked Save while it remained checked; (4) after reopening Settings the same checkbox is clearly unchecked/disabled. That is the baseline value=\"0\" save bug. Final verdict — PASS only if after the same checked → Save → reopen Settings path, \"Enable exclude auto BCC\" remains clearly checked/enabled. Do not FAIL for unrelated mail-server empty states, folder load warnings, or CSS-only issues once the checkbox state was clearly observed. Do not use API/fetch/XHR to toggle or read the setting.\n\n '\n- id: preservation-always-bcc-can-be-enabled\n category: preservation\n purpose: Always BCC sending address (value=1 checkbox) must still enable and stay checked after Settings Save.\n steps:\n - 'Open http://127.0.0.1:13200/ and sign in with username `MiraHolt` and password `bayNote7!` via the native login form if not already signed in. Wait for the signed-in Cypht chrome.\n\n '\n - 'Open http://127.0.0.1:13200/?page=settings and wait until Settings general rows are visible. Locate the checkbox labeled \"Always BCC sending address\".\n\n '\n - 'If \"Always BCC sending address\" is already checked, uncheck it and click Save, then reopen Settings so it starts unchecked. Then check \"Always BCC sending address\" so it is enabled, and click the Settings Save button. Wait for Settings updated / form processing to finish.\n\n '\n - 'Reopen http://127.0.0.1:13200/?page=settings and read the \"Always BCC sending address\" checkbox state.\n\n '\n - 'Final verdict — PASS only if after checking Always BCC sending address and saving, reopening Settings shows that checkbox still checked/enabled. Final verdict — FAIL only if that enable → Save → reopen path leaves Always BCC sending address clearly unchecked, or Settings/login is unreachable. Do not judge Enable exclude auto BCC in this workflow.\n\n '\n"} {"case_id": "sweeper-033", "slug": "docmost", "repo": "https://github.com/docmost/docmost", "base_commit": "64ecef09bc145da6ccbfc3914725552d620053dc", "reference_commit": "32c7a16d069f94db85694699e5dba336e9f19eea", "task_scoped": "Find and fix issues in Docmost’s workspace member invitations.", "task_specified": "Fix Docmost workspace invitation acceptance: the invite signup password is hashed twice before storage, so logging in after accepting an invitation fails. Accepting an invitation should store a single password hash so the invited user can log in with that password afterward.", "pr": 773, "issue": null, "workflows": "workflows:\n- id: target-invite-accept-password-login\n category: target\n purpose: After accepting a workspace email invitation, logging out and signing in again with the same password must succeed; baseline fails because acceptInvitation double-hashes the password so login rejects it.\n steps:\n - Open http://127.0.0.1:13200/setup/register (or /login if setup already completed). If the first-time workspace setup form is shown, create the admin workspace with workspace name `Maple Wiki`, admin name `Naomi Clark`, email `naomi.clark@admin.com`, and password `MapleGate8!`, then submit and wait until the signed-in Docmost home/dashboard is visible with Docmost branding (not a bare-text page).\n - If already on the login page instead of setup, sign in with email `naomi.clark@admin.com` and password `MapleGate8!` and wait until the signed-in home/dashboard is visible.\n - Open Workspace Members settings via the UI (Settings → Members, or navigate to http://127.0.0.1:13200/settings/members). Confirm the members/invites page is visible.\n - Invite a new member with email exactly `theo.brandt@invitee.com` using the invite form (role Member/default is fine). Submit/send the invitation and wait until `theo.brandt@invitee.com` appears in the pending invitations list.\n - Sign out completely using the product UI logout/account menu so the admin session ends and the login page is reachable. Do this before opening the invitation link, otherwise the invite URL may keep the admin session and skip the invite signup form.\n - Open Mailpit in the browser at http://127.0.0.1:13200/mailpit/. Find the invitation email for `theo.brandt@invitee.com` (subject mentions invited you to Docmost). Open that message and copy the invitation URL that contains `/invites/` and a `token=` query parameter.\n - Open that invitation URL. On the invite signup form, enter name `Theo Brandt` and password exactly `InviteNest4!`, then submit/join. Wait until signup finishes (home/dashboard or an authenticated Docmost page).\n - Sign out completely using the product UI logout/account menu so the session ends and the login page is reachable.\n - On the login page, sign in with email exactly `theo.brandt@invitee.com` and password exactly `InviteNest4!`.\n - 'Final verdict (tight): FAIL only if the login form remains and the UI shows the authentication error that the email or password does not match (or equivalent wrong-credentials error), proving the invited password was not accepted. PASS only if login succeeds and an authenticated Docmost page for this user is visible (home/dashboard/settings) without that wrong-credentials error. Do not FAIL for setup/navigation mistakes; do not PASS merely because some other page loaded.'\n- id: preservation-admin-password-login\n category: preservation\n purpose: After running the workspace invitation flow, the admin account must still be able to log in with its original setup password.\n steps:\n - Open http://127.0.0.1:13200/setup/register (or /login if setup already completed). If the first-time workspace setup form is shown, create the admin workspace with workspace name `Maple Wiki`, admin name `Naomi Clark`, email `naomi.clark@admin.com`, and password `MapleGate8!`, then submit and wait until the signed-in Docmost home/dashboard is visible. If already set up, sign in with `naomi.clark@admin.com` / `MapleGate8!`.\n - Open Workspace Members settings via the UI (Settings → Members, or navigate to http://127.0.0.1:13200/settings/members). Confirm the members/invites page is visible.\n - Invite a new member with email exactly `sam.lee@invitee.com` using the invite form (role Member/default is fine). Submit/send the invitation and wait until `sam.lee@invitee.com` appears in the pending invitations list.\n - Sign out completely using the product UI logout/account menu so the admin session ends and the login page is reachable.\n - On the login page, sign in with email exactly `naomi.clark@admin.com` and password exactly `MapleGate8!`.\n - 'Final verdict (tight): PASS only if login succeeds and an authenticated Docmost page is visible (home/dashboard or settings) for the admin account, with no wrong-credentials error. FAIL only if the login form remains and shows that the email or password does not match for these admin credentials. Do not FAIL for unrelated navigation issues.'\n"} {"case_id": "sweeper-034", "slug": "dokuwiki", "repo": "https://github.com/dokuwiki/dokuwiki", "base_commit": "53886d96e295c4cf801ca918e00807e259ecad40", "reference_commit": "7e687fd85a40bd8453b39b64bae8e989ab32fd36", "task_scoped": "Find and fix issues in DokuWiki’s media access control.", "task_specified": "Fix DokuWiki media detail ACL checks: The media detail page can grant access based on an exact media-ID ACL rule even when the media namespace ACL denies read. Media detail access should follow the media namespace ACL so a namespace deny blocks the detail page even if an exact-ID allow exists.", "pr": 4648, "issue": 4647, "workflows": "workflows:\n- id: media-detail-namespace-acl\n category: target\n purpose: Verify the media detail page denies access when the media namespace ACL denies read, even if an exact-ID ACL rule allows that media ID.\n steps:\n - Open the DokuWiki media detail page at http://127.0.0.1:13200/lib/exe/detail.php?media=secret:file.png\n - Wait until the themed DokuWiki detail page finishes loading (title area or main content visible; not a blank/error shell).\n - Inspect the main detail content in\n - FAIL only if ALL of the following are true (baseline bug still present): (1) the page does NOT show a main heading or prominent denied message containing \"Permission Denied\"; (2) the page DOES show the media detail success UI for this file, evidenced by a content heading \"file.png\" and/or an .img_detail section (or equivalent media metadata/detail block) for secret:file.png.\n - PASS only if ALL of the following are true (namespace ACL enforced): (1) the page shows a denied state with visible text \"Permission Denied\" in the main content; (2) the success media detail UI is absent — no content heading that presents the image as viewable detail such as \"file.png\" paired with an .img_detail media metadata block for this file.\n - If the detail page fails to load, shows a PHP/fatal error, or the scene cannot be identified, do not guess — treat as setup/environment failure rather than product PASS/FAIL.\n - Final verdict: FAIL only with clear bug evidence that secret:file.png detail is readable despite secret:* deny; PASS only with clear evidence that the same URL shows Permission Denied and not the media detail success UI.\n- id: allowed-namespace-media-detail\n category: preservation\n purpose: Verify media detail pages still open normally for media whose namespace ACL allows read.\n steps:\n - Open the DokuWiki media detail page at http://127.0.0.1:13200/lib/exe/detail.php?media=wiki:sample.png\n - Wait until the themed DokuWiki detail page finishes loading.\n - Inspect the main detail content in\n - PASS only if the page shows the media detail success UI for this allowed file: a content heading \"sample.png\" and/or an .img_detail section (or equivalent media metadata/detail block), and it does NOT show a Permission Denied denied state for this media.\n - FAIL if the page shows Permission Denied for wiki:sample.png, or if the media detail success UI for sample.png is missing while the page otherwise loaded.\n - If the detail page fails to load or the scene cannot be identified, do not guess — treat as setup/environment failure rather than product PASS/FAIL.\n - Final verdict: PASS only with clear evidence that wiki:sample.png detail remains readable; FAIL only with clear evidence that this allowed-namespace media detail is denied or missing.\n"} {"case_id": "sweeper-035", "slug": "dolibarr", "repo": "https://github.com/Dolibarr/dolibarr", "base_commit": "78ab3a9aecd3a1120e1c79e0d384f5eeb5815d2e", "reference_commit": "e6b54cbc72a37f1d27f34bb9b0d42e7209a93226", "task_scoped": "Find and fix issues in Dolibarr’s ticket list interface.", "task_specified": "Fix Dolibarr ticket list Remove filter so it clears the Company filter: after searching tickets by Company and clicking Remove filter, the Company filter text input must be empty. Baseline leaves the previous Company search value in the Company field after Remove filter.", "pr": 39375, "issue": 39374, "workflows": "workflows:\n- id: target-ticket-remove-filter-clears-company\n category: target\n purpose: The ticket list Remove filter control must clear the Company filter field, not leave the previous company search value in place.\n steps:\n - Open http://127.0.0.1:13200 and wait until the Dolibarr login page is visible with styled form controls (not a bare unstyled text shell).\n - If already signed in, open the user menu and choose Logout, then return to the login page.\n - Log in with username `NolanReeves` and password `briskOak58!`. Wait until the Dolibarr home/dashboard is visible.\n - Open `http://127.0.0.1:13200/ticket/list.php` and wait until the Tickets list page loads with a filter/search row above the table.\n - Locate the Company filter text input in the list filter row (often labeled Company / Third party / Societe). Type exactly `Acme Filter Co` into that Company filter field.\n - Click the Search / Filter submit control for the list (magnifying glass or Search button) and wait for the list to refresh. Confirm the Company filter input still shows `Acme Filter Co` after search.\n - Click the Remove filter / Clear filter control for the list (eraser / clear-filters control in the filter row). Wait for the list to refresh.\n - Final verdict - PASS only if after Remove filter the Company filter input is empty (no `Acme Filter Co` text remains in that Company field). FAIL if the Company filter input still contains `Acme Filter Co` or any non-empty remnant of that company search after Remove filter. Do not PASS/FAIL based on unrelated columns; the decisive evidence is whether the Company filter field itself was cleared.\n- id: preservation-ticket-company-filter-still-searches\n category: preservation\n purpose: Filtering the ticket list by Company must still narrow results to matching company tickets.\n steps:\n - Open http://127.0.0.1:13200 and wait until Dolibarr is reachable. If needed, log in with username `NolanReeves` and password `briskOak58!`.\n - Open `http://127.0.0.1:13200/ticket/list.php` and wait until the Tickets list page is ready.\n - In the Company filter text input, type exactly `Beta Preserve Co`, then click Search / Filter and wait for the list to refresh.\n - Final verdict - PASS only if the ticket list shows the seeded Beta ticket (subject containing `Beta ticket for preservation` or ref `TK-BETA-PRESERVE`) and does not show the Acme ticket (`Acme ticket for company filter` / `TK-ACME-FILTER`) while the Company filter is set to `Beta Preserve Co`. FAIL if company filtering is broken so both companies' tickets remain visible, or the Beta ticket is missing. Do not FAIL only because a PHP notice/warning such as Undefined array key QUERY_STRING is printed on an otherwise correct filtered list.\n"} {"case_id": "sweeper-036", "slug": "domainmod", "repo": "https://github.com/DomainMOD/DomainMOD", "base_commit": "2162b45ebb7eca66428d592edf3fbcf5b7346676", "reference_commit": "40996490760f3d41737199b685cbd42b45104423", "task_scoped": "Find and fix issues in DomainMOD’s administrator user management.", "task_specified": "Fix DomainMOD admin Reset and Display Password: clicking RESET AND DISPLAY PASSWORD should show a Success alert with the username and the new password, instead of a blank white page.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-reset-display-password-message\n category: target\n purpose: 'Clicking RESET AND DISPLAY PASSWORD for glenWard must show a Success alert \"The new password for glenWard is \" on the edit page. On the buggy build the click ends on a blank page or a visible HTTP/server error page instead of that alert.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Open exactly http://127.0.0.1:13200/ and wait until the DomainMOD login page is visible (Username and Password fields, styled page with DomainMOD title/logo — not a bare unstyled shell).\n - Type exactly admin into the Username field.\n - Type exactly wren4lodge into the Password field.\n - Click the login submit control and wait until the authenticated DomainMOD UI loads (Dashboard link/menu visible).\n - Open exactly http://127.0.0.1:13200/admin/users/edit.php?uid=2 and wait until the Edit User page for glenWard is visible (heading Edit User, username glenWard, and a button labeled RESET AND DISPLAY PASSWORD).\n - Click RESET AND DISPLAY PASSWORD on that verified glenWard Edit User page as a separate browser action, with no potentially failing preliminary reads in the same command. Confirm the click call completed. Then wait for the visible page to settle. If the click completed, treat whatever is now visible as the product outcome — including a blank/empty page or a browser/server error page (HTTP ERROR 500, \"This page isn't working\", or internal server error). Do not treat that error page as a failed click, a missed navigation, or a reason to retry the locator.\n - 'Look only at the visible page after that completed click: (A) the glenWard Edit User page with a Success alert that the new password for glenWard is shown, username before the password, and no leftover %s; (B) a blank/empty page with no Success alert; (C) a Success-style message that still contains a literal %s; or (D) a visible HTTP/server error page as above.'\n - Final verdict — PASS only if (A). FAIL only if the glenWard edit scene was verified, the reset click completed, and the visible result is (B), (C), or (D). Initial login/navigation failures, unrelated errors, and slow loads alone are uncertain, not this bug. Use visible page evidence only; do not use fetch, XHR, DevTools Network, API JSON, database reads, or any helper script/file.\n- id: preservation-users-list-shows-glenward\n category: preservation\n purpose: 'After login, the Admin Users list must still show the seeded glenWard user so adjacent user-admin navigation remains intact.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Open exactly http://127.0.0.1:13200/ and wait until the DomainMOD login page is visible.\n - Type exactly admin into the Username field.\n - Type exactly wren4lodge into the Password field.\n - Click the login submit control and wait until the authenticated DomainMOD UI loads (Dashboard visible).\n - Open exactly http://127.0.0.1:13200/admin/users/ and wait until the Users list page is visible.\n - Look at the users table/list for a row or link for username glenWard.\n - Final verdict — PASS only if the Users page visibly lists glenWard. FAIL if the Users page loads but glenWard is missing. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-037", "slug": "dotclear", "repo": "https://github.com/dotclear/dotclear", "base_commit": "8dbb53d7491e747f16c0099cc8abda6e3954788c", "reference_commit": "890f99095d061c2b8ccd6db86a7ce9a7d574bf57", "task_scoped": "Find and fix issues in Dotclear’s post list management.", "task_specified": "Fix Dotclear Posts Trackbacks filter: selecting Trackbacks Opened does not narrow the posts list. Filtering by Trackbacks Opened should list only posts with trackbacks open.", "pr": 79, "issue": null, "workflows": "workflows:\n- id: posts-trackbacks-opened-filter\n category: target\n purpose: Filtering Posts by Trackbacks Opened must list only entries with trackbacks open.\n steps:\n - Open http://127.0.0.1:13200/admin/auth.php and wait until the Dotclear login form is visible with Username and Password fields and styled admin chrome (not a bare unstyled page).\n - Log in with username \"nell.briggs\" and password \"amberWick8!\". Confirm the admin dashboard or navigation loads with a Posts link.\n - Go to Posts (admin/posts.php). Confirm the posts list includes both Saturday Market Notes and Quiet Week Ahead before filtering.\n - In the filters area, set the Trackbacks select to Opened (value 1) and apply/submit the filters so the URL or form state reflects trackback=1. Wait for the posts list to refresh.\n - Inspect the resulting posts list rows (the entry title links in the entries table/form).\n - Final verdict — PASS only if Saturday Market Notes is present in the filtered list AND Quiet Week Ahead is absent AND Welcome to Dotclear is absent. FAIL if Quiet Week Ahead or Welcome to Dotclear still appears in the filtered list while Trackbacks is Opened, or if Saturday Market Notes is missing. Do not PASS based on the Trackbacks select merely showing Opened without checking which post titles remain.\n- id: posts-comments-closed-filter-preserved\n category: preservation\n purpose: Filtering Posts by Comments Closed must still list only comment-closed entries.\n steps:\n - Open http://127.0.0.1:13200/admin/auth.php and wait until the Dotclear login form is visible.\n - Log in with username \"nell.briggs\" and password \"amberWick8!\" if not already signed in. Confirm admin navigation is available.\n - Go to Posts (admin/posts.php).\n - In the filters area, set the Comments select to Closed (value 0) and apply/submit so the list is filtered with comment=0. Wait for refresh.\n - Inspect the resulting posts list title links.\n - Final verdict — PASS only if Quiet Week Ahead is present AND Saturday Market Notes is absent. FAIL if Saturday Market Notes appears under Comments Closed, or if Quiet Week Ahead is missing. Do not treat Trackbacks filtering results as evidence for this check.\n"} {"case_id": "sweeper-038", "slug": "dufs", "repo": "https://github.com/sigoden/dufs", "base_commit": "7f8269881df3113d5310f8f47d1f79eb6bac13ea", "reference_commit": "f8a7873582567a85095ca9d2124b185cd3eb2ffd", "task_scoped": "Find and fix issues in Dufs’s file access control.", "task_specified": "Fix anonymous index permissions in Dufs: When the server is started with allow-all and only anonymous @/:ro auth, anonymous visitors can still write (for example upload a new text file successfully). Anonymous visitors must not be able to upload, modify, or delete files.", "pr": 619, "issue": null, "workflows": "workflows:\n- id: target-anonymous-readonly-rejects-upload\n category: target\n purpose: With global allow-all plus anonymous @/:ro auth, an anonymous visitor must not be able to upload a new text file to the index.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the Dufs index page loads as the styled SPA (not the noscript plain \"Index of /\" table). Confirm favicon and CSS/JS assets load (styled breadcrumb/toolbox header, not a bare-text shell).\n\n '\n - 'Confirm the directory listing shows seeded files hello.txt and preserve-note.txt in the paths table. If the listing is empty or the page failed to load assets, treat this as a setup/environment problem and do not score product pass/fail for the bug.\n\n '\n - 'As an anonymous visitor (do not log in), create a local file named exactly `anon-upload.txt` using write_file. The file must be plain text and must include the marker `anonymous upload probe for dufs-f8a7873`. Then attempt to upload that file. Prefer the normal Upload files UI control (file input / upload-file) when it is visible. If the Upload control is hidden, you may still attempt the same upload the UI would perform (browser-equivalent PUT of that same write_file file to http://127.0.0.1:13200/anon-upload.txt) only as a same-backend check — do not use unrelated APIs. Wait until the attempt finishes (success response, auth/permission error, or clear UI failure). Do not read or depend on any host `tmp/` path.\n\n '\n - 'Re-check the index listing (refresh if needed) for a file named `anon-upload.txt`.\n\n '\n - 'Final verdict FAIL only if the anonymous upload succeeded: the index lists `anon-upload.txt` (and/or the upload completed with a success/create status such as HTTP 201). That means anonymous @/:ro was ignored and writes leaked. Final verdict PASS only if the anonymous upload did not succeed: `anon-upload.txt` is absent from the listing AND the upload attempt was refused or could not complete as a successful create (for example HTTP 401/403, or Upload UI missing with no new file created). Do not FAIL for timeouts, missing assets, or inability to open the page.\n\n '\n- id: preservation-anonymous-can-browse-seeded-files\n category: preservation\n purpose: Anonymous visitors under @/:ro must still be able to browse and open seeded read-only files on the index.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the Dufs index SPA loads with styled UI (favicon/CSS present) and the paths table is visible.\n\n '\n - 'Confirm both seeded files hello.txt and preserve-note.txt appear in the directory listing by name.\n\n '\n - 'Open or download hello.txt using a normal UI click on the file name / link (not page-context HTTP). Wait until the file content or download result is visible.\n\n '\n - 'Final verdict PASS only if BOTH are true: (1) hello.txt and preserve-note.txt are listed on the index, AND (2) hello.txt content is reachable and includes the text \"Dufs demo file for anonymous read access\" (visible in a view/download/preview result). Final verdict FAIL only if the index loaded correctly but either seeded file is missing from the listing, or hello.txt cannot be opened/read through the UI. Do not FAIL for unrelated tooling/setup failures.\n\n '\n"} {"case_id": "sweeper-039", "slug": "e107", "repo": "https://github.com/e107inc/e107", "base_commit": "987e7cf96672cb2feeb76752501e6fe095c44335", "reference_commit": "45d9f48580aeac0ada328199cd482815b303a43d", "task_scoped": "Find and fix issues in e107’s Plugin Manager.", "task_specified": "Fix e107 Blank Plugin repair so missing extended fields are restored. After Plugin Manager Repair on Blank Plugin, Users Extended Fields must show plugin__blank_custom / Blank Custom Field again.", "pr": null, "issue": 5483, "workflows": "workflows:\n- id: target-blank-plugin-repair-restores-extended-field\n category: target\n purpose: After Blank Plugin's extended field is missing, Plugin Manager Repair must restore Blank Custom Field so it appears again in Users Extended Fields.\n steps:\n - Open http://127.0.0.1:13200/e107_admin/admin.php and wait for the admin login form with branding/styles loaded (not a bare unstyled page).\n - Type exactly tess.wren into the username field and bramble8! into the password field. Wait at least two seconds, then submit the login form. Confirm the admin dashboard loads.\n - Open Plugin Manager at http://127.0.0.1:13200/e107_admin/plugin.php and confirm Blank Plugin is listed as installed.\n - On the Blank Plugin row, click the control titled \"Repair plugin settings\" (repair icon/button). Wait for the Plugin Manager list to reload after repair.\n - Open Users Extended Fields at http://127.0.0.1:13200/e107_admin/users_extended.php and wait for the field list table to load.\n - Final verdict — PASS only if the Extended Fields list clearly shows the restored Blank Plugin field named plugin__blank_custom and/or labeled Blank Custom Field. FAIL only if that Blank Custom Field / plugin__blank_custom row is still absent after Repair (the refresh bug). Do not FAIL for login/navigation/timeout problems. Do not FAIL for an Error about Adding Media Category _blank_image.\n- id: preservation-blank-plugin-remains-installed-after-repair\n category: preservation\n purpose: Repairing Blank Plugin must leave the plugin installed and its Plugin Manager entry usable.\n steps:\n - Open http://127.0.0.1:13200/e107_admin/admin.php and wait for the admin login form.\n - Type exactly tess.wren into the username field and bramble8! into the password field. Wait at least two seconds, then submit the login form. Confirm the admin dashboard loads.\n - Open Plugin Manager at http://127.0.0.1:13200/e107_admin/plugin.php and wait until the plugin list loads.\n - Locate Blank Plugin in the installed plugins list.\n - On the Blank Plugin row, click the control titled \"Repair plugin settings\" (repair icon/button). Wait for the Plugin Manager list to reload after repair.\n - Final verdict — PASS only if signed in as tess.wren and Blank Plugin remains listed as an installed plugin in Plugin Manager (name Blank Plugin / path _blank visible, not uninstalled/missing). FAIL only if Blank Plugin disappears or is marked uninstalled after that Repair. Do not FAIL for login/setup problems or for an Error about Adding Media Category _blank_image. Do not FAIL for unrelated UI chrome differences.\n"} {"case_id": "sweeper-040", "slug": "easyappointments", "repo": "https://github.com/alextselegidis/easyappointments", "base_commit": "ed1a13f05fb5e79e601e69f33640cd0d18f6e8f7", "reference_commit": "d53bcf5c17f4a20236030b2e9f4b1ef1bd540900", "task_scoped": "Find and fix issues in Easy!Appointments’ provider management.", "task_specified": "Fix Easy!Appointments provider Mobile Number save: a Mobile Number typed in the backend Providers UI is dropped on Save, so the field is empty after the page reloads the provider. Saving a new Mobile Number for a provider should keep that value visible in the Mobile Number field after the post-save reload.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-provider-mobile-persist\n category: target\n purpose: 'Saving a provider Mobile Number in the backend Providers UI must persist after the post-save server reload. On the buggy build, the Mobile Number input is empty after Save reloads Jane Doe from the server. After the fix, the value must remain visible in the Mobile Number field.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/index.php/login and wait until the Easy!Appointments login page is visible (Username and Password fields).\n - Type exactly willaFen into the Username field.\n - Type exactly porch9wick into the Password field.\n - Click the Login button and wait until the authenticated backend UI loads (calendar or backend chrome with navigation).\n - Open exactly http://127.0.0.1:13200/index.php/providers and wait until the Providers management page is visible (filter list and provider form with Mobile Number).\n - In the providers results/filter list, click the Jane Doe provider entry (email jane@pippins.test) so her details load into the form.\n - Click the Edit button (id edit-provider / Edit) so the form enters editing mode and fields become enabled.\n - Clear the Mobile Number field (id mobile-number) if needed, then type exactly +15551234567 into Mobile Number.\n - Click the Save button (id save-provider / Save) and wait until the save finishes and the Providers UI reloads Jane Doe from the server (notification or form refresh is fine).\n - 'After the post-save reload, look at the Mobile Number input (id mobile-number) for Jane Doe. Decide which outcome you see: (A) the field visibly shows +15551234567 (or the same digits you typed), OR (B) the Mobile Number field is empty / blank / missing that value.'\n - Final verdict — PASS only if after Save the Mobile Number field still shows +15551234567 for Jane Doe. FAIL only if Mobile Number is empty/blank after Save reload (value not persisted). Do not FAIL for slow loads; use uncertain only if Providers UI cannot be completed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-provider-phone-persist\n category: preservation\n purpose: 'Adjacent provider Phone Number persistence must keep working and must not be broken by the Mobile Number save fix.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/index.php/login and wait until the Easy!Appointments login page is visible.\n - Type exactly willaFen into the Username field.\n - Type exactly porch9wick into the Password field.\n - Click the Login button and wait until the authenticated backend UI loads.\n - Open exactly http://127.0.0.1:13200/index.php/providers and wait until the Providers page is visible.\n - In the providers results/filter list, click the Jane Doe provider entry so her details load.\n - Click the Edit button so the form enters editing mode.\n - Clear the Phone Number field (id phone-number) if needed, then type exactly +15559876543 into Phone Number.\n - Click the Save button and wait until the save finishes and Jane Doe is reloaded from the server.\n - After the post-save reload, look at the Phone Number input for Jane Doe.\n - Final verdict — PASS only if after Save the Phone Number field still shows +15559876543 for Jane Doe. FAIL if Phone Number is empty/blank after Save reload. Do not FAIL for slow loads; use uncertain only if the flow cannot be completed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-041", "slug": "emlog", "repo": "https://github.com/emlog/emlog", "base_commit": "8a1a9035a69b71e12b516f0d50f22f2a0194c559", "reference_commit": "90a214d0c799354ca68051f9aed5ec7da1eace91", "task_scoped": "Find and fix issues in emlog’s user profile settings.", "task_specified": "Fix emlog writer profile save: when a writer saves only their nickname, the save fails and the nickname does not persist. Saving a nickname-only change should keep the existing username and persist the new nickname.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-writer-profile-nickname-save\n category: target\n purpose: 'A writer updating only their nickname on the profile page must succeed. On the buggy build Save shows username_cannot_be_modified; on the fixed build the new nickname Saved Pen Name remains after reopen.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin/account.php?action=signin and wait until the emlog login form is visible (user and password fields).\n - Type exactly jon-peck into the user field (name user / id user).\n - Type exactly cedar9mist into the password field (name pw / id pw).\n - Click the Login / submit button and wait until an authenticated admin/user-center page loads (profile or dashboard navigation visible).\n - Open exactly http://127.0.0.1:13200/admin/blogger.php and wait until the profile form is visible (Nickname and Username fields). Confirm the Username input is present and disabled.\n - Clear the Nickname field and type exactly Saved Pen Name into Nickname (name name).\n - Click the Save submit button (id submit_form) and wait a few seconds for the in-page success toast or error toast (cocoMessage) to appear.\n - Observe the visible result. Then open exactly http://127.0.0.1:13200/admin/blogger.php again and wait for the profile form to reload.\n - 'Look only at the visible Nickname input value and any error toast text. Decide: (A) Nickname shows Saved Pen Name after reopen (save succeeded), OR (B) an error toast/message about username cannot be modified appeared and/or Nickname is still not Saved Pen Name.'\n - 'Final verdict — PASS only if outcome (A): after Save, reopening the profile shows Nickname Saved Pen Name. FAIL only if outcome (B): save was blocked (username cannot be modified) and Nickname did not become Saved Pen Name. Do not FAIL for slow loads; use uncertain only if Login or the profile page cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.'\n- id: preservation-admin-profile-nickname-save\n category: preservation\n purpose: 'Admin profile nickname save must still work (adjacent privileged profile path must not regress).\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin/account.php?action=signin and wait until the login form is visible.\n - Type exactly evanRusk into the user field.\n - Type exactly haze4lint into the password field.\n - Click Login and wait until the admin area loads.\n - Open exactly http://127.0.0.1:13200/admin/blogger.php and wait until the profile form is visible.\n - Clear the Nickname field and type exactly Board Pen Name into Nickname.\n - Click Save and wait for the success toast.\n - Open exactly http://127.0.0.1:13200/admin/blogger.php again and wait for the form to reload.\n - Final verdict — PASS only if Nickname visibly shows Board Pen Name after reopen. FAIL if the nickname did not save. Do not FAIL for slow loads; use uncertain only if Login or the profile page cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-042", "slug": "espocrm", "repo": "https://github.com/espocrm/espocrm", "base_commit": "c8fecaf2aa24524f2ae0852e03e1a57b19adfc6b", "reference_commit": "41ca1ffa76710adfa4cad754d263e2b7f987fa49", "task_scoped": "Find and fix issues in EspoCRM’s Opportunity browsing views.", "task_specified": "Fix the EspoCRM Opportunity Kanban board: After Pipeline is enabled for Opportunity, a non-admin user who switches to Kanban is shown You don't have access to this area and the board does not load. A non-admin user with Opportunity read access should be able to open the Opportunity Kanban board.", "pr": null, "issue": 3762, "workflows": "workflows:\n- id: preservation-opportunity-list-without-kanban\n category: preservation\n purpose: 'The same non-admin user can still open Opportunity list or detail without switching to Kanban, and Wrenfield Deal remains visible.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official EspoCRM login is fully styled: the EspoCRM logo (client/img/logo.svg or img.logo), Username #field-userName, Password #field-password, and the Login submit button #btn-login. Theme CSS must be loaded (not a bare-text shell). Do not use fetch/XHR.\n\n '\n - 'Type username `junePark` and password `slateCup3!` into that official login form only. Click Login (#btn-login). Wait until the signed-in EspoCRM navbar loads (tabs such as Home and Opportunities). You must NOT still be on the login form. If login failed, treat this as a setup problem, not a product pass/fail.\n\n '\n - 'Open Opportunities. Prefer the Opportunities navbar tab, or go to http://127.0.0.1:13200/#Opportunity. Wait until the official Opportunity list is visible: header Opportunities, a List/Kanban view-mode switcher (buttons with title List and title Kanban, data-action=\"switchViewMode\"), and a row named Wrenfield Deal. Do NOT click the Kanban button. Do NOT switch view mode.\n\n '\n - 'You may click Wrenfield Deal to open its official detail page. On detail you should still see the name Wrenfield Deal (and typically Pipeline Commercial / stage Prospecting). Still do not open Kanban.\n\n '\n - 'Final verdict — PASS only if, while signed in as junePark and without switching to Kanban, the official Opportunity list shows Wrenfield Deal, or the Opportunity detail for that record shows Wrenfield Deal. FAIL only if that same list/detail path is replaced by the 403 page \"You don''t have access to this area\" or Wrenfield Deal is missing after a successful login and list load. Do not FAIL because you accidentally opened Kanban. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n- id: target-nonadmin-opportunity-kanban-not-403\n category: target\n purpose: 'After Pipeline is enabled, a non-admin with Opportunity read access who switches to Kanban must see the board, not the 403 forbidden page.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official EspoCRM login is fully styled: EspoCRM logo, Username #field-userName, Password #field-password, Login #btn-login. Theme CSS must be loaded. Do not use fetch/XHR.\n\n '\n - 'Type username `junePark` and password `slateCup3!`. Click Login. Wait until the signed-in navbar loads (Home / Opportunities). If login failed, treat this as a setup problem, not the Kanban ACL bug.\n\n '\n - 'Open Opportunities (navbar tab or http://127.0.0.1:13200/#Opportunity). Wait until the official Opportunity list is visible, including Wrenfield Deal and the List/Kanban view-mode switcher (title Kanban, data-action=\"switchViewMode\", data-name=\"kanban\"). Confirm you are on List (the List button is active). This setup must pass before the Kanban click.\n\n '\n - 'Click the official Kanban view-mode button (title=\"Kanban\", data-name=\"kanban\"). Wait until the page either (A) shows the Opportunity Kanban board or (B) is replaced by the forbidden page. Do not judge from Network JSON.\n\n '\n - 'Decide which outcome you see after that Kanban click: (A) PASS signals — the official Kanban board is visible: kanban columns / kanban-head / list-kanban-container, stage names such as Prospecting, Qualification, Proposal, Negotiation, or Closed Won, and/or a Wrenfield Deal card. The page is NOT the 403 forbidden page. The view-mode switcher may still be present. (B) FAIL signals — the main content is the official 403 page whose visible text is \"You don''t have access to this area.\" The Kanban board is gone and the List/Kanban switcher is typically gone with it. This FAIL is only valid if login succeeded, the Opportunity list showed Wrenfield Deal, and you clicked Kanban.\n\n '\n - 'Final verdict — PASS only if outcome (A): after junePark switched Opportunity to Kanban, the official Kanban board loaded (columns and/or Wrenfield Deal card), not the 403 page. FAIL only if outcome (B): that same Kanban switch replaced the page with \"You don''t have access to this area.\" Do not PASS merely because the list worked before the click. Do not FAIL because login failed or Kanban was never clicked. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n"} {"case_id": "sweeper-043", "slug": "etherpad", "repo": "https://github.com/ether/etherpad-lite", "base_commit": "e488a4338e75f6143d3f15db61cb8def7fccec24", "reference_commit": "270e3c657607be6dfd04fa0c45256328f4023f2f", "task_scoped": "Find and fix issues in Etherpad’s document import and export tools.", "task_specified": "Fix Etherpad pad import: Importing a very old .etherpad export that lacks revision author metadata fails with a server error. The imported pad should show the restored document text.", "pr": 7473, "issue": 6785, "workflows": "workflows:\n- id: target-legacy-etherpad-import-restores-text\n category: target\n purpose: Importing a very old .etherpad export that lacks revision author metadata should restore the document text in the official pad editor instead of failing.\n steps:\n - Open http://127.0.0.1:13200 and wait until the official Etherpad homepage is styled (colibris skin CSS, nav heading Etherpad, pad-name form with input id padname and form id go2Name — not a bare-text shell).\n - On the homepage, type exactly shift-brief into the pad name field and submit the official Open pad by name button so the pad editor at /p/shift-brief loads. Wait until the toolbar and editor are visible. If the editor still shows the default Welcome to Etherpad text, that is the correct empty-pad starting scene.\n - Click the official Import / Export toolbar button (data-l10n-id pad.toolbar.import_export.title, class buttonicon-import_export) so the Import / Export popup (id import_export) is visible with the native file input id importfileinput and the Import Now button.\n - 'Create a local file named exactly shift-brief.json using write_file. The file must contain this single JSON line and nothing else. Do not rewrite, pretty-print, add keys, add author, or otherwise change the JSON — a modified file is not this export: {\"pad:testing\":{\"atext\":{\"text\":\"hey\\n\",\"attribs\":\"|1+4\"},\"pool\":{\"numToAttrib\":{},\"nextNum\":0},\"head\":0,\"savedRevisions\":[]},\"pad:testing:revs:0\":{\"changeset\":\"Z:1>3+3$hey\",\"meta\":{\"timestamp\":1273769875976,\"atext\":{\"text\":\"hey\\n\",\"attribs\":\"|1+4\"}}}}'\n - 'Upload that shift-brief.json through the native file input importfileinput (upload_file is allowed). Then in page context run only this rename script so the submitted filename ends with .etherpad (do not rebuild the bytes, do not POST/fetch/XHR): (function(){var el=document.querySelector(''#importfileinput'');var old=el.files[0];var f=new File([old],''shift-brief.etherpad'',{type:''application/octet-stream''});var d=new DataTransfer();d.items.add(f);el.files=d.files;el.dispatchEvent(new Event(''change'',{bubbles:true}));return el.files[0].name+'':''+el.files[0].size;})(); The file input should show shift-brief.etherpad. If the size is not 252, rewrite shift-brief.json from the previous step and repeat.'\n - Click the official Import Now button (id importsubmitinput). If the browser shows the confirm dialog \"Importing a file will overwrite the current text of the pad\", accept it. Wait for the import to finish (the Import Now label returns, or the page reloads after a successful .etherpad import). Do not rewrite the JSON or re-upload just because Import failed appeared — that message is part of the outcome to judge.\n - Observe only the official UI. After a successful .etherpad import the page may reload; after a failed import the Import / Export popup stays open and the importmessagefail area shows an Import failed message.\n - Final verdict — PASS only if the official pad editor document (the pad iframe / inner document body, not toolbar or popup chrome) shows the restored imported text hey as the pad content, and the default Welcome to Etherpad welcome paragraph is gone. FAIL if importmessagefail shows Import failed, or the pad editor still shows Welcome to Etherpad, or the imported document text hey is missing. Do not use fetch, XHR, Network, DevTools, or API JSON as evidence.\n- id: preservation-plain-txt-import-still-works\n category: preservation\n purpose: A normal plain-text import through the same official Import / Export dialog should still replace the pad with the uploaded text.\n steps:\n - Open http://127.0.0.1:13200 and wait until the official Etherpad homepage is styled.\n - Type exactly stair-notes into the pad name field and submit the official Open pad by name button so /p/stair-notes loads. Wait until the toolbar and editor are visible.\n - Click the official Import / Export toolbar button so the Import / Export popup is visible with the native file input importfileinput and Import Now.\n - Use page context only to attach a File named stair-notes.txt to the native file input importfileinput. The file contents must be exactly Stair notes plus a trailing newline. Assign it via DataTransfer, then dispatch a bubbling change event so Import Now becomes enabled. Do not call fetch, XHR, or any Etherpad import/API endpoint from page context.\n - Click Import Now. If the overwrite confirm dialog appears, accept it. Wait until the import finishes and the editor updates.\n - Final verdict — PASS only if the official pad editor document shows Stair notes as the pad content. FAIL if Import failed is shown for this plain-text file, or the editor still only shows the default Welcome to Etherpad text, or Stair notes is missing. Do not use fetch, XHR, Network, DevTools, or API JSON as evidence.\n"} {"case_id": "sweeper-044", "slug": "eventum", "repo": "https://github.com/eventum/eventum", "base_commit": "941c1bb5ee6bfe2ed072a6f457377dee8ca6de59", "reference_commit": "3c207ca063abe7de413efa5c3de1177cffb7b868", "task_scoped": "Find and fix issues in Eventum’s custom field administration.", "task_specified": "Fix Eventum Manage Custom Fields edit form: Target Forms checkboxes are not filled from the saved field settings. Editing a custom field that has Report Form enabled should show the Report Form checkbox checked.", "pr": 1357, "issue": null, "workflows": "workflows:\n- id: target-custom-field-report-form-checkbox\n category: target\n purpose: 'Checking Report Form on the seeded Text Input edit form, saving with Update Custom Field, and reloading must keep Report Form checked. On the buggy build, toArray() omits fld_report_form so after save and reload the checkbox is unchecked even though it was just saved checked.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/login.php and wait until the Eventum Login page is visible (Login and Password fields, Login button, and styled page with Eventum title — not a bare unstyled shell).\n - Type exactly niles@test.com into the Login field (name=email).\n - Type exactly porch4ketch into the Password field (name=passwd).\n - Click the Login button and wait until the authenticated Eventum UI loads (Administration link and List Issues visible).\n - Open exactly http://127.0.0.1:13200/manage/custom_fields.php?cat=edit&id=1 and wait until the Manage Custom Fields edit form for Text Input is visible (page heading Manage Custom Fields, a Title input showing Text Input, and Target Forms checkboxes including Report Form).\n - 'Under Target Forms, make the Report Form checkbox checked: if it is unchecked, click it so it becomes checked; if it is already checked, leave it checked. Do not uncheck Report Form.'\n - In the Assigned Projects multi-select (label Assigned Projects), select Default Project so that option is highlighted/selected. If Default Project is already selected, leave it selected. Do not leave Assigned Projects empty.\n - Click the Update Custom Field submit button and wait until the save finishes (for example a thank-you / updated successfully message, or the Text Input edit form is visible again). If a browser alert says to assign projects, dismiss it, select Default Project in Assigned Projects, then click Update Custom Field again.\n - Reload the page (browser refresh) or open exactly http://127.0.0.1:13200/manage/custom_fields.php?cat=edit&id=1 again and wait until the Text Input edit form is visible with the Report Form checkbox.\n - 'Look only at the visible Report Form checkbox (input name=report_form under Target Forms): (A) it is checked, OR (B) it is unchecked while the Title field still shows Text Input.'\n - Final verdict — PASS only if after making Report Form checked, saving with Update Custom Field, and reloading, the Report Form checkbox is checked. FAIL only if that same checkbox is unchecked after that save-and-reload. Do not FAIL for slow loads or toast wording alone. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-custom-fields-list-text-input\n category: preservation\n purpose: 'The Manage Custom Fields list must still show the seeded Text Input field among Existing Custom Fields after login.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/login.php and wait until the Eventum Login page is visible.\n - Type exactly niles@test.com into the Login field (name=email).\n - Type exactly porch4ketch into the Password field (name=passwd).\n - Click the Login button and wait until the authenticated Eventum UI loads (Administration link visible).\n - Open exactly http://127.0.0.1:13200/manage/custom_fields.php and wait until the Manage Custom Fields page is visible with an Existing Custom Fields section.\n - Look at the Existing Custom Fields list for a row/link titled Text Input.\n - Final verdict — PASS only if Existing Custom Fields visibly lists Text Input. FAIL if the Manage Custom Fields page loads but Text Input is missing from Existing Custom Fields. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-045", "slug": "evershop", "repo": "https://github.com/evershopcommerce/evershop", "base_commit": "48901958d71d34a6d2e8c27787bdafc8955dbb04", "reference_commit": "be86e45583ea49634b3102962e43f1be1ad8e0a0", "task_scoped": "Find and fix issues in EverShop’s product editor.", "task_specified": "Fix the EverShop admin product editor variant quantity field: Editing a product variant shows Qty as 0 even when that variant still has stock. The Qty field should show the variant's real inventory quantity.", "pr": 838, "issue": 833, "workflows": "workflows:\n- id: target-variant-edit-qty-shows-real-stock\n category: target\n purpose: Opening the official variant Edit modal shows the variant's real non-zero Qty, not 0.\n steps:\n - 'Open http://127.0.0.1:13200/admin/login and wait until the official EverShop Admin login page is visible: the green EverShop logo SVG, themed CSS (not a bare-text shell), Email and Password fields, and a SIGN IN button. Do not use fetch, XHR, or API shortcuts.\n\n '\n - 'Sign in with Email ash.rowan@test.com and Password twillSoap6!. Click the official SIGN IN button. Wait until the signed-in Admin chrome loads (left Catalog menu, dashboard). This login setup must succeed before judging. Do not use fetch/XHR.\n\n '\n - 'In the official left sidebar, open Catalog then click Products. Wait for the official Products grid. Use the Search box if needed and press Enter. Open the product whose name is exactly \"Oxford Ash Tee\" (the parent). The Size M child is usually not its own grid row — do NOT hunt for \"Oxford Ash Tee M\" in the list, and do NOT open \"Linen Crew Tee\". Wait for the official product editor with a Variant card / variants table. Confirm a Size M row exists (SKU OXFORD_ASH_TEE_M). This navigation setup must succeed. Do not use fetch/XHR.\n\n '\n - 'On that Variant table row for Size M, click the official Edit control (link/button labeled Edit). Wait until the official variant edit modal/form is open and shows SKU and a Qty number input (label Qty, name variant_qty). Read the visible number inside that Qty input. Do not click Save. Do not shop or checkout. Do not use fetch/XHR or Network JSON as the oracle.\n\n '\n - 'Final verdict PASS only if ALL are true: (1) you signed in through the official Admin login form, (2) you opened the parent product Oxford Ash Tee and then the official Edit modal for the Size M variant, AND (3) the official Qty number input visibly shows 5 (the seeded inventory). Showing 0 is the bug, not a sold-out product. Do not use fetch/XHR for setup, triggering, or scoring.\n\n '\n - 'Final verdict FAIL if that official Qty input shows 0, is empty, or shows any number other than 5 after the Size M variant Edit modal is open. Do not FAIL for login/navigation setup problems alone. Do not FAIL based only on the variants table Stock column. Do not use fetch/XHR.\n\n '\n- id: preservation-simple-product-qty-still-correct\n category: preservation\n purpose: A simple product without variants still shows its real non-zero Inventory Quantity.\n steps:\n - 'Open http://127.0.0.1:13200/admin/login and wait until the official EverShop Admin login page is visible: the green EverShop logo SVG, themed CSS (not a bare-text shell), Email and Password fields, and a SIGN IN button. Do not use fetch, XHR, or API shortcuts.\n\n '\n - 'Sign in with Email ash.rowan@test.com and Password twillSoap6!. Click the official SIGN IN button. Wait until the signed-in Admin chrome loads. This login setup must succeed before judging. Do not use fetch/XHR.\n\n '\n - 'In the official left sidebar, open Catalog then click Products. Wait for the official Products grid. Use the Search box if needed and press Enter. Open the product whose name is exactly \"Linen Crew Tee\". Do NOT open Oxford Ash Tee or Oxford Ash Tee M. Wait for the official product editor. Find the Inventory card and the Quantity number input (label Quantity, name qty). Read the visible number in that input. Do not click Save. Do not use fetch/XHR.\n\n '\n - 'Final verdict PASS only if ALL are true: (1) you signed in through the official Admin login form, (2) you opened Linen Crew Tee, AND (3) the official Inventory Quantity number input visibly shows 7. Do not use fetch/XHR for setup, triggering, or scoring.\n\n '\n - 'Final verdict FAIL if that official Quantity input shows 0, is empty, or shows any number other than 7 after Linen Crew Tee is open. Do not FAIL for the variant Qty-shows-0 bug. Do not FAIL for login/navigation setup problems alone. Do not use fetch/XHR.\n\n '\n"} {"case_id": "sweeper-046", "slug": "expressionengine", "repo": "https://github.com/ExpressionEngine/ExpressionEngine", "base_commit": "121cb2a1f0484f9932ad3537604e24fb43f760fa", "reference_commit": "1a056eea602a69615acc8704c862de81c2adfa01", "task_scoped": "Find and fix issues in ExpressionEngine’s upload directory configuration.", "task_specified": "Fix ExpressionEngine Image Manipulations: A Short Name that matches a built-in processing folder is accepted and saved. A reserved Short Name should be rejected with a validation error and should not remain as a saved manipulation.", "pr": 5343, "issue": 4600, "workflows": "workflows:\n- id: target-reserved-image-manipulation-short-name\n category: target\n purpose: 'Saving an Image Manipulation whose Short Name is the reserved built-in name \"resize\" must show the invalid short name validation error and must not keep that reserved manipulation. On the buggy build, Save accepts \"resize\" and the Image Manipulations grid keeps a Short Name of resize with no reserved-name error.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin.php and wait until the ExpressionEngine Control Panel login page is visible (Username and Password fields, and the ExpressionEngine logo/branding — not a blank text-only shell).\n - Type exactly quinAdler into the Username field.\n - Type exactly Ford8nimbus into the Password field.\n - Click the login submit control and wait until the authenticated Control Panel loads (left/side navigation or top nav with Files / content areas visible).\n - Open exactly http://127.0.0.1:13200/admin.php?/cp/files/uploads/edit/4 and wait until the Edit Upload Directory form for Main Upload is visible, including the Image Manipulations section (heading Image Manipulations and a Short Name field / Add New Manipulation control).\n - In the Image Manipulations section, if an empty Short Name row is already visible use that row; otherwise click Add New Manipulation so a new Short Name input row appears.\n - In that manipulation row, clear any existing Short Name text and type exactly resize into the Short Name field.\n - In the same row, set Width to 100 and Height to 100 if those fields are empty (use the Width and Height inputs for that row). Leave Type as the default constrain/crop option if already selected.\n - Click the primary Save control for the Upload Directory form (button labeled Save) and wait for the page to finish processing (either validation errors on the form or a successful save return to the edit UI).\n - 'Look only at the visible Image Manipulations UI after that Save: (A) a reserved-name / invalid short name validation error is shown for Short Name (text about built-in manipulation names such as thumbs, resize, crop, rotate, webp, or avif, or invalid short name / invalid_short_name), and there is no successfully saved manipulation row whose Short Name is exactly resize without that error; OR (B) no such reserved-name validation error is shown and a manipulation row with Short Name resize remains accepted/saved in the Image Manipulations grid.'\n - Final verdict — PASS only if after saving Short Name resize the Upload Directory Image Manipulations UI visibly shows a reserved/invalid short name validation error and does not keep an accepted saved Short Name resize row without that error. FAIL only if Save accepts Short Name resize with no reserved-name validation error and the Image Manipulations UI still shows a Short Name of resize as saved/accepted. Setup steps (login, open Main Upload edit/4, fill Short Name) must succeed before this Save assertion; the fail must land on the Save/assertion step that exposes the bug, not on login. Do not FAIL for slow loads alone. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-valid-image-manipulation-short-name\n category: preservation\n purpose: 'A non-reserved Image Manipulation Short Name such as hero_small must still save successfully on the Main Upload directory.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin.php and wait until the ExpressionEngine Control Panel login page is visible (Username/Password and ExpressionEngine branding).\n - Type exactly quinAdler into the Username field.\n - Type exactly Ford8nimbus into the Password field.\n - Click the login submit control and wait until the authenticated Control Panel loads.\n - Open exactly http://127.0.0.1:13200/admin.php?/cp/files/uploads/edit/4 and wait until the Edit Upload Directory form for Main Upload is visible with the Image Manipulations section.\n - In the Image Manipulations section, use an empty Short Name row if present, otherwise click Add New Manipulation so a new row appears.\n - In that row, type exactly hero_small into the Short Name field, set Width to 120 and Height to 80 if empty, then click the primary Save control and wait for the form to finish.\n - Look at the Image Manipulations grid after Save for a Short Name of hero_small and confirm there is no fatal error page and no invalid-short-name error for hero_small.\n - Final verdict — PASS only if after saving Short Name hero_small the Image Manipulations UI visibly lists Short Name hero_small (saved) without a fatal/error page and without an invalid short name error for hero_small. FAIL if hero_small does not appear as a saved manipulation or the Control Panel shows a fatal/internal error. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-047", "slug": "fenrus", "repo": "https://github.com/revenz/Fenrus", "base_commit": "9b3445b12f60fd532e183bb42484f485dc69be3e", "reference_commit": "a9fac28eb300859f95ee855040b4e4d0396e3466", "task_scoped": "Find and fix issues in Fenrus’s system group management.", "task_specified": "Fix Fenrus system group creation: Add on System Groups follows a broken non-system create path, so entering a name and Save stores the group under ordinary Groups instead of System Groups. Creating a group from System Groups Add should save it under System Groups.", "pr": null, "issue": 179, "workflows": "workflows:\n- id: system-groups-add-save-lands-in-system-groups\n category: target\n purpose: 'Verify that creating a group via Add on System Groups actually saves it as a system group (listed under System Groups), not as an ordinary user group.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/login\n - 'Confirm the Fenrus login page is visible (Username and Password fields, Login button, Fenrus branding/logo). If the page is unreachable or shows a fatal error, stop as setup failure (not product pass/fail).\n\n '\n - 'Log in with username noahKline and password amberRidge5!. Submit using the Login button (action Login). Confirm an authenticated Fenrus UI loads (dashboard/home or settings navigation). If login fails, stop as setup failure.\n\n '\n - 'Open System Groups from the settings/side menu (link to /settings/system/groups, label System Groups). Confirm the System Groups list page is visible (title/heading System Groups and an Add control). If the page cannot be reached, stop as setup failure.\n\n '\n - 'Click the Add button on the System Groups toolbar (plus / Add). Wait until a group create/edit form is visible with a Name field (default text may be New Group or New Group (N)).\n\n '\n - 'Clear the Name field if needed and type the exact name Harbor System Pack. Do not use a generic New Group name for the verdict later.\n\n '\n - 'Click Save on the group editor. Wait until navigation finishes and a groups list page is shown again.\n\n '\n - 'Open System Groups at /settings/system/groups and check whether a row named Harbor System Pack is listed.\n\n '\n - 'Open the ordinary (non-system) Groups page at /settings/groups and check whether a row named Harbor System Pack is listed there.\n\n '\n - 'Final verdict (require both scene and bug-specific evidence). FAIL only if ALL are true: (1) Add was started from the System Groups list; (2) Harbor System Pack was entered and Save completed successfully; (3) Harbor System Pack appears under ordinary Groups (/settings/groups) and does NOT appear under System Groups (/settings/system/groups). That is the bug: System Groups Add wrongly creates a user group. PASS only if ALL are true: (1) Add was started from System Groups; (2) Harbor System Pack was saved; (3) Harbor System Pack appears under System Groups (/settings/system/groups) and does NOT appear as a new ordinary Groups row under /settings/groups. If login, opening System Groups, opening the editor, or Save fails before both lists can be checked, report setup/environment failure rather than PASS/FAIL on the bug.\n\n '\n- id: user-groups-add-save-lands-in-user-groups\n category: preservation\n purpose: 'Preserve that creating a group via Add on the ordinary Groups page still saves it as a user group under /settings/groups, not under System Groups.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/login\n - 'Confirm the Fenrus login page is visible. If unreachable, stop as setup failure.\n\n '\n - 'Log in as noahKline / amberRidge5! with the Login button. Confirm an authenticated UI loads. If login fails, stop as setup failure.\n\n '\n - 'Open Groups from the settings/side menu (link to /settings/groups, the non-system Groups item — not System Groups). Confirm the Groups list page is visible with an Add control.\n\n '\n - 'Click Add on the Groups toolbar. Wait until a group create/edit form is visible with a Name field.\n\n '\n - 'Clear the Name field if needed and type the exact name Cedar User Pack.\n\n '\n - 'Click Save. Wait until a groups list page is shown again.\n\n '\n - 'Confirm Cedar User Pack appears on the ordinary Groups list (/settings/groups).\n\n '\n - 'Open System Groups (/settings/system/groups) and confirm Cedar User Pack is NOT listed there as a system group row.\n\n '\n - 'Final verdict. PASS only if ALL are true: (1) Add was started from ordinary Groups; (2) Cedar User Pack was saved; (3) it appears under /settings/groups and does not appear under /settings/system/groups. FAIL only if Save from ordinary Groups Add clearly places Cedar User Pack under System Groups instead, or the named group never appears under ordinary Groups after a completed Save. Setup/login/navigation failures are not product FAIL for this preservation check.\n\n '\n"} {"case_id": "sweeper-048", "slug": "filebrowser", "repo": "https://github.com/filebrowser/filebrowser", "base_commit": "65a837de4916c054a89258bf84b35f075158a1b5", "reference_commit": "7dbf7a3528234b2a9ee9c4115e8ecf58d258ca51", "task_scoped": "Find and fix issues in File Browser’s file sharing.", "task_specified": "Fix File Browser public share access: After the share owner's Share or Download permission is revoked, existing public share links still expose the shared file. Opening such a share URL should show a forbidden error and should not expose the shared file.", "pr": 5888, "issue": null, "workflows": "workflows:\n- id: target-revoked-share-owner-blocks-public-link\n category: target\n purpose: After an admin revokes the share owner's Share permission, the existing public share link must no longer expose the shared file.\n steps:\n - Open `http://127.0.0.1:13200/login` and log in with username `NoraBlake` and password `oakLane7!pad`. Wait until the file listing loads.\n - Open the file `SHARE_URL.txt` from the root listing (click it / preview it) and read its full text content. It contains one absolute URL like `http://127.0.0.1:13200/share/`. Remember this exact sharer-owned public share URL.\n - Open Settings → User Management (or navigate to `http://127.0.0.1:13200/settings/users`). Open the user named `CalebNg` for editing.\n - In the CalebNg permissions, uncheck `Share files` so Share is disabled. Keep Download enabled. Save/update the user. When prompted for the current password, enter `oakLane7!pad`. Confirm the save succeeds (for example a success toast/message that the user was updated).\n - Log out if a logout control is available, or open a fresh navigation to the remembered sharer-owned public share URL from SHARE_URL.txt (do not stay only on the admin settings page).\n - Open the remembered sharer-owned public share URL and wait for the share page to finish loading.\n - Final verdict - PASS only if the share page shows a forbidden / no-permission error state whose visible text includes `You don't have permissions to access this` (or clearly equivalent forbidden wording) AND the shared file `shared-demo.txt` is not shown as an accessible shared file listing/preview. FAIL if the share page successfully shows `shared-demo.txt` (name, listing, or file preview/content) as if the share were still valid, or if no forbidden error is visible.\n- id: preservation-admin-owned-share-still-works\n category: preservation\n purpose: A public share owned by an admin who still has Share and Download permissions should remain accessible.\n steps:\n - Open `http://127.0.0.1:13200/login` and log in with username `NoraBlake` and password `oakLane7!pad` if not already signed in. Wait until the file listing loads.\n - Open the file `ADMIN_SHARE_URL.txt` from the root listing and read its full text content. It contains one absolute URL like `http://127.0.0.1:13200/share/`. Remember this admin-owned public share URL.\n - Open that admin-owned public share URL and wait for the share page to finish loading.\n - Final verdict - PASS only if the share page successfully shows the shared file `shared-demo.txt` (visible name in the share listing/preview). FAIL if the page shows a forbidden/no-permission error such as `You don't have permissions to access this`, or if `shared-demo.txt` is not visible.\n"} {"case_id": "sweeper-049", "slug": "filegator", "repo": "https://github.com/filegator/filegator", "base_commit": "a11449120e248c728193b9f27f49c909d5aac183", "reference_commit": "31321d21b65416026d119932a41894ded8323594", "task_scoped": "Find and fix issues in FileGator’s file upload workflow.", "task_specified": "Fix FileGator guest file upload so uploading as a guest with upload permission does not crash the upload chunk handler with a null-user error. A guest with upload permission should be able to upload a file and see it persist in the root listing after reload.", "pr": null, "issue": 583, "workflows": "workflows:\n- id: target-guest-upload-persists-file\n category: target\n purpose: A guest with upload permission must be able to upload a file so it appears in the root file listing.\n steps:\n - Open http://127.0.0.1:13200/\n - Wait until the FileGator file browser UI is visible (styled page with the file listing area). Do not log in; remain as the anonymous guest session.\n - Confirm the guest can upload: an \"Add files\" control (upload icon/button) must be visible in the toolbar. If \"Add files\" is missing, treat this as setup failure, not a product pass/fail.\n - Note the current root listing contents (it should typically be empty or not already contain the unique target filename below).\n - Using Add files (or an equivalent guest upload control), upload a small plain-text file whose exact filename is `guest_core_upload.txt` and whose content is `guest-core-upload-ok`. Prefer the native file picker / upload control from the FileGator UI. Wait until any upload progress UI finishes or settles (success, error toast, or stalled progress).\n - Refresh or re-open http://127.0.0.1:13200/ and wait for the root file listing to reload while still not logged in.\n - Observe whether `guest_core_upload.txt` appears as a file entry in the root listing.\n - Final verdict — PASS only if, after the guest upload attempt and listing reload, the root listing clearly shows a file named exactly `guest_core_upload.txt`. FAIL only if the guest upload UI was available and used, the listing reloaded, and `guest_core_upload.txt` is still absent from the root listing (upload soft-failed / never persisted). Do not FAIL solely because of a brief progress animation; do not PASS unless that exact filename is visible in the listing.\n- id: preservation-admin-login-upload-works\n category: preservation\n purpose: A logged-in admin must still be able to upload a file into the root listing.\n steps:\n - Open http://127.0.0.1:13200/\n - Wait until the FileGator UI loads.\n - Open Login (menu/button), sign in with username `admin` and password `admin123`, and wait until the authenticated file browser is available (guest Login entry should be gone / admin session active).\n - Confirm an \"Add files\" upload control is visible for the admin.\n - Upload a small plain-text file named exactly `admin_preserve_upload.txt` with content `admin-preserve-upload-ok` using Add files. Wait until upload progress finishes or settles.\n - Refresh or re-open http://127.0.0.1:13200/ while still logged in as admin and wait for the root listing to reload.\n - Final verdict — PASS only if the root listing clearly shows a file named exactly `admin_preserve_upload.txt` after the admin upload. FAIL if login failed, Add files was unavailable after login, or the file is missing from the listing after reload.\n"} {"case_id": "sweeper-050", "slug": "filestash", "repo": "https://github.com/mickael-kerjean/filestash", "base_commit": "aa253ddc592165b4d25d09a85fb5a2d861e5e9ab", "reference_commit": "84c87dd15f6e858e5117f8c7c3bd319db695478f", "task_scoped": "Find and fix issues in Filestash’s file sharing.", "task_specified": "Fix Filestash share link creation when the configured local storage path has no trailing slash: creating a Viewer share for a file must keep a usable share link that opens the shared file. Opening the share must not fail with Not Found because the session path and file path were concatenated without a directory separator.", "pr": 889, "issue": 878, "workflows": "workflows:\n- id: target-share-file-with-storage-path-missing-trailing-slash\n category: target\n purpose: When local storage path has no trailing slash (auth middleware attribute mapping), creating a Viewer share for a file must persist a usable share link that opens the shared file instead of a Not Found / broken share.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the Filestash connection UI is fully styled (logo/CSS loaded, not a bare text shell). If a single Local connection with authentication middleware is present, wait for the automatic redirect into the password CONNECT form, or click Local / CONNECT so the passthrough password form is visible.\n\n '\n - 'On the password form, type CedarShareLab001 into the Password field and click CONNECT using only normal keyboard/mouse actions (no page-context fetch/XHR/API shortcuts). Wait until the authenticated file manager loads and shows seeded items such as hello.txt and/or a demo folder.\n\n '\n - 'In the file manager, select hello.txt by clicking its checkbox (the selection checkbox next to the file row/tile — do NOT click the hello.txt filename/link itself, which opens the viewer). After the checkbox selects the file, a Share button must appear in the file-manager action toolbar / submenu. Click that Share button so the modal titled like \"Create a New Link\" opens with Viewer / Editor role choices.\n\n '\n - 'Click Viewer. In the share modal, a readonly shared-link URL input should show a URL containing /s/ — that URL is only a draft until you create it. You MUST create the share by clicking the shared-link row / copy-URL control (the control next to the readonly /s/ input). Wait until a success toast/notification appears (for example that the link was copied) or the modal switches to an Existing Links list that includes this share. Only after creation succeeds, open that same /s/ share URL in the browser (address bar navigation is fine — do not call APIs). Wait for the share page to finish loading.\n\n '\n - 'Final verdict PASS only if ALL are true after opening the share URL: (1) the shared viewer page loads without a Not Found / AjaxError failure for the shared file, AND (2) the shared content for hello.txt is visibly available (file name and/or file contents \"share-me\" shown in the share viewer UI). Final verdict FAIL only if that same share-creation path was reached AND the share is broken in the UI: for example the share URL opens with a visible Not Found / AjaxError / undefined error, the shared file cannot be viewed, or the share entry disappears / errors immediately after creation because the stored share path was joined without a directory separator. Do not FAIL for login failures, missing CSS, or inability to reach the file manager / share modal.\n\n '\n- id: preservation-browse-seeded-files-after-middleware-login\n category: preservation\n purpose: After the same admin-middleware login into Local storage, the seeded hello.txt and demo/readme.txt must remain visible and openable in the file manager (browsing must not regress when share path joining is fixed).\n steps:\n - 'Open http://127.0.0.1:13200/ and wait for the styled Filestash UI. Reach the password CONNECT form for the Local auth-middleware connection (auto-redirect or click Local / CONNECT).\n\n '\n - 'Type CedarShareLab001 as the Password and click CONNECT. Wait until the file manager lists the storage contents.\n\n '\n - 'Confirm hello.txt is visible in the listing. Open the demo folder (or navigate into demo/) and confirm readme.txt is visible. Open hello.txt with a normal UI action so its contents are shown in the viewer/editor. If the viewer shows Internal Error, close it, reopen hello.txt once, or reload the file manager and open it again.\n\n '\n - 'Final verdict PASS only if hello.txt and demo/readme.txt are both visible through normal file-manager navigation and hello.txt content \"share-me\" is shown after opening it. Final verdict FAIL only if that authenticated file manager scene was reached and those seeded files are missing, or hello.txt still cannot show its text after one reopen/reload. If the files are listed but the viewer hits a one-off Internal Error and a retry was not possible, judge uncertain — do not fail. Do not FAIL for share-modal problems or unrelated auth/asset failures.\n\n '\n"} {"case_id": "sweeper-051", "slug": "firefly-iii", "repo": "https://github.com/firefly-iii/firefly-iii", "base_commit": "e316d9ce6dcd49cf07770796e8f79acb65487265", "reference_commit": "048db14a08f877f8eecfc79f788a5cbcdfe8fe35", "task_scoped": "Find and fix issues in Firefly III’s budget configuration.", "task_specified": "Fix Firefly III budget edit Auto-budget amount prefilling: When a saved auto-budget amount is above 1000, the edit form number input is empty because number_format inserts a thousands separator. The Auto-budget amount field should show the saved amount.", "pr": 5371, "issue": null, "workflows": "workflows:\n- id: target-auto-budget-amount-above-1000-prefills-on-edit\n category: target\n purpose: Editing a budget whose auto-budget amount is above 1000 must prefill the Auto-budget amount number field with that saved amount.\n steps:\n - 'Open http://127.0.0.1:13200/login. Log in as maya.ortiz@example.com / riverCup3!. Prefer page-context form submit: read the _token hidden input, then POST application/x-www-form-urlencoded to /login with email=maya.ortiz@example.com&password=riverCup3!&_token=, and follow redirects until you land on a Firefly page (home, budgets, or new-user wizard).\n\n '\n - 'After login, the home/index page may show a Firefly III intro.js guided tour overlay (text like \"Welcome to the index page of Firefly III...\") with buttons Skip / Previous / Next. If that overlay is visible, click Skip once so the tour closes and does not block later clicks. If no intro overlay appears, continue.\n\n '\n - 'If the separate first-time account wizard appears at /new-user (bank/savings balances form — not the intro tour), complete it once with any valid bank name (e.g. Checking), bank balance 1000, savings balance 0, language en_US, then continue. Confirm you can open http://127.0.0.1:13200/budgets.\n\n '\n - 'Open http://127.0.0.1:13200/budgets/create. Create a budget named exactly Core Auto Budget 1500 with Auto-budget type set to \"Set a fixed amount every period\" (auto_budget_type=1), Auto-budget amount exactly 1500, period monthly, and save/store the budget. Prefer page-context POST to /budgets/store with CSRF _token and fields name=Core Auto Budget 1500&active=1&auto_budget_type=1&auto_budget_currency_id=1&auto_budget_amount=1500&auto_budget_period=monthly if the UI widgets are awkward. Confirm the budget appears on /budgets.\n\n '\n - 'After the first budget exists, the /budgets index page may show another intro.js guided tour overlay (text like \"Budgets are used to manage your finances and form one of the core functions of Firefly III.\") with buttons Skip / Previous / Next. If that overlay is visible, click Skip once so it closes and does not block the edit-page steps. If no budgets intro overlay appears, continue.\n\n '\n - 'Open the edit page for that budget (http://127.0.0.1:13200/budgets/edit/1 if it is the first budget, otherwise the edit URL shown for Core Auto Budget 1500). Locate the Auto-budget amount input (name=auto_budget_amount, type=number). Read the field''s visible/browser value (input.value), not only raw HTML source.\n\n '\n - 'Final verdict - PASS only if all are true: (1) budget Core Auto Budget 1500 exists with an auto-budget amount of 1500 saved, (2) the edit form''s Auto-budget amount number input visibly shows a numeric value of 1500 (or 1500.00), and (3) the field is not empty/blank. FAIL if the Auto-budget amount number input is empty/blank on the edit page while the budget was saved with amount 1500 (the thousands-separator bug), or if the visible value is clearly not 1500.\n\n '\n- id: preservation-auto-budget-amount-below-1000-still-prefills\n category: preservation\n purpose: Editing a budget whose auto-budget amount is below 1000 should still prefill the Auto-budget amount field correctly.\n steps:\n - 'Open http://127.0.0.1:13200/login. If not authenticated, log in as maya.ortiz@example.com / riverCup3! using the same page-context login method as the target workflow. If the intro.js guided tour overlay appears (Skip / Previous / Next), click Skip once to dismiss it. Then open http://127.0.0.1:13200/budgets.\n\n '\n - 'Open http://127.0.0.1:13200/budgets/create. Create a budget named exactly Preserve Auto Budget 500 with Auto-budget type \"Set a fixed amount every period\" (auto_budget_type=1), Auto-budget amount exactly 500, period monthly, and save. Prefer page-context POST to /budgets/store with CSRF token and name=Preserve Auto Budget 500&active=1&auto_budget_type=1&auto_budget_currency_id=1&auto_budget_amount=500&auto_budget_period=monthly when helpful. Confirm it appears on /budgets.\n\n '\n - 'After the budget is created, if the /budgets index shows an intro.js guided tour overlay (text like \"Budgets are used to manage your finances...\") with Skip / Previous / Next, click Skip once to dismiss it before opening the edit page. If no overlay appears, continue.\n\n '\n - 'Open that budget''s edit page. Locate the Auto-budget amount number input and read its visible/browser value.\n\n '\n - 'Final verdict - PASS only if both are true: (1) budget Preserve Auto Budget 500 exists, and (2) the edit form Auto-budget amount number input visibly shows 500 (or 500.00) and is not empty. FAIL if that amount field is empty or shows a value other than 500/500.00.\n\n '\n"} {"case_id": "sweeper-052", "slug": "flarum", "repo": "https://github.com/flarum/framework", "base_commit": "7d2c74f05259735f0443c871c4781beb311ca10c", "reference_commit": "506628bd60012937fba8e7b8e7b779217d283481", "task_scoped": "Find and fix issues in Flarum’s discussion authoring and editing.", "task_specified": "Fix Flarum restricted-tag discussion actions: Restrict by Tag blocks the author from renaming or hiding their own discussion. The author should still be able to rename or hide their own discussion.", "pr": 4379, "issue": 3692, "workflows": "workflows:\n- id: target-restricted-tag-author-rename-own-discussion\n category: target\n purpose: 'After len-quist signs in on the official 2.x forum and opens their own Wick Limited discussion Lift window slip, they must be able to Rename that discussion (or Hide/Delete it) with the official discussion controls. On the buggy build the restricted-tag policy hides those own-abilities, so the author cannot change their own title or soft-delete the thread.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official Flarum 2.x forum is fully styled: Wick Board title, compiled forum.css (not a bare unstyled page), discussion list chrome, and a header Log In control. Do not open /d/1-lift-window-slip (or any /d/… URL) while logged out: guests cannot see the restricted-tag thread and that URL 404s. Do not use fetch/XHR.\n\n '\n - 'Click the official header Log In control. Wait until the official Log In modal appears with Username or Email, Password, and a Log In submit. Type username `len-quist` and password `wickPlate4!` into those fields only. Click Log In. Wait until you are signed in as len-quist: the header session / avatar shows len-quist (or their email), Log In is gone, and the discussion list includes both Lift window slip and Yard roster draft. You must NOT still be on the Log In modal. If login failed, treat this as setup failure, not the restricted-tag own-ability bug. Do not register. Do not sign in as miraCole. Do not use fetch/XHR.\n\n '\n - 'From the official discussion list, open Lift window slip (the discussion in Wick Limited). Wait until the official discussion page loads: the title Lift window slip is visible and Wick Limited is shown as a tag. Do not open Yard roster draft. Do not use fetch/XHR.\n\n '\n - 'Look at the official right-hand discussion sidebar (desktop) or the header primary control (narrow). On this restricted thread the author also cannot reply, so the primary control is a full-width Can''t Reply button. On the buggy build that is the only control: Flarum hides the SplitDropdown toggle when the menu has a single item (itemCount1), so there is no narrow dropdown, no three-dot Toggle discussion actions control, no Rename, and no Delete. On a fixed build Can''t Reply stays, but a narrow dropdown toggle appears beside it and the menu includes Rename (pencil) and/or Delete (trash; hide/soft-delete). Do not use fetch/XHR.\n\n '\n - 'If the narrow dropdown toggle is present, open it. If Rename is present: click Rename, wait for the official Rename Discussion modal, change the title to exactly `Lift window slip — later edit`, and click the modal Rename submit. Wait until the modal closes and the discussion page title updates. If Delete is present and Rename is not: click Delete and confirm the official delete confirmation so the discussion is hidden. If there is only Can''t Reply and no dropdown / no Rename / no Delete, do not invent another path (do not use the first-post Edit composer as a substitute for discussion Rename). Do not use fetch/XHR.\n\n '\n - 'Final verdict — require both the correct scene and bug-specific discussion-control evidence. The scene is valid only if len-quist is signed in on the official forum UI and the Lift window slip discussion page (Wick Limited) was opened from the list (not via a logged-out 404). FAIL only if that scene is valid AND the author cannot rename or hide their own restricted-tag discussion: the sidebar shows only Can''t Reply with no dropdown and no Rename/Delete, a permission error appears, or a Rename save leaves the title as Lift window slip (it never becomes Lift window slip — later edit) / hide never takes effect. PASS only if that same scene is valid AND the author succeeded: the visible discussion title is Lift window slip — later edit, or the thread is clearly hidden/deleted in the official UI. Setup/login/404-while-logged-out failures are not product PASS/FAIL. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n- id: preservation-unrestricted-tag-author-rename-own-discussion\n category: preservation\n purpose: 'The same author len-quist must still be able to Rename their own discussion in an unrestricted tag (Yard roster draft in Field Open) with the official discussion controls.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official Flarum 2.x forum is fully styled. If you are already signed in as len-quist (header session shows len-quist and Log In is gone), skip the login form. Do not use fetch/XHR.\n\n '\n - 'If the header still shows Log In, open the official Log In modal and sign in as `len-quist` / `wickPlate4!`. Wait until the discussion list includes Yard roster draft. If login failed, treat this as setup failure, not a product fail. Do not sign in as miraCole. Do not use fetch/XHR.\n\n '\n - 'Open Yard roster draft (Field Open), not Lift window slip. Wait until that discussion page shows title Yard roster draft and the official sidebar Reply control. Because this tag is not restricted, Reply is enabled and a narrow SplitDropdown toggle sits beside it (that toggle is the discussion actions menu). Do not use fetch/XHR.\n\n '\n - 'Open that narrow dropdown toggle beside Reply. Click Rename. In the Rename Discussion modal, change the title to exactly `Yard roster draft — later edit` and submit Rename. Wait until the modal closes and the page title updates. Do not use fetch/XHR.\n\n '\n - 'Final verdict — PASS only if Yard roster draft was opened by signed-in len-quist and the visible title became Yard roster draft — later edit after the official Rename Discussion modal. FAIL only if that same unrestricted-tag discussion was opened and Rename was missing, was rejected, or the title stayed Yard roster draft. Do not FAIL because Lift window slip (the restricted-tag thread) could not be renamed; that is the core bug, not this preservation case. Setup/login failures are not product FAIL. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n"} {"case_id": "sweeper-053", "slug": "flatpress", "repo": "https://github.com/flatpressblog/flatpress", "base_commit": "377037e6fb1bca43b72c27c7883d50be74f723fd", "reference_commit": "63de05593ca51d3ab923c4122a98c70807bef47c", "task_scoped": "Find and fix issues in FlatPress’s PrettyURLs module.", "task_specified": "Fix FlatPress PrettyURLs so posts whose titles contain 4-byte emoji open from the home-page title link instead of showing Sorry, we could not find the page you requested.", "pr": 927, "issue": 925, "workflows": "workflows:\n- id: target-emoji-prettyurl-resolves\n category: target\n purpose: A blog entry whose title contains a 4-byte emoji must open via its PrettyURLs title link instead of showing the FlatPress 404 page.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the FlatPress blog home is fully styled (Leggero/Stringendo theme CSS loaded with layout/header/sidebar — not a bare unstyled text shell). Confirm the blog title text \"Mossline Journal\" is visible.\n\n '\n - 'On the home page entry list, find the post titled exactly \"Hello 😀 Core927\" (emoji grinning face between Hello and Core927). Using only a normal mouse click, open that post''s main title link (the H2 entry-title anchor for that post). In this theme the title link goes to the entry''s comments PrettyURL.\n\n '\n - 'Wait for the resulting page to finish loading after the click.\n\n '\n - 'Final verdict — FAIL only if that title-link navigation reaches a FlatPress 404 scene whose visible body contains \"Sorry, we could not find the page you requested\" and does not show the entry body \"Body for emoji core entry Core927.\". That is the baseline PrettyURLs bug for 4-byte emoji titles. Final verdict — PASS only if the same title-link navigation opens the entry/comments view successfully: the page shows the title \"Hello 😀 Core927\" and the body text \"Body for emoji core entry Core927.\" without that 404 sentence. Do not FAIL for unrelated login/admin issues, missing CSS alone, or inability to find the home-page title link. Only judge the emoji PrettyURL outcome after the home page and the Core927 title link were clearly reached.\n\n '\n- id: preservation-ascii-prettyurl-resolves\n category: preservation\n purpose: A normal ASCII-titled entry must still open correctly through PrettyURLs.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the styled FlatPress home page for \"Mossline Journal\" is visible.\n\n '\n - 'Find the post titled exactly \"Hello Preserve927\". Using only a normal mouse click, open that post''s main H2 entry-title link.\n\n '\n - 'Final verdict — PASS only if the entry/comments view opens successfully and the page shows title \"Hello Preserve927\" together with body text \"Body for ascii preserve entry Preserve927.\" without the 404 sentence \"Sorry, we could not find the page you requested\". Final verdict — FAIL only if that ASCII title link clearly lands on the FlatPress 404 page with that sorry/not-found sentence, or the preserve body never appears after a successful-looking navigation. Do not FAIL for home-page load/CSS problems alone.\n\n '\n"} {"case_id": "sweeper-054", "slug": "fluxbb", "repo": "https://github.com/fluxbb/fluxbb", "base_commit": "d5b6f631f6eb8a73aa83f9b1d8f03eb33dadca68", "reference_commit": "c64c6caca615dc38745e75c3077e8474d731b841", "task_scoped": "Find and fix issues in FluxBB’s ban administration.", "task_specified": "Fix FluxBB admin ban search ordering: when results are ordered by IP, pagination links encode order_by as b.ip so page 2 silently falls back to username order. Ban search results ordered by IP should keep IP ordering on later pages.", "pr": 219, "issue": null, "workflows": "workflows:\n- id: target-ban-search-ip-order-page2\n category: target\n purpose: Ban search results ordered by IP must keep IP ordering on page 2; pagination must not fall back to username order.\n steps:\n - ? Open http://127.0.0.1:13200/ and wait until the FluxBB forum home is ready. Confirm styled UI assets loaded (not a bare unstyled text page)\n : Air theme CSS / FluxBB branding should be present (for example a link to style/Air.css or visible themed header).\n - If not already signed in, open Login and sign in with username owen.briggs and password slateQuill5!. Confirm login succeeds (welcome/admin navigation appears and the guest login form is gone).\n - Open Administration → Bans (admin_bans.php). Wait until the Bans page shows the \"Ban search\" form with an \"Order by\" control that includes \"IP address\" / IP and direction Ascending/Descending, and a Submit search control.\n - In Ban search, set Order by to IP address and direction to Ascending. Leave username/IP/email/message filters empty. Click Submit search once. Wait for the Ban search results page listing banned usernames.\n - Confirm page 1 of results loaded with multiple usernames of the seeded pattern aNN (for example a55 near the start under IP string ordering). Confirm a page-2 pagination link is present.\n - Click the page 2 link from the results pagination (the link produced by the results page itself). Wait for page 2 results to load.\n - Observe the usernames listed on page 2 in the results table.\n - Final verdict — FAIL only if page 2 shows the username-ordered remainder a51, a52, a53, a54, and a55 (evidence that pagination silently fell back from IP order to username order). PASS only if page 2 instead continues IP ordering and includes username a01 together with a50/a49/a48/a47 (or the same IP-order remainder), and does not present a51–a55 as the page-2 set. Do not PASS if only page 1 is still showing. Do not use fetch/XHR/page-context HTTP, DevTools Network, or API/SQL for pass/fail. Do not FAIL for login/navigation setup problems; use uncertain only if the product UI cannot be reached or observed reliably after retries.\n- id: preservation-admin-bans-search-form\n category: preservation\n purpose: After admin login, the Bans administration page should still expose Add ban and Ban search controls so adjacent ban management remains usable.\n steps:\n - Open http://127.0.0.1:13200/ and wait until the FluxBB UI is ready with styled assets.\n - If needed, log in with username owen.briggs and password slateQuill5! and confirm the authenticated session.\n - Open Administration → Bans (admin_bans.php). Wait for the Bans page to finish loading.\n - Confirm the page shows an Add ban control/section and the Ban search form with Order by and Submit search.\n - Final verdict — PASS if Add ban and Ban search (with Order by and Submit search) are all visible on the Bans page. FAIL if the Bans page loads but those controls are missing. Do not run a ban search or open page 2 in this workflow. Do not use fetch/XHR/API calls for this judgment. Use uncertain only if login or Bans navigation cannot be completed reliably.\n"} {"case_id": "sweeper-055", "slug": "flyspray", "repo": "https://github.com/flyspray/flyspray", "base_commit": "ff477863f65e4b243056dfbc98e322f85942c350", "reference_commit": "7c698ff9d19a522049ac18e3a97f92758c8b2bb2", "task_scoped": "Find and fix issues in Flyspray’s task reminder management.", "task_specified": "Fix Flyspray task reminder deletion: selecting a reminder on the Reminders tab and clicking Remove does nothing. Removing the selected reminder should show \"The selected reminder has been deleted.\" and the reminder should no longer appear in the list.", "pr": 872, "issue": null, "workflows": "workflows:\n- id: delete-task-reminder-persists\n category: target\n purpose: Removing a selected task reminder must delete it and show the success message.\n steps:\n - Navigate to http://127.0.0.1:13200/\n - Wait until the Flyspray page loads with the CleanFS theme (logo / styled chrome). If the login form fields are not already visible, click the \"Login!\" link/button (top right) so the Username and Password fields appear. Do not POST to authenticate without the form.\n - Type \"sasha.kirk\" into the Username field.\n - Type \"peatCrest7!\" into the Password field.\n - Click the Login submit control on that form and wait until you are logged in (Logout visible) and the task list shows \"Sample Task\".\n - Open the Sample Task details page (click Sample Task or go to http://127.0.0.1:13200/index.php?do=details&task_id=1).\n - Open the Reminders tab (link/text \"Reminders\") so the reminders table is visible.\n - Confirm the seeded reminder message containing the exact text \"Please review the sample task.\" is listed in the reminders table.\n - Check only the checkbox on the row whose message contains \"Please review the sample task.\" (do not select other reminder rows).\n - Click the Remove button in the reminders table footer and wait for the page to finish reloading without browser connection errors. If a brief connection error appears, reload the task details Reminders tab once and continue judging from the resulting UI.\n - Final verdict: FAIL only if after Remove the page still shows the reminder row with \"Please review the sample task.\" AND the success flash \"The selected reminder has been deleted.\" is absent. PASS only if that success flash is visible AND \"Please review the sample task.\" is no longer listed under Reminders. If login fails, Sample Task cannot be opened, or the Reminders tab/seeded row cannot be reached, treat as setup failure rather than product PASS/FAIL.\n- id: preserve-add-reminder\n category: preservation\n purpose: Adding a new reminder on the Sample Task must still succeed with a visible success message.\n steps:\n - Navigate to http://127.0.0.1:13200/\n - Wait until Flyspray loads. If Username/Password fields are not visible, click the \"Login!\" link so the login form appears.\n - Type \"sasha.kirk\" into the Username field.\n - Type \"peatCrest7!\" into the Password field.\n - Click the Login submit control and wait until you are logged in and can open Sample Task.\n - Open Sample Task details (http://127.0.0.1:13200/index.php?do=details&task_id=1).\n - Open the Reminders tab.\n - In the Add Reminder form, set \"Remind this user\" / to_user_id to \"sasha.kirk\" (type sasha.kirk in the user field if needed).\n - Set \"This often\" / timeamount1 to \"1\" and keep the interval as Days (or Hours if Days is unavailable).\n - Ensure a start date is present (default today is fine).\n - In the reminder message textarea, replace the text with exactly \"Follow up after standup\".\n - Click the Add Reminder button and wait for the page to reload.\n - Final verdict: PASS only if the success flash \"Your reminder has been added.\" is shown AND the Reminders list includes a row whose message contains \"Follow up after standup\". FAIL if that success message is missing or the new reminder row never appears. If login or the Add Reminder form cannot be used, treat as setup failure rather than product PASS.\n"} {"case_id": "sweeper-056", "slug": "focalboard", "repo": "https://github.com/mattermost/focalboard", "base_commit": "bddeeedd75350613a4e508b4ed0b03c1a99041d2", "reference_commit": "d39abc305d8064d000e5ad0b8acbeb804a86ab77", "task_scoped": "Find and fix issues in Focalboard’s board sharing and membership.", "task_specified": "Fix Focalboard board sharing so adding a member via Share also puts that board in the member's default sidebar category. After a user shares a board with another member, that member should see the board under Boards in their left sidebar.", "pr": 4133, "issue": 4130, "workflows": "workflows:\n- id: target-shared-board-appears-in-member-sidebar\n category: target\n purpose: 'After miraDunn shares a newly created board with kadeRue via Share, kadeRue''s left sidebar Boards category must list that board. On the buggy build kadeRue is a member but the board never appears in his sidebar.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/login and wait until the official Focalboard Log in page is visible: a styled rounded login card (not a bare unstyled text shell), the heading Log in, the username field with placeholder Enter username (id login-username), the password field with placeholder Enter password (id login-password), a filled Log in submit button, and the link or create an account if you don''t have one.\n\n '\n - 'Type exactly miraDunn into the username field. Type exactly Slate6quay into the password field. Click the Log in button. Wait until the signed-in Focalboard chrome loads: the left sidebar shows the Focalboard logo wordmark and version, and + Add board. If a Welcome To Boards page appears, click No thanks, I''ll figure it out myself. If login fails or the sidebar never appears, stop and treat that as a setup problem, not a product pass/fail.\n\n '\n - 'In the left sidebar click + Add board. Wait until the official Create a board template selector is visible (heading Create a board, templates on the left, preview on the right, buttons Use this template and Create empty board). Click Create empty board. Wait until a new board canvas opens with the title placeholder Untitled board and a top-right Share button.\n\n '\n - 'Click the Untitled board title (the large board title, not the view name Board view). Type exactly Q3 Launch Desk and press Enter or click away so the title saves. Confirm the board title now reads Q3 Launch Desk and that the same name appears under the sidebar Boards category. If the empty board never opened or the title would not save, stop and treat that as a setup problem.\n\n '\n - 'Click the top-right Share button (title Share board). Wait until the Share Board dialog is visible with the search placeholder Search for people and channels. Click that search field, type exactly kadeRue, and wait until a people result for @kadeRue appears. Click the @kadeRue result so kadeRue is added. Wait until the member list in the same dialog shows kadeRue (not only miraDunn / You). Close the dialog. If kadeRue cannot be found or added, stop and treat that as a setup problem, not the sidebar bug.\n\n '\n - 'Open the Focalboard logo menu at the top of the left sidebar (the wordmark Focalboard). Click Log out. Wait until the Log in page is visible again.\n\n '\n - 'Type exactly kadeRue into the username field. Type exactly Moss3vale into the password field. Click Log in. Wait until kadeRue''s signed-in Focalboard chrome loads (sidebar Focalboard logo and + Add board). If Welcome To Boards appears, click No thanks, I''ll figure it out myself. Use the browser reload/refresh once on this signed-in page so the sidebar refetches categories. If login fails, stop as a setup problem.\n\n '\n - 'After that refresh, look only at kadeRue''s left sidebar list under the Boards category (the system category named Boards). Do not open Find Boards / the board switcher (Ctrl/Cmd+K) and do not paste a board URL. Judge only whether the sidebar category lists a board titled Q3 Launch Desk.\n\n '\n - 'Final verdict — FAIL only if kadeRue is signed in, the left sidebar Boards category is visible, and Q3 Launch Desk is absent from that sidebar list (the shared board never landed in kadeRue''s default category). PASS only if that same sidebar Boards category lists Q3 Launch Desk. Do not PASS because miraDunn could share, or because kadeRue can log in. Do not FAIL for login/navigation/template-selector problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n- id: preservation-owner-empty-board-stays-in-sidebar\n category: preservation\n purpose: 'Creating an empty board as the owner must still place that board in the owner''s sidebar Boards category, so the create-board path stays intact while member-share category assignment is broken or fixed.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/login and wait until the official Focalboard Log in page is visible: styled login card, heading Log in, username and password fields, and a Log in button.\n\n '\n - 'Type exactly miraDunn into the username field. Type exactly Slate6quay into the password field. Click Log in. Wait until the signed-in sidebar shows Focalboard and + Add board. If Welcome To Boards appears, click No thanks, I''ll figure it out myself.\n\n '\n - 'Click + Add board. Wait until Create a board is visible. Click Create empty board. Wait until Untitled board and Share appear. Click the Untitled board title, type exactly Hiring Pipeline, and press Enter or click away so the title saves.\n\n '\n - 'Confirm the board canvas title is Hiring Pipeline. Then look at miraDunn''s left sidebar Boards category and confirm Hiring Pipeline is listed there. Use the browser reload/refresh once. If the login page appears, sign in again as miraDunn / Slate6quay. Wait until the sidebar Boards category is visible again.\n\n '\n - 'After that refresh, read only miraDunn''s left sidebar Boards category for a board titled Hiring Pipeline.\n\n '\n - 'Final verdict — PASS only if miraDunn is signed in and the sidebar Boards category lists Hiring Pipeline after the refresh. FAIL if that owner-created board is missing from her sidebar, or if creating the empty board showed a visible error. Do not FAIL because a different shared board is missing. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n"} {"case_id": "sweeper-057", "slug": "foodcoopshop", "repo": "https://github.com/foodcoopshop/foodcoopshop", "base_commit": "f90f5de1bc79517152e74ea33119461ab050fe6b", "reference_commit": "dbe8f19eb8d09a2defba3fb51c444035600ac5d8", "task_scoped": "Find and fix issues in FoodCoopShop’s shopping cart and checkout.", "task_specified": "Fix FoodCoopShop cart checkout validation: A product that remains in a member cart after it is deleted can still be ordered. Checkout should fail and show that the product is no longer activated and cannot be ordered.", "pr": 1098, "issue": 1097, "workflows": "workflows:\n- id: preservation-active-product-checkout-still-works\n category: preservation\n purpose: An always-active shop product can still be added to the official cart and ordered after checkout.\n steps:\n - 'Open http://127.0.0.1:13200/anmelden and wait until the official FoodCoopShop German sign-in page is visible (styled login form with Email and Passwort fields and an Anmelden button, not a bare-text shell). After Anmelden the next page may briefly be blank; wait until the shop chrome loads. Do not use fetch, XHR, or API shortcuts.\n\n '\n - 'Sign in as the shop member Rowan Pike: Email exactly rowan.pike@test.com and Password exactly siltGrove8!. Submit Anmelden. Wait until the official shop frontend is visible (logo/theme, navigation, \"Rowan Pike\"). If an accept-updated-terms overlay appears, accept it through the official UI. This setup must succeed before judging.\n\n '\n - 'Open http://127.0.0.1:13200/suche?keyword=crate%20parsnip and wait until the official catalog search results show the product named exactly crate parsnip. Click the official \"In den Warenkorb\" button for that product only (#btn-cart-9002). Confirm the product appears in the cart (sidebar or Warenkorb anzeigen). Quantity 1 or more is fine. Do not add lot fennel.\n\n '\n - 'Open http://127.0.0.1:13200/warenkorb/anzeigen and wait until the official cart-detail page lists crate parsnip. Check both official checkout checkboxes (AGB / general terms and Rücktrittsrecht / cancellation terms). Click the official green submit button \"Zahlungspflichtig bestellen\" (button.btn-order). Do not use fetch/XHR.\n\n '\n - 'Final verdict PASS only if ALL are true: (1) you signed in as Rowan Pike on the official shop UI, (2) crate parsnip was added via official \"In den Warenkorb\", AND (3) after clicking Zahlungspflichtig bestellen the official UI shows a successful order (page title/heading Bestellung abgeschlossen, or the text \"Deine Bestellung wurde erfolgreich abgeschlossen\" / \"Vielen Dank, deine Bestellung wurde erfolgreich abgeschlossen\"). Do not use fetch/XHR for setup, triggering, or scoring.\n\n '\n - 'Final verdict FAIL if checkout of the always-active crate parsnip product does not complete on the official cart UI. Do not FAIL for the deleted-product checkout bug. Do not FAIL for login/setup problems alone.\n\n '\n- id: target-deleted-product-checkout-blocked\n category: target\n purpose: After a manufacturer deletes a product that is already in a member cart, official checkout must fail and show that the product is no longer activated.\n steps:\n - 'Open http://127.0.0.1:13200/anmelden and wait until the official FoodCoopShop German sign-in page is visible (styled login form with Email and Passwort fields and an Anmelden button, not a bare-text shell). After Anmelden the next page may briefly be blank; wait until the shop chrome loads. Do not use fetch, XHR, or API shortcuts.\n\n '\n - 'Sign in as the shop member Elke Noll: Email exactly elke.noll@test.com and Password exactly peatRind7!. Submit Anmelden. Wait until the official shop frontend is visible (\"Elke Noll\"). If an accept-updated-terms overlay appears, accept it through the official UI. This setup must succeed before judging.\n\n '\n - 'Open http://127.0.0.1:13200/suche?keyword=lot%20fennel and wait until the official catalog search results show the product named exactly lot fennel. Click the official \"In den Warenkorb\" button for that product only (#btn-cart-9001). Confirm the cart shows lot fennel. Quantity 1 or more is fine. Do not add crate parsnip.\n\n '\n - 'Open http://127.0.0.1:13200/abmelden and finish any official logout confirm (Ja) so the header shows Anmelden. Then open http://127.0.0.1:13200/anmelden and sign in as the shop superadmin: Email exactly cal-hurst@admin.com and Password exactly mossDrift2!. Wait until the official admin chrome is visible (\"Cal Hurst\").\n\n '\n - 'Open http://127.0.0.1:13200/admin/products?manufacturerId=5 and wait until the official product-admin table lists products for Demo Gemüse-Hersteller, including a row whose name is lot fennel (tr#product-9001). Tick that row''s official checkbox only (input.row-marker). Open the official \"Aktionen...\" dropdown and click \"Löschen\" (#deleteSelectedProducts). In #modal-product-delete the official confirm button is labeled exactly \"Speichern\" (green); click Speichern once, not Abbrechen. Wait for the page to reload. Confirm deletion succeeded (lot fennel is gone from the list). Do not use SQL or API. Do not delete crate parsnip.\n\n '\n - 'Open http://127.0.0.1:13200/abmelden and finish any official logout confirm. Open http://127.0.0.1:13200/anmelden and sign in again as Elke Noll elke.noll@test.com / peatRind7!. Open http://127.0.0.1:13200/warenkorb/anzeigen and confirm the official cart still lists lot fennel. Check both official checkout checkboxes (AGB and Rücktrittsrecht). Click \"Zahlungspflichtig bestellen\" (button.btn-order). Do not use fetch/XHR.\n\n '\n - 'Final verdict FAIL only if ALL are true: (1) lot fennel was added to the member cart via official shop UI, (2) an admin deleted that product via official product-admin Löschen then Speichern (not deactivate only), (3) the member then submitted Zahlungspflichtig bestellen, AND (4) the official UI shows a successful order (Bestellung abgeschlossen / \"Deine Bestellung wurde erfolgreich abgeschlossen\" / \"Vielen Dank, deine Bestellung wurde erfolgreich abgeschlossen\") instead of blocking checkout. Do not FAIL for login, add-to-cart, or admin-delete setup problems alone.\n\n '\n - 'Final verdict PASS only if ALL are true: (1) the same shop add-to-cart → admin delete → member checkout path was followed, AND (2) after Zahlungspflichtig bestellen the official cart UI still shows checkout failed with the official message that the product is no longer activated and cannot be ordered (\"ist leider nicht mehr aktiviert und somit nicht mehr bestellbar\" or equivalent flash/error on the cart page). Do not PASS if you never clicked Zahlungspflichtig bestellen. Do not use fetch/XHR for setup, triggering, or scoring.\n\n '\n"} {"case_id": "sweeper-058", "slug": "forkcms", "repo": "https://github.com/forkcms/forkcms", "base_commit": "15d5de74c44b1f76598cbf3907979ac81dd27746", "reference_commit": "ac1f84026747cede60bdc996ee7a2b0cf486a610", "task_scoped": "Find and fix issues in Fork CMS’s page creation and editing.", "task_specified": "Fix Fork CMS page creation authentication checkboxes: Authentication required (and related auth groups / remove-from-search-index) are not persisted when adding a page. Saving a new page with Authentication required checked should keep that setting when the page is reopened.", "pr": 2882, "issue": null, "workflows": "workflows:\n- id: pages-add-auth-required-persists\n category: target\n purpose: Creating a page with Authentication required checked must persist that flag so reopening the page still shows it checked.\n steps:\n - Open http://127.0.0.1:13200/private/en/authentication/index\n - Wait until the Fork CMS backend login form is visible with email/password fields and styled admin chrome (not a bare unstyled page).\n - Log in with email hugo.quinn@admin.com and password brineOak5!, then submit.\n - Wait until the backend dashboard or module navigation is visible after login.\n - Open Add Page at http://127.0.0.1:13200/private/en/pages/add (or navigate Pages > Add).\n - Wait until the Add Page form is visible with a Title field and tabs including Authentication.\n - Enter the title Members Lounge into the Title field.\n - Open the Authentication tab (or scroll to the Authentication section) and check the checkbox labeled like \"Users need to be logged to view this page\" (auth_required / Authentication required).\n - Confirm that authentication-required checkbox is checked before saving.\n - Click Add page and wait for the save to finish.\n - Reopen the same page in the Edit form (follow the success redirect or open it from the Pages overview by title Members Lounge).\n - Wait until the Edit Page form is visible, open the Authentication section again, and observe the authentication-required checkbox.\n - Final verdict. FAIL only if this Add→save→reopen path shows the authentication-required checkbox unchecked / off after it was checked on create — the unique persistence bug on Pages Add. PASS only if that checkbox remains checked on the reopened Edit form for Members Lounge. Do not FAIL for login mistakes, missing Profiles module, or unrelated UI chrome.\n- id: pages-add-title-without-auth-preserved\n category: preservation\n purpose: Creating a normal page without authentication required must still save and reopen with its title.\n steps:\n - Open http://127.0.0.1:13200/private/en/authentication/index\n - Wait until the Fork CMS backend login form is visible.\n - Log in with email hugo.quinn@admin.com and password brineOak5!, then submit.\n - Wait until the backend is visible after login.\n - Open Add Page at http://127.0.0.1:13200/private/en/pages/add.\n - Wait until the Add Page form is visible with a Title field.\n - Enter the title Visit Hours into the Title field.\n - Leave Authentication required unchecked (do not enable authentication for this page).\n - Click Add page and wait for the save to finish.\n - Reopen the page titled Visit Hours from the Pages overview or success redirect.\n - Wait until the Edit Page form shows Title Visit Hours.\n - Final verdict. PASS only if Visit Hours was created and reopens with that title while Authentication required stays unchecked. FAIL only if a normal non-auth page fails to save or loses its title on reopen while the Add Page form was correctly used. Do not FAIL for login or navigation mistakes.\n"} {"case_id": "sweeper-059", "slug": "fossbilling", "repo": "https://github.com/FOSSBilling/FOSSBilling", "base_commit": "28d71f9e2ea1dadbb7033fff75e7dd8120e0c658", "reference_commit": "a7e545db30ebe1ac6dcaacb01395e0da68c34195", "task_scoped": "Find and fix issues in FOSSBilling’s invoice editing and approval workflow.", "task_specified": "Fix the FOSSBilling admin invoice Approve action: Clicking Approve on an unapproved invoice discards unsaved line-item edits because Approve only calls the approve API. Editing a line title and clicking Approve should save those changes and then approve the invoice so the approved invoice shows the edited title.", "pr": 3997, "issue": 3991, "workflows": "workflows:\n- id: target-approve-keeps-unsaved-line-title\n category: target\n purpose: 'Editing an unapproved invoice line title and clicking Approve (without Update) must persist the edited title on the approved invoice. On the buggy build Approve only approves and discards the unsaved edit, so the approved invoice still shows the original seeded title.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin and wait until the FOSSBilling admin sign-in page is visible (email and password fields).\n - Type exactly nora@test.com into the email / username field.\n - Type exactly Mist8grove into the password field.\n - Click the Login button and wait until the authenticated admin UI loads (dashboard or left navigation).\n - 'Open exactly http://127.0.0.1:13200/admin/invoice/manage/1 and wait until the invoice detail page for invoice #1 is visible, including an editable line Title input that currently shows Shared Hosting Plan and an Approve control.'\n - In the invoice line items table, clear the existing Title input for the seeded line and type exactly Approved Hosting Marker into that Title field. Do not click Update.\n - Click the green Approve button (not the Update button) and wait until the page finishes the approve action (redirect to invoice list and/or reload of the invoice detail).\n - If you are not already on the invoice detail page, open exactly http://127.0.0.1:13200/admin/invoice/manage/1 and wait until the approved invoice details are visible (line items are read-only after approval).\n - 'Look only at the visible invoice line title text on the approved invoice page. Decide which outcome you see: (A) the line title visibly shows Approved Hosting Marker, OR (B) the line title still shows Shared Hosting Plan (or does not show Approved Hosting Marker).'\n - Final verdict — PASS only if the approved invoice visibly shows the line title Approved Hosting Marker. FAIL only if the approved invoice still shows Shared Hosting Plan (or Approved Hosting Marker is missing). Do not FAIL for slow loads; use uncertain only if the invoice page cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-update-saves-line-title-without-approve\n category: preservation\n purpose: 'Clicking Update (without Approve) on an unapproved invoice must still save line title edits and leave the invoice editable/unapproved. This path already worked before the fix and must not regress.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin and wait until the FOSSBilling admin sign-in page is visible.\n - Type exactly nora@test.com into the email / username field.\n - Type exactly Mist8grove into the password field.\n - Click the Login button and wait until the authenticated admin UI loads.\n - Open exactly http://127.0.0.1:13200/admin/invoice/manage/2 and wait until the unapproved invoice edit form is visible with a Title input showing Shared Hosting Plan and both Update and Approve controls.\n - In the invoice line items table, clear the Title input and type exactly Updated Without Approve into that Title field.\n - Click the Update button (not Approve) and wait until the page reloads the invoice edit form.\n - Confirm the Title input still shows Updated Without Approve and that an Approve control is still present (invoice remains unapproved/editable).\n - Final verdict — PASS only if after Update the Title field visibly shows Updated Without Approve and Approve is still available. FAIL if the title reverted to Shared Hosting Plan, or if the invoice became approved/read-only after Update alone. Do not FAIL for slow loads; use uncertain only if the invoice form cannot be opened after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-060", "slug": "freescout", "repo": "https://github.com/freescout-help-desk/freescout", "base_commit": "6583d6f5a593b51223904f9e0f2e721e63c76de0", "reference_commit": "c35fc2a502b1caa993b63d1eaf12f074ef18c1ae", "task_scoped": "Find and fix issues in FreeScout’s conversation assignment and routing.", "task_specified": "Fix FreeScout conversation Move: Moving a conversation assigned to an agent into a mailbox that agent cannot access leaves the conversation assigned, so it never appears in the target mailbox Unassigned list and becomes hidden from everyone. That Move should unassign the conversation so it appears in the target mailbox Unassigned list.", "pr": null, "issue": 5333, "workflows": "workflows:\n- id: target-move-inaccessible-mailbox-unassigns\n category: target\n purpose: 'After Pax Rowe moves her assigned Mesa Intake conversation Crane inspection delay into Ledger Desk (a mailbox she cannot access) with the official Move Conversation modal, that ticket must appear in Ledger Desk Unassigned. On the buggy build it stays assigned to Pax and never shows in Unassigned.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/login and wait until the official FreeScout login is fully styled: FreeScout banner/logo, Email Address and Password fields, a Login submit, and compiled CSS (not a bare unstyled form). Do not use fetch/XHR.\n\n '\n - 'Type email `pax.rowe@test.com` and password `flintOak6!` into the official login form only. Click Login. Wait until you are signed in as Pax: the dashboard shows a Mesa Intake mailbox card (Mine count 1) and a Log Out control. You must NOT still be on the login form. Pax must NOT see a Ledger Desk mailbox card. If login failed, treat this as setup failure, not the Move bug.\n\n '\n - 'From the official dashboard, open Mesa Intake (mailbox name or Open Mailbox). Wait until the Mesa Intake conversation list loads with the left folder list Unassigned / Mine / Assigned. The default folder is Unassigned and will not contain Crane inspection delay. Do not use fetch/XHR.\n\n '\n - 'In the left folder list, click Mine (not Unassigned, not Assigned, not Starred). Wait until the Mine list shows the seeded ticket Crane inspection delay assigned to Pax Rowe. If Mine is empty or login/mailbox navigation failed, treat this as setup failure.\n\n '\n - 'Click the conversation row Crane inspection delay. Wait until the official conversation view loads: subject Crane inspection delay, thread/reply chrome, and the conversation action toolbar (Reply / Note / Delete plus a Move log-out icon). Do not open Merge. Do not use fetch/XHR.\n\n '\n - 'Click the official toolbar Move control (glyphicon-log-out / tooltip Move / aria-label Move). Stay on the conversation page. Wait until an in-page modal overlay titled Move Conversation appears on top of the conversation (the URL must remain /conversation/1, not a raw /conversation/ajax-html/ page). The modal has Select Mailbox (Pax''s list is empty) because she only has Mesa Intake) AND or Enter Mailbox Email. If you land on a bare unstyled fragment, go Back and click the toolbar Move icon again so the overlay modal opens. Do not type a conversation URL. Do not use fetch/XHR.\n\n '\n - 'In or Enter Mailbox Email, type exactly `ledger.desk@admin.com`. Do not pick Mesa Intake. Click the modal''s primary Move button (not Merge, not Cancel). Wait until the move finishes: a Conversation moved flash and/or redirect back to Mesa Intake. Pax cannot open Ledger Desk. If the modal never submitted or login expired, treat this as setup failure, not the bug.\n\n '\n - 'Open the account menu (Pax) and click Log Out. Wait until the official login page returns. Then log in as `ivo.nash@admin.com` / `brineVeld8!`. Confirm the signed-in dashboard shows both Mesa Intake and Ledger Desk. If this admin login fails, treat this as setup failure.\n\n '\n - 'From the dashboard, open Ledger Desk. Wait until that mailbox list loads. Click Unassigned in the left folder list (the default may already be Unassigned). Also open Assigned if needed to see where the ticket went. Do not use fetch/XHR.\n\n '\n - 'Final verdict — require both the correct scene and bug-specific list evidence. The scene is valid only if Pax used the official Move Conversation modal to send Crane inspection delay to ledger.desk@admin.com, then Ivo opened Ledger Desk Unassigned. FAIL only if that scene is valid AND Crane inspection delay is NOT visible in Ledger Desk Unassigned (it stays assigned to Pax Rowe, so Unassigned shows There are no conversations here, and/or the ticket is only in Assigned as Pax Rowe). PASS only if that same scene is valid AND Crane inspection delay is visible in Ledger Desk Unassigned (not still assigned to Pax on that Unassigned list). Setup/login/Move-modal failures are not product PASS/FAIL. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n- id: preservation-move-keeps-assignee-with-access\n category: preservation\n purpose: 'When Ivo Nash moves his own assigned Mesa Intake conversation Dock overtime approval into Ledger Desk (a mailbox he can access) with the official Move Conversation modal, the ticket must stay assigned to Ivo and appear in Ledger Desk Mine (FreeScout Assigned hides tickets assigned to the current user).\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/login and wait until the official FreeScout login is fully styled: FreeScout banner/logo, Email Address and Password fields, and a Login submit. If you are already signed in as Ivo Nash (dashboard/mailbox UI and Log Out), skip the form. Do not use fetch/XHR.\n\n '\n - 'If the login form is showing, type `ivo.nash@admin.com` and `brineVeld8!` and click Login. Wait until the dashboard shows Mesa Intake and Ledger Desk. If login failed, treat this as setup failure, not a product fail.\n\n '\n - 'Open Mesa Intake, then click Mine in the left folder list (Ivo''s assigned ticket is in Mine, not Unassigned). Open Dock overtime approval. Wait until that conversation view shows subject Dock overtime approval and the toolbar Move icon. Do not open Crane inspection delay. Do not use fetch/XHR.\n\n '\n - 'Click the official toolbar Move control (glyphicon-log-out / tooltip Move). Wait for the in-page Move Conversation modal overlay (not a raw ajax-html page). Select Mailbox already lists Ledger Desk (ledger.desk@admin.com). Select Ledger Desk. Leave Enter Mailbox Email empty. Click the modal''s primary Move button. Wait until Conversation moved / the conversation reloads in Ledger Desk.\n\n '\n - 'After the Move, stay in official UI. Confirm the conversation is still assigned to Ivo Nash (not Unassigned). Then open Ledger Desk Mine from the left folder list (not Assigned: Assigned only lists tickets assigned to other people, so Ivo''s own ticket will not appear there). You may also glance at Unassigned. Do not use fetch/XHR.\n\n '\n - 'Final verdict — PASS only if Dock overtime approval is visible in Ledger Desk Mine and still assigned to Ivo Nash, AND it is not sitting in Ledger Desk Unassigned as an unassigned ticket. Do not require it in Assigned: that folder omits the current user''s tickets. FAIL only if this same-access Move clearly dropped the assignee (the ticket is Unassigned in Ledger Desk, or the conversation view shows Unassigned instead of Ivo Nash). Do not FAIL because Pax''s inaccessible-mailbox Move later unassigns a different ticket, or because Assigned is empty of Ivo''s own ticket. Setup/login failures are not product FAIL. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n"} {"case_id": "sweeper-061", "slug": "freshrss", "repo": "https://github.com/FreshRSS/FreshRSS", "base_commit": "57e1a375cbd2db9741ff19167813344f8eff5772", "reference_commit": "aeecba7b30cf04a53fc23f7ed7a8c5ce12cb11a6", "task_scoped": "Find and fix issues in FreshRSS’s article reading and read-state controls.", "task_specified": "Fix FreshRSS category Mark all as read: Using Mark all as read in a category view also marks Important feeds in that category as read. Important feeds should keep their unread articles.", "pr": 8067, "issue": null, "workflows": "workflows:\n- id: preservation-ordinary-category-mark-all-read-still-clears\n category: preservation\n purpose: 'Mark all as read on the ordinary Quay Digest category must still clear unread articles on Quay Bulletin. Do not open Inkline News and do not change any feed Visibility.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/i/ and wait until the official FreshRSS Login page is fully styled: Origine/base theme CSS, the FreshRSS logo, a Username field, a Password field, and the Login submit button (#loginButton). Wait until that Login button is enabled (JavaScript/bcrypt init finished). Do not use fetch/XHR.\n\n '\n - 'Type username `iris.vale` and password `mistWire5!` into the official login form only. Click Login. Wait until you are inside the signed-in reading UI: the sidebar shows Main stream, Important feeds, Inkline News, Inkline Extra, Quay Digest, and Quay Bulletin. The seeded titles Inkline Brief Dispatch, Inkline Extra Notice, and Quay Bulletin Ledger should be reachable from those feeds. You must NOT still be on the Login form. If login failed, treat this as a setup problem, not a mark-as-read problem.\n\n '\n - 'Open the official Quay Digest category in the sidebar (the category title, not a feed). Do NOT open Inkline News. Do NOT open Subscription management. Do NOT change Visibility / Important. Wait until the unread stream for Quay Digest shows the article titled exactly `Quay Bulletin Ledger`. Confirm the footer button labelled Mark all as read (#bigMarkAsRead) is visible.\n\n '\n - 'Click the official Mark all as read button (#bigMarkAsRead, the large check-mark control with the text Mark all as read). Do not click Mark feed as read on a single feed menu. Wait until Quay Digest''s unread count is 0 and Quay Bulletin Ledger is no longer unread. The official default view is adaptive: once unread hits 0, Show read turns on as well, so the title may still appear on the right as a read article. Do not require an empty list.\n\n '\n - 'Open the official Quay Bulletin feed from the sidebar. Leave the official top-bar filters alone: after unread hits 0, adaptive default has both Show unread and Show read on (there is no All articles control). Do not click Favourites / Show starred. Confirm Quay Bulletin Ledger is no longer unread (sidebar unread count 0, title not shown as unread). Seeing that title as a read article in this adaptive all view is expected, not a fail.\n\n '\n - 'Final verdict — PASS only if, after Mark all as read on Quay Digest, Quay Bulletin Ledger is no longer unread on Quay Bulletin. FAIL only if Quay Bulletin Ledger is still unread there. Do not FAIL because the adaptive default still lists the now-read title, or because the list is not empty. Do not FAIL because Inkline Brief unread changed on Inkline News. Do not open Inkline News. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n- id: target-important-feed-unread-survives-category-mark-all-read\n category: target\n purpose: 'After Inkline Brief is marked Important and Mark all as read is used on the Inkline News category, Inkline Brief Dispatch must remain unread on Inkline Brief, while the ordinary Inkline Extra Notice in the same category is cleared.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/i/ and wait until the official FreshRSS Login page is fully styled: Origine/base theme CSS, the FreshRSS logo, a Username field, a Password field, and the Login submit button (#loginButton). Wait until that Login button is enabled (JavaScript/bcrypt init finished). Do not use fetch/XHR.\n\n '\n - 'Type username `iris.vale` and password `mistWire5!` into the official login form only. Click Login. Wait until you are inside the signed-in reading UI: the sidebar shows Main stream, Important feeds, Inkline News, Inkline Brief, Inkline Extra, and Quay Digest. You must NOT still be on the Login form. If login failed, treat this as a setup problem, not the Important-feed bug.\n\n '\n - 'Mark Inkline Brief as Important through the official UI only: click Subscription management (#btn-subscription). Open the Inkline Brief feed configuration (the configure / manage control for Inkline Brief, not Inkline Extra). On the feed form, set the Visibility select (#priority) to `Show in important feeds`. Click the first Submit button in that Information/Visibility section (do not click Remove). Wait until the page reports Feed has been updated, or the Visibility select stays on Show in important feeds after save. If you cannot save Visibility, treat this as a setup problem.\n\n '\n - 'Return to the official reading UI (the FreshRSS logo / Main stream). Confirm Important feeds lists Inkline Brief. Open the Inkline News category in the sidebar. Wait until the unread stream shows both `Inkline Brief Dispatch` and `Inkline Extra Notice`. Confirm the footer Mark all as read button (#bigMarkAsRead) is visible. If either seeded unread title is already missing before you click Mark all as read, treat this as a setup problem, not the bug.\n\n '\n - 'Click the official Mark all as read button (#bigMarkAsRead) on the Inkline News category stream. Do not use a single-feed Mark feed as read control. Wait until the stream refreshes. Then open the official Inkline Extra feed and confirm Inkline Extra Notice is no longer unread (this proves the category mark-all-as-read actually ran). Adaptive default may still list that title as a read article once unread hits 0; do not require it to vanish from the list. If Inkline Extra Notice is still unread, treat this as a setup/trigger problem, not a target pass.\n\n '\n - 'Open the official Inkline Brief feed from the sidebar (or from Important feeds). Leave the official top-bar filters on the adaptive default. Do not click Favourites / Show starred. Do not click the individual article read/unread envelope. Decide which outcome you see: (A) PASS signals — Inkline Brief Dispatch is still unread on Inkline Brief after the Inkline News mark-all-as-read, and Inkline Extra Notice was already cleared (no longer unread). (B) FAIL signals — Inkline Brief Dispatch is also no longer unread after that same Inkline News mark-all-as-read, and Inkline Extra Notice was cleared too. Adaptive default may still show the now-read title; judge unread status, not whether the list is empty. This FAIL is only valid if login succeeded, Inkline Brief was Important, and the category Mark all as read control was used.\n\n '\n - 'Final verdict — PASS only if outcome (A): after Mark all as read on Inkline News, Inkline Brief Dispatch remains unread on Inkline Brief while Inkline Extra Notice is no longer unread. FAIL only if outcome (B): that same category mark-all-as-read also cleared the unread status of Inkline Brief Dispatch. Do not PASS merely because Important feeds still exists in the sidebar or Inkline Extra still works. Do not FAIL because a now-read title still appears under adaptive Show read, or because the list is not empty. Do not FAIL because login failed, Visibility was never saved, or Mark all as read was never clicked. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n\n '\n"} {"case_id": "sweeper-062", "slug": "friendica", "repo": "https://github.com/friendica/friendica", "base_commit": "36f21801b9a3631c8334aa199f400e838b8ea248", "reference_commit": "81f9ac39193230a4b032a7ccb01c0bab710d3c45", "task_scoped": "Find and fix issues in Friendica’s profile settings.", "task_specified": "Fix Friendica custom profile field deletion so emptying a field label and saving removes that custom field. After clearing a custom field label on Settings Profile and submitting, that custom field should no longer appear among custom profile fields.", "pr": 15382, "issue": 14877, "workflows": "workflows:\n- id: target-empty-label-deletes-custom-profile-field\n category: target\n purpose: Emptying a custom profile field label and saving must remove that field from Settings Profile.\n steps:\n - Open http://127.0.0.1:13200/login and wait for the styled Friendica login page (Bootstrap/frio theme, Username/Nickname and Password fields, not a bare-text page).\n - Log in with username `cleoMarsh` and password `pineLatch8!`. After submit you may land on the home timeline or a profile-photo prompt; that is fine.\n - Open http://127.0.0.1:13200/settings/profile and wait for the Profile settings page with a Display name / username field (value should be Cleo Marsh or similar) and a Custom Profile Fields section.\n - Expand the Custom Profile Fields accordion/section if it is collapsed. Confirm a custom field whose label input shows `SeedHobby` (seeded field) is visible.\n - Clear ONLY the Label input of the SeedHobby custom field so the label is empty. Leave the Display name field non-empty (keep `Cleo Marsh`). Do not fill the New field label. Click the `Save settings` button inside the Custom Profile Fields section only — do not click the Personal section `Save settings` (there are two).\n - Wait until that Custom Profile Fields save actually reloads the page (URL should remain on settings/profile). If the click hits both Save buttons, or the page does not reload, do not judge yet. After a confirmed reload, expand Custom Profile Fields again if needed. Check whether the previous SeedHobby field still exists as a custom-field row (including a row whose Label is empty but Value is still `Photography`).\n - 'Final verdict: FAIL only if the Custom Profile Fields Save already reloaded the page AND the section still shows the previous custom-field row (SeedHobby label text still present, OR a remaining row with empty Label and Value Photography). PASS only if after that confirmed reload the custom-field row is gone and Custom Profile Fields shows only the Add a new profile field controls (no leftover Photography value row). If you cleared the label but could not click the Custom Profile Fields Save, or the page did not reload, judge uncertain — do not fail. Do not FAIL for login/navigation/setup failures before the empty-label submit. Do not use API/Network/DB as the oracle—only the visible Settings Profile form.'\n- id: preservation-custom-profile-field-create-persists\n category: preservation\n purpose: Creating a custom profile field with a non-empty label must still save and remain visible after reload.\n steps:\n - Open http://127.0.0.1:13200/login and wait for the styled Friendica login page.\n - Log in with username `cleoMarsh` and password `pineLatch8!`. Confirm you are signed in.\n - Open http://127.0.0.1:13200/settings/profile. Expand Custom Profile Fields if collapsed.\n - In the New custom field row, set Label to `KeepMe` and Value to `StayValue`. Keep Display name non-empty. Click Submit.\n - After reload, open http://127.0.0.1:13200/settings/profile again (or remain there), expand Custom Profile Fields, and check for a field with label `KeepMe`.\n - 'Final verdict: PASS only if a custom field labeled KeepMe is still visible after save/reload. FAIL if KeepMe does not appear after a successful-looking submit. Do not FAIL solely because SeedHobby is present or absent.'\n"} {"case_id": "sweeper-063", "slug": "frontaccounting", "repo": "https://github.com/FrontAccountingERP/FA", "base_commit": "214a39ccb46b642bf8427df1131f7fd408e075d1", "reference_commit": "6368404125a25ef75691791087070cb3044b1689", "task_scoped": "Find and fix issues in FrontAccounting’s journal entry editor.", "task_specified": "Fix FrontAccounting journal entry attachments: Editing and re-saving a journal that has more than one attachment leaves the extra files on the voided journal, so they disappear from the updated entry. All attachments should follow the edited journal.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-edited-journal-keeps-all-attachments\n category: target\n purpose: 'Re-saving a journal that has two attachments must keep both files on the updated journal. On the buggy build only one file follows the new trans_no, so the extra supporting document disappears from the journal view.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/index.php and wait until the official FrontAccounting login UI is visible: the FrontAccounting logo (themes/default/images/logo_frontaccounting.png), styled default theme CSS (not a bare unstyled text shell), User name, Password, a Company selector showing Training Co., and a Login submit control.\n\n '\n - 'Type exactly lenCroy into the User name field. Type exactly Pebble4ash into the Password field. Click Login. Wait until the signed-in FrontAccounting application chrome loads (top application tabs such as Sales, Purchases, Items and Inventory, Banking and General Ledger, Setup).\n\n '\n - 'Open exactly http://127.0.0.1:13200/gl/view/gl_trans_view.php?type_id=0&trans_no=100 and wait until General Ledger Transaction Details for Journal Entry #100 is visible. Confirm the page shows memo/text Q2 freight invoices and two Attached File links whose filenames are acme-freight-1842.pdf and fuel-card-0612.png. If login failed or those two files are not both listed, stop and treat that as a setup problem, not a product pass/fail.\n\n '\n - 'Open exactly http://127.0.0.1:13200/gl/inquiry/journal_inquiry.php and wait until Journal Inquiry is visible. In Memo type exactly Q2 freight invoices. Click Search. In the result row for Journal Entry / Trans # 100 / reference 101/2026, click the edit pencil icon (it opens gl_journal.php with ModifyGL=Yes, trans_no=100 and trans_type=0). If you type the edit URL yourself, it MUST include trans_type=0; without that parameter the page refuses the form — that is a navigation mistake, retry with trans_type=0. Wait until Modifying Journal Transaction # 100 shows the existing debit/credit lines and Process Journal Entry. Do not add or delete lines. Leave Include in tax register unchecked. Click Process Journal Entry. Wait until the official success view appears (it may auto-forward to UpdatedID) reporting Journal entry has been updated #N.\n\n '\n - 'On that update-success page, click View this Journal Entry (or open the GL view for the new journal number shown in the success text). Wait until General Ledger Transaction Details for that new Journal Entry number is visible. Do not open Setup / Attach Documents as the global attachment list; judge only the updated journal view.\n\n '\n - 'Final verdict — FAIL only if the updated journal view is the post-edit journal (new trans number, not voided #100) and it is missing one of the two supporting files: the Attached File links do not include both acme-freight-1842.pdf and fuel-card-0612.png (typically only one file followed the new number). PASS only if that same updated journal view lists Attached File links for both acme-freight-1842.pdf and fuel-card-0612.png. Do not PASS merely because login or the edit form loaded. Do not FAIL for login/navigation problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n- id: preservation-single-attachment-journal-still-edits\n category: preservation\n purpose: 'Re-saving a journal that has exactly one attachment must still keep that file on the updated journal, so the single-file path remains usable while the multi-file move is broken or fixed.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/index.php and wait until the official FrontAccounting login UI is visible (logo, User name, Password, Company, Login).\n\n '\n - 'If not already signed in, type exactly lenCroy into User name and exactly Pebble4ash into Password, then click Login. Wait until the signed-in application chrome is visible.\n\n '\n - 'Open exactly http://127.0.0.1:13200/gl/view/gl_trans_view.php?type_id=0&trans_no=101 and wait until General Ledger Transaction Details for Journal Entry #101 is visible. Confirm memo/text Petty cash 8/14 and an Attached File link for till-slip-0814.pdf. If that file is missing, stop and treat that as a setup problem, not a product pass/fail.\n\n '\n - 'Open exactly http://127.0.0.1:13200/gl/inquiry/journal_inquiry.php and wait until Journal Inquiry is visible. In Memo type exactly Petty cash 8/14. Click Search. In the result row for Journal Entry / Trans # 101 / reference 102/2026, click the edit pencil icon (ModifyGL=Yes, trans_no=101, trans_type=0). If you type the URL yourself it MUST include trans_type=0. Wait until Modifying Journal Transaction # 101 is visible. Do not add or delete lines. Leave Include in tax register unchecked. Click Process Journal Entry. Wait until the official success view appears (it may auto-forward to UpdatedID) reporting the journal entry has been updated with a new journal number.\n\n '\n - 'Click View this Journal Entry for that new number. Wait until General Ledger Transaction Details for the updated journal is visible.\n\n '\n - 'Final verdict — PASS only if the updated journal view (new trans number, not voided #101) still shows an Attached File link for till-slip-0814.pdf. FAIL only if that same updated journal view loaded and till-slip-0814.pdf is absent from the Attached File links. Do not FAIL for login/navigation problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n"} {"case_id": "sweeper-064", "slug": "froxlor", "repo": "https://github.com/Froxlor/Froxlor", "base_commit": "2987b0e8806ef12b532410050ad76d13d673a87d", "reference_commit": "77d04badf549d5f8429828f0fbc69bc37a35e07a", "task_scoped": "Find and fix issues in Froxlor’s allowed email sender management.", "task_specified": "Fix Froxlor allowed-sender domain ownership: A customer can save an allowed sender address on another customer's domain. Saving an allowed sender whose domain belongs to another customer on the same panel should be rejected.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-reject-foreign-domain-allowed-sender\n category: target\n purpose: A customer must not be able to add an allowed sender on another customer's domain.\n steps:\n - Open http://127.0.0.1:13200/index.php and wait until the official Froxlor login page is visible, including the Froxlor logo and the username/password form. If the page is a bare unstyled shell or the form is missing, treat this as setup failure, not a product verdict.\n - Log in as customer piaFenwick with password Brine9ketch by typing into the native loginname and password fields and clicking the official login submit button. Do not use fetch, XHR, or page-context HTTP.\n - After login, open Email in the official sidebar, then Addresses (or the email-address list if it opens directly). Confirm the official styled customer panel loaded, not a login redirect.\n - On the email-address list, find the row for orders@fenwick-mail.net. Open that row's Options menu and click Edit (not the address text itself). Wait until the official Edit email-address page is visible. Confirm the Allowed sender section and the Add allowed sender control are visible.\n - Click Add allowed sender. On the official Add allowed sender form, type accounts into the local-part field and quillan-host.net into the domain field (so the intended address is accounts@quillan-host.net). Submit with the official Save button. Do not use fetch, XHR, or page-context HTTP.\n - ? Final verdict — decide only from the official UI. Do not use fetch, XHR, or page-context HTTP to read APIs, the database, or JSON. PASS only if the scene is correct (logged in as piaFenwick, Add allowed sender was submitted) AND the product refuses the foreign-domain sender\n : an error such as Given domain \"quillan-host.net\" cannot be used is shown, and accounts@quillan-host.net does not appear as a saved Allowed sender. FAIL only if that same scene is correct AND the foreign sender is accepted (accounts@quillan-host.net is listed under Allowed sender, or the Edit email-address page shows Allowed sender (1) with accounts@quillan-host.net). Do not fail on login/selector/timeout problems.\n- id: preservation-own-domain-allowed-sender-still-works\n category: preservation\n purpose: A customer must still be able to add an allowed sender on a domain they own.\n steps:\n - Open http://127.0.0.1:13200/index.php and wait until the official Froxlor login page is visible with the logo and login form.\n - Log in as customer piaFenwick with password Brine9ketch using the native form. Do not use fetch, XHR, or page-context HTTP.\n - Open Email then Addresses (or the email-address list). On the email-address list, find the row for orders@fenwick-mail.net, open that row's Options menu, and click Edit. Wait until the official Edit email-address page is visible.\n - Click Add allowed sender. Type noreply into the local-part field and fenwick-mail.net into the domain field. Submit with the official Save button. Do not use fetch, XHR, or page-context HTTP.\n - Final verdict — decide only from the official UI. Do not use fetch, XHR, or page-context HTTP. PASS only if noreply@fenwick-mail.net is visible as a saved Allowed sender on orders@fenwick-mail.net (Allowed sender list or Allowed sender (1) showing that address) and no ownership-error page blocked the save. FAIL only if the scene is correct and the own-domain sender is missing or the UI shows Given domain \"fenwick-mail.net\" cannot be used. Do not fail on login/selector/timeout problems.\n"} {"case_id": "sweeper-065", "slug": "galette", "repo": "https://github.com/galette/galette", "base_commit": "d8ef698a5630b9fa3d72a3c2b6b1f92281fdf0aa", "reference_commit": "17c084132a82a8eece6349f1ca60787e48b20774", "task_scoped": "Find and fix issues in Galette’s contribution browsing and summaries.", "task_specified": "Fix Galette group-manager contribution listing so members who belong to several managed groups do not inflate contribution counts and totals. The contributions list total should count each contribution once instead of distorting the footer total via a groups join.", "pr": 900, "issue": null, "workflows": "workflows:\n- id: group-manager-contribution-total-no-duplicates\n category: target\n purpose: As a group manager who can see group members contributions, the contributions list total must count each contribution once even when a member belongs to multiple managed groups.\n steps:\n - Open http://127.0.0.1:13200/\n - If a language chooser or installer is shown, stop and report setup failure (the product should already be installed and seeded).\n - On the login page, sign in with username lucas.grant and password mapleNest4! using the normal login form. Confirm you reach an authenticated Galette page (member area / dashboard / menu), not a login error.\n - Open the Contributions list for all accessible contributions (navigate via the UI menu to Contributions, or open http://127.0.0.1:13200/contributions). Confirm the contributions table is visible.\n - Read the footer total line that reports the found contributions total. English text looks like Found contributions total followed by a number. Also note how many distinct contribution rows are listed in the table body.\n - 'Final verdict: PASS only if the scene is the group-manager contributions list AND the displayed total is exactly 192 or 192.00 (Renee 92+8 plus Lucas 92, each counted once). FAIL if the total is any other number — especially the buggy footer total 184 (or other JOIN/GROUP-BY distortion when Renee belongs to two managed groups) — or if contribution rows/totals are clearly wrong due to multi-group duplication. Do not PASS on login success alone; the total value is required.'\n- id: admin-contributions-total-preserved\n category: preservation\n purpose: Super-admin contributions listing still shows the correct unduplicated grand total for the same seeded contributions.\n steps:\n - Open http://127.0.0.1:13200/\n - If already logged in as another user, log out first using the UI.\n - Sign in with username siennaCole and password riverOak9! using the normal login form. Confirm you reach an authenticated admin Galette page.\n - Open the Contributions list (menu Contributions, or http://127.0.0.1:13200/contributions). Confirm the contributions table is visible.\n - Read the footer total line (Found contributions total ...).\n - 'Final verdict: PASS only if the admin contributions list is shown AND the displayed total is exactly 192 or 192.00 for the three seeded contributions. FAIL if the page errors, the list is empty, or the total is not 192/192.00.'\n"} {"case_id": "sweeper-066", "slug": "getsimplecms", "repo": "https://github.com/GetSimpleCMS/GetSimpleCMS", "base_commit": "8e010c90dfaf67a764d9509755fbc02f71edcb3f", "reference_commit": "11b4e270ac5df30d0adfd9b04341616d2657f14a", "task_scoped": "Find and fix issues in GetSimpleCMS’s page permalink configuration.", "task_specified": "Fix GetSimpleCMS page URL generation so that when Custom URLs are enabled, the custom URL structure actually takes effect.", "pr": 1279, "issue": 1133, "workflows": "workflows:\n- id: custom-permalink-view-link\n category: target\n purpose: With Enable Custom URLs checked and Custom URL Structure page/%slug%/, the About Page view (#) link must target /page/about/ from generate_url, not the default /about/.\n steps:\n - Open http://127.0.0.1:13200/admin/index.php\n - If a login form is shown, sign in with username \"LenaCrowe\" and password \"dockRidge6!\" and submit until the admin UI loads (Page Management or equivalent).\n - Open Settings via the admin navigation (Settings / General Settings) so the site settings form is visible. Scroll to the \"Custom URL Settings\" section, which has the checkbox labeled \"Enable Custom URLs\" (id prettyurls) and the \"Custom URL Structure\" text field (id permalink; often disabled until the checkbox is on).\n - Check \"Enable Custom URLs\" if it is not already checked.\n - Set the Custom URL Structure / permalink field to exactly: page/%slug%/\n - Save Settings with the settings submit button and confirm a success message such as settings updated, with no CSRF error.\n - Open Pages / Page Management from the admin navigation.\n - Locate the content page row titled \"About Page\" (slug about / tr id tr-about). Do not use the Welcome homepage, 404, or 403 rows.\n - On that same About Page row, find the \"#\" view control to the right of the Date column (title like \"View Page: About Page\"; do not click the page title, which opens edit.php). Read its href / link URL using element inspection. Stay on Page Management if possible; only click the link if href cannot be read, then note the address bar and return to Pages.\n - Final verdict: result=pass only if the About Page \"#\" view href/URL is exactly http://127.0.0.1:13200/page/about/. result=fail if it is http://127.0.0.1:13200/about/ (default pretty path — target bug). If the URL difference was clearly observed, do not use uncertain.\n- id: default-pretty-url-without-custom-permalink\n category: preservation\n purpose: Enable Custom URLs with an empty Custom URL Structure still targets the default pretty path /about/ for the About Page view link.\n steps:\n - Open http://127.0.0.1:13200/admin/index.php\n - If a login form is shown, sign in with username \"LenaCrowe\" and password \"dockRidge6!\" and submit until the admin UI loads.\n - Open Settings / General Settings and scroll to \"Custom URL Settings\".\n - Check \"Enable Custom URLs\" if it is not already checked.\n - Clear the Custom URL Structure / permalink field so it is completely empty.\n - Save Settings and confirm the save succeeds without a CSRF error.\n - Open Pages / Page Management.\n - Locate the content page row titled \"About Page\".\n - On that same row, find the \"#\" view control to the right of the Date column (title like \"View Page: About Page\"; not the page-title edit link). Read its href via element inspection without leaving the admin page if possible.\n - Final verdict: result=pass only if the About Page \"#\" view href/URL is exactly http://127.0.0.1:13200/about/. result=fail if it is index.php?id=about or /page/about/, or if Settings/login failed.\n"} {"case_id": "sweeper-067", "slug": "ghost", "repo": "https://github.com/TryGhost/Ghost", "base_commit": "e096fbc8ddbeebac8ec9dada014bfd2d03eedd15", "reference_commit": "0c743d67af0203f2d84decb05a976c75ffdd42a4", "task_scoped": "Find and fix issues in Ghost’s member profile management.", "task_specified": "Fix Ghost Admin newsletter resubscribe: turning on Subscribed to newsletter for an unsubscribed member and saving must persist after a full member-page reload.", "pr": 16490, "issue": null, "workflows": "workflows:\n- id: target-ada-newsletter-subscription-persists\n category: target\n purpose: 'After Maren Holt is switched to Subscribed to newsletter and saved, a hard browser refresh of Members plus reopening Maren Holt must still show that switch on. On the buggy build the switch is off again because subscribed:false clears the newsletters payload. Ember in-memory state after Save is not enough.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ghost/#/signin and wait until the official Ghost Admin sign-in is visible: the heading Sign in to Riverbend Dispatch., the Email address field, the Password field, a Sign in button, and the Ghost site icon / Admin theme (not a bare unstyled text shell).'\n - Type exactly eden@test.com into the Email address field. Type exactly peat9willow into the Password field. Click the Sign in button. Wait until the signed-in Ghost Admin shell loads (left menu includes Members, Posts, Pages, Settings). If you see Access denied or Invalid email or password, stop and treat that as a setup problem, not a product pass/fail.\n - Open exactly http://127.0.0.1:13200/ghost/#/members and wait until the Members list is visible. Click the row for Maren Holt (email maren@admin.com). Wait until the Edit member form is fully visible, including the Name field, the Email field, and the control whose heading is exactly Subscribed to newsletter. If Maren Holt is missing, stop and treat that as a setup problem.\n - 'Read only the control headed Subscribed to newsletter. Off means the knob is on the left and the track is grey/light. On means the knob is on the right and the track is green or dark-enabled. If it is already on, click it once so it is off, then click Save and wait until the member form finishes saving. The starting state for the next action must be: Maren Holt is visible and Subscribed to newsletter is off.'\n - Click the Subscribed to newsletter switch so it turns on (knob right, enabled track). Click Save. Wait until the save finishes (button shows Saved, no error banner). Do not open browser DevTools. Do not judge persistence yet — the form may still show the unsaved-looking on state from Ember memory.\n - 'Leave the member form: open exactly http://127.0.0.1:13200/ghost/#/posts and wait until the Posts list is visible. Then open exactly http://127.0.0.1:13200/ghost/#/members and use the browser reload/refresh on that Members page so Ghost Admin fully restarts (not just a hash change). If the sign-in page appears after refresh, sign in again with eden@test.com / peat9willow. Wait until the Members list is visible again, then click Maren Holt. Wait until the Edit member form and the Subscribed to newsletter heading are visible.'\n - 'After that hard refresh, read two visible things on Maren Holt''s Edit member page: (1) the control headed Subscribed to newsletter (off = knob left + grey/light track; on = knob right + green/enabled track); AND (2) the member Activity / events list on the same page. Look for the exact activity phrase subscribed to newsletter (Ghost shows it in lowercase). Ignore Labels, Note, and subscription-tier cards. Do not use the pre-refresh form state.'\n - 'Final verdict — PASS only if BOTH are true after the hard refresh: the Subscribed to newsletter switch is on AND the Activity list contains subscribed to newsletter. FAIL if the switch is off, OR the Activity list has no subscribed to newsletter line (for example it only shows signed up / Created manually). A dark-looking knob is not enough if Activity does not say subscribed to newsletter. Do not PASS because Save showed Saved, or because the switch looked on only before the refresh. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.'\n- id: preservation-new-member-newsletter-on-persists\n category: preservation\n purpose: 'Creating a new member while leaving Subscribed to newsletter on must still persist after a hard refresh, so the default subscribe-on-create path stays intact.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/ghost/#/signin and wait until the official Ghost Admin sign-in is visible with Sign in to Riverbend Dispatch., Email address, Password, Sign in, and the Ghost Admin theme.\n - Type exactly eden@test.com into the Email address field. Type exactly peat9willow into the Password field. Click the Sign in button. Wait until the signed-in Ghost Admin shell loads (left menu includes Members).\n - Open exactly http://127.0.0.1:13200/ghost/#/members/new and wait until the New member form is visible, including Name, Email, and the control headed Subscribed to newsletter.\n - Type exactly Cal Reed into the Name field. Type exactly cal@inbox.com into the Email field. Leave Subscribed to newsletter on (knob right / enabled track; if it is off, click it so it is on). Click Save. Wait until Ghost finishes creating the member and shows the saved member / Edit member view. If Save says Member already exists, do not fail — open the existing Cal Reed row instead.\n - Open exactly http://127.0.0.1:13200/ghost/#/posts and wait until Posts is visible. Then open exactly http://127.0.0.1:13200/ghost/#/members and use the browser reload/refresh on that Members page so Ghost Admin fully restarts. If sign-in appears, sign in again with eden@test.com / peat9willow. Wait until the Members list is visible, then click Cal Reed. Wait until Subscribed to newsletter is visible.\n - After that hard refresh, read Cal Reed's Subscribed to newsletter switch and the Activity / events list on the same Edit member page.\n - 'Final verdict — PASS only if BOTH are true after the hard refresh: Cal Reed''s Subscribed to newsletter switch is on (knob right, enabled track) AND the Activity list contains subscribed to newsletter. FAIL if Cal Reed is missing, the switch is off, or the Activity list has no subscribed to newsletter line. Do not FAIL only because Save said Member already exists for a leftover Cal Reed. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.'\n"} {"case_id": "sweeper-068", "slug": "ghostfolio", "repo": "https://github.com/ghostfolio/ghostfolio", "base_commit": "c71bfa21bd375d50b258d8d80a78d0941cd7ce66", "reference_commit": "29e9336baf5fcec963e90e3fe981b3a8e2ede713", "task_scoped": "Find and fix issues in Ghostfolio’s account cash balance management.", "task_specified": "Fix Ghostfolio account cash balance updates for SELL activities with fees: when a SELL activity is created with updateAccountBalance enabled and a non-zero fee, the account cash balance is credited by (quantity * unitPrice) + fee instead of (quantity * unitPrice) - fee. Creating a SELL with a fee should reduce cash by the fee so the resulting balance equals previous cash plus (quantity * unitPrice - fee).", "pr": 6862, "issue": null, "workflows": "workflows:\n- id: target-sell-with-fee-cash-balance\n category: target\n purpose: Creating a SELL activity with a non-zero fee and Update Cash Balance enabled must credit cash by (quantity * unitPrice - fee), not (quantity * unitPrice + fee).\n steps:\n - Open http://127.0.0.1:13200/en and wait until the Ghostfolio landing page is visible with the product title or Get Started control.\n - If you are already signed in (Get Started does not appear / you land in the authenticated app shell), open the top-right account/user menu and Sign out / Log out first, then return to http://127.0.0.1:13200/en so the landing page with Get Started is visible.\n - Click Get Started and complete registration until you are signed into the app (an access-token dialog may appear; continue/close it so the authenticated app shell is usable).\n - Open http://127.0.0.1:13200/en/portfolio/activities (or Portfolio → Activities) and wait until the Activities page is usable.\n - 'Create a BUY via the UI: click Add activity (or equivalent create control), set Type to Buy, in Name/symbol/ISIN search CORESELLFEE and select the Manual result (display name may be Core Sell Fee Test Equity), set Quantity 10, Unit Price 50, Fee 0, enable Update cash balance, save/create so the activity appears in the list. Note: Ghostfolio will create a user-owned Manual copy of this asset for your account; the holding is on that copy, not on the catalog seed row.'\n - 'Create a SELL via the UI: click Add activity again, set Type to Sell. In Name/symbol/ISIN, either clear the field and pick CORESELLFEE from the holdings/default suggestions, or search CORESELLFEE — if two Manual matches appear, you MUST select the one that is your bought holding (typically labeled just CORESELLFEE / the portfolio holding), NOT the seeded catalog entry named Core Sell Fee Test Equity. Selecting the catalog seed sells a different asset and fails. Set Quantity 10, Unit Price 60, Fee 5, enable Update cash balance, save/create so the sell activity appears.'\n - Open http://127.0.0.1:13200/en/accounts and wait until the Accounts table with a Cash Balance column is visible for My Account.\n - Final verdict — PASS only if the Accounts page Cash Balance for My Account shows exactly 95 (or 95.00 / $95 formatting that clearly equals ninety-five). FAIL if Cash Balance shows 105 (or 105.00 / $105), any other numeric cash balance, or the Accounts Cash Balance cannot be read.\n- id: preservation-buy-with-fee-still-debits-cash\n category: preservation\n purpose: Creating a BUY activity with a non-zero fee and Update Cash Balance enabled must still debit cash by quantity * unitPrice + fee.\n steps:\n - Open http://127.0.0.1:13200/en and wait until Ghostfolio is reachable.\n - If you are already signed in (Get Started does not appear / you land in the authenticated app shell), open the top-right account/user menu and Sign out / Log out first, then return to http://127.0.0.1:13200/en so registration/Get Started is available.\n - 'Isolate from prior target activities: open the register flow and create a brand-new user account (different credentials), then continue until the authenticated app shell is usable (close any access-token dialog).'\n - Open http://127.0.0.1:13200/en/portfolio/activities and wait until the Activities page is usable.\n - 'Create a BUY via the UI: Add activity → Type Buy → search PRESERVEBUYFEE and select the Manual result (display name may be Preserve Buy Fee Test Equity) → Quantity 10, Unit Price 50, Fee 5 → enable Update cash balance → save. (Same Manual behavior: Ghostfolio creates a user-owned copy for this BUY; no SELL is required in this workflow.)'\n - Open http://127.0.0.1:13200/en/accounts and wait until the Accounts table with Cash Balance is visible for My Account.\n - Final verdict — PASS only if the Accounts page Cash Balance for My Account shows exactly -505 (or -505.00 / formatting that clearly equals negative five hundred five), which is the correct BUY debit of 10*50+5. FAIL if the Cash Balance is missing, zero, -500, or any other value.\n"} {"case_id": "sweeper-069", "slug": "gitea", "repo": "https://github.com/go-gitea/gitea", "base_commit": "c337ff0ec70618ef2ead7850f90ab2a8458db192", "reference_commit": "681ae6aa42813917296dedebfc8777dd939f4025", "task_scoped": "Find and fix issues in Gitea’s profile and account settings forms.", "task_specified": "Fix Gitea account deletion so submitting an incorrect password reports an account-settings form error instead of returning a 500 server error. A signed-in user should remain on the account settings page, see that the password is incorrect, and keep their account intact.", "pr": 29579, "issue": 26210, "workflows": "workflows:\n- id: target-delete-account-wrong-password-shows-form-error\n category: target\n purpose: Deleting an account with an incorrect password must show a form error instead of a server error.\n steps:\n - Open http://127.0.0.1:13200 and wait for the Gitea sign-in page or dashboard. If another user is logged in, sign out first.\n - Log in with username `JordanLee` and password `Sk8board!`.\n - Open `http://127.0.0.1:13200/user/settings/account` and scroll to the `Delete Your Account` section.\n - In the delete-account password field, enter exactly `totallyWrong1`, click the red delete/confirm button, and confirm the modal if one appears.\n - Final verdict - PASS only if Gitea stays on the account settings page and shows a visible form error saying the password is incorrect, such as `The password you entered is incorrect`, while user `JordanLee` remains signed in. FAIL if a `500`, `Internal Server Error`, fatal error page, logout, or successful account deletion occurs.\n- id: preservation-profile-settings-still-save\n category: preservation\n purpose: Normal account profile settings must still save after the delete-account error handling change.\n steps:\n - Open http://127.0.0.1:13200 and wait for Gitea. If another user is logged in, sign out first.\n - Log in with username `MorganEllis` and password `BookClub!`.\n - Open `http://127.0.0.1:13200/user/settings` and wait for the profile settings form.\n - Set the full name field to exactly `Morgan Ellis`, save/update the profile, then reload the settings page.\n - Final verdict - PASS if the profile settings page reloads without a fatal error and the full name field still shows exactly `Morgan Ellis`. FAIL if saving profile settings breaks, shows a server error, logs the user out, or the value is not persisted.\n"} {"case_id": "sweeper-070", "slug": "glpi", "repo": "https://github.com/glpi-project/glpi", "base_commit": "71adc95c84211c075c6c9c4ba8accf8ad828f068", "reference_commit": "21cda0feb66071b11a986033532a801118f9a1b5", "task_scoped": "Find and fix issues in GLPI’s ticket creation forms.", "task_specified": "Fix ticket category selection in GLPI: selecting a recursive category from a parent entity while creating a ticket in a child entity clears the category. The selected category should remain after the form reloads.", "pr": 18244, "issue": 18240, "workflows": "workflows:\n- id: target-child-keeps-inherited-category\n category: target\n purpose: 'Creating a ticket in West Annex and choosing the inherited category Mail Relay Down must keep that category after the form reloads.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official GLPI login UI is visible: title Authentication - GLPI, the GLPI logo mark (span.glpi-logo), heading Login to your account, Login and Password fields, and a Sign in button. Styled with /public/lib/base.css and the auror palette — not a bare unstyled text shell or PHP error.\n\n '\n - 'Type exactly glpi into the Login field. Type exactly glpi into the Password field. Click Sign in. Wait until the signed-in Standard interface loads (sidebar with Assistance / Tickets, profile Super-Admin, current entity shown as Root entity or Root entity (tree structure)). If a development-version or optional-requirements banner appears, leave it; do not treat it as this bug.\n\n '\n - 'Open exactly http://127.0.0.1:13200/front/ticket.form.php?active_entity=1 and wait until the official New Ticket form is visible (title Ticket - New item - GLPI, a Ticket tab, Type, Entity, and Category). The form Entity field often still says Root entity even after that URL — that is expected. Open the form Entity dropdown (the Entity control on the ticket form, not the top-right profile menu) and choose exactly West Annex. Wait until Entity reads Root entity > West Annex or West Annex (the page may say Ticket will be added in entity West Annex). Do not click Add / Save. Do not change Type away from Incident if Incident is already selected. If a login page appears, sign in again with glpi / glpi and repeat this step.\n\n '\n - 'Confirm Entity is West Annex / Root entity > West Annex. Then open the Category dropdown (Select2). Choose exactly Mail Relay Down. The new-ticket form auto-submits on category change (this.form.submit). Wait until the Ticket form finishes reloading and both Entity and Category are visible again.\n\n '\n - 'Final verdict — judge only while Entity is still West Annex / Root entity > West Annex. FAIL only if Category is empty / ----- / not Mail Relay Down after that reload, proving the inherited parent-entity category was cleared. PASS only if Category still shows Mail Relay Down after the reload on that same West Annex ticket. Do not PASS if Entity is still Root entity (that is the wrong ticket entity; the inherited- category bug is not under test). Do not PASS merely because the form loaded. Do not FAIL for login or a missing Mail Relay Down option before selection — those are setup problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n- id: preservation-root-keeps-same-entity-category\n category: preservation\n purpose: 'Creating a ticket in Root entity and choosing Mail Relay Down must still keep that same-entity category after the form reloads.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official GLPI login UI is visible (GLPI logo, Login to your account, Sign in).\n\n '\n - 'If not already signed in, type exactly glpi into Login and exactly glpi into Password, then click Sign in. Wait until the Standard interface is visible (Assistance / Tickets, Super-Admin).\n\n '\n - 'Open exactly http://127.0.0.1:13200/front/ticket.form.php?active_entity=0 so the ticket is created in Root entity (do not use active_entity=1 / West Annex). Wait until the form Entity field is Root entity — not Root entity > West Annex / West Annex — and Category is empty (-----). If Entity is West Annex, open the form Entity dropdown and choose Root entity.\n\n '\n - 'Open Category and choose exactly Mail Relay Down. Wait for the auto-submit reload to finish.\n\n '\n - 'Final verdict — PASS only if Entity is still Root entity AND Category still shows Mail Relay Down after the reload. FAIL if Category is empty / ----- after that same-entity selection. Do not switch to West Annex. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n"} {"case_id": "sweeper-071", "slug": "goatcounter", "repo": "https://github.com/arp242/goatcounter", "base_commit": "478f026eb9deacb9378a46b96db72e11e9f20557", "reference_commit": "88aaf81e6c12e9f20ac0531a172d643bc148e346", "task_scoped": "Find and fix issues in GoatCounter’s dashboard statistics widgets.", "task_specified": "Fix GoatCounter Locations widget pagination so countries that share the same visit count keep a stable order across pages. A country that belongs on the first Locations page must stay there and must not be replaced by another tied country; after Show more, a tied country that belongs on the next page should appear exactly once, and a first-page country must not go missing.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-locations-pagination-tie-order\n category: target\n purpose: Verify Locations pagination keeps Switzerland on page 1 and does not repeat Russia after Show more when three countries share the same visit count.\n steps:\n - Navigate to http://127.0.0.1:13200/user/new\n - Wait until the GoatCounter sign-in form is visible (email and password fields, styled page with CSS/favicon — not a bare error page).\n - Using normal keyboard/mouse input only (no page-context fetch/XHR/API shortcuts), sign in with email sofia.nguyen@pinegauge.test and password VisitMap6!cedar. Submit the login form.\n - After login, open http://127.0.0.1:13200/. Wait until the signed-in dashboard loads with the Locations widget header visible.\n - Wait until the Locations widget shows populated country rows (not \"Nothing to display\"). You should see multiple country names such as United States and Brazil on the first page.\n - In the Locations widget, read the country names shown on the first page (default page size 6). Note whether Switzerland, Netherlands, and Russia appear.\n - Click the Locations widget \"Show more\" control exactly once. Wait for additional location rows to append.\n - Re-read all Locations country names now visible (first page plus newly loaded rows).\n - 'Final verdict - FAIL only if BOTH hold: (1) the scene is the signed-in GoatCounter dashboard with a populated Locations widget, AND (2) Switzerland is missing from the first page of Locations while Russia appears there, OR Russia appears more than once across the first page plus the Show-more page. That pattern is the ORDER BY mismatch bug. PASS only if BOTH hold: (1) the same signed-in Locations scene is correct, AND (2) Switzerland appears exactly once in Locations, Russia appears exactly once, and Switzerland is present among the first six Locations rows (with Netherlands) while Russia is only among the Show-more rows. Do not FAIL for login failure, missing widgets, empty Locations, or unrelated dashboard chrome.'\n- id: preservation-locations-top-countries-listed\n category: preservation\n purpose: Verify the Locations widget still lists the highest-count countries United States and Brazil on the first page after login.\n steps:\n - Navigate to http://127.0.0.1:13200/user/new\n - Wait until the GoatCounter sign-in form is visible.\n - Using normal keyboard/mouse input only (no page-context fetch/XHR/API shortcuts), sign in with email sofia.nguyen@pinegauge.test and password VisitMap6!cedar. Submit the login form.\n - After login, open http://127.0.0.1:13200/. Wait until the signed-in dashboard loads and the Locations widget shows populated country rows (not Nothing to display).\n - 'Final verdict - PASS only if BOTH hold: (1) signed-in dashboard with Locations widget showing country rows, AND (2) the first page of Locations includes both United States and Brazil (the two highest seeded visit counts). FAIL only if that same signed-in Locations scene is present but United States or Brazil is missing from the first page of Locations. Do not FAIL for login/setup problems or unrelated widgets.'\n"} {"case_id": "sweeper-072", "slug": "gogs", "repo": "https://github.com/gogs/gogs", "base_commit": "ca4c656be5e3d5249f6a230dff8124a0d6bcefd9", "reference_commit": "11e19f28b5c82466fd1689c94344ef4313ee986c", "task_scoped": "Find and fix issues in Gogs’s repository mirror configuration.", "task_specified": "Fix Gogs repository mirror settings so updating Mirror Address validates the remote the same way migration does. Entering a local-network HTTP URL must show a visible form error that the clone address resolved to a blocked local network address and must not persist that address. Updating mirror settings with a valid permitted address must still succeed.", "pr": 8225, "issue": null, "workflows": "workflows:\n- id: target-mirror-address-blocks-local-network-url\n category: target\n purpose: Updating a mirror repository address to a local-network HTTP URL must be rejected with a visible form error instead of being saved.\n steps:\n - Open http://127.0.0.1:13200/user/sign-in and wait until the Gogs sign-in form is visible (username, password, Sign in). If another account is already signed in, sign out first.\n - Type username `miraokada` and password `cedarQuill42!` into the sign-in fields using normal keyboard input (do not use page-context fetch/XHR/API shortcuts). Click Sign in and wait until a logged-in Gogs page appears (dashboard/home/profile chrome).\n - Open http://127.0.0.1:13200/miraokada/seedmirror/settings and wait for the classic repository Settings page with a Mirror Settings section and a Mirror Address input.\n - In the Mirror Settings form only, set Mirror Address to exactly `http://127.0.0.1/ssrf-probe.git`. Keep Mirror Interval at `8` if shown. Click the green Update Settings button in that Mirror Settings form (not avatar/delete/convert forms) and wait for the page response.\n - 'Final verdict - PASS only if BOTH are true: (1) a visible negative/error message contains exactly `Clone address resolved to a local network address that is implicitly blocked`, and (2) Mirror Address is NOT saved as `http://127.0.0.1/ssrf-probe.git` (it should remain a previous safe value such as `/opt/seed-origin.git`) and the page does not show mirror-of `http://127.0.0.1/ssrf-probe.git`. FAIL if a positive success flash contains `Repository options has been updated successfully`, OR Mirror Address / mirror-of shows `http://127.0.0.1/ssrf-probe.git`.'\n- id: preservation-valid-mirror-address-still-updates\n category: preservation\n purpose: Updating mirror settings with a valid local-path mirror address must still succeed after the validation fix.\n steps:\n - Open http://127.0.0.1:13200/user/sign-in if needed and sign in with username `miraokada` and password `cedarQuill42!` using normal UI input. Wait until logged in.\n - Open http://127.0.0.1:13200/miraokada/seedmirror/settings and wait for Mirror Settings.\n - In the Mirror Settings form, set Mirror Address to exactly `/opt/seed-origin.git` and Mirror Interval to exactly `12`. Click the green Update Settings button in that Mirror Settings form and wait for the page to reload/respond.\n - Final verdict - PASS only if a visible success message contains `Repository options has been updated successfully` AND Mirror Address shows `/opt/seed-origin.git` AND Mirror Interval shows `12`. FAIL if a blocked-local-address error appears for this valid path, if a server error/500 appears, or if the values are not persisted.\n"} {"case_id": "sweeper-073", "slug": "gotify", "repo": "https://github.com/gotify/server", "base_commit": "ad137d69ad9e89471e838f9a90c52a297704c8aa", "reference_commit": "d09ea4e169f1bf5e9fa4ae8d21c3aa6fd9df2df8", "task_scoped": "Find and fix issues in Gotify’s user management.", "task_specified": "Fix Gotify user updates so promoting or editing an OIDC-registered user does not drop their OIDC binding. After an admin edits that user in the Users page, Login with OIDC for the same identity should still succeed instead of reporting that a local user already exists while linking by username is disabled.", "pr": 1010, "issue": 1009, "workflows": "workflows:\n- id: target-oidc-binding-preserved-after-admin-user-edit\n category: target\n purpose: Promoting an OIDC-registered user to admin via the Users page must keep their OIDC binding so a later Login with OIDC still succeeds.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the styled Gotify login page is fully loaded (Gotify branding/favicon/MUI theme present — not a bare text shell). Confirm the page shows a Username/Password login form and a \"Login with OIDC\" button (#oidc-login).\n\n '\n - 'Using only normal clicks (no page-context fetch/XHR/API shortcuts), click \"Login with OIDC\". On the Dex login page, type email rowan.klein@notifyhub.test into the login field (#login), type CloudBell7!oak into #password, and click the submit control (#submit-login). Wait until Gotify finishes the OIDC callback and you are signed in (UI shows All Messages / message list and a logout control). Then click Logout and wait until the Gotify login form is shown again (Username/Password fields and #oidc-login visible). Do not continue until logout has fully returned you to the login page.\n\n '\n - 'On the Gotify login page, sign in with the local admin account using only the native MUI form (no page-context fetch/XHR/API shortcuts): click the Username field (#username), type jade-orion; click the Password field (#password), carefully type PushNote8!willow, then click the Login button. Wait until you are signed in. Open Users via the in-app navigation or by going to http://127.0.0.1:13200/#/users. If an \"Authentication Required\" elevation form appears, enter password PushNote8!willow and submit elevation, then confirm the Users page heading and #user-table are visible. The table must include a non-admin user named rowan-klein (created by the earlier OIDC auto-register).\n\n '\n - 'In #user-table, open the edit dialog for user rowan-klein (edit control in that row). In #add-edit-user-dialog, enable \"has administrator rights\" (.admin-rights) and click Save (.save-create). Wait until the dialog closes and the Users table shows rowan-klein with Admin=Yes. Then log out.\n\n '\n - 'On the Gotify login page again, click \"Login with OIDC\". On Dex, sign in again as rowan.klein@notifyhub.test / CloudBell7!oak and submit. Wait for the browser to return through Gotify''s OIDC callback path.\n\n '\n - 'Final verdict PASS only if ALL are true after that second OIDC login: (1) OIDC completes successfully into the signed-in Gotify UI (All Messages / message list visible, logout control present), AND (2) the callback/body does NOT show the bug-specific rejection text that a local user with the username rowan-klein already exists and linking by username is disabled. Final verdict FAIL only if the Users edit of rowan-klein to Admin=Yes was completed AND the second OIDC login fails with that bug-specific visible rejection about rowan-klein already existing while linking by username is disabled (plain text on the OIDC callback page is enough). Do not FAIL for Dex/login/setup/asset problems, inability to reach Users, or unrelated auth errors.\n\n '\n- id: preservation-local-admin-password-login\n category: preservation\n purpose: Local admin username/password login must still reach the signed-in Gotify message UI.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the styled Gotify login page loads (Username/Password form visible). If already signed in, log out first so the login form is shown.\n\n '\n - 'Using only the native MUI login form (no page-context fetch/XHR/API shortcuts), click Username (#username) and type jade-orion, click Password (#password) and carefully type PushNote8!willow, then click Login.\n\n '\n - 'Final verdict PASS only if the admin password login succeeds and the signed-in Gotify UI is shown (All Messages / message list and a logout control). Final verdict FAIL only if that login form was reached and jade-orion / PushNote8!willow password login fails to enter the signed-in UI. Do not FAIL for unrelated OIDC or asset issues.\n\n '\n"} {"case_id": "sweeper-074", "slug": "grocy", "repo": "https://github.com/grocy/grocy", "base_commit": "57d70851c8d5031691f9a3046292e9de08b91b69", "reference_commit": "312dd8a200e2ccb800e1269b0890021957528ebe", "task_scoped": "Find and fix issues in grocy’s stock transactions.", "task_specified": "Fix grocy stock transfer and open/split so a stock entry note is copied onto newly created stock rows. When a user purchases stock with a note and then partially transfers it to another location, the destination stock entry should still show the same note.", "pr": null, "issue": 1961, "workflows": "workflows:\n- id: target-transfer-keeps-stock-note\n category: target\n purpose: Partially transferring a stock entry that has a note should keep that note on the destination stock entry.\n steps:\n - Open `http://127.0.0.1:13200/` once and wait for redirect/settle so the demo app is ready, then open `http://127.0.0.1:13200/purchase` and wait until the Purchase form heading is visible.\n - On the Purchase form, set Product to `Cookies`. Set Amount to `2`. For Due date, either enter `2030-12-31` or check `Never overdue`. Set Location to `Candy cupboard`. In the Note field, type exactly `CORE_KEEP_NOTE_1962`. Click the green `OK` button (`#save-purchase-button`) and wait until the purchase succeeds (success toast/message or the form resets ready for another purchase).\n - Open `http://127.0.0.1:13200/transfer` and wait until the Transfer form heading is visible. Set Product to `Cookies`. Set From location to `Candy cupboard`. Set Amount to `1`. Set To location to `Pantry`. Click the green `OK` button (`#save-transfer-button`) and wait until the transfer succeeds.\n - Open `http://127.0.0.1:13200/stockentries` and wait for the Stock entries table to load.\n - In the Location filter dropdown (`#location-filter`), choose `Pantry` so only Pantry stock rows remain visible.\n - Find the visible Cookies stock entry row at Pantry. Read the Note cell for that row.\n - Final verdict - PASS only if a Cookies stock entry is visible under the Pantry filter AND its Note cell shows exactly `CORE_KEEP_NOTE_1962`. FAIL if the Pantry Cookies entry is missing, if its Note cell is empty, or if the note text is anything other than `CORE_KEEP_NOTE_1962`.\n- id: preservation-purchase-note-still-saved\n category: preservation\n purpose: Purchasing a product with a note should still show that note on the stock entry without needing a transfer.\n steps:\n - Open `http://127.0.0.1:13200/purchase` and wait until the Purchase form heading is visible.\n - On the Purchase form, set Product to `Gummy bears`. Set Amount to `1`. For Due date, either enter `2030-12-31` or check `Never overdue`. Optionally leave Location at the product default. In the Note field, type exactly `PRESERVE_NOTE_OK_1962`. Click the green `OK` button (`#save-purchase-button`) and wait until the purchase succeeds.\n - Open `http://127.0.0.1:13200/stockentries` and wait for the Stock entries table to load.\n - If a Location filter is active, set it to `All` or click Clear filter. Use the Product filter to select `Gummy bears` (or scan the table for a Gummy bears row).\n - Final verdict - PASS only if a Gummy bears stock entry is visible and its Note cell shows exactly `PRESERVE_NOTE_OK_1962`. FAIL if that note text is missing from the stock entries table.\n"} {"case_id": "sweeper-075", "slug": "healthchecks", "repo": "https://github.com/healthchecks/healthchecks", "base_commit": "2f983279935798b33e9c37f63f53051b0b5dc960", "reference_commit": "10fdc078c6ab0a74dfbe208b1a34c4eb67140857", "task_scoped": "Find and fix issues in Healthchecks’ notification integration setup and editing forms.", "task_specified": "Fix the Healthchecks ntfy integration form: When server-side validation fails after submit, the selected down and up priority values are not preserved on the reloaded form. The selected priority values should remain selected after a validation error.", "pr": null, "issue": null, "workflows": "workflows:\n- id: target-ntfy-priorities-preserved-on-validation-error\n category: target\n purpose: After an invalid ntfy URL fails server validation, the selected down/up priorities must remain selected on the reloaded form.\n steps:\n - Open http://127.0.0.1:13200/accounts/login/ and wait until the Healthchecks sign-in page is visible with email/password fields (styled page with branding/logo, not a bare-text shell).\n - Sign in with email `sora.tanaka@test.com` and password `lanternKite9!`. Wait until you leave the login page.\n - Open http://127.0.0.1:13200/projects/11111111-1111-1111-1111-111111111111/add_ntfy/ and wait for the ntfy integration settings form (heading containing `ntfy`, Topic field, Server URL field, and two priority dropdowns for down/up events).\n - Using only UI controls, fill Topic = `nightly-cron`; Server URL = `this is not an url`; leave Access Token empty; set Priority for down events to the option beginning with `Min priority`; set Priority for up events to the option beginning with `Disabled`.\n - Click the primary save/submit button and wait for the same ntfy form to reload with a visible Server URL validation error such as `Enter a valid URL`.\n - Read the currently selected option text in both priority dropdowns on the reloaded form.\n - 'Final verdict — PASS only if all are true together: (1) still on the ntfy form page, (2) a visible URL validation error such as `Enter a valid URL` is shown, (3) down-events priority select still shows `Min priority` selected, and (4) up-events priority select still shows `Disabled` selected. FAIL if either priority select has reset to another choice (for example `Default priority` or `Max priority`), even if the URL error is visible. Do not PASS from topic preservation alone.'\n- id: preservation-ntfy-valid-create-still-works\n category: preservation\n purpose: A valid ntfy integration submission must still create the channel and return to the integrations list.\n steps:\n - Open http://127.0.0.1:13200/accounts/login/ and wait for the Healthchecks sign-in page. If already signed in, continue; otherwise sign in with email `sora.tanaka@test.com` and password `lanternKite9!`.\n - Open http://127.0.0.1:13200/projects/11111111-1111-1111-1111-111111111111/add_ntfy/ and wait for the ntfy form.\n - Fill: Topic = `status-alerts`; Server URL = `https://example.org`; Priority for down events = `Max priority`; Priority for up events = `Min priority`. Submit with the primary save button.\n - Wait until you are on the project integrations/channels list (`/projects/11111111-1111-1111-1111-111111111111/integrations/` or equivalent).\n - Final verdict — PASS only if the integrations list is shown and contains a visible ntfy entry mentioning topic `status-alerts` (and/or `example.org`). FAIL if the form remains with a validation/server error or the new ntfy channel is missing from the list.\n"} {"case_id": "sweeper-076", "slug": "heimdall", "repo": "https://github.com/linuxserver/Heimdall", "base_commit": "a1f0d8f75d1c1f7f242a4b54390d8e7f5cac32f6", "reference_commit": "caa4f39edd9bb4773d64c08df7c6464f1ab9cb95", "task_scoped": "Find and fix issues in Heimdall’s application import and export tools.", "task_specified": "Fix Heimdall item export and import so tag assignments round-trip: exporting items must include their tag titles and importing that export must restore those tags instead of forcing every item onto the default dashboard. After creating a tagged item, exporting, deleting it, and importing the export, the item should still show its original tag in the application list.", "pr": 1567, "issue": 1555, "workflows": "workflows:\n- id: preservation-untagged-item-import-roundtrip\n category: preservation\n purpose: Exporting and re-importing an item without a custom tag should still recreate that item on the application list.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the Heimdall dashboard loads. Confirm branded UI (page title Heimdall, CSS applied, favicon/logo assets present — not a bare-text shell).\n\n '\n - 'Open http://127.0.0.1:13200/items/create. Create an application/item with title exactly `PreservePlainApp`, URL exactly `http://preserve-plain.example.test`, leave tags at the default Home dashboard only (no custom tag), and save. If the tags multi-select is hard to drive, use page context to submit the same repo-native create form / POST to `/items` with CSRF and tags=[0] only. Wait until save completes.\n\n '\n - 'Open http://127.0.0.1:13200/items and confirm `PreservePlainApp` is listed.\n\n '\n - 'Using page context on the Heimdall origin: GET `/api/item` and keep the JSON export that includes `PreservePlainApp`. Then delete the `PreservePlainApp` item through the items list UI (or an equivalent DELETE to the item''s destroy route with CSRF). Confirm it is gone from `/items`.\n\n '\n - 'Open http://127.0.0.1:13200/import. Using page context, create a File named `HeimdallExport.json` from the exported JSON and assign it to `input[name=''import'']`, then dispatch a change event (or click Import) so the repo-native import path runs. Wait until the import status shows success for `PreservePlainApp`.\n\n '\n - 'Open http://127.0.0.1:13200/items and wait for the list to refresh.\n\n '\n - 'Final verdict — PASS only if `PreservePlainApp` is visible again in the application list after the export→delete→import round-trip. FAIL if the item is missing after import or import clearly failed. Do not require a custom tag for this workflow.\n\n '\n- id: target-export-import-preserves-item-tags\n category: target\n purpose: Exporting an item that has a custom tag and re-importing it must restore that tag assignment in the UI.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the Heimdall dashboard loads with branded UI (Heimdall title/logo/CSS — not a bare-text shell).\n\n '\n - 'Open http://127.0.0.1:13200/tags/create. Create a tag named exactly `MediaSection` and save. Confirm it appears on http://127.0.0.1:13200/tags.\n\n '\n - 'Open http://127.0.0.1:13200/items/create. Create an item titled exactly `TaggedExportApp` with URL exactly `http://tagged-export.example.test`, assign the `MediaSection` tag (Home dashboard may also be selected), and save. If the Select2 tags control is unreliable, use page context to submit the repo-native `/items` create form with CSRF, including the numeric id for `MediaSection` in `tags[]` (and optionally 0 for Home dashboard).\n\n '\n - 'Open http://127.0.0.1:13200/items. Confirm the `TaggedExportApp` row''s tags cell includes `MediaSection` before testing export/import.\n\n '\n - 'Using page context on the Heimdall origin: GET `/api/item` and keep that JSON as the export payload (this is the same endpoint the Settings Export button uses). Then delete only the `TaggedExportApp` item (keep the `MediaSection` tag). Confirm `TaggedExportApp` is absent from `/items`.\n\n '\n - 'Open http://127.0.0.1:13200/import. Using page context, create a File named `HeimdallExport.json` from the export JSON, assign it to `input[name=''import'']`, and dispatch change / click Import so the repo-native importer runs. Wait until import status reports success for `TaggedExportApp`.\n\n '\n - 'Open http://127.0.0.1:13200/items and locate the `TaggedExportApp` row.\n\n '\n - 'Final verdict — PASS only if `TaggedExportApp` is listed AND its tags cell visibly includes `MediaSection` after the export→delete→import round-trip. FAIL only if the bug is present: `TaggedExportApp` reappears but its tags cell does not include `MediaSection` (for example only Home dashboard / empty custom tag). Do not PASS based on API JSON alone; the items-list tags column is the oracle. If setup (tag/item create, export, or import UI) cannot be completed, report uncertain — not a product FAIL.\n\n '\n"} {"case_id": "sweeper-077", "slug": "homarr", "repo": "https://github.com/ajnart/homarr", "base_commit": "4933b4f60d053b1afb23b6d727abb942257779cf", "reference_commit": "02249d20c2578edaea3eaea1507ec8e854433886", "task_scoped": "Find and fix issues in Homarr’s board creation and management interface.", "task_specified": "Fix Homarr board creation: Creating a board with a name that already exists overwrites the existing board without an error. Submitting a duplicate board name should show that the config already exists and should keep the original board intact.", "pr": 1887, "issue": null, "workflows": "workflows:\n- id: target-duplicate-board-name-rejected\n category: target\n purpose: Creating a board with a name that already exists must show a conflict error and must not overwrite the existing board.\n steps:\n - 'Open http://127.0.0.1:13200/onboard. If redirected elsewhere, open that URL. Wait until the Welcome to Homarr page is visible with the Homarr logo.\n\n '\n - 'Click the button labeled \"Start update process\". Wait until the account-creation step is visible (username and password fields, \"Create your administrator account\").\n\n '\n - 'Create the administrator account with Username exactly `JulesNguyen`, Password exactly `copperBell3!`, and the same value in the password confirmation field. Submit the form. Wait until the finished onboarding screen appears (\"Congratulations\" / next-step links).\n\n '\n - 'Open http://127.0.0.1:13200/manage/boards directly (or use \"Go to the management dashboard\" then Boards). Wait until the Boards management page is visible with a Create / create-board control.\n\n '\n - 'Click Create (create board). In the create-board modal, set the board name to exactly `dupetest` and submit. Wait until the modal closes and `dupetest` appears in the boards list. This first create must succeed before testing the duplicate.\n\n '\n - 'Open the `dupetest` board: either click its \"View board\" control on the Boards page, or go directly to http://127.0.0.1:13200/board/dupetest. Wait until the board page is visible.\n\n '\n - 'In the top-right header, click Edit (Enter Edit Mode). Then in the top-right, click Add a tile. In the tile selector, choose Apps. Keep the default app settings and save/confirm the modal. Then in the top-right, click Exit and Save. Wait until edit mode ends and the board has finished saving.\n\n '\n - 'Return to http://127.0.0.1:13200/manage/boards. Wait until the Boards management page is visible and confirm that the `dupetest` card shows Apps as 1 (exactly one app). Do not continue until Apps is visibly 1.\n\n '\n - 'Click Create again. In the create-board modal, set the board name again to exactly `dupetest` and submit. Wait a few seconds and observe the modal and the boards list (including the Apps count on `dupetest`). Do not navigate away yet.\n\n '\n - 'Final verdict — PASS only if after the second submit the create-board modal remains open AND the name field shows a visible conflict/error message containing \"Config already exists\" (or equivalent clear already-exists wording), AND the boards list still shows exactly one `dupetest` board whose Apps count remains 1. FAIL if the bug appears: the second create succeeds (modal closes with no name-field conflict error) and/or `dupetest` Apps becomes 0 (content wiped by overwrite), silently overwriting/accepting the duplicate name. If onboarding, first create, adding the app tile, or the boards page cannot be completed, report uncertain.\n\n '\n- id: preservation-unique-board-create-still-works\n category: preservation\n purpose: Creating a board with a new unique name should still succeed after authentication.\n steps:\n - 'Open http://127.0.0.1:13200/onboard. If an administrator account already exists from an earlier workflow in this same phase and /onboard is no longer shown, skip account creation and sign in at http://127.0.0.1:13200/auth/login with Username `JulesNguyen` and Password `copperBell3!` instead.\n\n '\n - 'If still onboarding: click \"Start update process\", create administrator Username `JulesNguyen` / Password `copperBell3!` (with confirmation), wait for the finished screen.\n\n '\n - 'Open http://127.0.0.1:13200/manage/boards. Wait until the Boards management page is visible.\n\n '\n - 'Click Create (create board). Set the board name to exactly `preserveboard` and submit. Wait until the modal closes and the boards list refreshes.\n\n '\n - 'Final verdict — PASS only if `preserveboard` is visibly listed on the Boards management page after submit and no blocking error prevented creation. FAIL if creation fails, the modal stays open with an error for this unique name, or `preserveboard` never appears in the list. If login/onboarding or the boards page cannot be reached, report uncertain.\n\n '\n"} {"case_id": "sweeper-078", "slug": "homebox", "repo": "https://github.com/sysadminsmedia/homebox", "base_commit": "2daf3009e90f8ce38117293862fb853aea25ed9e", "reference_commit": "6dd5864fd68b24aa4b302b0516192ebeaf981cfe", "task_scoped": "Find and fix issues in Homebox’s inventory import and export tools.", "task_specified": "Fix Homebox CSV inventory import so re-importing a row matched by import_ref does not bump the item's Asset ID when the CSV leaves asset_id empty. A user should be able to import the same CSV twice and still see the original Asset ID on the item detail page.", "pr": 1610, "issue": 1100, "workflows": "workflows:\n- id: target-csv-reimport-preserves-asset-id\n category: target\n purpose: Re-importing a CSV row matched by import_ref must keep the existing Asset ID instead of bumping it.\n steps:\n - 'Open http://127.0.0.1:13200/. Log in with email noah.reed@example.com and password mapleDesk8! (the product container seeds this account on start via the register API). Wait until the signed-in Homebox UI is visible (for example Home, Items, or Locations in the navigation).\n\n '\n - 'Use the browser page context to exercise the same CSV import path as Collection → Tools → Import Inventory: build a File named core-reimport.csv whose text is exactly the two-line CSV with header HB.purchase_date,HB.warranty_expires,HB.sold_date,HB.import_ref,HB.parent_import_ref,HB.url,HB.name,HB.description,HB.notes,HB.purchase_from,HB.manufacturer,HB.model_number,HB.serial_number,HB.warranty_details,HB.sold_to,HB.sold_notes,HB.location,HB.tags,HB.asset_id,HB.quantity,HB.purchase_price,HB.sold_price,HB.archived,HB.insured,HB.lifetime_warranty and data row ,,,core_ref_aa_batteries,,,AA Batteries Core,,,,,,,,,,Office,,,200,0,0,false,false,false Then POST multipart form-data twice (two separate requests) to http://127.0.0.1:13200/api/v1/entities/import with credentials included (session cookies from the logged-in browser) and form field name csv set to that File. Both imports must succeed (HTTP 204 or success without an error body).\n\n '\n - 'Open the Items list at http://127.0.0.1:13200/items. Find the item named exactly \"AA Batteries Core\" and open its detail page. On the item detail page, locate the visible Asset ID value (for example a field labeled Asset ID showing a value like 000-001).\n\n '\n - 'Final verdict - PASS only if all are true: (1) item \"AA Batteries Core\" exists after the two imports, (2) the item detail page visibly shows Asset ID exactly 000-001, and (3) the Asset ID is not 000-002 or any higher number. FAIL if the visible Asset ID is 000-002 (or higher) after re-importing the same import_ref with an empty asset_id column — that is the re-import bumping bug — or if the item is missing / Asset ID cannot be read on the detail page.\n\n '\n- id: preservation-first-csv-import-still-assigns-asset-id\n category: preservation\n purpose: A first-time CSV import of a new import_ref should still auto-assign a non-empty Asset ID.\n steps:\n - 'Open http://127.0.0.1:13200/. If not authenticated, log in as noah.reed@example.com / mapleDesk8! (pre-seeded by the product container). Wait until the signed-in Homebox UI is visible.\n\n '\n - 'Use the browser page context once for a first-time CSV import: build a File named preserve-once.csv with the same header as the target workflow and data row ,,,preserve_ref_once_item,,,Preserve Once Item,,,,,,,,,,Office,,,1,0,0,false,false,false POST multipart form-data to http://127.0.0.1:13200/api/v1/entities/import with credentials included and form field csv set to that File. The import must succeed.\n\n '\n - 'Open http://127.0.0.1:13200/items, find the item named exactly \"Preserve Once Item\", and open its detail page. Read the visible Asset ID.\n\n '\n - 'Final verdict - PASS only if both are true: (1) item \"Preserve Once Item\" exists, and (2) its detail page visibly shows a non-empty auto-assigned Asset ID in the 000-NNN form (for example 000-001 or 000-002) and not blank / 000-000. FAIL if the item is missing or the Asset ID is empty / 000-000.\n\n '\n"} {"case_id": "sweeper-079", "slug": "htmly", "repo": "https://github.com/danpros/htmly", "base_commit": "b6a59ea7680eb1892dd0878a387fc78e7c7b3da6", "reference_commit": "152b5990bbfc6d70e424843e44e1b0f964539312", "task_scoped": "Find and fix issues in HTMLy’s post permalinks.", "task_specified": "Fix HTMLy dated post URL resolution: Opening a /year/month/slug URL for an older post that shares its slug with a newer post shows the newer post. That dated URL should show the older post matching the year and month.", "pr": 430, "issue": null, "workflows": "workflows:\n- id: shared-slug-dated-url-resolves-older-post\n category: target\n purpose: Opening a year/month permalink for an older post that shares its slug with a newer post must show the older post, not the newest same-slug post.\n steps:\n - Open http://127.0.0.1:13200/2020/01/shared-demo\n - Wait until the page finishes loading. Confirm this is a rendered HTMLy blog post page with the twentysixteen theme (not a login form and not a bare PHP fatal).\n - Read only the main article heading h1.entry-title at the top of the post. Ignore Previous/Next link titles in the footer.\n - Read the main article body text inside the entry-content/content area. Ignore sidebar widgets and prev/next titles.\n - 'Final verdict (tighten): FAIL only if ALL are true — (1) h1.entry-title is exactly \"Newer Shared Demo Post\"; (2) the main article body contains \"BETA-NEW-BODY-MARKER\"; (3) the main article body does not contain \"ALPHA-OLD-BODY-MARKER\". PASS only if ALL are true — (1) h1.entry-title is exactly \"Older Shared Demo Post\"; (2) the main article body contains \"ALPHA-OLD-BODY-MARKER\"; (3) the main article body does not contain \"BETA-NEW-BODY-MARKER\". Do not treat prev/next navigation titles as evidence. If the page is unreachable or the h1/body cannot be read, treat as setup failure rather than a product PASS/FAIL on the bug.'\n- id: unique-slug-dated-url-still-works\n category: preservation\n purpose: A unique-slug dated permalink must continue to open its own post after the find_post fix.\n steps:\n - Open http://127.0.0.1:13200/2020/03/unique-preserve\n - Wait until the page finishes loading. Confirm this is a rendered HTMLy blog post page.\n - Read h1.entry-title and the main article body text.\n - 'Final verdict (tighten): PASS only if h1.entry-title is exactly \"Unique Preserve Post\" AND the main article body contains \"GAMMA-PRESERVE-BODY-MARKER\". FAIL if this is a post page but the title/body are wrong or the unique post marker is missing. If the page is unreachable or not a post page, treat as setup failure rather than a preservation FAIL tied to the fix.'\n"} {"case_id": "sweeper-080", "slug": "humhub", "repo": "https://github.com/humhub/humhub", "base_commit": "858f15e1d941172a1885e5348a451350225e5b0f", "reference_commit": "6ed3dda4c59abf6e1c6aa6247037ff9768cab0d2", "task_scoped": "Find and fix issues in HumHub’s space post creation and editing.", "task_specified": "Fix HumHub new post topic attachment: Selecting an existing topic when creating a post in a space does not attach that topic for members without Add Topics permission. Creating a post with an existing topic selected should show that topic on the new stream entry.", "pr": 8077, "issue": 8066, "workflows": "workflows:\n- id: new-post-existing-topic-persists\n category: target\n purpose: 'Verify that a space member without AddTopic can create a new post with an existing topic selected and see that topic on the resulting stream entry.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/\n - 'Confirm the HumHub UI loads with branding/styles (not a bare PHP error or installer wizard). If unreachable or still installing, stop as setup failure (not product pass/fail).\n\n '\n - 'Open http://127.0.0.1:13200/index.php?r=user/auth/login if needed. Log in as the seeded space member: username lenaOrtiz, password cinderBay7!. Submit the login form.\n\n '\n - 'Confirm an authenticated dashboard/stream UI loads. If login fails, stop as setup failure.\n\n '\n - 'Open Spaces (top navigation / Spaces directory), then open the seeded space Studio Lounge. Confirm the Studio Lounge space stream/wall is visible.\n\n '\n - 'Open the new-post composer through normal UI (click the \"What''s on your mind?\" / ProseMirror placeholder at the top of the stream so the full composer expands). Do not use fetch/XHR or page-context HTTP. Enter a unique message that includes the token CedarTopicMark.\n\n '\n - 'Attach topic Planning using the native composer menu (not by inventing API calls): (1) open the composer options gear / cogs dropdown next to Submit; (2) choose Topics so the Topics picker panel appears; (3) click the visible Select2/search field for topics (the \"Select topic(s)\" / \"0 selected\" control — prefer the visible picker UI, not a hidden raw ; do not call Roundcube APIs or write the address book directly). Submit/start the import with default options (Personal Addresses / SQL address book) and wait until import finishes and returns to the contacts UI.\n\n '\n - 'In the contacts list, open the imported contact named Jane Doe (click the contact row / name so the contact detail/properties pane is shown).\n\n '\n - 'Final verdict PASS only if ALL are true: (1) a contact named Jane Doe exists after the import, AND (2) the visible contact detail clearly shows the email address jane@example.com (in an Email field/property, not only buried in raw source that a normal user would not open). Final verdict FAIL only if the import of that HOME.EMAIL vCard completed and Jane Doe is present BUT the contact detail does NOT show jane@example.com as an email (email missing/empty while the name is present — the bug-specific symptom). Do not FAIL for login/IMAP/setup problems, missing Elastic assets, or inability to open Import.\n\n '\n- id: preservation-plain-vcard-email-still-imports\n category: preservation\n purpose: Importing a normal ungrouped EMAIL vCard must still create a contact that shows the email address.\n steps:\n - 'Open http://127.0.0.1:13200/. If not already signed in, log in with the native form as lena-moss / MailGate5!willow and wait for the Roundcube UI. Open Address Book / Contacts.\n\n '\n - 'Open Import contacts. Attach a vCard file whose contents are exactly:\n\n BEGIN:VCARD VERSION:3.0 N:Smith;John;;; FN:John Smith EMAIL:john@example.com END:VCARD\n\n Use only the native file input / import form (no API shortcuts). Submit the import and wait until it finishes.\n\n '\n - 'Open the imported contact John Smith in the contacts UI.\n\n '\n - 'Final verdict PASS only if John Smith is present AND the contact detail clearly shows email john@example.com. Final verdict FAIL only if that plain EMAIL import completed but the email is missing from the visible contact detail. Do not FAIL for unrelated login or asset issues.\n\n '\n"} {"case_id": "sweeper-161", "slug": "searxng", "repo": "https://github.com/searxng/searxng", "base_commit": "0734ee6c7168ced321bac5f9ec2ef3fa49aee1d1", "reference_commit": "aa059419ff027cb23be88ffa3b080a41e386fa95", "task_scoped": "Find and fix issues in SearXNG’s search suggestion interface.", "task_specified": "Fix SearXNG autocomplete suggestions so query suggestions that contain an ampersand are not HTML-escaped in the dropdown. A user typing a query that contains an ampersand should see suggestion text with a literal ampersand, not the HTML entity spelling.", "pr": 6485, "issue": null, "workflows": "workflows:\n- id: target-autocomplete-ampersand-not-html-escaped\n category: target\n purpose: Autocomplete suggestions that contain '&' must show a literal ampersand in the dropdown, not the HTML entity &.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the SearXNG home search page is visible (search input `#q` / placeholder \"Search for...\" and a search button). Do not open preferences yet.\n\n '\n - 'Click the search input `#q`. Clear any existing text. Type exactly `AT&` (letters A, T, then an ampersand) and stop typing. Wait at least 1 second for the autocomplete dropdown (`.autocomplete` / `.autocomplete ul`) to open with suggestion list items. If the dropdown does not open, wait a few more seconds and ensure the input still contains exactly `AT&`.\n\n '\n - 'Read the visible text of the autocomplete suggestion items in `.autocomplete ul li` (use the on-screen list labels, not DevTools / Network / API JSON). Note whether any suggestion shows the literal HTML-entity spelling `AT&T` versus a normal `AT&T` with a real ampersand character.\n\n '\n - 'Final verdict - PASS only if all of the following are true: (1) the autocomplete dropdown is open with at least one suggestion item after typing `AT&`, (2) a suggestion whose readable text is exactly `AT&T` (literal ampersand between T and T) is visible in the dropdown, AND (3) no visible suggestion item shows the HTML-entity text `AT&T`. FAIL if the dropdown shows `AT&T` (or other AT&T-family suggestions with a visible `&` sequence such as `AT&T customer service`) — that is the server-side HTML-escape bug on `/autocompleter`. FAIL if the dropdown never opens, if setup cannot reach the home search box, or if only entity-escaped suggestions appear.\n\n '\n- id: preservation-autocomplete-still-suggests\n category: preservation\n purpose: Autocomplete should still open and list multiple suggestions for a short typed query.\n steps:\n - 'Open http://127.0.0.1:13200/ and wait until the SearXNG home search page is visible with search input `#q`.\n\n '\n - 'Click `#q`, clear it, and type exactly `foo` (three letters). Wait at least 1 second for the `.autocomplete` dropdown to open with suggestion list items under `.autocomplete ul`.\n\n '\n - 'Confirm the dropdown lists multiple suggestion rows (at least two `
  • ` entries) whose visible text is non-empty. Do not require any particular brand name; only that autocomplete still returns a usable suggestion list for this short query.\n\n '\n - 'Final verdict - PASS only if both are true: (1) after typing `foo`, the autocomplete dropdown opens, AND (2) it shows at least two non-empty suggestion items. FAIL if the dropdown never opens, shows only an empty / \"No results found\" state, shows fewer than two suggestions, or if the home search page cannot be reached.\n\n '\n"} {"case_id": "sweeper-162", "slug": "selfoss", "repo": "https://github.com/fossar/selfoss", "base_commit": "0dd3393abf2ead062c1c6c2def68be9d016a7085", "reference_commit": "f54ca796012f014f11b52bedfe3006d38a4c9ed6", "task_scoped": "Find and fix issues in selfoss’ source import and export tools.", "task_specified": "Fix selfoss OPML export: Exporting sources fails with a server TypeError when a source is tagged with an int-like tag name. Export sources should download OPML where that tag appears as a string outline title/text and nested sources remain included.", "pr": 1439, "issue": null, "workflows": "workflows:\n- id: target-opml-export-int-like-tag\n category: target\n purpose: Exporting sources when a source is tagged with an int-like tag name such as \"123\" must produce OPML XML with that tag outline, not a server TypeError error page.\n steps:\n - ? Open http://127.0.0.1:13200/ and wait until the selfoss UI is ready (login form with Username/Password and a Log in control, or the main app shell). Confirm styled UI assets loaded (not a bare unstyled text page)\n : selfoss branding/logo or themed background/CSS should be present.\n - If the login form is shown, log in with username nina-cho and password velvetInk4!. Confirm login succeeds by reaching the authenticated app (navigation such as Settings / Sources / Refresh is available, and the login form is gone).\n - Open Sources management: click Settings if needed, then open Sources (route /manage/sources). Wait until the Sources page shows \"Add source\" and \"Export sources\".\n - If any sources are already listed, delete every one of them: on each source row open \"More actions\" and choose \"Delete\", then confirm \"Really delete this source?\". Wait until the list is empty (or shows \"No sources configured.\"). If the list is already empty, continue.\n - Click \"Add source\". In the new source form, set Title to City Transit Digest, set Tags to 123, set Type to RSS Feed, and set the URL field to http://127.0.0.1:13200/data/sample.xml. Click Save. Wait until the source titled \"City Transit Digest\" is listed as a saved source (not \"New unsaved source\").\n - Click the \"Export sources\" link once. Wait for navigation or download to finish.\n - Observe the result in the browser UI only: either the visible page body text, or the contents of a downloaded selfoss-subscriptions-*.xml / OPML file if the browser saved an attachment (read the downloaded file text if the page itself is blank after download).\n - Final verdict — FAIL only if the visible page shows the selfoss server error copy that an error occurred (for example \"An error occured\" / \"An error occurred\" and a log-file hint), which is the TypeError path for int-like tag OPML export. PASS only if OPML/XML was obtained whose text includes an outline for tag \"123\" (for example title=\"123\" or text=\"123\") together with the source \"City Transit Digest\". Do not PASS if only the Sources page is still showing without an export result. Do not use fetch/XHR/page-context HTTP, DevTools Network, or API JSON for pass/fail. Do not FAIL for login/navigation setup problems; use uncertain only if the product UI cannot be reached or observed reliably after retries.\n- id: preservation-word-tag-opml-export\n category: preservation\n purpose: Exporting sources when a source is tagged with a non-numeric word tag such as commute must still produce OPML XML with that tag outline.\n steps:\n - Open http://127.0.0.1:13200/ and wait until the selfoss UI is ready.\n - If needed, log in with username nina-cho and password velvetInk4! and confirm the authenticated app shell is shown.\n - Open Sources management (/manage/sources). Wait until the Sources page shows \"Add source\" and \"Export sources\".\n - If any sources are already listed, delete every one of them: on each source row open \"More actions\" and choose \"Delete\", then confirm \"Really delete this source?\". Wait until the list is empty (or shows \"No sources configured.\"). If the list is already empty, continue.\n - Click \"Add source\". In the new source form, set Title to Morning Commute Brief, set Tags to commute, set Type to RSS Feed, and set the URL field to http://127.0.0.1:13200/data/sample.xml. Click Save. Wait until the source titled \"Morning Commute Brief\" is listed as a saved source (not \"New unsaved source\").\n - Click the \"Export sources\" link once. Wait for navigation or download to finish.\n - Observe the result in the browser UI only: either the visible page body text, or the contents of a downloaded selfoss-subscriptions-*.xml / OPML file if the browser saved an attachment.\n - Final verdict — PASS only if OPML/XML was obtained whose text includes an outline for tag commute (for example title=\"commute\" or text=\"commute\") together with the source Morning Commute Brief. FAIL if the visible page shows the selfoss server error copy that an error occurred. Do not use fetch/XHR/API for this judgment. Use uncertain only if login, Sources, or the export result cannot be observed reliably.\n"} {"case_id": "sweeper-163", "slug": "shaarli", "repo": "https://github.com/shaarli/Shaarli", "base_commit": "e8a65396b03a14f3b8b8f08f1d03fe08bdb67ddb", "reference_commit": "11be9eeedb1b64f6e81fb8fc81fbc44abc2e46e6", "task_scoped": "Find and fix issues in Shaarli’s bookmark creation and editing.", "task_specified": "Fix the Shaarli New Shaare form: The async metadata request consumes the single-use CSRF token, so Save fails with Wrong token. Saving a new bookmark after metadata retrieval should succeed without a Wrong token error.", "pr": 2243, "issue": 2242, "workflows": "workflows:\n- id: target-new-shaare-save-after-metadata-keeps-token\n category: target\n purpose: Saving a new bookmark after async metadata retrieval must succeed without a Wrong token error.\n steps:\n - Open `http://127.0.0.1:13200/login`. Log in with username `RileyCho` and password `teaKettle9`. Confirm you reach the logged-in home page (menu shows `Shaare`, `Tools`, and `Logout`).\n - Open `http://127.0.0.1:13200/admin/add-shaare` (or click the `Shaare` menu item). In the URL field enter exactly `https://example.com/` and submit `Add link`.\n - Wait for the `New Shaare` edit form to load. Confirm the page title/heading is `New Shaare` and that the Title field area was in a loading state or otherwise that async metadata retrieval had a chance to run (wait at least 3 seconds after the form appears before saving).\n - Click the `Save` button on the New Shaare form (do not navigate away first). Wait for the response page.\n - 'Final verdict - PASS only if both are true: (1) the response is NOT a Wrong token error page (no visible heading/text `Wrong token.`), and (2) the new bookmark save succeeds, for example by redirecting to the home/permalink view where `example.com` or the saved title is visible in the bookmark list. FAIL if the page shows `Wrong token.` after Save, or if save is rejected with a 403 token error instead of creating/showing the bookmark.'\n- id: preservation-edit-existing-shaare-still-saves\n category: preservation\n purpose: Editing an already-saved bookmark (no new-link metadata retrieval) should still save successfully.\n steps:\n - Open `http://127.0.0.1:13200/login` and log in with username `RileyCho` and password `teaKettle9` if not already logged in. Confirm the home page lists at least one existing bookmark (fresh installs seed default bookmarks after first login).\n - Open the edit form for an existing bookmark, for example `http://127.0.0.1:13200/admin/shaare/1` or by clicking that bookmark's edit control from the home list. Confirm the heading is `Edit Shaare` (not `New Shaare`) and that `metadata.min.js` is not required for this path.\n - Change the Title field to exactly `Preservation Edit Title`, then click `Apply Changes`. Wait for the response.\n - 'Final verdict - PASS only if both are true: (1) the response is NOT a Wrong token error page, and (2) after returning to the home/permalink view (or reopening the edit form) the bookmark title shows `Preservation Edit Title`. FAIL if `Wrong token.` appears, or if the title change is not persisted.'\n"} {"case_id": "sweeper-164", "slug": "silverbullet", "repo": "https://github.com/silverbulletmd/silverbullet", "base_commit": "fc674577b15121d52bc558cf133847d050f78649", "reference_commit": "51cd6c0a86703b592a46e033579093f9aafffe3c", "task_scoped": "Find and fix issues in SilverBullet’s page organization and linking.", "task_specified": "Fix SilverBullet page rename: Renaming a page updates ordinary [[wiki]] links but leaves ![[page]] transclusions and ![alt](page) image links pointing at the old name. Those embeds should be rewritten to the new page name so the transclusion keeps showing the renamed page content.", "pr": 2084, "issue": null, "workflows": "workflows:\n- id: target-rename-rewrites-transclusion\n category: target\n purpose: After renaming TargetPage, Holder's ![[TargetPage]] transclusion must be rewritten so the embed still shows TargetPage body text.\n steps:\n - Open http://127.0.0.1:13200/ and wait until the SilverBullet editor UI is visible (top bar with page name input, editor area). Confirm branding/styles loaded (not a bare unstyled text page).\n - Open Holder at http://127.0.0.1:13200/Holder. Wait until it loads and UNIQUE_TARGET_BODY_SILVERBULLET_MARK is visible from the working ![[TargetPage]] transclusion. This also helps indexing discover the backlink before rename.\n - Open TargetPage at http://127.0.0.1:13200/TargetPage. Wait until the top-bar page-name input (#sb-current-page input.sb-input) shows TargetPage and the editor shows UNIQUE_TARGET_BODY_SILVERBULLET_MARK.\n - Rename using the top-bar page-name input: click it, select all, type RenamedTarget, press Enter. Wait until the URL ends with /RenamedTarget and the top-bar input shows RenamedTarget.\n - Navigate to http://127.0.0.1:13200/Holder. Wait for the page to finish loading and for live preview to settle (retry for several seconds if needed).\n - 'Observe Holder for bug-specific evidence about the transclusion after rename. Prefer the live-preview embed outcome and, if visible, the markdown source `![[...]]`. An H1 `TargetPage` inside the embed is the old page heading in the transcluded body, not proof the transclusion still points at TargetPage. Record whether source still shows `![[TargetPage]]`, whether `Error: Unsupported content: TargetPage` appears, and whether UNIQUE_TARGET_BODY_SILVERBULLET_MARK is still rendered from the embed.\n\n '\n - 'Final verdict — PASS only if rename succeeded AND UNIQUE_TARGET_BODY_SILVERBULLET_MARK is visibly rendered from the Holder embed AND there is no `Error: Unsupported content: TargetPage`. FAIL only if rename succeeded and Holder reopened AND you can see stale source `![[TargetPage]]`, or the embed shows `Error: Unsupported content: TargetPage`, or the unique body text is missing from the embed. Do not FAIL because the embed heading still says TargetPage. Do not FAIL for slow UI alone; wait/retry first.\n\n '\n- id: preservation-rename-rewrites-wikilink\n category: preservation\n purpose: Renaming WikiSource still rewrites ordinary [[WikiSource]] wiki links on WikiHolder.\n steps:\n - Open http://127.0.0.1:13200/ and wait until the SilverBullet editor UI is visible with styles loaded.\n - Open WikiHolder at http://127.0.0.1:13200/WikiHolder. Confirm an ordinary wiki link to WikiSource is present.\n - Open WikiSource at http://127.0.0.1:13200/WikiSource. Confirm the top-bar page-name input shows WikiSource.\n - Rename via the top-bar page-name input: select all, type WikiRenamedSource, press Enter. Wait until the URL ends with /WikiRenamedSource and the top-bar shows WikiRenamedSource.\n - Open WikiHolder at http://127.0.0.1:13200/WikiHolder and wait for load.\n - Verify the ordinary wiki link on WikiHolder was rewritten from [[WikiSource]] to [[WikiRenamedSource]] (visible link target/text in the UI or page source).\n - Final verdict — PASS only if rename succeeded AND WikiHolder's ordinary wiki link was rewritten to WikiRenamedSource. FAIL only if rename succeeded but WikiHolder still shows an ordinary wiki link to WikiSource.\n"} {"case_id": "sweeper-165", "slug": "silverstripe", "repo": "https://github.com/silverstripe/silverstripe-framework", "base_commit": "fd57f06755d73ae77ecb93a5380e2ba3d56dbe95", "reference_commit": "f88b7c3c2be6fde3d02d7f1f88ffacfe89c45072", "task_scoped": "Find and fix issues in Silverstripe’s page authoring interface.", "task_specified": "Fix Silverstripe page duplication: Duplicating a page copies view/edit access type but not ViewerGroups or EditorGroups, so the copy Settings shows Only these groups with empty group lists. Duplicating a page should copy its viewer and editor groups onto the new page.", "pr": 10806, "issue": null, "workflows": "workflows:\n- id: target-duplicated-page-keeps-viewer-editor-groups\n category: target\n purpose: Duplicating a page that is limited to specific viewer/editor groups must copy those groups onto the new page (Settings still lists Board Readers).\n steps:\n - Open http://127.0.0.1:13200/admin and wait until the official Silverstripe login screen loads with styled login-forms CSS (not a bare-text page), the heading \"Log in\", Email and Password fields, and a Log in button. If redirected toward /Security/login, that is expected.\n - Sign in with Email `cleoHart` and Password `Tallow9brim` using the native login form. Do not use fetch, XHR, or page-context HTTP. Wait until the official CMS chrome loads (Silverstripe logo / cms-menu, Pages section).\n - Open http://127.0.0.1:13200/admin/pages and wait until the site tree is visible, including the page titled `Trustee Notes`.\n - In the site tree, right-click `Trustee Notes`, open the Duplicate submenu, and choose This page only (not This page and subpages). Wait until a success status such as \"Duplicated 'Trustee Notes' successfully\" appears and the CMS opens the new page (a second Trustee Notes, typically a draft).\n - On that newly opened copy, open the Settings tab (next to Content). Confirm \"Who can view this page?\" is set to \"Only these groups\". Inspect the Viewer Groups field (placeholder text is \"(Search or choose Group)\") and the Editor Groups field.\n - 'Final verdict: Decide only from the official CMS Settings UI on the duplicated page. Do not use fetch, XHR, Network, or the database as the oracle. FAIL only if Duplicate succeeded and the copy''s Settings still shows Who can view this page? = Only these groups, but Viewer Groups does not list Board Readers (the field is empty aside from the Search or choose Group placeholder). PASS only if that same copy''s Viewer Groups still shows Board Readers as a selected group. Do not FAIL for login/tree/menu/setup problems before the copy Settings observation. Do not use API/Network/DB as the oracle.'\n- id: preservation-original-restricted-page-keeps-access-groups\n category: preservation\n purpose: The original Trustee Notes Settings Access form still shows Only these groups with Board Readers selected.\n steps:\n - Open http://127.0.0.1:13200/admin and wait for the official styled Silverstripe login page (Log in, Email, Password).\n - Sign in with Email `cleoHart` and Password `Tallow9brim` using the native form. Do not use fetch, XHR, or page-context HTTP.\n - Open http://127.0.0.1:13200/admin/pages and wait for the site tree. Click the original `Trustee Notes` (the existing seeded page, URL segment trustee-notes — not a newly duplicated draft if one exists).\n - Open the Settings tab. Confirm \"Who can view this page?\" includes the \"Only these groups\" option and that Viewer Groups shows `Board Readers` as a selected group.\n - 'Final verdict: Decide only from the official Settings UI on the original Trustee Notes. Do not use fetch, XHR, Network, or the database as the oracle. PASS only if that original page''s Settings loaded and Viewer Groups still lists Board Readers with Who can view this page? set to Only these groups. FAIL if the original Settings page cannot be opened after login, the Who can view / Viewer Groups controls are missing, or Board Readers is not selected on the original page. Do not FAIL based on whether a duplicated copy kept or lost its groups (that is the core bug).'\n"} {"case_id": "sweeper-166", "slug": "siyuan", "repo": "https://github.com/siyuan-note/siyuan", "base_commit": "618bf33db3e36101cee24aa9b88f494c31226f85", "reference_commit": "91fa9bfb0e73b3e77f3dd2702b1fd54a038ca6ee", "task_scoped": "Find and fix issues in SiYuan’s document viewing and navigation.", "task_specified": "Fix SiYuan callout content when opening documents with folded headings: Callout child blocks disappear when a document containing folded headings is opened. Callout children should remain visible after the document loads.", "pr": 18247, "issue": null, "workflows": "workflows:\n- id: target-callout-children-survive-folded-heading-doc-open\n category: target\n purpose: 'Opening a document that contains folded headings must keep callout child text visible in the editor (getDoc must not strip callout children).\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/stage/build/desktop/ exactly (browser web UI). Do not open `/` alone and do not open `/stage/build/app/` — those can land on the Electron app shell and stick on the SiYuan logo with \"Click to Refresh\" / \"点击刷新\" without a usable notebook UI. Wait for the themed SiYuan desktop shell to load (logo / appearance styles / editor chrome / left notebook tree visible), not a bare unstyled text page and not a stuck logo-only splash. If an access-auth / agreement / language / onboarding dialog appears, dismiss or confirm it with the default/OK/Agree controls so the main notebook UI becomes usable. Do not use fetch, XHR, or any API calls.\n\n '\n - 'In the left notebook/file tree, open the notebook named `Work notes` if it is collapsed. Click the document titled `Weekly outline` so it opens in the editor. Wait until the document body finishes loading (headings such as `Visible Section` / `Visible Subheading` and a SiYuan Note callout box — the labeled box with a pencil icon and title `Note` — are visible). Do not use fetch/XHR.\n\n '\n - 'Inspect only the visible editor body of `Weekly outline`. Find the Note callout box (pencil icon + title `Note`). Look inside the box body (`callout-content` area under the title, not the `Note` title itself) for the exact paragraph text `CALLOUT_KEEP_MARKER_18247`.\n\n '\n - 'Final verdict — judge only from the visible editor UI after the document has loaded. PASS only if the Note callout box body clearly shows the exact text `CALLOUT_KEEP_MARKER_18247`. FAIL if the bug appears: the Note box shell/title may still be visible, but the box body is empty or does not contain that exact text after open. Do not PASS based on headings alone, sidebar titles, the word `Note`, or any network/API inspection.\n\n '\n- id: preservation-simple-callout-children-remain-visible\n category: preservation\n purpose: 'A document with a callout and no folded-heading residue must still show callout child text when opened.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/stage/build/desktop/ exactly (browser web UI). Do not open `/` alone and do not open `/stage/build/app/` — those can stick on the SiYuan logo with \"Click to Refresh\" / \"点击刷新\". Wait for the themed SiYuan desktop shell and left notebook tree. Dismiss any access-auth / agreement / language / onboarding dialogs so the main UI is usable. Do not use fetch, XHR, or API calls.\n\n '\n - 'In the left notebook/file tree, open `Work notes` if needed. Click the document titled `Quick memo` so it opens in the editor. Wait until the document body loads (intro paragraph and a Tip callout box — labeled box with title `Tip` — are visible).\n\n '\n - 'Inspect the visible editor contents. Look inside the Tip callout box body (under the `Tip` title, not the title itself) for the exact text `PRESERVE_CALLOUT_MARKER_18247`.\n\n '\n - 'Final verdict — PASS only if the Tip callout box body clearly shows `PRESERVE_CALLOUT_MARKER_18247` in the visible editor. FAIL if that text is missing/empty after open, or if the document fails to open.\n\n '\n"} {"case_id": "sweeper-167", "slug": "smf", "repo": "https://github.com/SimpleMachines/SMF", "base_commit": "6d3d6b3aeeea380b8ff184f015966353df343eef", "reference_commit": "a046875ec1823b32ef3478e7c50583255fe8883c", "task_scoped": "Find and fix issues in SMF’s post draft management.", "task_specified": "Fix SMF post draft saving: after the first Save draft, opening that draft from My Drafts, changing the body, and clicking Save draft again shows a Database Error (Out of range value for column 'type'). The second Save draft should succeed without that Database Error.", "pr": 9339, "issue": null, "workflows": "workflows:\n- id: target-post-draft-second-save-persists\n category: target\n purpose: After a first Save draft, opening that draft from My Drafts, changing the body, and saving again must not show a Database Error about column type; the second Save draft should succeed.\n steps:\n - Open http://127.0.0.1:13200/ and wait until the SMF board home loads with Ridgeway Forum branding and themed layout (smflogo / CSS styles present, not a bare unstyled text shell).\n - Open http://127.0.0.1:13200/index.php?action=login and wait until the login form is visible (username/password fields and a login submit control).\n - Type exactly mira.holt into the username field and duskRail9! into the password field. Wait at least two seconds, then submit the login form.\n - Confirm you are signed in as mira.holt (header shows mira.holt and/or Logout; you must not remain on the login form with a credentials error).\n - Open http://127.0.0.1:13200/index.php?action=post;board=1 and wait until the new-topic post editor is visible (Subject field and message body editor, plus a Save draft control).\n - Type exactly Weekend stall notes into the Subject field.\n - Type exactly FERRY_NOTE_V1 into the message body editor (the main post textarea / SCEditor body).\n - Click the Save draft button. If a browser confirm dialog appears about drafts not saving attachments/polls, accept/confirm it. Wait until a draft-saved notice is visible (text mentioning the contents have been saved as a draft / Show Drafts area). Ignore a companion 'No name was provided' validation line if it appears; that is not the bug under test.\n - Click the signed-in username (mira.holt) in the header to open the profile menu. Click My Drafts. Wait until the profile drafts list loads (breadcrumb or sidebar may also say Show Drafts; that is the same page). Confirm a draft whose subject is Weekend stall notes is listed and its preview contains FERRY_NOTE_V1.\n - On that Weekend stall notes row, click Edit draft. Wait until the post editor reopens with that draft loaded.\n - Clear the message body, then type exactly FERRY_NOTE_V2 into the message body editor. Keep the same subject Weekend stall notes. Do not start a brand-new unrelated topic.\n - Click Save draft again. If a confirm dialog appears, accept it. Wait until the page finishes (either a draft-saved notice / editor remains, or an error page).\n - Final verdict — PASS only if (a) signed in as mira.holt, (b) the draft was opened from My Drafts and edited to FERRY_NOTE_V2, AND (c) the second Save draft does not show a Database Error whose text includes Out of range value for column 'type'. FAIL only if (a)+(b) are true and the second Save draft lands on a Database Error page showing Out of range value for column 'type' (File Draft.php). Do not FAIL for the first-save 'No name was provided' line, and do not FAIL for login/navigation/setup problems; use uncertain only if the product UI cannot be reached or the second Save draft result cannot be observed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-first-post-draft-save\n category: preservation\n purpose: The first Save draft on a new post must still create an accessible draft under My Drafts with the saved body.\n steps:\n - Open http://127.0.0.1:13200/index.php?action=login and wait until the login form is visible.\n - Type exactly mira.holt into the username field and duskRail9! into the password field. Wait at least two seconds, then submit the login form.\n - Confirm you are signed in as mira.holt.\n - Open http://127.0.0.1:13200/index.php?action=post;board=1 and wait until the new-topic post editor is visible with a Save draft control.\n - Type exactly Library hours notice into the Subject field.\n - Type exactly QUAY_KEEP_BODY into the message body editor.\n - Click Save draft. If a confirm dialog appears, accept it. Wait until a draft-saved notice is visible. Ignore a companion 'No name was provided' line if it appears.\n - Click the signed-in username (mira.holt) in the header to open the profile menu. Click My Drafts. Wait until the profile drafts list loads (breadcrumb or sidebar may also say Show Drafts; that is the same page).\n - Find the draft whose subject is Library hours notice and read the body preview on that list (or open it with Edit draft and read the editor body).\n - Final verdict — PASS only if signed in as mira.holt, My Drafts lists Library hours notice, and the listed or loaded body contains QUAY_KEEP_BODY. FAIL if the drafts page loads while signed in but that first-save draft is missing or its body does not contain QUAY_KEEP_BODY. Do not FAIL for the first-save 'No name was provided' line or for login/setup problems; use uncertain only if the draft UI cannot be reached or observed after retries. Do not use fetch/XHR/API/database for this judgment.\n"} {"case_id": "sweeper-168", "slug": "snipe-it", "repo": "https://github.com/grokability/snipe-it", "base_commit": "32a2eed5ecbb6b8889e7c80da47fa93a0e5ed190", "reference_commit": "6703448b80c2fd6acdc83fe398b81d4372b9784c", "task_scoped": "Find and fix issues in Snipe-IT’s user profile interface.", "task_specified": "Fix user profile viewing in Snipe-IT: Viewing a user whose permissions field is null throws a server error. The user profile page should load without a server error when permissions are unset.", "pr": 18102, "issue": 18132, "workflows": "workflows:\n- id: target-null-permissions-user-profile-loads\n category: target\n purpose: Viewing a user whose permissions field is null must load the profile instead of a server error.\n steps:\n - Open http://127.0.0.1:13200/login and wait for the Snipe-IT login page with the site logo and styled form (not a bare-text page). If already signed in, open http://127.0.0.1:13200/logout first, then return to login.\n - Log in with the admin account: username `selene-park` and password `cedarWind7!`. Wait until the authenticated dashboard or main navigation is visible.\n - Open `http://127.0.0.1:13200/users/2` — this is the seeded bug-trigger user `kai-morales` / Kai Morales (permissions column is SQL NULL). Wait for the page to finish loading.\n - Final verdict - PASS only if the user profile page loads successfully (HTTP success, no Ignition/Whoops/500 page) and visibly shows this user as Kai Morales or username kai-morales on a normal Snipe-IT user view. FAIL if the page shows a server error, Ignition/Whoops exception, Undefined variable $permissions, Internal Server Error, or any fatal error page instead of the user profile.\n- id: preservation-admin-user-profile-still-loads\n category: preservation\n purpose: Viewing a normal admin user with permissions set must still load the user profile.\n steps:\n - Open http://127.0.0.1:13200/login and wait for the Snipe-IT login page. If already signed in as another account, open http://127.0.0.1:13200/logout first, then return to login.\n - Log in with the admin account: username `selene-park` and password `cedarWind7!`. Wait until the authenticated UI is visible.\n - Open `http://127.0.0.1:13200/users/1` (the admin account `selene-park` / Selene Park). Wait for the page to finish loading.\n - Final verdict - PASS only if the admin user profile page loads successfully and shows View User / Selene Park (or equivalent user profile content for selene-park) without a server error. FAIL if a 500, Ignition/Whoops, Undefined variable, or other fatal error appears, or if the profile content for the admin user is missing.\n"} {"case_id": "sweeper-169", "slug": "solidinvoice", "repo": "https://github.com/SolidInvoice/SolidInvoice", "base_commit": "6fc370496f75bc02631ef802eaa4ad254ad34dd7", "reference_commit": "8a92cb86100391b9e5fe924bb48433f220e603cb", "task_scoped": "Find and fix issues in SolidInvoice’s invoice creation and editing.", "task_specified": "Fix SolidInvoice money form handling for zero-decimal currencies: amounts are multiplied and divided by a hardcoded factor of 100, so an entered amount is stored and displayed one hundred times too large. Entering an amount for a zero-decimal currency invoice should store and display that same amount.", "pr": 2637, "issue": null, "workflows": "workflows:\n- id: target-jpy-invoice-amount-not-scaled-by-100\n category: target\n purpose: For a JPY company, an onboarding invoice amount of 800 must be stored and shown as ¥800, not multiplied by 100 into ¥80,000.00.\n steps:\n - Open http://127.0.0.1:13200/login and wait until the SolidInvoice login page is fully styled (title/branding SolidInvoice, Email and Password fields, login CSS/assets loaded — not a bare unstyled text shell).\n - Sign in with Email elena-voss@test.com and Password quietMaple42. Submit via the login form (POST goes to /_login_check). Wait until you leave the login page.\n - You should land on the Get Started / onboarding wizard (or Create Company). Complete company setup with Name exactly Sakura Ledger Co and Currency exactly JPY (Japanese Yen). Continue/Next.\n - On the First Client step, set Client Name to Acme Client and Email to client@example.com, then Continue/Next.\n - On the First Invoice step, set Service Description to Consulting services and Amount exactly 800, then submit Create & View My Invoice (or equivalent Continue that creates the invoice).\n - Wait until the invoice view page loads (URL contains /invoices/view/, title like Invoice\n - ? Final verdict — FAIL only if this JPY invoice created with entered amount 800 clearly shows the 100x-scaled wrong amount as ¥80,000.00 (or ¥80,000) on the invoice view. That is the subunit bug\n : reverseTransform multiplied by 100 even for zero-decimal JPY.\n - Final verdict — PASS only if the same path shows ¥800 (or ¥800 with no thousands-group into 80,000) as the invoice/line total and does not show ¥80,000.00 / ¥80,000 for that amount.\n - Do not FAIL for unrelated login/onboarding/setup failures, Iconify/network noise, or missing optional widgets. Only FAIL when the invoice view for this 800 JPY amount clearly displays the scaled ¥80,000 figure.\n- id: preservation-usd-invoice-amount-still-correct\n category: preservation\n purpose: For a USD company, a normal invoice amount of 100 must still display as $100.00 after onboarding create-and-view.\n steps:\n - Open http://127.0.0.1:13200/login and wait until the styled SolidInvoice login page is visible.\n - Sign in with Email JonahWhitfield@admin.com and Password BaySide!9. Wait until onboarding / create-company appears (this account has no company yet, even if the target workflow already created one under a different user).\n - Complete company setup with Name exactly Harbor Billing Co and Currency exactly USD (US Dollar). Continue/Next.\n - On the First Client step, set Client Name to Usd Client and Email to usd-client@example.com, then Continue/Next.\n - On the First Invoice step, set Service Description to USD consulting and Amount exactly 100, then submit Create & View My Invoice.\n - Wait for the invoice view page (/invoices/view/). Inspect the visible totals.\n - Final verdict — PASS only if the invoice view shows $100.00 (or an equivalent clear $100 total for this invoice) and does not show a 100x-scaled wrong value such as $10,000.00 for the entered amount 100.\n - Final verdict — FAIL if the USD invoice total is clearly wrong for amount 100 (for example $10,000.00) or the create-and-view path errors before any total is visible. Do not FAIL for unrelated cosmetic/icon issues if $100.00 is clearly shown.\n"} {"case_id": "sweeper-170", "slug": "speedtest-tracker", "repo": "https://github.com/alexjustesen/speedtest-tracker", "base_commit": "dc4dd2ff660246da1b450bea620760e0535a8169", "reference_commit": "eb9a3e676ecb242b8854b7bfb9e074b03570b9aa", "task_scoped": "Find and fix issues in Speedtest Tracker’s notification configuration.", "task_specified": "Fix Speedtest Tracker Apprise Server URL settings: An Apprise Server URL that does not contain /notify is accepted when notification settings are saved. The form should reject Apprise Server URLs that do not contain /notify.", "pr": 2579, "issue": null, "workflows": "workflows:\n- id: target-apprise-server-url-requires-notify-suffix\n category: target\n purpose: 'Saving an Apprise Server URL that does not contain ''/notify'' must be rejected with a visible form validation error. Baseline wrongly accepts URLs like http://localhost:8000 without the notify path.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/admin/login. Confirm the Speedtest Tracker Filament login page is styled (theme CSS loaded, product icon/logo visible, Email and Password fields). Sign in with Email `priya.shah@test.com` and Password `cedarLamp42!`. Wait until the signed-in admin shell loads (left navigation includes Settings items such as Notifications).\n\n '\n - 'Open http://127.0.0.1:13200/admin/notification. Wait for the Notifications settings page titled about Notifications. Click the visible tab labeled `Apprise` (not Database / Mail / Webhook). Confirm the Apprise tab content is visible, including the toggle `Enable Apprise notifications`.\n\n '\n - 'Turn ON `Enable Apprise notifications` so the Apprise Server fields appear. In the `Apprise Server URL` text input, clear any existing value and type exactly `http://localhost:8000` (no `/notify` suffix). Do not fill channel URLs unless a channel field blocks saving; if a channel URL row is required to enable Save changes, add one non-http Apprise scheme value such as `mailto://test@example.com`. Click the page Save changes button exactly once. Do not use fetch, XHR, or any API calls. Wait for either a success toast or an inline field validation error.\n\n '\n - 'Observe only the visible UI after that single Save changes: any Filament success toast/notification, any red validation message under `Apprise Server URL` or near the form, and whether the typed URL `http://localhost:8000` remains accepted as saved (no validation error).\n\n '\n - 'Final verdict — judge only from the visible UI. PASS only if Save changes is rejected for `http://localhost:8000` with a clear validation error that the Apprise Server URL must contain `/notify` (or equivalent visible wording that `/notify` is required), and there is no success toast claiming settings were saved. FAIL if the bug appears: Save changes succeeds (success toast / settings saved) for `http://localhost:8000` with no `/notify` validation error. FAIL if login or the Apprise tab cannot be reached. If the branded admin UI cannot load after reasonable waits, report uncertain.\n\n '\n- id: preservation-apprise-server-url-with-notify-still-saves\n category: preservation\n purpose: 'A valid Apprise Server URL that already ends with ''/notify'' must still save successfully from the Notifications Apprise tab.\n\n '\n steps:\n - 'Open http://127.0.0.1:13200/admin/login. Sign in with Email `priya.shah@test.com` and Password `cedarLamp42!` and wait for the admin shell.\n\n '\n - 'Open http://127.0.0.1:13200/admin/notification. Open the `Apprise` tab. Turn ON `Enable Apprise notifications` if it is off. In `Apprise Server URL`, clear the field and type exactly `http://localhost:8000/notify`. If a channel URL row is required to save, keep or add one valid non-http scheme value such as `mailto://preserve@example.com`. Click Save changes exactly once. Do not use any API. Wait for the UI result.\n\n '\n - 'Final verdict — judge only from the visible UI. PASS only if Save changes succeeds for `http://localhost:8000/notify` with a visible success confirmation (success toast/notification that settings were saved) and there is no validation error saying the URL must contain `/notify`. FAIL if that valid `/notify` URL is rejected or Save changes clearly does not succeed. If login or the Apprise tab cannot be reached, report uncertain.\n\n '\n"} {"case_id": "sweeper-171", "slug": "statping-ng", "repo": "https://github.com/statping-ng/statping-ng", "base_commit": "ad39c6523da055360f71f879a6b8824743484d92", "reference_commit": "c02149f0a5f67fec1e60cfa3537478cd50899b15", "task_scoped": "Find and fix issues in Statping-ng’s service check-in monitoring.", "task_specified": "Fix Statping-ng static service check-ins: pushing a check-in does not mark the static service online. The service should show as online after a check-in.", "pr": 178, "issue": 16, "workflows": "workflows:\n- id: target-static-checkin-marks-service-online\n category: target\n purpose: 'After a user opens the official check-in URL shown on the Dock Pulse Checkins page, the public status page must show Dock Pulse as ONLINE. On the buggy build the hit is accepted but the static service stays OFFLINE.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official Statping-ng public status page is visible: the document title contains Ashfen Status and Service Monitoring, a styled header shows the heading Ashfen Status (id title) and the description Live shop uptime, vendor/theme CSS is loaded (not a bare unstyled text shell), and the page lists service rows with green ONLINE or red OFFLINE badges. Favicon/theme chrome must be present. If this official status page never appears, stop and treat that as a setup problem, not the check-in bug.\n\n '\n - 'On this public status page, find the service named exactly Dock Pulse and the service named exactly Storefront. Confirm Dock Pulse currently shows a red OFFLINE badge, and Storefront shows a green ONLINE badge. If Dock Pulse is missing, or if it is already ONLINE before any check-in, stop as a setup problem. Do not use Storefront as a substitute for Dock Pulse.\n\n '\n - 'In the page footer click the Dashboard link (it goes to /login when you are not signed in). Wait until the official Statping-ng login form is visible: a styled login card with a Username field (id username), a Password field (id password), and a Sign In button. If a login form never appears, stop as a setup problem.\n\n '\n - 'Type exactly glenWatt into the Username field (id username). Type exactly Hazel8tor into the Password field (id password). Click Sign In. Wait until the signed-in dashboard chrome loads: the top nav shows Statping-ng plus Dashboard and Services, and the main area is the official dashboard (service cards or totals), not the login form. If login fails, stop as a setup problem, not the check-in bug.\n\n '\n - 'On the dashboard, find the Dock Pulse service card (or open Services in the top nav and then open Dock Pulse). Click the Checkins button on that service — the small calendar-check button with class checkins, or the Checkins nav item for this service. Wait until the official Dock Pulse Checkins page is visible: a heading that includes Dock Pulse and Checkins, and a readonly URL field whose value is the check-in URL http://127.0.0.1:13200/checkin/dockpulse (or the same host plus /checkin/ and the api key shown in that field). If this Checkins page or URL field never appears, stop as a setup problem.\n\n '\n - 'Trigger the check-in by opening that exact official check-in URL in the browser: copy it from the readonly field (the Copy button next to the field is fine) and paste it into the address bar, or type/navigate to the URL shown in the field. Wait until the browser leaves the Checkins page and the check-in endpoint responds (the product shows a small JSON success page). Do not use fetch, XHR, curl, DevTools, or the API to trigger the check-in. If you cannot open the URL that was shown on the Checkins page, stop as a setup problem.\n\n '\n - 'After the check-in URL has been opened, go back to the public status page at exactly http://127.0.0.1:13200/ (type that address or use the Statping-ng / Home navigation — do not stay on the JSON page). Wait until the official status page lists Dock Pulse and Storefront again with ONLINE/OFFLINE badges. Refresh once if the list looks stale.\n\n '\n - 'Final verdict — FAIL only if the official public status page is showing Dock Pulse and that service still has a red OFFLINE badge after the check-in URL from the Checkins page was opened in the browser. PASS only if Dock Pulse now shows a green ONLINE badge on that same status page. Do not FAIL because Storefront is ONLINE, because the check-in JSON page looked brief, or because a login dialog was dismissed. Do not PASS if you never opened the check-in URL shown on the Checkins page. Do not use fetch, XHR, or page-context HTTP to construct data, trigger the check-in, or decide pass/fail.\n\n '\n- id: preservation-http-status-site-stays-online\n category: preservation\n purpose: 'A normal HTTP service (Storefront) must still appear ONLINE on the public status page. Guards against a patch that breaks all service status updates.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official Statping-ng public status page is visible: Ashfen Status heading (id title), Live shop uptime description, vendor/theme CSS, and service rows with ONLINE/OFFLINE badges. If already on this page from a previous step, stay there. If the official status page never appears, stop as a setup problem.\n\n '\n - 'Find the service named exactly Storefront on this public status page. This is the HTTP monitor, not Dock Pulse.\n\n '\n - 'Final verdict — PASS if Storefront is visible on the official public status page and shows a green ONLINE badge. FAIL only if Storefront is missing from that page or shows a red OFFLINE badge. Do not FAIL because Dock Pulse is OFFLINE or ONLINE — that is the core check-in bug, not this preservation check. Do not use fetch, XHR, or page-context HTTP to construct data, trigger anything, or decide pass/fail.\n\n '\n"} {"case_id": "sweeper-172", "slug": "stirling-pdf", "repo": "https://github.com/Stirling-Tools/Stirling-PDF", "base_commit": "1c1ead5d6243969f034e67d40d41bb44ceb0f033", "reference_commit": "b7da84d2579e17c4c492b1f0745a901e10fce215", "task_scoped": "Find and fix issues in Stirling-PDF’s PDF metadata editor.", "task_specified": "Fix Stirling-PDF Change Metadata custom fields: newly added custom metadata key/value pairs are not written into the downloaded PDF. After reopening the downloaded PDF on Change Metadata, Show Custom Metadata should be enabled and show the added key/value.", "pr": 2382, "issue": 2346, "workflows": "workflows:\n- id: target-change-metadata-custom-fields-persist\n category: target\n purpose: Verify Change Metadata persists a newly added custom key/value into the downloaded PDF so re-opening the file enables Show Custom Metadata.\n steps:\n - 'Open http://127.0.0.1:13200/change-metadata and wait until the Change Metadata tool page is fully loaded (tool header visible, PDF file selector visible, Title input visible, Add Custom Metadata Entry button visible).\n\n '\n - 'Using browser page context only (no fetch/XHR/HTTP), inject a local File into the native file input. Evaluate JavaScript that (1) base64-decodes the constant string JVBERi0xLjQKMSAwIG9iago8PCAvVHlwZSAvQ2F0YWxvZyAvUGFnZXMgMiAwIFIgPj4KZW5kb2JqCjIgMCBvYmoKPDwgL1R5cGUgL1BhZ2VzIC9LaWRzIFszIDAgUl0gL0NvdW50IDEgPj4KZW5kb2JqCjMgMCBvYmoKPDwgL1R5cGUgL1BhZ2UgL1BhcmVudCAyIDAgUiAvTWVkaWFCb3ggWzAgMCAzMDAgMTQ0XSAvQ29udGVudHMgNCAwIFIgL1Jlc291cmNlczw8IC9Gb250PDwgL0YxIDYgMCBSID4+ID4+ID4+CmVuZG9iago0IDAgb2JqCjw8IC9MZW5ndGggMzYgPj4Kc3RyZWFtCkJUIC9GMSAxMiBUZiA0MCAxMDAgVGQgKEhlbGxvKSBUaiBFVAplbmRzdHJlYW0KZW5kb2JqCjUgMCBvYmoKPDwgL1RpdGxlIChTYW1wbGUpIC9BdXRob3IgKFNhbXBsZXIpIC9Qcm9kdWNlciAoQ2VkYXJUb29scykgPj4KZW5kb2JqCjYgMCBvYmoKPDwgL1R5cGUgL0ZvbnQgL1N1YnR5cGUgL1R5cGUxIC9CYXNlRm9udCAvSGVsdmV0aWNhID4+CmVuZG9iagp4cmVmCjAgNwowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAwMDAwMDkgMDAwMDAgbiAKMDAwMDAwMDA1OCAwMDAwMCBuIAowMDAwMDAwMTE1IDAwMDAwIG4gCjAwMDAwMDAyMzkgMDAwMDAgbiAKMDAwMDAwMDMyNSAwMDAwMCBuIAowMDAwMDAwNDAzIDAwMDAwIG4gCnRyYWlsZXI8PCAvU2l6ZSA3IC9Sb290IDEgMCBSIC9JbmZvIDUgMCBSID4+CnN0YXJ0eHJlZgo0NzMKJSVFT0YK into a Uint8Array, (2) creates new File([bytes], ''cedar-sample.pdf'', {type:''application/pdf''}), (3) assigns it to #fileInput-input via DataTransfer, and (4) dispatches a bubbling change event so the repo-native pdf.js metadata loader runs.\n\n '\n - 'Wait until pdf.js has finished reading the uploaded file and the Title input is populated (it may show Sample). Confirm the Show Custom Metadata checkbox is present (it may be disabled until the downloaded PDF with custom fields is re-uploaded).\n\n '\n - 'Clear the Title field and type exactly: CedarMetaTitle'\n - 'Click the Add Custom Metadata Entry button to create a new custom key/value pair of inputs.\n\n '\n - 'In the newly added custom Key input type exactly: CedarKey'\n - 'In the newly added custom Value input type exactly: CedarVal'\n - 'Click the primary Change button (blue submit, id submitBtn, label Change) and wait for the browser to download the resulting PDF (filename typically ends with _metadata.pdf). Confirm a PDF download completed.\n\n '\n - 'Wait 3 seconds, then navigate again to http://127.0.0.1:13200/change-metadata (fresh page load). If briefly unreachable, retry navigation up to 3 times.\n\n '\n - 'Upload the just-downloaded metadata PDF into the file selector using the downloaded file from this browser session (native file input / upload of the download). Do not use fetch/XHR to read the downloaded PDF for the verdict.\n\n '\n - 'Wait until the Title input shows CedarMetaTitle. This confirms the re-opened file is the processed result, not the original sample.\n\n '\n - Inspect the Show Custom Metadata checkbox after metadata load.\n - 'Final verdict — PASS only if all are true from visible UI: (1) re-uploaded Title shows CedarMetaTitle; (2) Show Custom Metadata checkbox is enabled (not disabled); (3) enabling Show Custom Metadata reveals CedarKey with value CedarVal. FAIL if Title is correct but Show Custom Metadata stays disabled or CedarKey/CedarVal is missing — that is the target bug. FAIL if Change/download failed or re-uploaded Title is not CedarMetaTitle (setup/wrong file; not a product pass).\n\n '\n- id: preservation-change-metadata-standard-title-author\n category: preservation\n purpose: Verify Change Metadata still persists standard Title and Author fields through download and reopen.\n steps:\n - 'Open http://127.0.0.1:13200/change-metadata and wait until the Change Metadata tool page is fully loaded.\n\n '\n - 'Using browser page context only (no fetch/XHR/HTTP), inject a sample PDF as a File named cedar-sample.pdf into #fileInput-input via DataTransfer and dispatch change. Base64-decode this exact string into bytes for the File: JVBERi0xLjQKMSAwIG9iago8PCAvVHlwZSAvQ2F0YWxvZyAvUGFnZXMgMiAwIFIgPj4KZW5kb2JqCjIgMCBvYmoKPDwgL1R5cGUgL1BhZ2VzIC9LaWRzIFszIDAgUl0gL0NvdW50IDEgPj4KZW5kb2JqCjMgMCBvYmoKPDwgL1R5cGUgL1BhZ2UgL1BhcmVudCAyIDAgUiAvTWVkaWFCb3ggWzAgMCAzMDAgMTQ0XSAvQ29udGVudHMgNCAwIFIgL1Jlc291cmNlczw8IC9Gb250PDwgL0YxIDYgMCBSID4+ID4+ID4+CmVuZG9iago0IDAgb2JqCjw8IC9MZW5ndGggMzYgPj4Kc3RyZWFtCkJUIC9GMSAxMiBUZiA0MCAxMDAgVGQgKEhlbGxvKSBUaiBFVAplbmRzdHJlYW0KZW5kb2JqCjUgMCBvYmoKPDwgL1RpdGxlIChTYW1wbGUpIC9BdXRob3IgKFNhbXBsZXIpIC9Qcm9kdWNlciAoQ2VkYXJUb29scykgPj4KZW5kb2JqCjYgMCBvYmoKPDwgL1R5cGUgL0ZvbnQgL1N1YnR5cGUgL1R5cGUxIC9CYXNlRm9udCAvSGVsdmV0aWNhID4+CmVuZG9iagp4cmVmCjAgNwowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAwMDAwMDkgMDAwMDAgbiAKMDAwMDAwMDA1OCAwMDAwMCBuIAowMDAwMDAwMTE1IDAwMDAwIG4gCjAwMDAwMDAyMzkgMDAwMDAgbiAKMDAwMDAwMDMyNSAwMDAwMCBuIAowMDAwMDAwNDAzIDAwMDAwIG4gCnRyYWlsZXI8PCAvU2l6ZSA3IC9Sb290IDEgMCBSIC9JbmZvIDUgMCBSID4+CnN0YXJ0eHJlZgo0NzMKJSVFT0YK\n\n '\n - Wait until pdf.js has loaded the file metadata into the form.\n - 'Clear the Title field and type exactly: CedarPreserveTitle'\n - 'Clear the Author field and type exactly: CedarPreserveAuthor'\n - Do not add any custom metadata rows.\n - 'Click the primary Change button (blue submit, id submitBtn, label Change) and wait for the browser to download the resulting PDF.\n\n '\n - Wait 3 seconds, then navigate again to http://127.0.0.1:13200/change-metadata. If the page is briefly unreachable, retry navigation up to 3 times.\n - Upload the just-downloaded metadata PDF into the file selector.\n - Wait until the form fields are populated from the uploaded file.\n - 'Final verdict — PASS only if Title shows CedarPreserveTitle and Author shows CedarPreserveAuthor after re-upload. FAIL if either standard field is missing or wrong. Do not pass if download failed or the wrong file was re-uploaded.\n\n '\n"} {"case_id": "sweeper-173", "slug": "suitecrm", "repo": "https://github.com/salesagility/SuiteCRM", "base_commit": "4e4ad3bb9057844cc575dafe17f90b058ec8ae4d", "reference_commit": "f11cca5d4e61d7ea898e672603293f1255cb23d2", "task_scoped": "Find and fix issues in SuiteCRM’s outbound email account configuration.", "task_specified": "Fix SuiteCRM outbound email account saving so that renaming or saving a Basic-Auth SMTP account without re-entering the password preserves the stored SMTP password. After such a save, Send Test Email should still succeed with the existing credentials instead of failing SMTP authentication.", "pr": 10869, "issue": 10763, "workflows": "workflows:\n- id: outbound-resave-preserves-smtp-password\n category: target\n purpose: 'Verify that renaming a Basic-Auth outbound email account and saving without re-entering the password keeps SMTP authentication working for Send Test Email.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Navigate to http://127.0.0.1:13200/\n - 'Confirm the SuiteCRM login page is visible (SuiteP login logo/branding and Username / Password fields). If the page is unreachable, shows a PHP/database error, or is an unstyled bare-text shell, stop as setup failure.\n\n '\n - 'Log in as noah.reed / quiltForge6!. Confirm you reach an authenticated SuiteCRM home (top navigation / sidebar modules). If login fails, stop as setup failure.\n\n '\n - 'Open Admin from the user/admin menu, then open Email → Outbound Email (index.php?module=OutboundEmailAccounts&action=index). Confirm the list of Outbound Email Accounts is visible.\n\n '\n - 'Open the seeded account named exactly \"Northline Office SMTP\". If that name is gone and the list only has \"Northline Office SMTP Renamed\" (leftover from an earlier try), open that leftover row instead — do not stop as setup failure. Confirm the edit form shows Account settings / Server Configuration fields including Name, Auth Type (Basic Auth), SMTP server 127.0.0.1, and a Send Test Email control. If neither name is present, stop as setup failure.\n\n '\n - 'On this same Outbound Email Account Edit view (the record edit form / Actions → Edit page — not the list index), click Send Test Email. In the dialog, set the recipient to noah.reed@test.com (or keep the prefilled current-user email) and send. If you opened the original \"Northline Office SMTP\" name, confirm the success overlay stating that an email was sent / test notification was sent; if this first test fails, stop as setup failure (Mailpit/SMTP seed problem), not a product verdict. If you opened leftover \"Northline Office SMTP Renamed\", skip this first-test setup requirement and go to the rename/test steps using that leftover row.\n\n '\n - \"If the Name is still \\\"Northline Office SMTP\\\", change only the Name field to \\\"Northline Office SMTP Renamed\\\". Do NOT enter a new password (leave the writeonly password blank / do not use Change password unless required to leave it empty). Keep Auth Type as Basic Auth. Save the record. If the leftover row is already named \\\"Northline Office SMTP Renamed\\\", do not rename again and do not enter a password.\\n Change only Name: do not reconfigure SMTP or perform an extra corrective save between the first successful test and this rename save.\"\n - 'Confirm the save succeeds and the form/list reflects the renamed account. If save fails for unrelated validation, stop as setup failure.\n\n '\n - 'With the renamed account still on the Outbound Email Account Edit view (or reopen it via Actions → Edit on that record — not from the list page alone), click Send Test Email again on that Edit form, send to noah.reed@test.com, and observe the result overlay/dialog.\n\n '\n - 'Final verdict (require both scene and bug-specific evidence). FAIL only if ALL are true: (1) you are on the renamed leftover account (Name is Northline Office SMTP Renamed, whether you just saved that name or opened a leftover already renamed); (2) Send Test Email after that rename/leftover open shows a clear SMTP authentication failure in the UI (for example text containing \"An email error occurred\" together with authentication / credentials invalid / Could not authenticate / 535); (3) there is no success message that an email notification was sent. PASS only if ALL are true: (1) same renamed-account scene; (2) that Send Test Email shows the success notification that an email was sent using the outgoing mail settings; (3) there is no SMTP authentication/credentials-invalid error. Do not use uncertain only because the original \"Northline Office SMTP\" name is already gone. Setup/login/navigation failures (neither name present) are not product PASS/FAIL for this bug.\n\n '\n- id: outbound-explicit-password-save-still-works\n category: preservation\n purpose: 'Preserve that creating/saving an outbound account with an explicitly entered Basic-Auth password still allows Send Test Email to succeed.\n\n '\n steps:\n - 'Action-evidence rule: a command that raises before a click/save did not perform that action. After an exception, inspect the current UI and complete the missing action before judging its effect. Never claim an unexecuted step succeeded. If a required setup/action cannot be completed, return uncertain with the reason; retain the workflow-specific product PASS/FAIL conditions below.'\n - Navigate to http://127.0.0.1:13200/\n - Confirm the SuiteCRM login page with SuiteP branding is visible. If unreachable, stop as setup failure.\n - Log in as noah.reed / quiltForge6!. Confirm an authenticated UI loads.\n - Open Admin → Email → Outbound Email (OutboundEmailAccounts index).\n - Create Northline Preserve SMTP using Basic Auth. Select SMTP protocol/SSL None (0/no SSL) FIRST, then enter server 127.0.0.1, username smtpuser, From Name Preserve Sender, From Address noah.reed@test.com, and explicitly enter password SmtpPass123!. Set port 1025 LAST, after choosing the protocol, because choosing None can reset the port to 25. Before Save, verify the visible nonsecret configuration including port=1025 and protocol=None and ensure you explicitly entered the password on this same save. Save once. If any correction requires another save, explicitly re-enter SmtpPass123! again before that save, or recreate the account; never perform a password-blank corrective save in this preservation workflow.\n - \"Confirm creation/save succeeded. If creation fails, stop as setup failure.\\n Verify the saved port is 1025. If correcting it, follow the explicit-password-on-every-save rule above.\"\n - 'Open the new account on the Outbound Email Account Edit view if it is not already open (Actions → Edit on that record — not the list index alone). On that Edit form, click Send Test Email, send to noah.reed@test.com, and observe the result.\n\n '\n - 'Final verdict. PASS only if Send Test Email shows the success notification that an email was sent with these explicitly entered Basic-Auth settings. FAIL only if that explicitly configured account''s Send Test Email clearly fails with an SMTP authentication/credentials error in the UI. Setup/login/create failures are not product FAIL for this preservation check.\n\n '\n"} {"case_id": "sweeper-174", "slug": "sylius", "repo": "https://github.com/Sylius/Sylius", "base_commit": "b12d46116d3b0b262b18a3316dd2f8762dfbb7c2", "reference_commit": "14f5fc8d44e6d1dcdf00100b19576600f95c030f", "task_scoped": "Find and fix issues in Sylius’ shopping cart and checkout handoff.", "task_specified": "Fix Sylius shop Checkout so a valid coupon with an items-total rule is not rejected after it applies. Applying such a coupon and continuing to checkout should keep the coupon applied and should not treat the cart as invalid.", "pr": 19052, "issue": 16303, "workflows": "workflows:\n- id: target-coupon-checkout-self-invalidation\n category: target\n purpose: A coupon whose items-total rule is met before the discount must stay valid on Checkout. Revalidating against the already-discounted total wrongly shows \"Coupon code is invalid\" and blocks checkout.\n steps:\n - Open http://127.0.0.1:13200/en_US/ and wait until the official Sylius Fashion Web Store homepage loads with shop CSS (not a bare-text page), the Fashion Web Store title/branding, and homepage banner or product images.\n - Open http://127.0.0.1:13200/en_US/login and wait for the official shop Login page (styled, Username and Password fields, a Login submit button). Sign in as Nella Voss with username `nella@test.com` and password `Flint6bracken`. Confirm you leave the login form and the official shop chrome is visible (for example a cart icon or account area).\n - Open http://127.0.0.1:13200/en_US/products/gilt-jersey-tee and wait for the official product page titled Gilt Jersey Tee. Confirm the visible price includes $22.00 and an Add to cart control is shown.\n - On that product page, set the quantity field to `2` (not 1). Click Add to cart and wait until the cart updates (flash, cart total, or mini-cart no longer $0.00).\n - Open http://127.0.0.1:13200/en_US/cart/ and wait for Your shopping cart. If the cart already has other items or an applied coupon, click Clear cart (or remove coupon) first, then go back to the Gilt Jersey Tee page, set quantity 2, and Add to cart again. Confirm Gilt Jersey Tee is listed with quantity 2 and the coupon area shows an input (placeholder such as Enter your code) plus an Apply coupon button.\n - 'Type VIRECREW10 into the coupon input. Click Apply coupon and wait for the cart to refresh. Confirm the first application succeeded: the page shows Applied coupon VIRECREW10 and/or a Discount line around -$10.00. Items total is about $34.00 excluding shipping; Estimated shipping cost is $9.72, so the order total including shipping is about $43.72. Do not treat the shipping line as a coupon failure. If this first apply already says Coupon code is invalid, treat that as a setup problem only if the two $22 items are not in the cart; if they are, it is still the target bug.'\n - Click the primary Checkout button on the cart page (not a header mini-cart). Wait until the page finishes navigating or re-rendering.\n - Inspect the visible result of that Checkout click. Look specifically for (A) remaining on the cart with a validation error such as Coupon code is invalid or Due to invalid values in your cart, it has not been recalculated, so the address checkout step does not open, versus (B) reaching the official checkout address step (URL containing /checkout/address, or visible address fields such as first name / last name / street) without that cart-invalid error.\n - 'Final verdict: FAIL only if, after two Gilt Jersey Tee items were in the cart and VIRECREW10 first applied, clicking Checkout keeps you on the cart with Coupon code is invalid or Due to invalid values in your cart, it has not been recalculated, so the address checkout step does not open. PASS only if that same Checkout click reaches the address checkout step and VIRECREW10 is not rejected. Do not FAIL for login/navigation/add-to-cart problems before Checkout. Do not FAIL because Estimated shipping cost $9.72 is present. Do not use fetch, XHR, DevTools Network, API, logs, or the database as the oracle.'\n- id: preservation-plain-coupon-checkout\n category: preservation\n purpose: A coupon without an items-total threshold (ALDERFOLD5) still applies and still allows Checkout to the address step.\n steps:\n - Open http://127.0.0.1:13200/en_US/ and wait for the official styled Fashion Web Store homepage (shop CSS, branding, not a bare-text page).\n - Open http://127.0.0.1:13200/en_US/login and sign in as Nella Voss with username `nella@test.com` and password `Flint6bracken`. Confirm the official shop UI loads after login.\n - Open http://127.0.0.1:13200/en_US/products/gilt-jersey-tee. Confirm Gilt Jersey Tee and Add to cart. Set quantity to `2` and click Add to cart. Wait until the cart updates.\n - Open http://127.0.0.1:13200/en_US/cart/. If another coupon is already applied, remove it (trash icon) or click Clear cart and re-add two Gilt Jersey Tees. Confirm Gilt Jersey Tee is in Your shopping cart with a coupon input and Apply coupon.\n - Type ALDERFOLD5 into the coupon input. Click Apply coupon and wait for the cart to refresh. Confirm Applied coupon ALDERFOLD5 and/or a Discount around -$5.00. Items total is about $39.00 excluding shipping; Estimated shipping cost is $9.72, so the order total including shipping is about $48.72. Do not treat the shipping line as a coupon failure.\n - Click the primary Checkout button. Wait for navigation or re-render.\n - 'Final verdict: PASS only if ALDERFOLD5 applied on the cart (Applied coupon: ALDERFOLD5 or a visible -$5 discount) and Checkout then reached the official address step (URL containing /checkout/address or visible address fields) without Coupon code is invalid. FAIL if ALDERFOLD5 cannot be applied on a 2-item Gilt Jersey Tee cart, or Checkout is blocked after ALDERFOLD5. Do not FAIL based on VIRECREW10 / items-total self-invalidation (that is the core bug). Do not FAIL because Estimated shipping cost $9.72 is present. Do not use fetch, XHR, DevTools Network, API, logs, or the database as the oracle.'\n"} {"case_id": "sweeper-175", "slug": "tandoor-recipes", "repo": "https://github.com/TandoorRecipes/recipes", "base_commit": "e71ed76554a0a55d24ba8722b58c1fd8cf1542e9", "reference_commit": "934deded0f4bc78b7a03129d599cfe0b37146972", "task_scoped": "Find and fix issues in Tandoor’s recipe import tools.", "task_specified": "Fix Tandoor Mealie 1.x recipe import so ingredient section headers keep their position order when a Mealie export zip is imported. Imported recipes with section headers should show those headers in the original order around their foods instead of grouping the headers incorrectly.", "pr": 4454, "issue": 4443, "workflows": "workflows:\n- id: target-mealie1-import-keeps-ingredient-section-order\n category: target\n purpose: Mealie 1.x import of a recipe with ingredient section headers must preserve section order in the recipe ingredient list.\n steps:\n - Open http://127.0.0.1:13200/accounts/login/ and log in with username `mira-chen` and password `pineShelf42!`. Wait until the signed-in Tandoor UI is visible.\n - Open http://127.0.0.1:13200/recipe/import and confirm the App Import UI is visible.\n - \"Run this Python on the host against http://127.0.0.1:13200 (same `/api/import/` path as App Import).\\nIt logs in, builds a Mealie 1.x zip with stdlib `zipfile`, and POSTs it.\\nPaste the script exactly. Do not rewrite the payload.\\nIt retries the same zip when the log contains `ERROR`, up to 8 times, and prints the successful log.\\n```\\npython3 - <<'PY'\\nimport io, json, re, time, zipfile, urllib.request, http.cookiejar\\nfrom urllib.parse import urlencode\\nBASE = \\\"http://127.0.0.1:13200\\\"\\nDB = json.loads(r'''{\\\"categories\\\":[],\\\"tags\\\":[],\\\"multi_purpose_labels\\\":[],\\\"ingredient_foods\\\":[{\\\"id\\\":\\\"f1\\\",\\\"name\\\":\\\"Flour\\\",\\\"plural_name\\\":\\\"Flour\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f2\\\",\\\"name\\\":\\\"Water\\\",\\\"plural_name\\\":\\\"Water\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f3\\\",\\\"name\\\":\\\"Cheese\\\",\\\"plural_name\\\":\\\"Cheese\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f4\\\",\\\"name\\\":\\\"Salt\\\",\\\"plural_name\\\":\\\"Salt\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f5\\\",\\\"name\\\":\\\"Butter\\\",\\\"plural_name\\\":\\\"Butter\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false}],\\\"ingredient_units\\\":[{\\\"id\\\":\\\"u1\\\",\\\"name\\\":\\\"cup\\\",\\\"plural_name\\\":\\\"cups\\\",\\\"description\\\":\\\"\\\"},{\\\"id\\\":\\\"u2\\\",\\\"name\\\":\\\"g\\\",\\\"plural_name\\\":\\\"g\\\",\\\"description\\\":\\\"\\\"}],\\\"recipes\\\":[{\\\"id\\\":\\\"r1\\\",\\\"name\\\":\\\"Section Order Demo\\\",\\\"description\\\":\\\"demo recipe\\\",\\\"org_url\\\":\\\"\\\",\\\"recipe_servings\\\":2,\\\"recipe_yield\\\":\\\"2 servings\\\",\\\"perform_time\\\":\\\"10 minutes\\\",\\\"prep_time\\\":\\\"5 minutes\\\",\\\"created_at\\\":\\\"2026-01-01T00:00:00\\\"}],\\\"recipe_instructions\\\":[{\\\"id\\\":\\\"s1\\\",\\\"recipe_id\\\":\\\"r1\\\",\\\"position\\\":0,\\\"title\\\":\\\"Mix\\\",\\\"text\\\":\\\"Mix ingredients.\\\",\\\"summary\\\":\\\"\\\"}],\\\"notes\\\":[],\\\"recipe_ingredient_ref_link\\\":[],\\\"recipes_ingredients\\\":[{\\\"recipe_id\\\":\\\"r1\\\",\\\"title\\\":\\\"For the filling\\\",\\\"food_id\\\":\\\"f3\\\",\\\"unit_id\\\":\\\"u2\\\",\\\"original_text\\\":\\\"100 g cheese\\\",\\\"position\\\":11,\\\"quantity\\\":100,\\\"note\\\":\\\"\\\"},{\\\"recipe_id\\\":\\\"r1\\\",\\\"title\\\":\\\"For the dough\\\",\\\"food_id\\\":\\\"f1\\\",\\\"unit_id\\\":\\\"u1\\\",\\\"original_text\\\":\\\"2 cups flour\\\",\\\"position\\\":1,\\\"quantity\\\":2,\\\"note\\\":\\\"\\\"},{\\\"recipe_id\\\":\\\"r1\\\",\\\"title\\\":null,\\\"food_id\\\":\\\"f2\\\",\\\"unit_id\\\":\\\"u1\\\",\\\"original_text\\\":\\\"1 cup water\\\",\\\"position\\\":2,\\\"quantity\\\":1,\\\"note\\\":\\\"\\\"},{\\\"recipe_id\\\":\\\"r1\\\",\\\"title\\\":null,\\\"food_id\\\":\\\"f4\\\",\\\"unit_id\\\":\\\"u2\\\",\\\"original_text\\\":\\\"5 g salt\\\",\\\"position\\\":3,\\\"quantity\\\":5,\\\"note\\\":\\\"\\\"}],\\\"recipes_to_categories\\\":[],\\\"recipes_to_tags\\\":[],\\\"recipe_nutrition\\\":[],\\\"recipe_comments\\\":[],\\\"recipe_timeline_events\\\":[],\\\"group_meal_plans\\\":[],\\\"shopping_list_items\\\":[]}''')\\nclass C:\\n def __init__(self):\\n self.cj = http.cookiejar.CookieJar()\\n self.op = urllib.request.build_opener(urllib.request.HTTPCookieProcessor(self.cj))\\n def csrf(self):\\n for c in self.cj:\\n if c.name == \\\"csrftoken\\\":\\n return c.value\\n return \\\"\\\"\\n def get(self, p):\\n with self.op.open(urllib.request.Request(BASE + p), timeout=30) as r:\\n return r.read()\\n def post(self, p, fields, raw=None, fn=\\\"section-order-demo.zip\\\"):\\n if raw is None:\\n body = urlencode(fields).encode()\\n hdr = {\\\"Content-Type\\\": \\\"application/x-www-form-urlencoded\\\"}\\n else:\\n b = \\\"----S\\\"\\n data = b\\\"\\\"\\n for k, v in fields.items():\\n data += f\\\"--{b}\\\\r\\\\nContent-Disposition: form-data; name=\\\\\\\"{k}\\\\\\\"\\\\r\\\\n\\\\r\\\\n{v}\\\\r\\\\n\\\".encode()\\n data += f\\\"--{b}\\\\r\\\\nContent-Disposition: form-data; name=\\\\\\\"files\\\\\\\"; filename=\\\\\\\"{fn}\\\\\\\"\\\\r\\\\nContent-Type: application/zip\\\\r\\\\n\\\\r\\\\n\\\".encode() + raw + f\\\"\\\\r\\\\n--{b}--\\\\r\\\\n\\\".encode()\\n body = data\\n hdr = {\\\"Content-Type\\\": f\\\"multipart/form-data; boundary={b}\\\"}\\n t = self.csrf()\\n if t:\\n hdr[\\\"X-CSRFToken\\\"] = t\\n hdr[\\\"Referer\\\"] = BASE + p\\n with self.op.open(urllib.request.Request(BASE + p, data=body, headers=hdr, method=\\\"POST\\\"), timeout=180) as r:\\n return r.read()\\nbuf = io.BytesIO()\\nwith zipfile.ZipFile(buf, \\\"w\\\", zipfile.ZIP_STORED) as z:\\n z.writestr(\\\"database.json\\\", json.dumps(DB, ensure_ascii=False))\\nzbytes = buf.getvalue()\\nc = C()\\nhtml = c.get(\\\"/accounts/login/\\\").decode(\\\"utf-8\\\", \\\"replace\\\")\\nm = re.search(r'name=\\\"csrfmiddlewaretoken\\\" value=\\\"([^\\\"]+)\\\"', html)\\ntok = c.csrf() or (m.group(1) if m else \\\"\\\")\\nc.post(\\\"/accounts/login/\\\", {\\\"csrfmiddlewaretoken\\\": tok, \\\"login\\\": \\\"mira-chen\\\", \\\"password\\\": \\\"pineShelf42!\\\"})\\nlast = None\\nfor i in range(8):\\n data = json.loads(c.post(\\\"/api/import/\\\", {\\\"type\\\": \\\"MEALIE1\\\", \\\"duplicates\\\": \\\"true\\\", \\\"meal_plans\\\": \\\"false\\\", \\\"shopping_lists\\\": \\\"false\\\", \\\"nutrition_per_serving\\\": \\\"false\\\"}, zbytes))\\n iid = data.get(\\\"import_id\\\") or data.get(\\\"id\\\")\\n log = data\\n for _ in range(40):\\n log = json.loads(c.get(f\\\"/api/import-log/{iid}/\\\"))\\n if not log.get(\\\"running\\\"):\\n break\\n time.sleep(0.4)\\n last = log\\n msg = str(log.get(\\\"msg\\\") or \\\"\\\")\\n print(\\\"attempt\\\", i, \\\"error\\\", \\\"ERROR\\\" in msg)\\n if \\\"ERROR\\\" not in msg and \\\"Imported 1 recipes\\\" in msg:\\n print(json.dumps(log))\\n break\\nelse:\\n raise SystemExit(\\\"import kept failing\\\")\\nPY\\n```\\nConfirm the script prints a log with `running` false, no `ERROR`, and `Imported 1 recipes`.\\n\"\n - 'Open the newest `Section Order Demo` created by the successful import (the last attempt, highest recipe id / most recently created). Do not open an earlier empty copy from a failed attempt. Wait until the ingredient list is visible: section headers `For the filling` / `For the dough` or foods `Flour` / `Cheese`. A short wait or one hard refresh on this same recipe is fine if the page is still settling.\n\n '\n - 'Final verdict — decide ONLY from the visible ingredient list order on that newest successful recipe. The top-level `result` must match the section-order substep. PASS only if section header `For the dough` appears before foods `Flour`, `Water`, and `Salt`, and section header `For the filling` appears after those dough foods and before `Cheese`. FAIL only if you can see the list and `For the filling` appears before `For the dough`, or both headers are stacked together above all foods while `Cheese` is listed after `Salt` with no filling header between them. If the successful import still shows a title with a completely missing list after a short wait and one hard refresh, the top-level result MUST be uncertain. When you call done, the text MUST be ONLY a single JSON object with no markdown and no prose, for example: {\"result\":\"fail\",\"substeps\":[{\"step\":\"login\",\"result\":\"pass\",\"reason\":\"signed in\"},{\"step\":\"import\",\"result\":\"pass\",\"reason\":\"import finished\"},{\"step\":\"section order\",\"result\":\"fail\",\"reason\":\"For the filling appears before For the dough; headers stacked above foods\"}]}\n\n '\n- id: preservation-mealie1-import-simple-recipe\n category: preservation\n purpose: Normal Mealie 1.x import of a simple recipe without section headers should still create the recipe with its ingredients.\n steps:\n - Open http://127.0.0.1:13200/accounts/login/ and log in with username `mira-chen` and password `pineShelf42!` if needed. Wait until the signed-in Tandoor UI is visible.\n - Open http://127.0.0.1:13200/recipe/import and confirm the App Import UI is visible.\n - \"Run this Python on the host against http://127.0.0.1:13200 (same `/api/import/` path as App Import).\\nIt logs in, builds a Mealie 1.x zip with stdlib `zipfile` for a simple recipe without section headers, and POSTs it.\\nPaste the script exactly. Do not rewrite the payload.\\nIt retries the same zip when the log contains `ERROR`, up to 8 times, and prints the successful log.\\n```\\npython3 - <<'PY'\\nimport io, json, re, time, zipfile, urllib.request, http.cookiejar\\nfrom urllib.parse import urlencode\\nBASE = \\\"http://127.0.0.1:13200\\\"\\nDB = json.loads(r'''{\\\"categories\\\":[],\\\"tags\\\":[],\\\"multi_purpose_labels\\\":[],\\\"ingredient_foods\\\":[{\\\"id\\\":\\\"f1\\\",\\\"name\\\":\\\"Flour\\\",\\\"plural_name\\\":\\\"Flour\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f2\\\",\\\"name\\\":\\\"Water\\\",\\\"plural_name\\\":\\\"Water\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f3\\\",\\\"name\\\":\\\"Cheese\\\",\\\"plural_name\\\":\\\"Cheese\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f4\\\",\\\"name\\\":\\\"Salt\\\",\\\"plural_name\\\":\\\"Salt\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false},{\\\"id\\\":\\\"f5\\\",\\\"name\\\":\\\"Butter\\\",\\\"plural_name\\\":\\\"Butter\\\",\\\"description\\\":\\\"\\\",\\\"label_id\\\":null,\\\"on_hand\\\":false}],\\\"ingredient_units\\\":[{\\\"id\\\":\\\"u1\\\",\\\"name\\\":\\\"cup\\\",\\\"plural_name\\\":\\\"cups\\\",\\\"description\\\":\\\"\\\"},{\\\"id\\\":\\\"u2\\\",\\\"name\\\":\\\"g\\\",\\\"plural_name\\\":\\\"g\\\",\\\"description\\\":\\\"\\\"}],\\\"recipes\\\":[{\\\"id\\\":\\\"r1\\\",\\\"name\\\":\\\"Simple Butter Flour\\\",\\\"description\\\":\\\"demo recipe\\\",\\\"org_url\\\":\\\"\\\",\\\"recipe_servings\\\":2,\\\"recipe_yield\\\":\\\"2 servings\\\",\\\"perform_time\\\":\\\"10 minutes\\\",\\\"prep_time\\\":\\\"5 minutes\\\",\\\"created_at\\\":\\\"2026-01-01T00:00:00\\\"}],\\\"recipe_instructions\\\":[{\\\"id\\\":\\\"s1\\\",\\\"recipe_id\\\":\\\"r1\\\",\\\"position\\\":0,\\\"title\\\":\\\"Mix\\\",\\\"text\\\":\\\"Mix ingredients.\\\",\\\"summary\\\":\\\"\\\"}],\\\"notes\\\":[],\\\"recipe_ingredient_ref_link\\\":[],\\\"recipes_ingredients\\\":[{\\\"recipe_id\\\":\\\"r1\\\",\\\"title\\\":null,\\\"food_id\\\":\\\"f1\\\",\\\"unit_id\\\":\\\"u1\\\",\\\"original_text\\\":\\\"1 cup flour\\\",\\\"position\\\":0,\\\"quantity\\\":1,\\\"note\\\":\\\"\\\"},{\\\"recipe_id\\\":\\\"r1\\\",\\\"title\\\":null,\\\"food_id\\\":\\\"f5\\\",\\\"unit_id\\\":\\\"u2\\\",\\\"original_text\\\":\\\"50 g butter\\\",\\\"position\\\":1,\\\"quantity\\\":50,\\\"note\\\":\\\"\\\"}],\\\"recipes_to_categories\\\":[],\\\"recipes_to_tags\\\":[],\\\"recipe_nutrition\\\":[],\\\"recipe_comments\\\":[],\\\"recipe_timeline_events\\\":[],\\\"group_meal_plans\\\":[],\\\"shopping_list_items\\\":[]}''')\\nclass C:\\n def __init__(self):\\n self.cj = http.cookiejar.CookieJar()\\n self.op = urllib.request.build_opener(urllib.request.HTTPCookieProcessor(self.cj))\\n def csrf(self):\\n for c in self.cj:\\n if c.name == \\\"csrftoken\\\":\\n return c.value\\n return \\\"\\\"\\n def get(self, p):\\n with self.op.open(urllib.request.Request(BASE + p), timeout=30) as r:\\n return r.read()\\n def post(self, p, fields, raw=None, fn=\\\"simple-butter-flour.zip\\\"):\\n if raw is None:\\n body = urlencode(fields).encode()\\n hdr = {\\\"Content-Type\\\": \\\"application/x-www-form-urlencoded\\\"}\\n else:\\n b = \\\"----S\\\"\\n data = b\\\"\\\"\\n for k, v in fields.items():\\n data += f\\\"--{b}\\\\r\\\\nContent-Disposition: form-data; name=\\\\\\\"{k}\\\\\\\"\\\\r\\\\n\\\\r\\\\n{v}\\\\r\\\\n\\\".encode()\\n data += f\\\"--{b}\\\\r\\\\nContent-Disposition: form-data; name=\\\\\\\"files\\\\\\\"; filename=\\\\\\\"{fn}\\\\\\\"\\\\r\\\\nContent-Type: application/zip\\\\r\\\\n\\\\r\\\\n\\\".encode() + raw + f\\\"\\\\r\\\\n--{b}--\\\\r\\\\n\\\".encode()\\n body = data\\n hdr = {\\\"Content-Type\\\": f\\\"multipart/form-data; boundary={b}\\\"}\\n t = self.csrf()\\n if t:\\n hdr[\\\"X-CSRFToken\\\"] = t\\n hdr[\\\"Referer\\\"] = BASE + p\\n with self.op.open(urllib.request.Request(BASE + p, data=body, headers=hdr, method=\\\"POST\\\"), timeout=180) as r:\\n return r.read()\\nbuf = io.BytesIO()\\nwith zipfile.ZipFile(buf, \\\"w\\\", zipfile.ZIP_STORED) as z:\\n z.writestr(\\\"database.json\\\", json.dumps(DB, ensure_ascii=False))\\nzbytes = buf.getvalue()\\nc = C()\\nhtml = c.get(\\\"/accounts/login/\\\").decode(\\\"utf-8\\\", \\\"replace\\\")\\nm = re.search(r'name=\\\"csrfmiddlewaretoken\\\" value=\\\"([^\\\"]+)\\\"', html)\\ntok = c.csrf() or (m.group(1) if m else \\\"\\\")\\nc.post(\\\"/accounts/login/\\\", {\\\"csrfmiddlewaretoken\\\": tok, \\\"login\\\": \\\"mira-chen\\\", \\\"password\\\": \\\"pineShelf42!\\\"})\\nlast = None\\nfor i in range(8):\\n data = json.loads(c.post(\\\"/api/import/\\\", {\\\"type\\\": \\\"MEALIE1\\\", \\\"duplicates\\\": \\\"true\\\", \\\"meal_plans\\\": \\\"false\\\", \\\"shopping_lists\\\": \\\"false\\\", \\\"nutrition_per_serving\\\": \\\"false\\\"}, zbytes))\\n iid = data.get(\\\"import_id\\\") or data.get(\\\"id\\\")\\n log = data\\n for _ in range(40):\\n log = json.loads(c.get(f\\\"/api/import-log/{iid}/\\\"))\\n if not log.get(\\\"running\\\"):\\n break\\n time.sleep(0.4)\\n last = log\\n msg = str(log.get(\\\"msg\\\") or \\\"\\\")\\n print(\\\"attempt\\\", i, \\\"error\\\", \\\"ERROR\\\" in msg)\\n if \\\"ERROR\\\" not in msg and \\\"Imported 1 recipes\\\" in msg:\\n print(json.dumps(log))\\n break\\nelse:\\n raise SystemExit(\\\"import kept failing\\\")\\nPY\\n```\\nConfirm the script prints a log with `running` false, no `ERROR`, and `Imported 1 recipes`.\\n\"\n - 'Open the newest `Simple Butter Flour` created by the successful import (the last attempt, highest recipe id / most recently created). Do not open an earlier empty copy from a failed attempt. Wait until its ingredient list is visible.\n\n '\n - 'Final verdict — PASS only if the recipe `Simple Butter Flour` is visible and its ingredient list shows both `Flour` and `Butter`. FAIL if the recipe is missing or either ingredient is missing. When you call done, the text MUST be ONLY a single JSON object with no markdown and no prose, for example: {\"result\":\"pass\",\"substeps\":[{\"step\":\"login\",\"result\":\"pass\",\"reason\":\"signed in\"},{\"step\":\"import\",\"result\":\"pass\",\"reason\":\"import finished\"},{\"step\":\"ingredients\",\"result\":\"pass\",\"reason\":\"Flour and Butter visible\"}]}\n\n '\n"} {"case_id": "sweeper-176", "slug": "tastyigniter", "repo": "https://github.com/tastyigniter/TastyIgniter", "base_commit": "ef6aa9ea9f5b454ec3067e9dc2935ae8d99c2da5", "reference_commit": "2b1e99ec8de5d9993adaf4a4457cd5130ff28b8d", "task_scoped": "Find and fix issues in TastyIgniter’s reservation management.", "task_specified": "Fix TastyIgniter reservation edit Delete so the edit form Delete action forwards the reservation id and removes the reservation. After opening a reservation and clicking Delete, that reservation should be gone from the reservations list instead of showing that the form record ID was not specified.", "pr": 1115, "issue": null, "workflows": "workflows:\n- id: target-reservation-edit-delete\n category: target\n purpose: 'Deleting a reservation from its edit form must remove that reservation. On the buggy build, edit_onDelete does not forward the record id, so the UI shows that the form record ID was not specified and Piper Lang remains. After the fix, Delete succeeds and Piper Lang is gone from the reservations list.\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin/login and wait until the TastyIgniter admin login page is visible (Username and Password fields).\n - Type exactly beckOrne into the Username field.\n - Type exactly flint8prairie into the Password field.\n - Click the Login button and wait until the authenticated admin UI loads (dashboard or admin chrome with a side menu).\n - Open exactly http://127.0.0.1:13200/admin/reservations and wait until the Reservations list is visible.\n - Find the reservation row for guest Piper Lang (first name Piper, last name Lang). Click that row's edit control / name link so the reservation edit form opens.\n - On the reservation edit form, click the Delete button (danger/delete toolbar control). If a browser confirm dialog appears asking to confirm deletion, accept/confirm it.\n - Wait for the delete request to finish (flash/notification, error message, or return to the reservations list).\n - 'Decide which outcome you see: (A) a success message that a reservation was deleted and/or the reservations list no longer shows Piper Lang, OR (B) an error about Form record ID has not been specified / missing id, and/or Piper Lang is still present in the reservations list after revisiting http://127.0.0.1:13200/admin/reservations.'\n - Final verdict — PASS only if Piper Lang was deleted (success flash and/or absent from the reservations list). FAIL only if delete from the edit form failed with a missing form-record-id style error and/or Piper Lang remains listed. Do not FAIL for slow loads; use uncertain only if login or the reservations edit UI cannot be completed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-reservation-list-delete\n category: preservation\n purpose: 'Deleting a reservation from the list/index toolbar must keep working (index_onDelete is separate from the edit_onDelete bug and must not break).\n\n '\n steps:\n - Open exactly http://127.0.0.1:13200/admin/login and wait until the TastyIgniter admin login page is visible.\n - Type exactly beckOrne into the Username field.\n - Type exactly flint8prairie into the Password field.\n - Click the Login button and wait until the authenticated admin UI loads.\n - Open exactly http://127.0.0.1:13200/admin/reservations and wait until the Reservations list is visible and includes Nolan Reeve.\n - In the reservations list, select/check the row for Nolan Reeve.\n - Click the list Delete action/button for selected records. If a confirm dialog appears, accept/confirm it.\n - Wait until the list refreshes or a success notification appears.\n - Final verdict — PASS only if Nolan Reeve is no longer shown in the reservations list after list delete. FAIL if Nolan Reeve remains listed after the list delete action. Do not FAIL for slow loads; use uncertain only if the list-delete flow cannot be completed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n"} {"case_id": "sweeper-177", "slug": "teampass", "repo": "https://github.com/nilsteampassnet/TeamPass", "base_commit": "6e8ae187df95dd923afaa1fee0ccc5a98e93269d", "reference_commit": "21636b019cd261a1c5e4c8c81c901ef3dee24f39", "task_scoped": "Find and fix issues in TeamPass’ item editor.", "task_specified": "Fix the TeamPass item edit password field: Clearing an item password and saving leaves the old password stored, so reopening the item still shows the previous secret. Clearing the password and saving should persist an empty password so the item no longer reveals the old secret.", "pr": null, "issue": 5220, "workflows": "workflows:\n- id: target-clear-item-password-is-persisted\n category: target\n purpose: 'Editing a saved TeamPass item, clearing its password field, and saving must persist an empty password. On the buggy build the same save keeps the old secret, so reopening the item still reveals it.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official TeamPass login UI is visible: the Teampass logo image (assets/images/teampass-logo2-login.png), the bold Teampass title, a styled login card (not a bare unstyled text shell), the login field (#login), the password field (#pw), and the Log in button (#but_identify_user).\n\n '\n - 'Type exactly nollKerr into the login field. Type exactly Sedge8wick into the password field. Click the Log in button. After login, open the official Passwords/Items page: click the sidebar key icon labeled with the passwords/items entry (data-name=items), or open exactly http://127.0.0.1:13200/index.php?page=items. Wait until the items UI loads: the folder tree, the Lockbox folder, and a New item control (#btn-new-item). Do not stay on Administration/options pages. If login fails or the items page never shows Lockbox and New item, stop and treat that as a setup problem, not a product pass/fail.\n\n '\n - 'Click the Lockbox folder in the tree so it is the current folder. Click New item. Wait until the official item form (#form-item) is visible with the Label field (#form-item-label), the Password field (#form-item-password), and the Save button (#form-item-button-save).\n\n '\n - 'Type exactly Dock Latch into the Label field. Type exactly CedarLatch1 into the Password field. Click Save. Wait until the form finishes saving and the item Dock Latch is visible in the Lockbox item list or item detail. If the item was not created, stop and treat that as a setup problem, not a product pass/fail.\n\n '\n - 'Open Dock Latch for editing (use the item''s Edit / pencil control so #form-item is shown again with Label Dock Latch). Wait until the Password field is present. Clear the Password field completely so it is empty. Click Save. Wait for the save to finish — the form must leave the loading/spinner state. Do not use fetch, XHR, or any API call to save.\n\n '\n - 'Reopen Dock Latch so the item detail is visible again. Reveal the stored password with the official show/unmask control (#card-item-pwd-toggle-button or #item-button-password-show or the visible password text in #card-item-pwd). Final verdict — FAIL only if the revealed item password is still exactly CedarLatch1 (the previous secret was kept) or the save stayed stuck on a loading spinner and the detail view never refreshed. PASS only if the same clear-and-save path leaves the password empty: #card-item-pwd does not show CedarLatch1, and the UI shows an empty password (empty field, hidden password controls, or the official empty-password igloo / \"password is empty\" indicator). Do not PASS merely because login or the item form loaded. Do not FAIL for login/navigation problems. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n- id: preservation-changing-item-password-still-works\n category: preservation\n purpose: 'Changing an item password to a different non-empty value through the official item form must still persist, so normal password updates remain usable while empty-password clearing is broken or fixed.\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/ and wait until the official TeamPass login UI is visible (Teampass logo, login, password, Log in).\n\n '\n - 'If not already signed in, type exactly nollKerr into login and exactly Sedge8wick into password, then click Log in. Open the Passwords/Items page (sidebar key icon or http://127.0.0.1:13200/index.php?page=items). Wait until the items UI and the Lockbox folder are visible.\n\n '\n - 'Click the Lockbox folder. If Yard Key is already in the list, do not create it again. Otherwise click New item. Wait until the item form is visible. Type exactly Yard Key into Label. Type exactly BrineGate2 into Password. Click Save. Wait until Yard Key appears. If Save says This item already exists, open the existing Yard Key instead. Do not clear the password on this item.\n\n '\n - 'Open Yard Key for editing. Change the Password field to exactly OsierGate3 (a different non-empty value). Click Save. Wait until the save finishes.\n\n '\n - 'Reopen Yard Key and reveal the stored password with the official show/unmask control. Final verdict — PASS only if the revealed password is exactly OsierGate3. FAIL if the revealed password is still BrineGate2, is empty, or the edit save never completed. Do not FAIL only because creating Yard Key said This item already exists. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for setup or pass/fail.\n\n '\n"} {"case_id": "sweeper-178", "slug": "thelia", "repo": "https://github.com/thelia/thelia", "base_commit": "b42df895e264ca042b48a26f6e1571b956ac026a", "reference_commit": "6f271172d89be8716c882fac0b661e6c4ca7e789", "task_scoped": "Find and fix issues in Thelia’s product creation and duplication.", "task_specified": "Fix the Thelia admin product clone: cloning a virtual product that has a download file leaves the clone marked virtual without that file association. The clone should keep the virtual flag and point at its own copy of the download file.", "pr": 3691, "issue": 3662, "workflows": "workflows:\n- id: target-virtual-product-clone-keeps-download-file\n category: target\n purpose: 'After signing into the official Thelia admin, opening the seeded virtual product DIG-HANDBK, and cloning it with the official Clone product modal, the clone must still be virtual AND its Virtual document select must point at the clone''s own copied download file. On the buggy build the clone stays virtual but the select stays on \"- No document -\".\n\n '\n steps:\n - 'Open exactly http://127.0.0.1:13200/admin/login and wait until the official Thelia back-office login is fully styled: title Welcome / Welcome back, a Thelia wordmark, Username or e-mail address and Password fields, a Sign-in submit button, and the compiled default-twig CSS (not a bare unstyled form). Do not use fetch/XHR.\n\n '\n - 'Type username `keira.holm` and password `cedarQuilt6!` into the official login form only. Click the Sign-in / login submit button (data-testid login-submit). Wait until you are inside the signed-in admin: the left sidebar shows Catalog / Products, the main area is the Dashboard (or another admin page with the Thelia side nav), and a Logout control is available. You must NOT still be on Welcome back. If login failed, treat this as a setup problem and do not treat it as the clone bug.\n\n '\n - 'From the official left sidebar, open Catalog and click Products. Wait until the Products list is visible (heading / page data-testid products-page, a Search field for Title or reference, and a table of products). Do not open Categories. Do not use fetch/XHR.\n\n '\n - 'Find the seeded virtual product using the official UI only: in the Products Search field type exactly `DIG-HANDBK` and submit Search if needed. Open Digital Handbook / DIG-HANDBK via its title or reference link (or the Edit button). Wait until the official Edit product page is visible: heading Digital Handbook, a Clone product button, a \"Virtual product (no physical shipping)\" checkbox that is CHECKED, and a Virtual document select. Confirm the selected Virtual document is Handbook PDF (not \"- No document -\"). If this source product is not virtual or has no selected download file, that is a setup/seed problem, not the clone bug.\n\n '\n - 'Clone using the official admin only — do NOT type a rewritten URL and do NOT invent a French path: (1) Click the Clone product button (data-testid product-clone-btn). (2) Wait until the Clone product modal is visible (data-testid product-clone-form) with the field \"New product reference (must be unique)\". (3) Type exactly `DIG-HANDBK-CL` into that field. (4) Click the modal''s Clone product submit button (data-testid product-clone-submit). Wait until the Products list is visible again. Find the new row whose reference is DIG-HANDBK-CL (search for that ref if the table is filtered). If clone is rejected with a visible form error, that is a setup/navigation problem, not this bug.\n\n '\n - 'Open DIG-HANDBK-CL with the official Edit control / title link. Wait until the Edit product page for THIS clone is visible: the Reference field is exactly `DIG-HANDBK-CL`, the title is Digital Handbook. Inspect only the General tab Virtual product checkbox and the Virtual document (or the Dropzone instance) — do NOT call /upload or /upload/web via fetch/XHR, and do NOT write the database. A minimal 1x1 PNG base64 payload is: iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8z8BQDwAEhQGAhKmMIQAAAABJRU5ErkJggg== After attaching the file, let Dropzone perform its normal upload to /upload/web and wait until the Dropzone preview finishes (success link, error mark, or settled progress). On the buggy baseline the progress may sit at 100% without a success link — that is expected; still proceed to Home to judge whether the file row was created.'\n - Open http://127.0.0.1:13200/home and wait until the Home media table/list finishes loading.\n - Look in the Home media list for a row whose visible filename is exactly \"quay-note.png\".\n - 'Final verdict (tighten): FAIL only if ALL are true — (1) login and the Upload Dropzone page were reached successfully; (2) the Dropzone upload attempt for quay-note.png was performed through the native UI path; (3) after that attempt, the Home media list does NOT show a row with filename \"quay-note.png\". That missing Home row is the baseline web-upload failure (upload does not persist the media). PASS only if ALL are true — (1) login and Upload were reached; (2) the same Dropzone upload path was used; (3) Home shows a media row whose visible filename is exactly \"quay-note.png\". Do not PASS based only on a Dropzone preview quirk without the Home list row. Do not FAIL for unrelated login/CSS/timeout setup problems — those are setup failures, not a product FAIL on this bug.'\n- id: preservation-login-home-upload-ui-loads\n category: preservation\n purpose: Admin login and the Home/Upload pages must keep loading with the real XBackBone navbar and Dropzone UI.\n steps:\n - Open http://127.0.0.1:13200/login\n - Wait until the styled XBackBone login form is visible (Bootstrap, favicon/branded page — not a bare text shell).\n - Log in with username \"ElenaVoss\" and password \"harborUp7!\". Wait until the authenticated navbar shows Home and Upload.\n - Open http://127.0.0.1:13200/home. Confirm the Home dashboard/media page loads with the navbar (Home/Upload) and no Slim Application Error page.\n - Open http://127.0.0.1:13200/upload. Confirm the Upload page shows the Dropzone area with text like \"Click or drop your files here to upload.\" and Bootstrap styling.\n - 'Final verdict (tighten): PASS only if ALL are true — (1) login succeeded into the authenticated navbar; (2) Home loaded as the media dashboard (not a login form and not a Slim Application Error page); (3) Upload shows the Dropzone upload UI text. FAIL only if login succeeded but Home or Upload clearly fails to render that product UI (for example Slim Application Error, missing Dropzone, or forced logout on those pages). Do not FAIL for unrelated cosmetic differences or empty media lists.'\n"} {"case_id": "sweeper-198", "slug": "yourls", "repo": "https://github.com/YOURLS/YOURLS", "base_commit": "9bd75f1d69c1ed704144129f61df97a44fb505bd", "reference_commit": "65655a5c7ba031be611045bb04c9b3a99bbdf170", "task_scoped": "Find and fix issues in YOURLS’ short-link list management.", "task_specified": "Fix YOURLS admin short-URL listing: An empty click-threshold field hides links with zero clicks. Zero-click short URLs should remain visible when click_limit is empty.", "pr": 3589, "issue": 3657, "workflows": "workflows:\n- id: target-empty-click-limit-keeps-zero-click-links\n category: target\n purpose: An empty admin click-threshold field must not hide short URLs that have zero clicks.\n steps:\n - Open http://127.0.0.1:13200/admin/ and wait until the YOURLS login page is visible with the YOURLS logo image, styled login form, Username and Password fields (not a bare unstyled text shell).\n - Sign in with username rowan-phelps and password quietBay17!. Include the login form nonce if present. Wait until login succeeds and the signed-in admin dashboard is visible (Hello rowan-phelps / Logout and the short URL table).\n - Open exactly http://127.0.0.1:13200/admin/?click_limit= and wait until the admin short-URL table finishes loading.\n - In that table, check whether the seeded zero-click short URLs with keywords ozh and yourls are listed, and whether the non-zero-click keyword yourlsblog is listed.\n - Final verdict — FAIL only if yourlsblog is visible in the table AND at least one of the zero-click keywords ozh or yourls is clearly missing from the table, proving empty click_limit was treated as a \"more than 0 clicks\" filter.\n - Final verdict — PASS only if ozh, yourls, and yourlsblog are all clearly visible in the short-URL table on that empty click_limit page.\n - Do not FAIL for login/setup/network problems. Do not PASS unless the empty click_limit admin table itself shows the zero-click keywords.\n- id: preservation-more-than-one-click-filter-still-works\n category: preservation\n purpose: An explicit \"more than 1 click\" filter must still show clicked links and hide zero-click links.\n steps:\n - Open http://127.0.0.1:13200/admin/ and wait until the YOURLS login page or signed-in admin UI is visible.\n - If not signed in, sign in with username rowan-phelps and password quietBay17! (include nonce if present) and wait until the admin dashboard is available.\n - Open exactly http://127.0.0.1:13200/admin/?click_limit=1&click_filter=more and wait until the admin short-URL table finishes loading.\n - Final verdict — PASS only if keyword yourlsblog is clearly visible in the table AND both zero-click keywords ozh and yourls are clearly absent from that filtered table.\n - Final verdict — FAIL if yourlsblog is missing, or if ozh or yourls still appears under the more-than-1 filter.\n"} {"case_id": "sweeper-199", "slug": "zencart", "repo": "https://github.com/zencart/zencart", "base_commit": "0e6664dd9e3e0c6a565c8d38cec058d5ce566fd3", "reference_commit": "558bb6b1c0e74028998aac4fa558acfaae93897f", "task_scoped": "Find and fix issues in Zen Cart’s EZ-Pages administration.", "task_specified": "Fix Zen Cart EZ-Pages status toggle: clicking a Header status square should set that flag OFF and show the OFF icon, not die with Table 'zencart.status_header' does not exist.", "pr": 7743, "issue": null, "workflows": "workflows:\n- id: target-ezpages-header-status-toggle\n category: target\n purpose: Toggling the Header status square on demo EZ-Page \"EZPages\" must persist via zen_set_ezpage_status. With reversed field_exists(table,field) args the admin fatals on SHOW FIELDS FROM status_header (systemError / Table zencart.status_header doesn't exist) and the Header icon stays ON. After the fix, the same toggle redirects back to EZ-Pages and the Header icon for EZPages is OFF (txt-status-off).\n steps:\n - Open exactly http://127.0.0.1:13200/admin/login.php and wait until the Zen Cart Admin Login screen is visible (title or heading Admin Login, username/password fields).\n - Type exactly tamsin-reed into the admin username field and loom-wick9 into the password field. Wait at least two seconds, then click the login submit button.\n - Confirm you are signed into the Zen Cart admin backend (leave the login form; admin chrome such as sidebar/menu or dashboard is visible). If any dismissible notice appears, close it and continue.\n - Open exactly http://127.0.0.1:13200/admin/ezpages.php and wait until the EZ-Pages admin list is visible with a table of pages including a row titled EZPages.\n - On the EZPages row, locate the Header status column (sort order near 10 plus a colored square status button). Confirm that Header status currently shows ON (green/on square with class txt-status-on or title indicating status on).\n - 'IMPORTANT: Click the Header status square/button itself for the EZPages row (the submit control inside the Header status form), not the EZPages title text and not other status columns (Sidebox/Footer/Visible). Prefer the button click; if the row navigation steals the click, submit that same Header status form for ezID 1 / fieldName status_header using page context (same form the button would submit).'\n - Observe the result page after that Header toggle. Either (A) a fatal admin error page / systemError mentioning Table 'zencart.status_header' doesn't exist or SHOW FIELDS FROM status_header, with HTTP error styling, or (B) you return to the EZ-Pages list where the EZPages row Header status is now OFF (txt-status-off / status-off square).\n - Final verdict — PASS only if (a) you reached the EZ-Pages list while signed in, AND (b) after the Header toggle for EZPages the list is shown again and that row's Header status is visibly OFF. FAIL only if (a) is true and the Header toggle produces the systemError / missing table status_header / SHOW FIELDS FROM status_header fatal page (or the Header icon remains ON with no successful toggle). Do not FAIL for login/setup problems; use uncertain only if login or the EZPages Header control cannot be observed after retries. Do not use fetch, XHR, DevTools Network, API JSON, or database reads for pass/fail.\n- id: preservation-ezpages-list-loads\n category: preservation\n purpose: Opening the EZ-Pages admin list without toggling status must still show demo page titles (adjacent Tools → EZ-Pages path unaffected).\n steps:\n - Open exactly http://127.0.0.1:13200/admin/login.php and wait until the Admin Login screen is visible.\n - Type exactly tamsin-reed into the username field and loom-wick9 into the password field. Wait at least two seconds, then click login.\n - Confirm you are signed into the admin backend. Dismiss any notice if present.\n - Open exactly http://127.0.0.1:13200/admin/ezpages.php. Do NOT click any status square/toggle buttons.\n - Final verdict — PASS only if signed into admin and the EZ-Pages list visibly shows demo page titles including EZPages and Shared without a systemError / missing-table fatal. FAIL if signed in but the EZ-Pages list is blank or shows a fatal database/systemError page. Do not FAIL for login/setup problems; use uncertain only if the EZ-Pages list cannot be reached after retries. Do not use fetch/XHR/API/database reads for this judgment.\n"} {"case_id": "sweeper-200", "slug": "zenphoto", "repo": "https://github.com/zenphoto/zenphoto", "base_commit": "841e482c646ae017c0e7df1bce91afd82f5df21a", "reference_commit": "aeb481a81a6d5e4e935832aa1021db4bb834e01e", "task_scoped": "Find and fix issues in Zenphoto’s image commenting workflow.", "task_specified": "Fix Zenphoto image comment text quiz validation: guest comments with a wrong text-quiz answer are still accepted and shown on the image page. Wrong quiz answers should be rejected with a visible quiz error and the comment must not appear in the published list.", "pr": 1462, "issue": null, "workflows": "workflows:\n- id: comment-text-quiz-rejects-wrong-answer\n category: target\n purpose: 'Guest image comments with a wrong text-quiz answer must be rejected with a visible quiz error and must not appear in the published comment list.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/\n - Wait until the gallery page loads with Zenphoto styling (not a bare unstyled page) and a visible Coastal Frames album link or Coastal Frames album entry.\n - Open the Coastal Frames album, then open the Blue Hour image page so the image comment form is visible.\n - 'Confirm the visible comment form fields under \"Add a comment:\": the text quiz question \"What color is the sky?\" with an answer input (name comment_textquiz), a comment textarea (name comment), and an \"Add Comment\" submit control.\n\n '\n - 'Fill the comment form as a guest (do not log in as admin): Comment body = Wrong quiz should be rejected uniquely; Text quiz answer = red (intentionally wrong; the seeded correct answer is blue). Name and E-Mail are required unless you tick the visible (anonymous) box. Tick that box or fill both fields so the browser will actually submit.\n\n '\n - 'Submit with a normal UI click on the \"Add Comment\" submit control, not the \"Add a comment:\" heading. If the comment and quiz fields are still filled after the click and the comment list did not change, the form did not send. Complete Name/E-Mail or (anonymous), then click submit again. Do not treat a blocked browser submit as a product fail.\n\n '\n - Wait for the page to finish handling the submission (reload or in-place update).\n - 'Final verdict — FAIL only if ALL of the following bug-specific evidence are true on this Blue Hour image page after submit: (1) there is NO visible error about the correct text quiz answer / quiz failure for this submission; AND (2) the published comments area shows the new comment body \"Wrong quiz should be rejected uniquely\" as an accepted comment. PASS only if ALL of the following fix-specific evidence are true: (1) a visible error box/list mentions the correct text quiz answer (or equivalent quiz failure text); AND (2) the published comments area does NOT show \"Wrong quiz should be rejected uniquely\" as an accepted comment (empty comments or only unrelated prior comments is fine). If the gallery/image/comment form cannot be reached, or the quiz field is missing, do not invent a product pass/fail — treat as setup/navigation failure rather than a product PASS.\n\n '\n- id: comment-text-quiz-accepts-correct-answer\n category: preservation\n purpose: 'Guest image comments with the correct text-quiz answer must still be accepted and shown in the published comment list.\n\n '\n steps:\n - Navigate to http://127.0.0.1:13200/\n - Wait until the gallery page loads with Zenphoto styling and a visible Coastal Frames album entry.\n - 'Open the Coastal Frames album, then open the Blue Hour image page so the image comment form is visible with the quiz question \"What color is the sky?\", a comment textarea, and \"Add Comment\".\n\n '\n - 'Fill the comment form as a guest (do not log in as admin): Comment body = Correct quiz should be accepted uniquely; Text quiz answer = blue (the seeded correct answer). Name and E-Mail are required unless you tick the visible (anonymous) box. Tick that box or fill both fields so the browser will actually submit.\n\n '\n - 'Submit with a normal UI click on the \"Add Comment\" submit control, not the \"Add a comment:\" heading. If the comment and quiz fields are still filled after the click and the comment list did not change, the form did not send. Complete Name/E-Mail or (anonymous), then click submit again. Do not treat a blocked browser submit as a product fail.\n\n '\n - Wait for the page to finish handling the submission.\n - 'Final verdict — PASS only if the Blue Hour image page shows the new published comment with body containing \"Correct quiz should be accepted uniquely\", and there is no blocking quiz-error that prevented this correct submission. FAIL if that correct-answer comment is missing from the published comments after submit, or if a text-quiz error is shown despite answering blue. If the gallery/image/comment form cannot be reached, treat as setup/navigation failure rather than a product PASS.\n\n '\n"}