GitHub Actions masks the link to the created Bluesky post

Because the Bluesky username comes from an environment variable, it is presumed to be a secret and it ends up masked in the logs where we log the URL to the post created. This makes the log almost useless.

No file or test is named. Start by locating the GitHub Actions workflow that creates the Bluesky post and logs its URL, then reproduce the masking behavior. Done means the created-post URL is useful in logs without exposing the secret username.

Written by the indexing model from the issue text.