Routing and upgrades

Routers own the market proxies they deploy. Updating an implementation pointer affects future deployments; an existing proxy requires its explicit upgrade path. Upgrade review must compare populated storage, namespaced/assembly storage conventions, initializer or migration calldata, immutable bindings, runtime bytecode, and all route and authority relationships.

A Perp route replacement requires the AccountCore market to be disabled and an off-chain proof that the old book is drained. The contract does not enumerate all old orders to prove this itself. Close old implementation and route intervals at the exact authoritative log position; never decode historical logs using only the latest implementation.