feat: validator, bundle builder and release checks for 0.1.0

- Add tools/validate.py: validates packages, and with --correction runs
  proposed corrections through the gate against a package without
  writing anything (spec/11 §11.4). The gate now refuses a proposal that
  fails the correction schema, rule correction.schema.
- tools/load.py validates every package before loading, and with
  --bundle --built-from builds a scienting-bundle/1 with the FTS5 search
  index and bundle_meta (spec/13 §13.5). Search rows are defined per
  unit (sentence, cell, equation outside a sentence, figure-text) with
  the parent kind as context.
- Roster keys carry a role, and a key with the role owner may revoke any
  receipt (spec/08 §8.7, spec/20); roster schema, store table and the
  fixture roster updated. The checker signs a trial revocation to prove
  the rule both ways.
- A qa: receipt raises the nodes it sampled except those in its errors
  (spec/08 §8.2); the example paper's fidelity counts become 27 F3,
  13 F2, 4 F1 and 1 F0.
- The destination chooses the keyed scheme, not the text policy:
  hmac-team between the team's machines, hkdf-pages outside the team
  (spec/05 §5.8, spec/12 §12.5).
- A TextQuoteSelector must repeat the anchor's plain quote and is absent
  for hashed or keyed anchors (spec/18 §18.3).
- Add fixtures/records/suspect.json, a scienting-suspect/1 record.
- Oracle: hashes are kept incrementally and checked after every
  correction against a full recomputation; load and write refuse unsafe
  manifest paths; Ed25519, HKDF and schema validation come from the
  cryptography and jsonschema packages; canonical JSON uses the built-in
  encoder with an exact RFC 8785 fallback.
- The tools need Python 3.14 with cryptography and jsonschema; the py310
  CI environment is dropped and the workflow runs the default only.
- Resolve every [CHECK] note in the docs, READMEs and context; add
  CONTRIBUTING.md; every tool answers --help and refuses unknown options.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

spec/11-corrections.md

@@ -54,16 +54,20 @@ Drift ([6.6](06-anchors.md#66-drift)) is computed from `path`, `to_path` and `to
 
 A correction is refused, naming the rule ([22](22-conformance.md)), when:
 
-1. a target, parent or sibling is not live, or the root would be deleted, moved, merged or reclassified;
-2. `find` is empty or does not occur exactly once;
-3. an `insert` has no crop evidence;
-4. a digit changes without crop evidence: in a `replace` whose `find` and replacement have different digits, a `delete` of leaves that hold digits, or a `relabel` whose labels have different digits;
-5. any leaf outside `touched` has different digits afterwards;
-6. a `split` falls outside the sentence, inside a run other than text, or leaves a part empty;
-7. a `merge` joins nodes that differ in kind, are not mergeable, or are not adjacent siblings;
-8. a `move` would put a node inside itself;
-9. a `reclassify` changes the content shape, or a `relabel` or `set` targets a kind that does not take it; or
-10. the result breaks a rule of [3](03-nodes.md).
+1. it does not match the correction schema, `schemas/correction.schema.json`;
+2. a target, parent or sibling is not live, or the root would be deleted, moved, merged or reclassified;
+3. `find` is empty or does not occur exactly once;
+4. an `insert` has no crop evidence, or names a run or offset its target does not have;
+5. a digit changes without crop evidence: in a `replace` whose `find` and replacement have different digits, a `delete` of leaves that hold digits, or a `relabel` whose labels have different digits;
+6. any leaf outside `touched` has different digits afterwards;
+7. a `split` falls outside the sentence, inside a run other than text, or leaves a part empty;
+8. a `merge` joins nodes that differ in kind, are not mergeable, or are not adjacent siblings;
+9. a `move` would put a node inside itself;
+10. a `reclassify` changes the content shape, or a `relabel` or `set` targets a kind that does not take it; or
+11. the result breaks a rule of [3](03-nodes.md).
+
+The gate needs only the document's current state, so a tool can run it on a proposal before applying anything, and get back the record the correction would append or the rule it breaks.
+`tools/validate.py --correction` does this against a package.
 
 Digits are characters of General Category Nd in the plain projection.
 A package's corrections are also checked as a whole: indexes run from 1 without gaps, each `id` derives from its record, `rev` equals their number, every retired ID is in `ids.jsonl`, and the last correction of each leaf ends at its current `node_hash`.