kit-pr-workflow-boundary
Kit-PR Workflow Boundary — Consumer ≠ Kit Maintainer Shell
Section titled “Kit-PR Workflow Boundary — Consumer ≠ Kit Maintainer Shell”Inside a consumer project you MUST NOT propose, offer, or perform on a kit PR: gh pr merge without --auto on any theonekit-* PR · resolving conflicts on, force-pushing to, or rewriting history of a theonekit-* PR branch you did not open this session · watching or acting on a theonekit-* PR you did not open this session (/t1k:babysit-pr on someone else’s) · asking “want me to babysit/merge/watch the kit PR?” for a PR opened outside this session. That belongs to the kit maintainer session (a theonekit-* clone: its origin matches theonekit- → you ARE the maintainer, the boundary does not apply). A PR you did NOT open → cd into the kit clone.
Carve-out — your OWN just-opened PR, watched by the run that opened it
Section titled “Carve-out — your OWN just-opened PR, watched by the run that opened it”A background /t1k:sync-back sub-agent opens its PR, arms gh pr merge --auto and watches that SAME PR to merged, fixing a red check on its own diff. Without a required_status_checks gate --auto merges at once: gate the merge on an observed green. Line = ownership + method: own just-opened PR + --auto = yes; hand-merge or someone else’s PR = no.
Full detail: docs/kit-pr-workflow-boundary.md.