From 392e8dd44538b52024f3b6845ea9cab275bbb23f Mon Sep 17 00:00:00 2001 From: PJ Date: Sun, 16 Aug 2026 01:07:58 +0530 Subject: [PATCH] docs(skills): screen= is the chrome driver's url, web only --- skills/sanderling-setup/SKILL.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/skills/sanderling-setup/SKILL.md b/skills/sanderling-setup/SKILL.md index bdfd1fb..c8d4dfa 100644 --- a/skills/sanderling-setup/SKILL.md +++ b/skills/sanderling-setup/SKILL.md @@ -213,8 +213,13 @@ against an empty page gives `nodes=2` for every step, and still exits 0 with no violations. If `nodes` is a handful and never grows, the run is looking at something that is not your app. -`screen=` is the route marker your spec's screen hooks produce. A run where it -never changes never left one screen. +`screen=` is web-only and has nothing to do with your spec's screen hooks: the +Chrome driver puts the URL hash, or the pathname when there is no hash, on the +root node, and only that driver writes the attribute. On Android and iOS it is +empty on every step, so an empty `screen=` there is the normal reading and not a +symptom. On web, a `screen=` that never changes means the run never left one +URL, which for a single-page app that routes in memory is also normal. Your +spec's own route extractor is the thing to trust on every platform. The summary can carry a third line you should never skim past: