re0-merge

1Land a contribution fairly: credit preserved, the maintainer's changes legible, accepted on the record.
2 
3## Goal
4 
5A review must respect the contribution and its permanent carrying cost. `re0-merge` guides any collaborator or maintainer, not just the author, through judging a pull request against the suite's thesis, landing it by the smallest of three outcomes it needs (as it is, with follow-up commits on its own branch, or carried into a new PR), preserving contributor authorship, keeping maintainer edits in separate commits, and closing with approval and credit.
6 
7## Workflow
8 
91. **Gate before landing.** Decline additions by default: the addition must show the suite is worse without it. Judge each PR alone, never as a batch. A bug-fix removes a defect and is the easy yes; tooling earns a place only if it mechanizes a rule already enforced by hand; a new skill must close a real gap no existing skill covers. A well-reasoned decline is a completed outcome.
102. **Cold-read it first.** Before deciding, read the entire contribution as a stranger would, calling the Skill tool with "shower" when it is installed. A name or claim clear to its author may confuse another reader.
113. **Verify, do not re-fix.** Where the author already pushed a fix, prove it with a throwaway regression case rather than rewriting it; the credit for the fix is theirs.
12…