Track Notion DB Markdown Sync ratification residuals

Context

During ratification of context/notion-db-markdown-sync/decisions/proposed/, the old 0012-tracked-phase-followups.md record was not graduated into the VRS decision log because it was a follow-up ledger, not a durable architecture decision.

The ratified VRS decisions absorb or supersede several items from that ledger, but a few residuals should remain explicitly tracked outside the VRS decision directory.

Residuals to audit

• Dry-run coverage for object/attachment storage and bodies-on .nmd materialization where the mechanism exists but fixtures do not yet falsifiably prove it.
• Settlement-proof production wiring currently described by TODO(settlement-wiring) if any dormant path remains.
• Transactional createReplicaSchema creation so schema and CDC triggers cannot be observed half-installed.
• Matrix scenarios still declared from docs/vrs/spec.md instead of concrete executable tests, especially daemon-timing, fixture, and live-lane cases.
• Any remaining comments that say a gap is tracked by the removed proposed ledger should point to this issue or to a concrete follow-up issue.

Acceptance

• Each remaining residual is either closed, linked to a concrete issue, or intentionally documented as out of scope.
• Traceability comments do not reference decisions/proposed or deleted proposed decision numbers.
• Scenario metadata points to executable tests where behavior is genuinely proven.

Start by auditing context/notion-db-markdown-sync/decisions/proposed/ and docs/vrs/spec.md, then search for TODO(settlement-wiring), removed proposed decision references, and scenario metadata that lacks executable tests. Check each listed residual against the repository and classify it as closed, linked, or out of scope. Done means traceability is current and scenario metadata points to genuinely proven tests.