WordPress to Astro: Git Is the Undo Button

Put the work in git. Put the diary in git. Preview before it is live. That is how a team of models ships like a team of people.

Git is the undo button because the site is a folder of files. Agent notes are how Claude, Cursor, Codex, Gemini, and Grok see the last job and pick up the next one. That is Learn, Do, Teach on a multi-model desk: we run the method, we keep the receipts, we publish the working copy.

How an agent QAs and then writes the note: How Agents QA a Partner Local Audit (and Write It to GitHub). The memory layer under it: How I Built Shared AI Memory Without Lock-In. Execution: If You Can Do It, You Should.

What the four days look like

We stood the notes folder up on 17 Aug 2026. Counted on this Mac, 20 Aug:

By day: 28 on the 17th, 146 on the 18th, 47 on the 19th, then the 20th still writing. 217 of the 294 commits landed after the folder existed. The git author is often my name, because agents commit as me. The model lives in the filename on purpose: YYYY-MM-DD-cursor-grok-slug.md. That is how you ask “what did that model do last night?” and get an answer.

Those notes are not one kind of job. Audits, Gmail threads, WordPress publishes, Descript tapes, AWS host checks, speaker-kit pages, overnight queues. Same sections every time. Next agent reads the three newest files, then writes the fourth.

Astro is the factory. Git is the shelf.

Astro takes Markdown, YAML, images, and a few components and emits HTML. Nothing named Astro has to run in the browser. Content collections fail the build if a required field is missing. That is the contract a page-builder cannot give you.

Hosting can be Amplify, Cloudflare, or any shelf that serves a folder. The rollback package is the last good dist/ zip plus the commit that built it. One repo per site so a client can leave with a clone, not a paid extraction.

WordPress to Astro, in order

Do not cut DNS because the preview looks pretty. Cut DNS when the new site matches the crawl, the leads still arrive, and you can restore last night’s zip.

1. Owner and intent. Domain, registrar, DNS, Search Console, forms. Who signs cutover.
2. Baseline. Crawl every URL. Screenshot desktop and mobile. Write down where a lead goes. That crawl is the test.
3. Export as files. Pages and posts to Markdown. NAP and offers to YAML. Redirects to CSV. Map each plugin to an outcome. Do not copy PHP.
4. Pin the factory. Node, Astro, lockfile. Required fields in collections so a missing canonical fails CI.
5. Preview, then DNS. Technical signature and business signature. TTL and rollback command written. WordPress stays on the team network through the hold, not on the public internet.

A personal-brand homepage is the person’s canvas. New proof is new articles. That is how Dylan Haugen gets tapes onto URLs Google can quote without rebuilding the hero every night. Case: tapes to articles.

Same loop for work that is not a website

If two agents can see the last commit and the last note, they work in tandem. That is the team. Dennis Yu.

Working copy, 20 Aug 2026. Counts from the live notes clone that morning. Skill packs: github.com/dennisyu/local-service-spotlight-skills.