consultant-pluslisted

# КонсультантПлюс Use the user's own authenticated browser session. Never request, receive, store or inspect a ConsultantPlus login, password, one-time code, cookie, browser profile or session token. Leave sign-in, CAPTCHA, subscription acceptance and other protected account steps to the user in the provider page. Use only the signed `runtimeExecution.command` from the current `get_agent_skill` response for local preference state. Append arguments after its terminal `--`. The runtime does not access ConsultantPlus and stores no credentials; browser work happens through the client-supported browser surface. ## Resolve access once Run `status` before substantive ConsultantPlus work on a local supported surface. Follow the returned `accessState`: - `connected`: use the saved `browserPreference`, then verify the visible live page is still authenticated before relying on it; - `unknown`: ask once whether the user wants this skill and has access to ConsultantPlus. If yes, select a supported browser surface and let the user sign in. After an authenticated page is visibly available, run `set-connected --browser SURFACE`. If no, run `set-no-access` and continue through the independent-source fallback; - `no_access`: do not ask again for this device and Trelio identity. Use the independent-source fallback automatically; - `needs_reconnect`: let the user restore the saved browser session. If the requested result does not require proprietary ConsultantPlus commentary,