W05b: remove DEVICE_COMMAND_OFFLINE_QUEUE_ENABLED flag and W01 compatibility aliases (offline work queue #5131)

[ToddHebebrand]

Deferred remainder of Wave 5 of the offline work queue (parent #5131, spec #5128, plan docs/superpowers/plans/misc/2026-09-06-offline-work-queue.md § Wave 5 / "W05b").

W04 (#5243) flipped DEVICE_COMMAND_OFFLINE_QUEUE_ENABLED to default ON. Nothing from W01–W05 has shipped in a release yet, so the flag stays as the operator opt-out until customers have seen queueing behave in production.

Do this one release after the first release that contains W01–W04 (expected v0.111):

• Remove DEVICE_COMMAND_OFFLINE_QUEUE_ENABLED and isOfflineQueueEnabled() (apps/api/src/services/commandOfflinePolicy.ts) and every caller/test that sets it; drop it from .env.example, docker-compose.yml api env block, and apps/docs/.../deploy/environment.mdx.
• Remove the previouslyRejected option.
• Remove the decryptClaimedCommandsForDelivery alias.
• Delete the SW_INSTALL_COMMAND_ID_REGEX fallback if no in-flight frames from pre-W01 agents can remain.
• Commit: chore(commands): remove offline-queue flag and W1 compatibility aliases (#5128 W5)

Optional low-priority docs follow-ups noted by W05: audit-baselines.mdx and sensitive-data.mdx may still carry stale offline-device claims (unverified); 4 of the 10 aiTools*.ts files have a dead requireOnline: true branch (pre-existing, harmless).

🤖 Generated with Claude Code

https://claude.ai/code/session_01F1Ywn7RzqkTd1MghTp9wDH