The technical side of profiles is done (--profile, src/profiles/, waiver annotation). The remaining work is social:
- Co-own profiles: hand tranquil-pds maintainers the seeded
tranquil-pds.tsprofile (4 absent endpoints + the OAuth-consent acknowledgment) and invite pds.js to own theirs. Their own docs are the seed content (tranquil CONTRIBUTING.md, pds.js docs/endpoint-comparison.md). - Socialize: post the plan to the atproto community discourse, bnewbold's dev-tooling discussion (bluesky-social/atproto#2754), and the IETF ATP WG list. Bluesky's Spring 2026 roadmap names the need for exactly this tool.
- Feed findings upstream: the WWW-Authenticate spec-vs-reference divergence and the undocumented headless-OAuth requirements (sec-fetch-mode, DPoP nonce two-step, the
rememberdevice-binding flag; seedocs/interop-traps.md) belong in the spec or atproto-interop-tests, not only here.
Done when: at least one external maintainer has co-signed a profile file.