The regeneration in #1569 found the .markdownlint-cli2.jsonc Financial-Modeling disposition no longer live, so it renders under reports/divergences.md "Resolved", whose own heading says what is owed:
Resolved (recorded but no longer live - remove from the ledger)
- .markdownlint-cli2.jsonc - Financial-Modeling (re-vendor)
Financial-Modeling's copy now matches the hub canonical byte for byte, verified during #1569 by fetching it and comparing against the hub's own file, and #1487, the entry's tracking value, is closed. The entry in spec/divergences.json is therefore a recorded divergence with nothing left to record.
This was also the row #1554 was filed about, from the other side: the report lagged the ledger there, and the lag is now moot because the divergence itself is gone rather than because the tracking value ever rendered.
Leaving the entry costs more than tidiness. --report re-derives the resolved section from live fleet state on every run, so a stale entry re-renders the same resolved row indefinitely, and a reader cannot tell a row that resolved this week from one that resolved months ago. A repository that later diverges again on the same file would also fold into this entry rather than reading as the new divergence it is.
Closing this takes deleting the entry from dispositions and regenerating, per the report's own generated-file header, never a hand-edit of the report. Note that the first .markdownlint-cli2.jsonc entry, the one covering AudioCleaner and PhotoCleaner, is still live and stays.
The regeneration in #1569 found the
.markdownlint-cli2.jsoncFinancial-Modeling disposition no longer live, so it renders underreports/divergences.md"Resolved", whose own heading says what is owed:Financial-Modeling's copy now matches the hub canonical byte for byte, verified during #1569 by fetching it and comparing against the hub's own file, and #1487, the entry's
trackingvalue, is closed. The entry inspec/divergences.jsonis therefore a recorded divergence with nothing left to record.This was also the row #1554 was filed about, from the other side: the report lagged the ledger there, and the lag is now moot because the divergence itself is gone rather than because the tracking value ever rendered.
Leaving the entry costs more than tidiness.
--reportre-derives the resolved section from live fleet state on every run, so a stale entry re-renders the same resolved row indefinitely, and a reader cannot tell a row that resolved this week from one that resolved months ago. A repository that later diverges again on the same file would also fold into this entry rather than reading as the new divergence it is.Closing this takes deleting the entry from
dispositionsand regenerating, per the report's own generated-file header, never a hand-edit of the report. Note that the first.markdownlint-cli2.jsoncentry, the one covering AudioCleaner and PhotoCleaner, is still live and stays.