Quality Score

Define what good looks like for this repo. Include fast checks, slow checks, evals, and known blind spots.

Use these principles:

Make code legible to agents with semantic names and explicit boundaries.
Prefer small, testable modules over files that require broad context to edit.
Enforce style, architecture, and reliability rules mechanically where possible.
Keep a cleanup loop for stale docs, generated artifacts, and accumulated implementation debt.