docs: raise v1 review budget to 5,200 lines - #62
Merged
Merged
Conversation
This was referenced Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Maintainer authorization now allows the v1 installed-package review budget to increase from
<5000to<5200rather than performing a riskier pre-release refactor solely to recover ~100 lines.This focused policy/enforcement change updates only:
AGENTS.mddocs/developer/api.mdtest_production_size_budgets_are_enforcedThe current
reviewability-v1package measures 4,893 nonblank/noncomment Python lines with the same recursive counter. The previously simulated combined v1 stack measured ~5,102, leaving ~98 lines of headroom under the authorized cap.Local verification:
git diff --checkThe full repository test suite is delegated to PR CI because the local system Python lacks the pinned test-only
bip32/coincurveoracle dependencies.This supersedes issue #61's earlier no-budget-increase condition following explicit maintainer authorization.
Closes #61