LEDGERMACHINE

LM-DRIFT-002

Detect CSS regressions that return after repair

A finding previously verified as repaired appears again in a later scan.

What Ledgermachine reports

A repaired issue has returned

Decision, not automatic repair

Restore the repair, or record that the product decision changed. Regression status is ledger evidence, not guesswork.

Source example

What this finding can look like

The exact candidate comes from the project’s own tokens and repeated values. This example shows the shape of the issue, not a universal replacement.

Flagged source
/* The repaired hardcoded value returned. */
.card { color: #1a1a1a; }
One possible resolution
.card { color: var(--ink); }

Resolution workflow

Fix the source without erasing intent

  1. Inspect

    Review every reported occurrence and the established candidates Ledgermachine found in the same project.

  2. Decide

    Restore the repair, or record that the product decision changed. Regression status is ledger evidence, not guesswork.

  3. Verify

    Make the change in your editor or coding agent, then rescan. Ledgermachine stays read-only and records whether the finding cleared.

Run it on your source

See the evidence behind this rule.

Open a folder locally, inspect the exact occurrences, and decide whether to repair or preserve the difference.

Open Ledgermachine