staging-to-production

staging-to-production prepares the owner's production promotion and stops there: it reads branch and CI state from GitHub and prints the commands, but performs no write anywhere. Production promotion belongs to the owner, so the output is a readiness table and a command list, never an action.

Inputs

• Projects — the rows of the workspace Project Matrix (rules/projects.md, or inline in an older AGENTS.md), or the repos the user names. No matrix and no names → stop and ask.
• Staging branch — default staging, unless the user or workspace AGENTS.md names another. Repos without it on origin are listed as skipped.
• Production branch — from the user or workspace AGENTS.md; otherwise the repo's default branch from gh repo view <owner/repo> --json defaultBranchRef. Confirm it with git ls-remote --heads origin <branch>. When a branch named production or prod also exists and differs from the default, stop for that repo and ask which one is production.
• Merge method — merge commit, for the same long-lived-branch reason as /local-to-staging; a repo that disallows merge commits gets its allowed method in the printed command, with a note that staging and production will diverge.

Rules