Card: drop the note on where D1A is served

README.md

@@ -19,7 +19,7 @@ D1A is a small open decision model. One document and a set of typed questions go
 
 **v0.6 labels pull requests the way they are labelled today.** On 487 pull requests created after all of its training, severity goes from **74.7% to 79.1%** (+4.3 points) and change type from **86.7% to 90.6%** (+3.9) against v0.5, and P1 recall returns to v0.4's 0.35 (v0.5: 0.22). It also gains on long documents (+2.0), agent-factory routing (+3.4) and held-out transfer (+1.4), with lower calibration error on most suites. It costs hard decisions (−2.7) and change type on the older frozen PR test set (−4.1), so it ships as a **release exception** (below). v0.5 stays available. See Results.
 
-**Release exception.** v0.6 does not pass D1A's release rule against v0.5. `scripts/decide.py` vetoes it (V1) on hard decisions: hard-v1 −2.7 points [−4.9, −0.5], 61 fixes against 90 breaks, past the −2.0 limit for a card suite. It also loses change type on the older frozen PR test set, −4.1 [−6.0, −2.3] (19 fixes, 58 breaks), and pooled over all 21 lines it is level with v0.5, −0.20 [−0.98, +0.52]. It ships anyway, by the owner's decision of 2026-10-10: the model's live job, the one model on the owner's Mac mini, is labelling current pull requests, and on PRs newer than all of its training it is clearly better. The likeliest reading of the disagreement is that the project's labelling conventions have changed over time and v0.6 follows the current ones. **Stay on v0.5** (`JohnP1/d1a-e4b@v0.5`) if you rely on hard-v1-style reasoning or on the older PR-label conventions.
+**Release exception.** v0.6 does not pass D1A's release rule against v0.5. `scripts/decide.py` vetoes it (V1) on hard decisions: hard-v1 −2.7 points [−4.9, −0.5], 61 fixes against 90 breaks, past the −2.0 limit for a card suite. It also loses change type on the older frozen PR test set, −4.1 [−6.0, −2.3] (19 fixes, 58 breaks), and pooled over all 21 lines it is level with v0.5, −0.20 [−0.98, +0.52]. It ships anyway, by the owner's decision of 2026-10-10: the model's live job is labelling current pull requests, and on PRs newer than all of its training it is clearly better. The likeliest reading of the disagreement is that the project's labelling conventions have changed over time and v0.6 follows the current ones. **Stay on v0.5** (`JohnP1/d1a-e4b@v0.5`) if you rely on hard-v1-style reasoning or on the older PR-label conventions.
 
 ## D1A models: what each can do (2026-10-14)