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: set viewer_filters to exclude content-scopes-530 and the webfetch dynamic track, so a Webstone republish from this revision reproduces the current viewer configurations (verified: Webstone DatasetRelease.build output equals the committed data/*.jsonl byte for byte).
  • README.md: describe --score-scope (both main and full scored from the same saved responses since Webstone PR #276) and the role of --content-scope; rename browser-harness-eval run to webstone 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

Sign up or log in to comment