feat(verify): add laptop and monitor domain scoring - #102
Merged
Merged
Conversation
Seungpyo1007
force-pushed
the
feat/laptop-monitor-scoring
branch
from
September 26, 2026 20:41
aa7d64a to
50937b3
Compare
This was referenced Sep 26, 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
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.
Laptop and monitor records now have domain completeness and plausibility rules, so consistent records with T1/T2 sources use the normal 100-point scale and can reach green. Impossible measurements force red; soft ranges cover the observed laptop configurations, touch monitors and signage displays.
Validation: mypy app and ruff check app tests pass; full pytest suite 445 passed and targeted scoring/boundary suite 30 passed. Local status: laptop 107 green / 1888 yellow / 0 red; monitor 0 green / 882 yellow / 0 red. Only one monitor size outlier is flagged (a monitor-arm accessory), with no hard flags.
Refs #98
Refs GetTechAPI/TechAPI#297