Approved workflow

Retest the complete swarm by building and launching VolatilityGuard Lab on Sepolia: VolatilityGuardHook, VolatilityGuardToken, independent adversarial review, verified factory deployment with a seeded pool, then a working public swap dapp with explanatory information. Publish real source, receipts, test evidence and the live site.

Hook: per-PoolId isolation; bounded observation ring/TWAP and EWMA volatility; adaptive price-deviation limits; rolling volume budget resistant to split swaps; NORMAL/WARMUP/GUARDED/RECOVERY states, stale/low-liquidity handling and deterministic recovery. Authenticate canonical PoolManager callbacks/accounting, never trust sender/hookData identity. Specify both swap directions and exact-input/output, units/rounding, bounded execution and caps. Keep LP exits possible and initialization/warmup non-bricking. Reverts cannot persist breaker transitions. No discretionary admin powers or claim of total MEV protection. Support arbitrary currencies.

VGL: Volatility Guard Lab, 18 decimals, no constructor args, fixed 10^27 units minted to deployer, no mint backdoor. Native ETH pair (zero address), static fee 3000, tickSpacing 60; initial sqrtPriceX96 792281625142643375935439503360000 (0.00000001 ETH/VGL). Verify Sepolia PoolManager 0xe03a1074c86cfedd5c142c4f04f1a1536e203543. Use only existing verified periphery, no new deployed helper. Workers never receive keys or broadcast deployments.

Deliver pinned/vendored Foundry project, bytecode_hash=none, offline build/test/fmt checks, fuzz/invariant/stress tests for accounting, isolation, manipulation/split volume, unauthorized callbacks, reentrancy, stale history, edge values, recovery and LP exits; report actual counts, gas, failures and limitations. Independent reviewer checks code AND launch manifest; repair blocking findings before deployment. Export ABI JSON and architecture/threat-model/integration docs with exact pool key, quote/swap/liquidity recipes and decoded errors.

After verified deployment handoff, build React/Vite/TypeScript + RainbowKit/wagmi/viem in web/, committed relative-base export in dist/. Include hook explanation, risk/limitation information and live pool dashboard (tick/TWAP, volatility, deviation, volume/state/events). Primary ETH/VGL swap UI: amounts, direction, balances/max, real quotes, slippage/minimum received, approvals and wallet-signed swaps, transaction states/errors/explorer links. Support injected wallets without extra credentials. Handle token-sided bootstrap: buy with ETH first; reverse trades depend on accrued ETH liquidity. No fabricated quotes or receipts. Add supported-position exits and clearly labeled simulation demos. Test both directions, wallet/chain states, rejected signing, guard reverts, funds/RPC errors and responsive UI. Complete only when contracts are live, source published and the functional IPFS dapp is reachable.

Resolved operator settings, not planner choices: Sepolia univ4_hook policy v2. All token/hookAdmin/treasury/LP owners: 0x09ec38170e94532eddb57c69dfc4f1fdcd0d4a60; no extra admin behavior. Supply splits: 80% LP, 10% treasury, 10% contributors (1h lock, 30% per-wallet cap). Factory seeds up to 8e26 VGL units, ZERO ETH: deployer derives widest aligned token-only range from opening price/spacing and rounds liquidity down. Gas from configured deployer under existing 0.3 Sepolia ETH ceiling; no additional funding or spending authority. GitHub destination is the existing signed publisher's configured org with automatic launch repository naming; IPFS uses its configured Pinata service and automatic naming. No caller repo/CID needed; both services are online. Contracts/tests -> auto manifest + independent review -> verified deployment -> frontend-for-contract -> publication. Max five proposed steps; manifest adds sixth. DeFi references are background, not separate research. Never mainnet.

Implement the original request using these shared interfaces and integration agreements: Sequential handoffs: contracts produces a complete offline Foundry project, docs/abi/VolatilityGuardHook.json, docs/abi/VolatilityGuardToken.json, and docs/integration.md with exact pool key, units/rounding, public state/events, decoded errors and verified-periphery quote/swap/liquidity/exit recipes. The control plane generates the launch manifest before contract review; it occupies the integration slot. Review gates verified factory deployment; blocking findings return to their author for repair and independent recheck. Frontend also waits for actual .imd/reads/deployment.json with verified addresses, pinned source and ABI hashes, never guessed deployment data. Frontend is the final integration step: checks the reviewed contract/deployment handoff against web/ source and dist/ export, and delivers docs/frontend-evidence.md. Writers are sequential; review is read-only. Only Sepolia chainId 11155111 univ4_hook policy v2 is authorized, never mainnet. GitHub publication uses the existing signed publisher configured org and automatic repository name; IPFS uses configured Pinata and automatic naming. No caller repository/CID or new credentials are required. Control plane owns manifest generation, deployment/verification, source/receipts/test-evidence publication, hosting and reachability checks; workers never receive keys or broadcast. Completion of the overall launch requires live contracts, published real source and a reachable functional IPFS dapp, verified by those services.

After independent contract clearance AND actual verified deployment handoff at .imd/reads/deployment.json, build the complete responsive public VolatilityGuard Lab swap dapp using React/Vite/TypeScript and RainbowKit/wagmi/viem. Keep all frontend source, package.json, lockfiles and build configuration in web/, committed relative-base static export in root dist/, and documentation in docs/ or web/. Root configuration/lockfiles remain protected.

Use pinned deployed addresses and ABI hashes with verified existing periphery. Deliver source, export and meaningful tests/evidence; the control plane publishes and validates the live site. Finish by validating the integrated dapp against the reviewed contracts, manifest and actual deployment; repair frontend integration failures within this scope.