Acceptance criteria

• Hook isolates every PoolId, supports arbitrary currencies, uses bounded observation ring/TWAP and EWMA volatility, adaptive price-deviation limits and rolling volume budgets resistant to split swaps. Define NORMAL/WARMUP/GUARDED/RECOVERY, stale/low-liquidity behavior and deterministic recovery; initialization/warmup cannot brick the pool and LP exits remain possible. Breaker transitions must not rely on reverted writes.

• Authenticate canonical PoolManager callbacks/accounting; never trust sender/hookData identity. Specify both directions, exact-input and exact-output, units, rounding, caps and bounded execution. No discretionary admin powers or claims of total MEV protection. Verify Sepolia PoolManager 0xe03a1074c86cfedd5c142c4f04f1a1536e203543 and existing verified periphery; no newly deployed helper.

• VolatilityGuardToken is Volatility Guard Lab (VGL), 18 decimals, no constructor arguments, fixed 10^27 units minted to deployer, no mint backdoor. Pair native ETH (zero address) with VGL using static fee 3000, tickSpacing 60, initial sqrtPriceX96 792281625142643375935439503360000 (0.00000001 ETH/VGL); document the exact sorted pool key and hook permissions.

• Preserve all token/hookAdmin/treasury/LP owners as 0x09ec38170e94532eddb57c69dfc4f1fdcd0d4a60, with no extra admin behavior. Supply allocations: 80% LP, 10% treasury, 10% contributors, 1h contributor lock and 30% per-wallet cap. Launch specification uses resolved Sepolia univ4_hook policy v2, not worker-chosen ownership or policy.

• Factory seeds up to 8e26 VGL units and ZERO ETH. Document/test the deployer derivation of widest aligned token-only range from opening price/spacing, rounding liquidity down. Gas comes from configured deployer under existing 0.3 Sepolia ETH ceiling; no additional funding/spending authority. No worker keys or broadcasts.

• Pinned/vendored ordinary files support network-free build, test and fmt with bytecode_hash=none, no submodules. Run meaningful fuzz/invariant/stress coverage for accounting, isolation, manipulation/split volume, unauthorized callbacks, reentrancy, stale history, edge values, recovery and LP exits, including swap modes/directions; record actual counts, gas, sizes, failures and limitations in docs/contract-evidence.md.

• Export valid ABI JSON at docs/abi/VolatilityGuardHook.json and docs/abi/VolatilityGuardToken.json. Deliver architecture/threat-model docs and docs/integration.md defining dashboard reads/events, units, exact pool key, quote/swap/liquidity recipes, supported-position exits and decoded errors. Explain token-only bootstrap and accrued-ETH limits for reverse swaps; evidence contains no fabricated receipts.

Acceptance criteria

• Review directly covers the contracts writer and the generated manifest, checks per-pool isolation, callback authentication, units/rounding, all swap modes, manipulation/split volume, bounded execution, stale/low-liquidity recovery, reverted transitions, initialization and LP exits; assess meaningful fuzz/invariant/stress evidence and remaining limitations.

• Check token supply/ownership/allocations/lock/cap, canonical Sepolia PoolManager, verified periphery, hook permission bits, exact ETH/VGL pool key/opening price and token-only range/liquidity arithmetic against the approved requirements. Confirm zero ETH seed, 8e26 VGL seed ceiling, 0.3 Sepolia ETH gas ceiling and no extra admin powers, helpers, funding or mainnet authorization.

• Validate offline reproducibility, ABI/documentation consistency and manifest source/bytecode linkage. Clearly report findings, evidence and limitations; all blocking findings must be repaired by the author and independently cleared before the control plane deploys. The reviewer neither edits files nor broadcasts.

Acceptance criteria

• Validate deployment handoff chainId 11155111, addresses, pinned source and ABI hashes against docs/abi and integration docs; use actual deployments only. Injected wallets work without extra credentials. No worker keys, broadcasting deployments, new helpers, fabricated quotes or fabricated receipts.

• Provide hook explanation and candid risk/limitation information without total-MEV-protection claims; live pool dashboard shows tick/TWAP, volatility, deviation, rolling volume, state and events with accurate units and unavailable/stale/RPC states.

• Primary ETH/VGL swap UI supports amounts, direction, balances/max, real quotes, slippage/minimum received, necessary approvals, wallet-signed swaps, transaction progress/errors and explorer links. Implement against documented verified periphery and actual pool; expose actionable decoded guard errors.

• Explain and handle token-sided bootstrap: buy with ETH first and allow reverse trades according to accrued ETH liquidity. Provide supported-position exits and clearly labeled simulation demos, distinct from actual quotes/transactions.

• Test both swap directions, wallet connection and chain states, rejected signing, guard reverts, insufficient funds/RPC failures and responsive UI. Record actual results/limitations in docs/frontend-evidence.md; validate production build and relative asset paths for the committed dist/ export. No service publication receipts or live URL are worker prerequisites.

File scope: web/**, dist/**, docs/**

Acceptance criteria

• Final review joins both writers directly and confirms contract-review clearance, manifest/deployment/ABI consistency and source linkage through the actual frontend configuration. Review wallet-signed transaction construction, quote/slippage/approval behavior, supported exits and dashboard units/events against contract interfaces.

• Inspect frontend tests and export alongside contract evidence; confirm bootstrap behavior, risk explanations and simulation labeling, complete required deliverables, and absence of fabricated results. Confirm frontend writes are limited to web/, dist/ and docs/** and root configuration remains protected.

• No unresolved blocking findings remain after author repair/recheck. Report limitations without expanding behavior or authorization. Handoff is ready for control-plane publication of real source, receipts, test evidence and site under the configured GitHub/Pinata destinations; service validation owns overall launch completion.