docs: document renaming a site

[vigneshrajsb]

Reader and task

• Audience: application developers and site owners
• Task/outcome: rename a hosted site in the UI, CLI, or API

Source of truth

• Exact owning repository revisions, PR head SHAs, or immutable artifacts: GoodRxOSS/lifecycle, GoodRxOSS/lifecycle-cli, and GoodRxOSS/lifecycle-ui site-rename branches (PRs open, not merged)
• Frontmatter verification baseline added or reused: reused (not changed)
• Product or runtime verification: not run; based on the PR branches
• Contract checks (schema / OpenAPI / CLI; identify any SKIP): check:contracts ran with schema, OpenAPI, and CLI all SKIP
• Unavailable or unresolved sources: none

Documentation changes

• Changed pages: Sites, CLI
• ASD-STE100 human review: style baseline refreshed with update:style-baseline; reviewer to confirm wording
• Navigation or redirects: none
• Raw Markdown projection: check:raw passes
• External state: none
• Screenshots, catalog status, and manual pixel/state review: none; no visuals changed

Verification

• Formatted changed files
• Kept source-review evidence and non-actionable implementation details out of end-user prose
• Confirmed that each changed sentence helps the reader understand, complete, verify, or recover the task
• Reviewed all 53 rule rows in .agents/skills/update-lifecycle-docs/references/ste100-review.md
• bun run check:styles
• Updated the style baseline only after the complete human review
• bun run check:raw
• bun run verify
• bun run check:contracts --require-all when schema, API, or CLI claims changed
• Checked changed routes with an approved desktop browser inspection tool
• Checked every theme enabled by the current theme config
• Ran bun run check:screenshots when visuals changed
• Confirmed screenshots contain no secrets or personal/private data
• Confirmed tracked guidance has no contributor-specific paths, hosts, credentials, or fixture identities