docs(siteruntime): mark WaitAsync deferred items implemented (§3/§4.2/§6) + fast-path throwing-predicate test

docs/plans/2026-06-17-waitfor-attribute-change-helper-spec.md

@@ -82,9 +82,13 @@ Task<bool> Attributes.WaitAsync(string name, Func<object?, bool> predicate, Time
 
 // Optional richer overload that also returns the matched value + quality.
 Task<WaitResult> Attributes.WaitForAsync(string name, object? targetValue, TimeSpan timeout);
-// record WaitResult(bool Matched, object? Value, string Quality, bool TimedOut);
+// record WaitResult(bool Matched, object? Value, string? Quality, bool TimedOut);
 ```
 
+> **Status:** IMPLEMENTED. `Attributes.WaitForAsync(...)` returns a `WaitResult`
+> (`readonly record struct WaitResult(bool Matched, object? Value, string? Quality, bool TimedOut)`
+> in Commons), populated on match (Value + Quality) and `Matched:false, TimedOut:true` on timeout.
+
 Return **bool** (not throw) for the common case — the handshake wants matched/timed-out, not an
 exception. The value-equality overload is the one the handshake needs and is the one that can also
 be exposed on the inbound/routed side (§6), because a value serializes and a delegate does not.
@@ -159,6 +163,10 @@ public record WaitForAttributeTimeout(string CorrelationId);
 - Optional: a `quality == "Good"`-only mode (parameter on the request) if a handshake must ignore
   Bad-quality transients.
 
+> **Status:** IMPLEMENTED as an opt-in `requireGoodQuality` parameter on `WaitAsync`/`WaitForAsync`
+> (additive trailing `RequireGoodQuality` field on `WaitForAttributeRequest`, gated at both the
+> fast-path and resolve-loop match sites). Default `false` = quality-agnostic (matches on value only).
+
 ### 4.3 `ScriptRuntimeContext` (`src/…/SiteRuntime/Scripts/ScriptRuntimeContext.cs`)
 - **Thread the script timeout token in.** Add a `CancellationToken scriptTimeoutToken` constructor
   parameter (today only `_askTimeout` is available to helpers; the per-script `cts.Token` is **not**
@@ -228,6 +236,11 @@ so the routed form takes the encoded target value (the predicate overload stays
 optional: the receiver handshake runs **inside** the template script (site-local), so §3–§5 alone
 fully cover the DELMIA/MES use case.
 
+> **Status:** IMPLEMENTED. `Route.To(code).WaitForAttribute(name, targetValue, timeout)` is wired
+> end-to-end (`RouteToWaitForAttributeRequest/Response` → `IInstanceRouter` → `CommunicationService`
+> → `SiteCommunicationActor` → `DeploymentManagerActor` → `InstanceActor`), value-equality only
+> across the wire. NOT wired into the CentralUI Test-Run sandbox — that remains a follow-up.
+
 ---
 
 ## 7. Acceptance criteria