fix: retain PSL in compact catalogs
Some checks failed
Standalone registry checks / check (push) Has been cancelled
Some checks failed
Standalone registry checks / check (push) Has been cancelled
This commit is contained in:
parent
3b6966c81a
commit
3c89a540d9
7 changed files with 16 additions and 5 deletions
|
|
@ -34,7 +34,7 @@ source attribution and application-specific malware/content policy.
|
|||
|
||||
## Current contracts
|
||||
|
||||
Code version 0.6.1 uses writer schema 5 and `argand.site-rules/v4`.
|
||||
Code version 0.6.2 uses writer schema 5 and `argand.site-rules/v4`.
|
||||
New compact `COMPLETE.json` files use `argand.site-registry/v3` and bind:
|
||||
|
||||
- authenticated `registry.sqlite` bytes;
|
||||
|
|
|
|||
|
|
@ -7,6 +7,8 @@ Patch release 0.6.1 additionally replays the real provider-shaped
|
|||
accounting but is not retained as a DNS target. The following valid
|
||||
`com.facebook` row is retained at its original `row:2` coordinate. Schema and
|
||||
numeric corruption continue to fail closed.
|
||||
The compact-generation lifecycle now also executes the review queue, proving its
|
||||
PSL normalization input remains in the runtime catalog.
|
||||
|
||||
The evaluation contract was written before implementation. The new Common Crawl
|
||||
domain-rank integration passed five default integration tests; its sixth test is
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue