badness

Use when the user wants to (re)run the formatter/linter speed benchmark or refresh the docs benchmark page — "run the benchmark", "task bench", "update the benchmark numbers", "refresh benchmarks". Regenerates the committed JSON artifact that feeds docs/src/reference/benchmarks.md, then fact-checks that page against the code.

Profile-driven performance work on the badness parser, formatter, or linter. Measure first with the in-process micro-bench + perf/flamegraph on a real document; classify hotspots into a small set of buckets; apply the matching cheap fix; verify the median wall-time moved AND the invariants still hold before committing. Use for "speed up formatting/parsing/linting", "close the gap with tex-fmt on <doc>", "profile the formatter/parser/linter", "why is masters_dissertation slow".

Add a new built-in lint rule to the Badness LaTeX linter — implement the Rule trait (id/severity/description/examples + check), register it in the three lockstep lists, add unit + integration tests with a losslessness-safe fix, and regenerate the living-docs rules reference. Use when asked to add a lint (warning/error/info), with or without an auto-fix.

Use when the user wants to check or analyze badness's LaTeX parse concordance against texlab — "run parse-compat", "parse concordance vs texlab", "analyze parse-compat divergences", or after a parser/CST change that might shift the differential gauge. Runs the soft gauge and triages any unexplained divergence.

Use when the user wants to check or analyze badness's BibTeX parse concordance against texlab — "run bib-parse-compat", "bib parse concordance vs texlab", "analyze bib divergences", or after a `.bib` parser/CST change. Runs the soft gauge and triages any unexplained divergence.