docs: explain the frozen input default content scope
Browse files
README.md
CHANGED
|
@@ -362,6 +362,7 @@ Public reference hashes do not replace those inputs.
|
|
| 362 |
|
| 363 |
Use `webstone validate --dataset <exported-dataset.json>
|
| 364 |
--content-scope main` or `--content-scope full` before a run. Each run selects one
|
| 365 |
-
scope
|
| 366 |
-
|
|
|
|
| 367 |
released edition; the cohort's `implementation` field identifies its scoring code.
|
|
|
|
| 362 |
|
| 363 |
Use `webstone validate --dataset <exported-dataset.json>
|
| 364 |
--content-scope main` or `--content-scope full` before a run. Each run selects one
|
| 365 |
+
scope. The approved input bound by this cohort declares `main` as its default.
|
| 366 |
+
An explicit option overrides a saved scope; annotated tasks without a saved scope
|
| 367 |
+
fall back to `full`. Older suites keep their original rules. The existing manifest tooling pin still describes the
|
| 368 |
released edition; the cohort's `implementation` field identifies its scoring code.
|