feat(bot): complete Worker migration and roster interactions

[MagicTheDev]

Summary

• Archive the tracked Python/disnake bot under archived/python and add the Cloudflare Worker runtime with signed Discord interactions, typed bindings, API client, and command routing.
• Complete /base publishing and legacy button conversion through the API-owned message and media contract; preserve idempotent conversion recovery.
• Move /link to a token-required modal and retain /unlink, with localized help and error responses.
• Add /roster selection, views, signup/withdrawal, posting, and confirmation-based ping flows. Roster writes remain scoped to the invoking actor and signed interaction, with server-side API checks as the final authority.
• Add localized command and response catalogs, local tunnel documentation/configuration, and an offline army-family research prototype with sample output. The prototype has no production data or write path.
• Keep the default cloud Wrangler config on cloud API/Dashboard URLs; the separate local config uses loopback API and local Dashboard, with optional user restriction for local testing.

Contract inputs and limits

The Worker depends on the corresponding API and schema PRs for roster publication, linking, and automation behavior. The offline army-family output is descriptive research and cannot be copied into the durable schema without identity/cohort review. No deployment, production command registration, or live Discord signup validation is claimed by this PR.

Validation

• worker: npm run check — 31 locales/95 keys, four command definitions, generated types, lint, TypeScript, 187 tests across 13 files, Wrangler dry-run build.
• research/army_family_local: python3 -m unittest test_prototype.py — four passed.
• git diff --check passed.
• Ignored .dev.vars, .env.dev, and Python caches were excluded from commits.

Current quality gate

SonarCloud was already failing on the full PR before this update: three findings in archived/python/Dockerfile (S8541, S8544, S7018) and 12.55% duplicated lines on new code in its last completed analysis. The new push needs reanalysis. No rule, gate, or exclusion was changed to bypass these results; the archive's treatment needs a separate reviewed decision.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.