[agent] outcome_unread still fires when the declared consequence was a route change or an element matched by role/name/testid

[divshekhar]

Update: the original scope of this issue landed on main — a declared, body-independent
consequence now stands down the unread-body caveat instead of downgrading the verdict.
A narrow residual survives, and this issue is retitled to it.

The residual

declaresBodyIndependentChannel (packages/server/src/events/declared.ts:87-107) returns true
for text, signal, state, and an element matched by value or text. Everything else falls
to default: false, including:

• PredicateKind.ROUTE
• a non-absent element located by role, name or testid

So a caller who declares "this action lands on /lobby" in advance, and whom Reticle then watches
land on /lobby, still gets verified: "unknown" with reason outcome_unread if the write's
response body was not captured — even though the consequence they named held on a channel that has
nothing to do with the body.

Repro

1. Leave captureNetworkBodies off (the default).
2. reticle_act_and_wait on a control that issues a write and changes route, with
   until: { kind: "route", ... } — or until: { kind: "element", query: { role: "heading", name: "…" } }.
3. The route/element change is observed and the embedded evidence says pass; the top-level verdict
   is unknown / outcome_unread.

Fix

Add PredicateKind.ROUTE, and non-absent element matches by role / name / testid, to
declaresBodyIndependentChannel. A route change the caller named before the action and Reticle
watched happen is body-independent evidence by construction — the same argument the existing text
and state cases already rest on.

Keep the same conservatism the function already documents: top level and allOf only, never an
anyOf branch, and never an absent predicate.

[Pranav5255]

hey @divshekhar, can i work on this issue?

[hardikguptaofficialgit]

Status check: fix is already on release/v2.12.0. Remains open until that ships via #564 (install-gate unblock: #581).

[divshekhar]

Narrowed. The original scope (a body-independent declaration no longer being overruled by an unread body) landed on main on 2026-08-23 in fix(server): do not grade unread bodies over a body-independent declaration. What survives is that route, and elements located by role/name/testid, are not yet in the body-independent set — retitled and rescoped above. Thanks for the original report; the trace in it is what identified the escape hatch.

[kushals256]

Opened #649 for the residual.

PredicateKind.ROUTE and a non-absent element located by role / name / testid now count as body-independent, so a declared landing on /lobby that Reticle watched happen is no longer graded unknown / outcome_unread just because the write body was not captured. Top-level and allOf only; anyOf and absent stay out.

[divshekhar]

Adjacent evidence from 2.13.1, filed as #801: several sessions hit repeated unknown/outcome_unread verdicts on writes that returned a real 2xx with a real JSON body, and the advice printed each time — enable captureNetworkBodies — was in one case impossible to follow, because the pinned SDK predated the setting. #801 asks that the remedy check whether the connected SDK can satisfy it, and that it arrive on the first unknown rather than the fifth.