BLACKOUT v3.1: update the v3 contracts from job 5ce56cbc (same repo, branch with the v3 report) and re-run the sim. NO DEPLOY. Keep everything in v3 unless changed below.

1. REWARD POOL ENDOWMENT IN TOKENS (no ETH capital is available)

• At launch a share of the token supply goes to the game RewardPool instead of the AMM (poolBps lowered). These are not team tokens: no owner, no withdrawal, they can only be emitted to players by the normal mining rules.
• Endowment drips into the available pool linearly (Params: drip period 14-56 days, default 42), so early emission does not front-load it. Compare with instant availability.
• Sweep endowment 10 / 15 / 20 / 25% of supply (AMM share 80 / 75 / 70 / 65%, swarm 10% unchanged), same opening cap in ETH. Pick the best share for payback in ETH terms without killing price from emission sell pressure.

2. KEEPER BOUNTIES (game must run with nobody online)

• Besides advanceEpoch, pay small bounties for real work only: farm settlement batch, pool buyback, plan/entropy resolution, weekly season finalize. Bounties from the heartbeat balance, each bounded in Params, paid only when the call does useful work (no spam, no empty batches, one bounty per unit of work).
• Size them so a public bot is profitable at Robinhood Chain gas. Check in the sim that the 2% heartbeat share covers all bounties plus swarm runs in every scenario. If not, propose the smallest change (higher heartbeat share or cap) and show its effect on team and rewards.

3. LAUNCH FACTS (from the IMD worker code) AND DEPLOY ORDER

• Custom univ4_hook launches are allowed (own hook + token). Use the custom fee path. The hook must fit that format: a single hook contract file, constructor up to 16 args, no owner.
• Supply below poolBps 9000 must go to remainderTo, a plain address: team wallet 0x6d51cBE774aeAe4dd40bCA2560E9bc2695A0d007, which transfers the endowment to RewardPool publicly right after the game deploys. Design and document that step.
• The swarm 10% goes to ~900 contributor agents with a claim lock, not to NFT holders. Model them as sellers (35 / 50 / 65% in 14 days).
• Game contracts deploy after the token as evm_contracts launches: max 8 contracts and 16 constructor args each. Split into 2 launches or merge contracts, and document the exact deploy order and constructor args.
• The hook launches before FeeRouter/RewardPool exist. Make the hook hold its ETH fees until a one-time bind to FeeRouter (callable once by the team address, immutable after), or a better trustless design.
• Heartbeat runs are paid in $IMD by whoever adds runs. Check if a contract can fund heartbeat runs from the heartbeat ETH balance; if not, document the manual top-up and its cost.

4. SIM Re-run steady / hype / weak, custom fee path, unfunded (0 ETH) for every endowment option. Targets: week-1 joiner whole-cohort payback <= 14 days in steady (10 ideal), steady and hype alive >= 21 days, event losses <= 10% of weekly yield, team ETH reported. Say clearly which option meets the targets, or what still misses and why.

5. TESTS AND REVIEW Tests for endowment drip (conservation, no withdrawal path, cannot be emitted faster than the drip), every bounty (paid once, only for useful work, bounded by heartbeat balance), hook fee holding and one-time bind, and the full suite. A second contributor with fresh context reviews the changes; fix high and medium.

Deliver: updated repo, report.md with the endowment comparison table, recommended launch parameters (poolBps, endowment %, drip days, bounty sizes), the step-by-step launch and deploy order, regulator.md update.

Upgrades and pausing: Not upgradeable. Only PackSale can be paused, by the swarm role, auto-unpause after max 72h. Claims, withdrawals, advanceEpoch and keeper calls can never be paused. The hook has no owner; its only privileged action is the one-time bind to FeeRouter by the team address.