# Repository examples: checks that protect the intended result

- **T3 custom lint:** [PR #7209](https://github.com/pingdotgg/t3code/pull/7209) adds a narrow tooltip rule with fixtures and config integration. At the inspected commit, the [rule](https://github.com/pingdotgg/t3code/blob/6c583620ff7ad3235b135af7107c0543467eecfa/oxlint-plugin-t3code/rules/no-native-title-tooltip.ts) handles direct intrinsic JSX attributes with specific exceptions; it is not a proof against every tooltip route. [PR #9300](https://github.com/pingdotgg/t3code/pull/9300) illustrates maintenance of suppressions and baseline allowances.
- **Melee completeness:** the [initial verifier](https://github.com/doldecomp/melee/commit/035d9711623a32fbe891cffdcf44a91a550c1947) checked build/diff success and a reference hash. A [follow-up](https://github.com/t3dotgg/melee4mac/commit/74e73873038b821bbc46b0a18434e6b7cb556c0e) also rejects incomplete source reports. We reproduced the initial false acceptance and later rejection using synthetic bytes and mocked commands; no game build was run.
- **Boris's compiler:** the [CI workflow](https://github.com/bcherny/json-schema-to-typescript/blob/5caacfc53671f9c891bb4e2a78bccc6190ed3ef4/.github/workflows/ci.yml) layers platform/runtime checks, seeded fuzzing and generated-output validation. Its aggregate `ci-ok` expression omits two dependencies, so inspect required checks instead of trusting the aggregate name. We read this source; we did not run its compiler suite.

Choose the invariant appropriate to the product. Exact bytes suit matching decompilation; they are not a universal acceptance condition for renderers, refactors or generated code.