Tidepool v2 puts native Coves users' ActivityPub surface on the coves.social hostname (AP_USER_ORIGIN), served by the tidepool container over the shared coves-prod-network. Adds, inside the existing coves.social site block: - handle /.well-known/webfinger, /.well-known/nodeinfo, /nodeinfo/2.0, /ap/* -> reverse_proxy tidepool:80 (original Host preserved; tidepool's Host router keys on it) - an Accept-negotiated apex split: explicit text/html goes to the appview as before; activity+json, ld+json, and absent-Accept requests fall through to tidepool's instance actor Everything else (static .well-known, /img/ redirect, catch-all, CSP, tdpl.io blocks) unchanged. Spec: tidepool DEPLOY.md §4. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>