docs: the stale-Good quality contract, stated once (R3-02)

archreview/plans/R3-02-stale-good-family-plan.md

@@ -806,3 +806,13 @@ test could only pass once the production change landed.
 - `_lastPublishedBad` became `_hasPublished` + `_lastPublishedStatus`, which is also what makes
   `ReassertValue` re-emit `BadNoCommunication` after a deploy instead of guessing Good.
 - Docs: `docs/ScriptEditor.md` §"Input quality: what a script sees, and when it runs at all".
+
+### T17 — Docs: the contract stated once
+
+- `docs/DriverLifecycle.md` gains §"The quality contract" (the contract quoted verbatim + a table of the
+  six seams that implement it + the consumer-visible warning) and a new sub-section under the comms-loss
+  fan-out covering the value-node fan, `WriteStatuses`, and the recovery audit.
+- Pointers added, each linking back rather than restating: `docs/Raw.md`, `docs/Uns.md`,
+  `docs/ScriptEditor.md` (T16), `docs/drivers/Calculation.md` (T14), `docs/drivers/Mqtt.md` (T5).
+- `CLAUDE.md`: one bullet under the comms-loss watchdog section — value nodes go Bad, nothing Good on
+  reconnect (+ the audit meter), and the **(value, status)** dedup rule any future consumer must repeat.

archreview/plans/R3-02-stale-good-family-plan.md.tasks.json

@@ -125,7 +125,7 @@
     {
       "id": "T17",
       "subject": "Docs: the quality contract stated once (DriverLifecycle.md) + Raw/Uns/ScriptEditor/Calculation pointers + CLAUDE.md bullet",
-      "status": "pending",
+      "status": "done",
       "blockedBy": []
     },
     {