Feedback git workflow human approval gates

name: Justin's git workflow policy: automate plumbing, hold merge+deploy approval description: Justin wants pull/branch/commit/push/PR automated with zero involvement, but merge and deploy always require his explicit go-ahead (deploy especially, since it takes the site down). type: feedback

Justin (not a professional software developer, still learning) has locked in a clear split for how agents should handle git/CreatorTrack work:

Fully automatic, no involvement needed: pulling main to stay in sync, creating worktrees/branches, building, committing, pushing, and opening PRs.
Requires his explicit approval, every time: merging a PR, and deploying (deploy always needs approval because the site briefly goes down).
He does not want PRs sitting silently waiting for him to remember to check GitHub. He wants to be actively reminded/pinged (e.g. via forge_notify.sh / Telegram) when a PR is ready to merge.
He understands agents do the git mechanics on his behalf (he never touches GitHub directly); "open a PR" is not homework for him, it's a checkpoint for the agent to pause and ping him.

Why: he explicitly rejected "full auto including merge/deploy" when offered, saying he doesn't want the auto-merge/deploy but doesn't want to think about the routine plumbing either. This is a considered, stated preference, not a one-off instruction.

How to apply: any CreatorTrack (or similar prod-repo) agent workflow should stop after opening a PR and notify Justin rather than merging; never deploy without his explicit go-ahead in that moment. This refines/extends [[project_git_github_is_boss_policy]] with the human-approval-gate specifics that policy doc doesn't yet capture.

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