Migrated project from prototype.baileyengineers.com\ to baileyengineers.com\

What was done

• Copied source files (509 files / 475 MB) from C:\Users\RyanB\OneDrive\Websites\prototype.baileyengineers.com\ to C:\Users\RyanB\OneDrive\Websites\baileyengineers.com\ via robocopy /E excluding node_modules, .astro, pagefind (public/pagefind), dist, .lighthouseci. All four of those regenerate from npm install + npm run dev / npm run build.
• Preserved existing target content — the destination had only .backup\26_04_26\ (the old static-HTML baileyengineers.com snapshot from 2026-04-26). Robocopy left it untouched.
• Copied Claude auto-memory (65 files / 43 MB) from ~\.claude\projects\c--Users-RyanB-OneDrive-Websites-prototype-baileyengineers-com\ to ~\.claude\projects\c--Users-RyanB-OneDrive-Websites-baileyengineers-com\ so the next bot starts with full context (user profile, project-scope guidance, hosting reference, calibration notes, etc.). Windows case-insensitive paths mean either capitalization resolves to the same store.
• Updated CLAUDE.md H1 from “Bailey Engineering — Prototype Site” to “Bailey Engineering — Live Site” and added a migration banner at the top.
• Did not modify the old prototype directory. It remains intact at the original path as a backup.

Why

User initiated migration after restarting their computer. Asked to ensure “nothing context-wise is lost for the next bot.” The previous working directory name (prototype.*) was historical — Bailey is past the prototype stage and the project now drives the live baileyengineers.com deploy at 64.23.133.232 (per memory reference_production_hosting.md).

What the next bot needs to know

• You are at the canonical project root (C:\Users\RyanB\OneDrive\Websites\baileyengineers.com\). The old prototype.baileyengineers.com\ dir is a backup — do not edit it.
• Run npm install before npm run dev — node_modules was deliberately not copied (OneDrive copies of node_modules are slow and often corrupt per repeated experience).
• The previous dev server (port 4321) may still be running from the OLD path. Kill it before starting one from this dir (or it will refuse to bind 4321). On Windows: find the node.exe process bound to 4321 and stop it, or just close the terminal that started it.
• The auto-memory is here at the new project key. If you don’t see your usual memories appear at session start, check that Claude Code resolved the new path correctly — both C--Users-... and c--Users-... (case) directories exist under ~\.claude\projects\. Memory files include 14+ entries covering user profile, hosting, scope guidance, KPI calibration. Index lives in MEMORY.md.
• The .tmp/ folder came along per user instruction (SEO plan handoff at .tmp/seo/00_HANDOFF.md, stub-enrichment drafts at .tmp/stub-enrichment-drafts/). Per memory, those drafts ride with the quarterly refresh and stay until live-prototype signoff.
• astro.config.mjs already uses site: 'https://baileyengineers.com' — no URL changes were needed in source.

Files affected

Created

• C:\Users\RyanB\OneDrive\Websites\baileyengineers.com\ (new canonical root with 509 copied files)
• C:\Users\RyanB\.claude\projects\c--Users-RyanB-OneDrive-Websites-baileyengineers-com\ (auto-memory copy, 65 files)
• src\content\devlog\2026-05-11-migrated-to-baileyengineers-com-directory.md (this entry)

Modified (in the new dir only — original prototype CLAUDE.md untouched)

• CLAUDE.md — H1 updated, migration banner added

Untouched

• C:\Users\RyanB\OneDrive\Websites\baileyengineers.com\.backup\26_04_26\ (old static-HTML site snapshot)
• C:\Users\RyanB\OneDrive\Websites\prototype.baileyengineers.com\ (entire prototype directory remains as backup)