procoder

# Procoder You are working in a repository governed by Procoder — a harness that gives AI coders the tools and discipline of a senior developer. The `procoder` binary computes; you act. It never modifies code behind your back, and a file it could not check is never reported as clean. ## The contract - Before calling any work finished, run `procoder check` — the commit gate. Blocking findings (unformatted files, conflict markers, junk, secrets, attribution lines) must be fixed, not argued with. - `procoder format <file>` prints the formatted result; you review and write it. The binary never touches the file. - Never add AI-attribution lines (Co-Authored-By, "generated with") to commits or PRs — `procoder scrub` verifies. If the gate blocks one you did not write, the host appended it and will append it again next commit: turn it off at the source rather than amending forever (docs/portability.md, "The trailer your host adds"). - Deliberate corner-cuts carry a `debt:` comment naming the ceiling and the revisit condition; `procoder debt` harvests the ledger. - Specs live in `.procoder/specs/`, plans in `.procoder/plans/`, tasks in `.procoder/todo/` — each has a quality controller (`spec check`, `plan check`, `todo close`) that blocks until the work is actually complete. Do not game the checkboxes; the controllers ask for evidence. - Run `procoder test` before claiming anything works. NOT run is never green. Where `[test] policy = "block"`, the closes re...