Keep coverage materialization theme-specific
This commit is contained in:
@@ -24,6 +24,10 @@
|
||||
`catalog_checked_at` was incorrectly compared as publication identity.
|
||||
Reviews now tolerate a later probe timestamp while still blocking any
|
||||
identifier, release URL/version or catalog content-hash change.
|
||||
- Live coverage verification then exposed a cross-theme materialization leak:
|
||||
the Statbel population Dataset also appeared under `admin`. The coverage
|
||||
registry now enforces each source's `operational_themes`, leaving NGI as the
|
||||
administrative authority and Statbel as population evidence only.
|
||||
- Focused backend and frontend suites passed before full release validation;
|
||||
full local and Tower evidence follows in the final P5 gate.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user