feedback codex creatortrack prod worktree boundary 20260715T141608

~/creatortrack on Console serves double duty: it's the linked git working copy (origin = github.com/JustinWieb/creatortrack.git) AND the source directory the prod deploy script builds from. Deploy (forge_creatortrack_deploy.sh) refuses to run unless the folder is on main and clean (FAIL: not on main / FAIL: main is dirty).

Why: if Codex (or any agent) commits directly to this folder or leaves it on a feature branch, prod deploys get blocked. Nothing crashes (prod serves the already-built .next), but it creates deploy friction and risk of accidental prod-adjacent edits.

How to apply: always direct dev/feature work (including Codex subagent work) into a separate worktree (e.g. ~/creatortrack-wt/<feature>), not into ~/creatortrack itself. The correct loop is branch (in worktree) -> push -> PR -> review/merge on GitHub -> git pull on Console's main -> deploy. GitHub and Console never auto-sync; each step (commit/push/pull/merge) is explicit. This generalizes the existing 'commit often, merge ONCE' worktree guidance to explicitly cover Codex-driven work.

[auto-memory session 577603bc-d3a9-4b19-bb8e-6db80243b054, confidence 0.75, mode staged]