docs: clarify remote setup and connection verification

[iuyo5678]

Summary

Make remote setup guidance distinguish a configured service or existing pairing link from a server that still needs deployment. Give agents a complete pairing and first-use verification path, with feedback based on what has actually been checked.

This is a documentation-only follow-up to #254, based on docs/release-0.3.0-readiness so the diff contains only this patch. After #254 merges, retarget this PR to main.

Changes

• Route remote users before local installation steps; clarify which steps run on the Agent server and which require the browser user.
• Replace the generic extension-installation response with separate local and remote instructions.
• Add a pairing and verification section: identify the connected browser, start a session, read a page, stop the session, and report cleanup errors. Preserve the native-tool path for DSH.
• Distinguish link generation, browser connection, and successful first use; report missing prerequisites or unverified steps explicitly.
• Add one early remote-guide pointer to each skill variant and keep the packaged CLI copy synchronized. Relative to docs: prepare 0.3.0 guidance and streamline browser skills #254, the CLI skill grows by 11 tokens and the DSH skill by 36 tokens using o200k_base.

Scope: five Markdown files.

Validation

• CLI parsing/install integration tests: 45 passed.
• Skill installation unit tests: 38 passed with --test-threads=1.
• DSH skill generation and injection tests: 5 passed.
• All 12 remote-guide CLI examples parsed with the current CLI parser, without executing deployment commands.
• Checked 16 repository links/anchors, validated all three skill frontmatters, confirmed identical CLI skill copies, and passed git diff --check.

The initial parallel installation-test run hit an existing HERMES_HOME race between detects_hermes_from_home_layout and the environment-override test. All 38 tests passed serially; the test/runtime implementation is unchanged by this patch.

Remote deployment was not exercised in this documentation patch. Validation covers command syntax, links, packaging, and the documented verification flow.