Fix viewer filters and content-scope wording for v3.0.0
#10
by gehuageyan - opened
Patch-level metadata/docs fix for v3.0.0. No task, reference, edition, population, archive or definitions change.
manifest.json: setviewer_filtersto excludecontent-scopes-530and thewebfetchdynamictrack, so a Webstone republish from this revision reproduces the current viewer configurations (verified: WebstoneDatasetRelease.buildoutput equals the committeddata/*.jsonlbyte for byte).README.md: describe--score-scope(bothmainandfullscored from the same saved responses since Webstone PR #276) and the role of--content-scope; renamebrowser-harness-eval runtowebstone run.
Checks: make check (37 tests OK) and tools/rebuild_publication.py --check -> 530 tasks, 65 archive members. Archive sha256 and all Webstone data-lock file hashes are unchanged.
gehuageyan changed pull request status to merged