[linnnn89]

Change

Add explicit client UI workflows to the persistent Skill session. readonly-ui supports bounded observations and the installed checkbox-audit recipe; expand-ui can observe, expand one proven parent when needed, and independently read a child checkbox. Successful findings require observed identity, uniqueness, state and the relevant evidence. Cancellation, unknown actions and incomplete results stop without automatic replay.

Add wincode_ui_set_expanded and observed scopePath selectors for inspect/review/setExpanded. The client carries the parent range through discovery, selection, expansion, continuation and final child readback. For example, two regions with identical advanced-group and checkbox IDs now return only the selected region's state, leaving the other region unchanged. Scoped requests require Host inspectionVersion 5; scoped actions verify capability before dispatch. A parent identical to the path's final selector reuses that root rather than querying a duplicate strict descendant.

Keep existing single-tool JSON requests, readonly recipes and click/type behavior. Product/source and native components are aligned at 0.17.0. README, Skill, architecture and existing plans record the supported workflow, focus effects and M1–M6 merge line. The branch's historical model experiments are retained as limited evidence; benchmarks remain opt-in and do not run as a default application workflow.

Validation

• Final npm run check: 493 tests, 492 passed, 0 failed, 1 existing optional fixed Tavern fixture skipped; typecheck, locked restore, Gateway/native publication, stdio and delivery checks passed.
• Final npm run check:desktop: 7 stages passed; 55/55 UI/source tests, no skips; actual desktop owner-death, native Tray and dual-client Tray workflow passed.
• Actual JSON CLI against a WPF fixture with duplicate parent names/IDs and child IDs: scoped independent On/Off results, one expansion per request, no expansion on resume, no action for missing/ambiguous ranges, owned-process exit verified.
• Actual Codex PTY CLI against an isolated synthetic Tavern profile: one expansion (5 calls), independent On readback, expanded continuation (4 calls, no action), visible read (1 call, no action). All 18 helper starts and both CLI/Gateway sessions exited; the owned app was closed separately and its existing Git changes were preserved.
• First desktop run's 3 failures are retained in docs: one-call compatibility, legacy parent failure classification, and a fixture partial-file omission. All three focused reproductions passed after fixes. The real app also reproduced a scope-root duplication failure; its regression and actual workflow passed after the bounded fix.
• Four managed Skill files are hash-matched in each of the three existing generic installations, after backups; no MCP configuration or adapter-specific Skill changed. Documentation links/anchors, versions and staged whitespace checked.

Review and limits

Author self-review covers the entire increment from main, including client serialization/cancellation, scope validation and fresh resolution, old-Host action gating, audit/cleanup, and opt-in model execution. This is not an independent review. Required PR-head Node 22/24 and three CodeQL checks must pass before merging.

No recursive navigation, generated ancestor paths, scoped click/type, new services/dependencies, release assets or default-client reconnection. Non-WPF navigation, broad application/model coverage and stable performance remain outside the merge line. Expansion events may bring an application forward; functional validation does not establish a universal background guarantee. Raw window results and process identity reports remain in ignored local directories.