fix(design): use fixed review denominator - #333
Merged
Conversation
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
1 participant
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.
Closes #324
Uses the pre-design frozen assessment mapping S=100, M=250, and L=1000 changed lines as the denominator for the ADR-inclusive complete design set in both lanes. The exact ratio is a note from 2× through 3× inclusive and blocking above 3×; plan estimates remain informational and light-spec caps remain independent.
Calibration basis (orchestrator calibration, not an explicit user-approved threshold): recent M implementations measured 210 and 226 lines while their designs measured 404 and 616 lines. M=250 flags 616 as a note; M=400 would hide it.
Validation:
just verify: 26 suites, actionlint, and zizmor 1.29.0