You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Financial-Modeling's .markdownlint-cli2.jsonc is modified against the canonical and carries no divergence entry #1487
Surfaced while fixing #1466, which asked whether that repository's ignores block was the fix to promote. It is not, so its state needs its own disposition.
What it holds
ptr727/Financial-Modeling's copy adds three keys the canonical did not have when it was written:
data/** is a committed document archive and notes/forms-decisions.md is the owner's freeform working notes, excluded from the fleet prose gate too via that repository's .github/prose-gate-excludes. Both are repository-specific by construction, so neither belongs in the canonical.
Why it needs a decision
spec/files.json declares .markdownlint-cli2.jsoncverbatim, whole. The copy matches no hub revision, so it audits as modified: the repository changed fixed content. spec/divergences.json already carries an entry for this path covering aiopurpleair, PhotoCleaner, and AudioCleaner at disposition re-vendor, and Financial-Modeling is not in that list, so nothing records that this one is deliberate.
The dispositions are not equivalent:
accept, recording a governed divergence for a repository that carries content the fleet does not, which leaves it permanently off the canonical and needing a hand merge on every hub change to this file.
re-vendor, which erases the two exclusions and puts that repository's archive and notes back under the linter.
A seam, if the fleet decides an exclusion list is per-repository content that a verbatim file should not own, which is the same argument markdown-exclude-globs already settled for the CI side.
What changed under it
e7cb1cf (#1474) added globs and an ignores entry to the canonical, so the two files now differ by the entries rather than by the keys. Whichever disposition is chosen, the fix has to originate in the hub to reach that repository cleanly, per #1466.
Activity
Settle the Markdown Lint Exclusion Seam as a Nested Config (#1494)
Regenerate reports/divergences.md Against the Current Fleet (#1569)
Promote develop to main: Regenerate the Fleet Divergence Report (#1570)
Remove the Resolved Financial-Modeling markdownlint Entry From the Di…