Verify the public self-hosting guide through connection and first collection #44

The public self-hosting manual needs a verified path from deployment through connection to the first collection. impl-ts#120 contains deployment screenshots, but does not identify their versions, steps, or current applicability.

Documentation contributions are welcome. Coordination contact: @xiaoland. Comment before taking this task and name the deployment method you intend to check.

Start with website/content/en/self-hosted/index.md, one concrete deployment guide, website/content/en/guide/connect.md, and website/content/en/guide/first-source.md. The published entry is Self-hosted.

Check the existing public instructions and released artifacts, record successful steps or precise blockers, and correct guide problems supported by those observations. Verify screenshots against the actual versions before reusing them. Remove real JWT secrets, connection files, and personal information from any new images.

No organization package token or impl-ts source build is required. If a supposedly public artifact cannot be obtained anonymously, record its URL, version, and a redacted response as a blocker rather than requesting organization credentials.

Acceptance:

• Record the guide, client/peer/extension versions, deployment method, and observation date.
• Describe the actual outcome of deployment, connection, and first collection. For a blocked step, provide the shortest reproduction and the condition needed to continue.
• Link documentation changes to the observations that justify them. Screenshots must match the steps and contain no secrets.
• For website changes, run pnpm --dir website check and identify any acceptance work still requiring a maintainer.

This is a help wanted task involving deployment judgment, not yet a good first issue. Leave the implementation assignee empty until someone takes it; @xiaoland coordinates scope and questions.