Repository navigation
Conversation
The design said a type checker and a linter are required checks. The decision record on the authors' context says there is none, because each is an install and the required check runs only what is in the commit. The Maintainer ruled on 2026-10-11 that the decision record stands. The design's two lines now agree with it. What is given up, and accepted: types and style caught by standard tools. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 54 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
CodeAnt PR Risk: Medium Risk
Assessed commit: |
The org was renamed to combsmith; GitHub Actions does not redirect uses: after a rename. Same rewrite as the org cutover, nothing else. This branch still conflicts with main for reasons unrelated to the rename.
Restores every other file to this branch's previous content, so the PR diff stays this PR's own change; its petry-projects references stay rewritten to combsmith.
Restores every other file to this branch's previous content, so the PR diff stays this PR's own change; its petry-projects references stay rewritten to combsmith.
|
|
|
Superseded: the ruling is already on |



What this is
The Maintainer's ruling of 2026-10-11, written into the design: the required check installs nothing, so no formatter, linter or type checker is a required check.
The design said "a type checker and a linter are required checks" (§9.12). Decision record 0014, on the pull request "Context for the Factory's authors: lessons, standards, decisions and the checks that hold them", says there is none, because each is an install and the required check runs only what is in the commit. The ruling is that 0014 stands.
What changed
lintmeans in this repo.Part of the story "Land the authors' context: lessons, standards, decisions and the checks that hold them". Its other criterion on this ruling, the
lintLens inconfig/defaults.json, is left to that pull request, which already edits the configuration.What is given up, and accepted
Types and style caught by standard tools. The repo's own checks and the mutation check stand in their place.
Verification
make verifypasses. One document.🤖 Generated with Claude Code