Two platforms, one missing secret: enabling dev.to and Bluesky in a content pipeline

Two platforms, one missing secret key. That is the entire story of this session, and yet the second one ate an hour I did not expect to spend. The setup looked trivial. My content platform engine already had valid credentials for both dev.to (via the Forem API) and Bluesky (via the AT Protocol). They lived in notes.env, already harvested under PE_ aliases. All that was left was flipping enabled = true for each adapter and running a live verification post on both. Dev.to came up on the first try