GitLab + Bitbucket mirrors not operating — intentional or unfinished setup? #302

What I found

Empirical check of `.github/workflows/mirror.yml` (in both `affinescript` and `casket-ssg`, and the aggregator `repos-monorepo`):

• All recent runs report `completed/skipped`. Both jobs (`mirror-gitlab` and `mirror-bitbucket`) are gated by `if: vars.GITLAB_MIRROR_ENABLED == 'true'` / `BITBUCKET_MIRROR_ENABLED == 'true'`.
• Neither variable is set at the repo level on `affinescript`, `casket-ssg`, or `repos-monorepo`. (I can't see org-level vars from a non-admin token.)
• Repo-level secrets on each: only `FARM_DISPATCH_TOKEN`. No `GITLAB_TOKEN` or `BITBUCKET_TOKEN`.
• Live probes:
  • `https://gitlab.com/hyperpolymath/` → HTTP 302 (sign-in redirect / private / not-found)
  • `https://bitbucket.org/hyperpolymath/` → HTTP 404 (doesn't exist)
• Interesting contrast: `repos-monorepo` does have `CODEBERG_MIRROR_ENABLED` and `RADICLE_MIRROR_ENABLED` set as repo variables, suggesting those forges are the actively used mirror destinations.

The question

Two possibilities:

1. Intentional — Codeberg + Radicle are the active forges; GitLab + Bitbucket were the original plan but the move replaced them. In that case, `mirror.yml` is dead code; close-and-delete (or move to a separate `mirror-archived.yml`) so the skipped jobs don't keep showing up on every push.
2. Unfinished setup — GitLab + Bitbucket mirrors are still wanted but never had their vars/secrets configured. Owner needs to:
   • Set `GITLAB_MIRROR_ENABLED=true` / `BITBUCKET_MIRROR_ENABLED=true` (per repo or org-wide)
   • Add `GITLAB_TOKEN` (GitLab PAT, `write_repository` scope)
   • Add `BITBUCKET_TOKEN` (Bitbucket app password)
   • Pre-create the projects if the tokens don't have create-on-push privilege

Why filed

Visible noise (`mirror.yml` skipping on every push) + ambiguity over forge strategy. One-line decision either way.

Discovered while triaging `repos-monorepo#9` (nested mirror coherence) — see this PR's discussion for the original context.