The regeneration in #1569 surfaced PSScriptAnalyzerSettings.psd1 as a live manifest gap for the first time, so it renders under reports/divergences.md "Untriaged" and needs a disposition in spec/divergences.json.
- PSScriptAnalyzerSettings.psd1 - hub-hosted and undeclared in the manifest, carried by HomeAutomation-Config
A gap is a file the hub tracks, spec/files.json does not declare, and a cataloged repository carries anyway. The disposition vocabulary the ledger's own note field defines gives three candidates here, and which one applies is the decision this issue asks for.
track, if every repository with a PowerShell surface is owed the hub's analyzer settings. That makes it a manifest entry with an appliesTo selector, and the fidelity choice, intent or verbatim, comes with it.retire, if the settings are the hub's own and a downstream copy is deleted rather than converged, the way the repo-config/ payloads and the reusable-workflow tasks already are.accepted, if HomeAutomation-Config's copy is a path collision rather than a carry, which is how .github/actionlint.yaml and scripts/README.md are already dispositioned for that same repository and for KiCadLibrary. Settling this one means reading HomeAutomation-Config's copy against the hub's rather than reasoning from the shared path.
#1153 is adjacent context rather than a duplicate: it asks whether the hub should ship PowerShell at all, where this asks what the manifest says about the analyzer settings it currently does ship.
Closing this takes a ledger edit plus a regeneration, per the report's own generated-file header, never a hand-edit of the report.
The regeneration in #1569 surfaced
PSScriptAnalyzerSettings.psd1as a live manifest gap for the first time, so it renders underreports/divergences.md"Untriaged" and needs a disposition inspec/divergences.json.A gap is a file the hub tracks,
spec/files.jsondoes not declare, and a cataloged repository carries anyway. The disposition vocabulary the ledger's ownnotefield defines gives three candidates here, and which one applies is the decision this issue asks for.track, if every repository with a PowerShell surface is owed the hub's analyzer settings. That makes it a manifest entry with anappliesToselector, and the fidelity choice,intentorverbatim, comes with it.retire, if the settings are the hub's own and a downstream copy is deleted rather than converged, the way therepo-config/payloads and the reusable-workflow tasks already are.accepted, if HomeAutomation-Config's copy is a path collision rather than a carry, which is how.github/actionlint.yamlandscripts/README.mdare already dispositioned for that same repository and for KiCadLibrary. Settling this one means reading HomeAutomation-Config's copy against the hub's rather than reasoning from the shared path.#1153 is adjacent context rather than a duplicate: it asks whether the hub should ship PowerShell at all, where this asks what the manifest says about the analyzer settings it currently does ship.
Closing this takes a ledger edit plus a regeneration, per the report's own generated-file header, never a hand-edit of the report.