Validate Perps Multiproject

Validate one perps change across multiple local MetaMask repo checkouts.

Canonical direction: a CLIENT validates a CORE controller change. The @metamask/perps-controller package lives in Core; Mobile and Extension consume it. The owner is wherever the controller change is; the targets are the clients that must not break. (Client↔client parity is a secondary mode — see below.)

Deterministic layer — use scripts/perps-validate.sh

Do not re-derive the per-folder commands each run. scripts/perps-validate.sh encodes them and is portable across machines and Node managers. Run it in order:

SC="$(dirname "$0")/scripts/perps-validate.sh"   # or the skill's scripts/ path