v2.8.0

It tells the truth about what it saw.

2.7.0 was about getting connected. This one is about the two ways a verdict can lie once you are: claiming something it never observed, and refusing to claim something it did.

Every fix below was found by driving Reticle against a running app, not by a failing test.

What changed

• Assertions that could not fail now can. An element predicate's value and text are really checked, and fields the locator would have dropped are refused instead of ignored.
• Verdicts stop shrugging when they had the answer. A state path only one store exposes is read rather than refused, a value the transport truncated is no longer compared as if it were the value, and an action gets the full budget it was given before anything is called uncertain.
• A crawl says what it did not reach. Controls its own clicks revealed are reported as unvisited instead of counted as a clean sweep.
• A mistyped mock rule is refused. It used to turn mocking off and report success, so an error state got tested against the real backend.
• Vue apps connect. The installer wired the React adapter into them, so they never dialled in at all. Vue is now scaffolded from scratch by the install gate on every change.
• reticle doctor says whether anything is connected, which is the state a setup most often stalls in.

Before you upgrade

Some assertions that passed before will now fail. That is the point: each one is a case where a green meant less than you thought it did. The changelog lists them at the top.

Thanks

@DevChiniwala for a run of fixes across the MCP transport, the CLI and the browser SDK, @XonkelX for making learned routes survive the session that found them, and @DivyamTalwar for putting the Rust dependencies under watch.

Full detail: CHANGELOG.md