Hosted public OAuth surfaces for app review and ATProto provider setup.
SheerVue now hosts a static ATProto OAuth client metadata document under the SheerVue domain alongside its support, privacy, and terms pages. This gives the mobile app a stable hosted client identity for OAuth configuration.
Required public pages and metadata
Landing page explaining what SheerVue is and why it exists.
/support/Public support URL with contact method for users and reviewers.
/support/tos/Terms of Service URL for provider and store requirements.
/support/privacy/Privacy Policy URL for trust, provider setup, and app review.
/oauth/client-metadata.jsonHosted ATProto OAuth client metadata for the SheerVue native app.
What the hosted client metadata declares
The metadata uses its own hosted URL as client_id, declares application_type as native, and sets token_endpoint_auth_method to none.
The current static metadata assumes the native callback is sheervue://oauth/callback and the default requested scope is atproto transition:generic transition:chat.bsky, matching the app-side migration notes provided for this repo task.
This web repo only hosts the public metadata and informational pages. OAuth callback handling remains in the mobile app via the SheerVue deep link unless future provider requirements add a web callback endpoint.