NEW Sepolia workflow for PvPad ONE-SHOT v3 (replacement for failed launch-138 deploy and blocked 1899c31b / launch 137). Build Foundry contracts with tests, adversarial review, deploy on Sepolia as univ4_hook, then publish website site label pvpad. First token MUST be PVP (name Pepe Values Pepe, ticker PVP) with mandatory 10^27 minor-unit mint. FACTORY-COMPATIBLE HOOK (mandatory, this is why 138 failed): the IMD factory launch() deploys token, CREATE2s the hook, then calls PoolManager.initialize with the factory as sender and seeds LP. PvPadHook MUST NOT use beforeInitialize. FORBIDDEN: any beforeInitialize permission; any require that pad be bound before initialize; any OnlyPad/NotBound check inside beforeInitialize. Permissions MUST be swap-path only, BurnHook-style, so factory initialize succeeds. Recommended: beforeSwap, afterSwap, and beforeSwapReturnDelta (CREATE2 flags matching those bits). CRITICAL ATTESTATION RULE: hook.constructorArgs in launch.json may contain ONLY literal addresses or integers. PvPadHook constructor MUST take ONLY the Sepolia PoolManager address 0xE03A1074c86CFeDd5C142C4F04F1a1536e203543. FORBIDDEN in launch.json constructorArgs: any placeholder such as $pad, $token, $pvp, $king, $subsidy, or sibling-contract names. ECONOMICS LIVE IN THE HOOK (mandatory one-shot): do NOT require separate KingOfThePad, WorkerSubsidy, PvPadFeeRouter, or PvPad contracts to be deployed by the factory. Collapse king claim, swap fees, and worker merkle drip into PvPadHook itself (one contract). Optional external pad router is OUT OF SCOPE for this workflow and must not block launch or attestation. forge test must pass including a local simulation where PoolManager.initialize is called with a non-pad sender (factory-shaped) and succeeds.