Skip to main content

DEBT.RESOLVED — a recorded debt the catalog shows as settled

  • Category: safety
  • Level: 0
  • Stability: stable
  • Suites: audit, deploy

The ledger records this debt and the catalog shows it settled — the constraint is validated, the index is valid. Somebody did the work.

Why the entry is still in the file​

sqlens:audit runs against a live server, on a machine that has a copy of the repository rather than a working copy of it. Editing a committed file from there would put a change into somebody's tree that nobody made, on a machine where nobody could review it — and the next deploy would overwrite it anyway.

So the removal belongs to the repository:

php artisan sqlens:lint --debt=record

That run has a working copy, a person behind it, and a pull request to land in.

Why it is reported at all​

An account that quietly kept settled debts would overstate what a project owes, and the number in the report is what people act on. Saying so is how the file gets brought up to date at all.