🔴 "local" IS READ AND LINTED, NEVER SCORED, and that is a decision with a
measurement behind it rather than a preference. The browser twin reads a
GitHub tree, so it can never see a gitignored file; any design that scored
one would put the CLI and the browser permanently out of agreement about the
same commit, and would make a published grade irreproducible between two
teammates. So the weight carries TWO numbers — committedTotal (what a
teammate or CI sees) and effectiveTotal (what this working copy actually
loads) — and only the first is judged against the budget.
Team instruction (committed) or one machine's?
🔴
"local"IS READ AND LINTED, NEVER SCORED, and that is a decision with a measurement behind it rather than a preference. The browser twin reads a GitHub tree, so it can never see a gitignored file; any design that scored one would put the CLI and the browser permanently out of agreement about the same commit, and would make a published grade irreproducible between two teammates. So the weight carries TWO numbers —committedTotal(what a teammate or CI sees) andeffectiveTotal(what this working copy actually loads) — and only the first is judged against the budget.