user creatortrack ship git flow verbs 20260715T144745

Justin explicitly said: 'I am not a software developer by trade and am still learning. All handwritten coding is done by you.' He walked through the full pull -> branch -> build -> commit -> push -> PR -> merge -> pull -> deploy loop and got it conceptually right but needed verb corrections (clone happens once ever, not every time; pull != deploy, they're two separate steps). Critically, he pushed back hard on any workflow that 'creates a job for me to do' on GitHub itself, he does not want to click merge buttons or review PRs on github.com. His stated preference: full auto (agent pulls, builds in worktree, opens PR, triggers automated review, merges, pulls, deploys, all itself) with an optional second-agent review step as a safety net, rather than a human-checkpoint pause.

Why: This shapes how any future git/GitHub-workflow-related AGENTS.md or CLAUDE.md rules should be written for CreatorTrack and other repos, they should default to full-auto merge/deploy by the agent, not 'open PR and wait for Justin.'

How to apply: When writing or updating git workflow rules (in CreatorTrack AGENTS.md, forge CLAUDE.md, or elsewhere), default to agent-does-everything-including-merge, with an optional automated review agent, not human-review-gate-on-GitHub. When explaining git concepts to Justin, keep using plain analogies (vault master, desk copy, printed shelves) and correct verb precision (clone vs pull, pull vs deploy) since he's actively building this model.

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