BLACKOUT v3.7: extend v3.6 (job c379f49a, same repo). NO DEPLOY. Keep v3.6 unless changed below.

X: https://x.com/IMDBlackout | Site: playblackout.xyz | Free pack: https://playblackout.xyz/freepack

PROBLEM: the IMD swarm has no signing wallet. Its only on-chain voice is the IMD oracle: Intake (Robinhood Chain 0xa43e6f75ee006411f79ac1c84120606c2330de82), IntakeDelivery for results bought on Ethereum (0xce0e6a670aa75e161d02aca3c7f00b94ca428ccb), answers attested by the IMD Intake writer (EIP-712, OracleAttestationConsumer pattern, requestWithFailure). Follow the current IMD docs (imd.fun/docs) exactly; verify addresses and interfaces from the docs, do not guess.

GOAL: no admin wallet anywhere. The swarm role in every module is a new contract, SwarmDesk, driven only by attested oracle answers.

1. SWARMDESK

• Is the swarmWallet for Params, GridOperator, Civic, Enhancement, StarterClaim, Billboards and the dormant modules. No owner, no key, not upgradeable.
• Accepts only attested IMD oracle results (direct Intake callbacks and IntakeDelivery from Ethereum schedules). Verifies the attestation, request id, expected question id and freshness; ignores duplicates and stale answers.
• Every value is clamped to the existing hard-coded ranges; existing limits (10%/24h Params steps, 48h notice for features, 30-day enhancement cap steps, once-only actions) still apply.

2. QUESTIONS (paid by IMD schedules = the heartbeat)

• Event plan, every epoch (6h): answer as numbers (event kind, severity, district hint, random number). Applied to the next epochs exactly like submitPlan today. No answer = existing fallback table. Letters stay off-chain; the answer may carry a letter hash stored on-chain.
• Weekly regulator: numeric answers for bounded Params, feature announcements (feature id to announce) and enhancement cap steps. Applied only through the existing announce/notice paths.
• Document the exact oracle and schedule bodies (question text, answer format, cadence, cost) in launch-v37.md so the requester can create the schedules. Keep cost low: about 4 event questions per day plus 1 weekly regulator.
• Option for a keeper to trigger a paid ask from Robinhood Chain via Intake using an IMD balance held by SwarmDesk (topped up by anyone), as a backup to the Ethereum schedules.

3. REMOVE ADMIN ACTIONS AT LAUNCH

• Pack profile fixed to Balanced (1) at deploy; remove selectProfile.
• Free pack Merkle root and Identity MD starter root/snapshot passed as constructor arguments (the list is frozen before deploy); remove setFreeRoot. Keep the 30-day claim window.
• Billboard moderation: remove, or allow only via an oracle answer with the slot id.
• Endowment fallback must not rely on any swarm wallet; keep predicted RewardPool funding only, and document what to do if the launcher cannot pre-fund it.

4. GENERAL

• FarmCore headroom is ~246 bytes: keep SwarmDesk logic out of FarmCore.
• Tests: forged or wrong-signer attestations rejected, replay rejected, stale answers ignored, clamping, no-answer fallback, schedule delivery path, phased release via oracle, no remaining admin path anywhere (grep and test).
• Update keeper/ (trigger backup asks, show oracle status) and ui/ (show the last swarm answer and next epoch plan).
• Second contributor reviews the v3.7 diff. Report: changes, tests, oracle costs per day, launch-v37.md with ordered steps and job A/B objective drafts, open questions. No deploy, no broadcast, no token actions.