feat(tracker): add alpha calibration and dynamic pricing

Add TOPLOC honest-noise calibration storage/dispatch and validator divergence reporting for AH-021.

Add opt-in HuggingFace marketplace pricing refresh, price-change history, CLI flags, and AH-023 tracking docs.

Verification: .venv/bin/python -m pytest tests/ -q -k 'not integration' => 346 passed, 2 skipped, 1 deselected; compileall packages tests passed; focused AH-021/AH-023 tests 32 passed.

packages/validator/README.md

@@ -51,8 +51,31 @@ skip_prefill = true
 encoding = "base64"
 ```
 
+`verify_activation_proofs_detailed()` (`meshnet_validator.audit`) surfaces the
+raw TOPLOC divergence — `exp_intersections` (worst-case across chunks),
+`mant_err_mean`, `mant_err_median` — alongside the pass/fail bool. This is
+what the calibration corpus below is built from; existing callers that only
+need the bool keep using `verify_activation_proofs()`.
+
+**Do not enable production audit thresholds before issue 21 closes.**
 Production audit thresholds remain gated on the honest-noise calibration
-corpus in issue 21.
+corpus in issue 21: the tracker's `POST /v1/calibration/toploc/run`
+(admin/validator-only, mirrors `POST /v1/benchmark/hop-penalty`) dispatches a
+fixed prompt to every solo-capable registered node, verifies each node's
+on-demand commitment against a teacher-forced reference replay, and records
+the divergence into a SQLite corpus (`meshnet_tracker.calibration.
+ToplocCalibrationStore`) keyed by node wallet + GPU model + dtype.
+`GET /v1/calibration/toploc/results` reports the corpus plus:
+
+- `envelope`: p99 honest-noise value per metric with a 20% safety margin —
+  the recommended (not yet wired) tolerance constants.
+- `gate_status.ready`: whether the corpus covers enough distinct hardware
+  profiles (`--toploc-calibration-gate-min-hardware-profiles`, default 1).
+  **Alpha exception:** with the hired-VPS-only launch fleet, `ready` may
+  legitimately mean "covers every node we currently operate" — this must be
+  revisited (raise the minimum) before a public/volunteer launch broadens
+  the hardware mix, since a new corpus is required whenever the fleet's
+  hardware composition changes.
 
 Two operational notes: