contributinglisted

# contributing Everything that leaves the machine under the user's name goes through one gate, in their own repositories as much as in anyone else's, and everything sent to another project is preceded by reading how that project wants to be approached. [`contrib.sh`](contrib.sh) beside this file is the mechanical half. It is not on the PATH, so run it by its path, and its help is the reference: read `contrib.sh help` before an unfamiliar command rather than guessing one from this page ## The gate Never push, open, edit, close, reopen or merge an issue or a pull request, submit a review, post a comment or a discussion, or perform any other externally visible action under the user's identity without their explicit approval immediately before that action, unless a standing permission below covers exactly that action on exactly that repository 1. Draft it: `contrib.sh draft KIND …` stores the payload and prints its card — the destination, the metadata, the exact text, the commits, the files or the diff, the warnings, and an approval hash 2. Show the whole card, and ask the user to review it personally. A tool's output, a passing test or another agent's review is no substitute for their own reading 3. Wait for an unambiguous approval of that card. A request made earlier in the task is not the approval 4. `contrib.sh send ID --approved HASH` publishes exactly the stored bytes - **One card, one approval, one send.** Approvals are never batched, and `send` takes one draft - **On