What have we verified, how strong is that verification, and what is left · TIG sandbox
Coverage at a glance
Role × module matrix
Click any cell for its case list. A grey dashed cell means nobody has verified it yet — that is a gap with no owner, which is a different problem from a red cell, which is a defect with an issue link.
functional-cases.json next to this page — one small block per case, edited by hand and
reviewed as a pull request like any other change. Each block names the role, the module, and the user task it
proves in plain language (never a file name or a test function). After executing a case, set
last_result to "pass" or "fail", set last_run to the date, and
link the GitHub issue in defect if it failed. The README.md in this folder walks through
it field by field. If the file has a mistake, this page names the exact case and field rather than going blank.
Mutation trend — the headline
Kill rate is the share of deliberate code changes the suite catches. It is the only measure here that distinguishes a test that would catch a regression from one that merely executes the line. The floor may not go down.
Suite composition
Flake state
Drift indicators