Nexus v2.15.0

Maintenance release: the project's record of known gaps is now one countable list. No app, extension or installer behavior changes.

Known gaps

• Every known-gaps file from v1.17 to v2.12, including the v2.12 carry-forward register, now reads cleanly in the release completion checker (204 unreadable rows before, 0 now), with no wording changed. Rows that only repeated an entry recorded elsewhere now point at it (v2.4#BG-2) instead of counting twice.
• The 47 items still open in v2.12 were checked against the current code: 3 are resolved with evidence, and 44 moved into the v2.15 known gaps word for word, each with why it is still owed and a next step. The v2.12 register is finalized.
• The 199 older items that are still open are listed once each in four follow-up batches, each sized for one plan (v2.15.1 to v2.15.4).
• What is still owed: 62 items in v2.15 plus the 199 batched items, 261 in all, with none counted twice.

Tooling

• node scripts/known-gaps/inventory.mjs reports every ledger's items, the open count, drift against a dated baseline, and (--triage, --batches, --verify-migrations) whether the triage record and batch list cover every item once and every migrated copy verifies. It reads ledgers through scripts/known-gaps/checker-adapter.py, which runs the completion checker only when its files match pinned hashes.

Not changed

• The app, the VS Code extension and the installers behave as in v2.14.2. The installers are rebuilt by the release workflow from the same product code.
• Release completion is still blocked by conflicts in the external completion checker, recorded with a handoff for its maintainer (v2.15 QG-11).