Aliases: compiler feedback; tests; assertions; verification; workflow; release cadence; lint; project policy.
Use compiler feedback where it exposes an inadmissible composition; do not widen a bound merely to silence it. Use relevant observations for actual behavior, external effects and runtime uncertainty. A failed negative example must fail for its intended boundary, with a working valid use in the same environment.
Ask what requirement gives an assertion authority. Independent expected behavior matters when implementation and test could repeat the same mistake. Tests of a discarded private helper need not preserve that helper forever; public compatibility and legitimate behavior remain real commitments.
The project defines its development and release sequence, configurations and acceptance evidence. This doctrine shapes what those checks should protect; it does not prescribe a universal first command, test count or release gate. Report unexecuted work honestly. More tests, lints or prose cannot repair an unreadable or wrongly owned story. Human learning exercises are judged by the designated human reviewer, not an automated course verifier.
Your Reflection
Notes are browser-local. Export a copy to keep them; they are not submitted or judged.