feedback creatortrack console main never direct commit 20260715T142037

---

name: Console's creatortrack main folder must stay a pure GitHub mirror, never hand-committed description: Rule established with Justin: Console's ~/creatortrack main is both prod source and deploy source; never commit directly there, always branch/worktree -> push -> PR -> merge -> pull -> deploy. type: feedback

---

Established during a session where Claude had committed directly to Console's ~/creatortrack main (dev-scoped AGENTS.md edit), which Codex later had to reroute into a branch/PR to avoid divergence from GitHub. Justin then independently identified the divergence risk (Console main growing local commits while GitHub main also advances via merged PRs) as the core danger.

Why: ~/creatortrack on Console is simultaneously the deploy source (forge_creatortrack_deploy.sh builds directly from this folder) and the git working copy tracking origin on GitHub. If it ever grows commits GitHub doesn't have, a later pull/merge can produce conflicts, and the deploy script's FAIL: main is dirty / FAIL: not on main guardrails get triggered.

How to apply: Never commit directly to ~/creatortrack main on Console (even small doc-only edits). Always do work in a separate worktree (e.g. ~/creatortrack-wt/<feature>), push, open a PR, merge on GitHub, then git pull in ~/creatortrack before running the deploy script. This complements [[reference_creatortrack_parallel_dev]] (commit often, merge once) and [[reference_codex_workspace_write_git_readonly]].

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