Sync from docs: document self-serve Private Endpoints dashboard flow (powersync-docs #454)

[bean1352]

Generated by Claude. Review carefully before merging.

Source docs PR: powersync-ja/powersync-docs#454

What changed in docs

Private Endpoints for PowerSync Cloud are now self-serve via the Dashboard. The previous limitation ("Self-service is not yet available — contact PowerSync support") was removed and replaced with a step-by-step flow: configure an Endpoint Service, create the endpoint in Dashboard → Organization Settings → Private Endpoints, accept the VPC connection, wait for Available status, then select the endpoint in the instance's database connection form.

Skill updates in this PR

• skills/powersync/references/powersync-service.md — added a ## Private Endpoints section under PowerSync Cloud Setup with the self-serve dashboard flow (5 steps), endpoint status table, supported regions, and limitations (Dashboard-only, AWS-only, Postgres + MongoDB Atlas only, Team/Enterprise plans). Also added private-endpoints, privatelink, vpc, and aws to frontmatter tags.

Notes for reviewer

• The old docs listed four limitations; two were removed: "self-service not available" (now available) and "Test Connection not supported" (now works per the new docs). The skill section reflects the current state only.
• "CLI support is not yet available" is noted in the section. If/when CLI support ships, this section will need a follow-up update.
• The 5-step flow is intentionally concise for agent consumption. The full Atlas-region nuances (cross-region restrictions, newer region availability) are summarised rather than reproduced verbatim — agents can link out to the docs page if they need more detail.
• No new standalone reference file was created; the content fits naturally as a subsection of powersync-service.md. If Private Endpoints grow significantly in scope (e.g. self-hosted support, CLI commands), a dedicated private-endpoints.md may be warranted.

---

Generated by Claude Code