Elliot

> For performance reasons I would suggest only running the monorepo tests in CI on some schedule (e.g. every 4 hours) to avoid having to wait multiple minutes to simulate...

> For performance reasons I would suggest only running the monorepo tests in CI on some schedule (e.g. every 4 hours) to avoid having to wait multiple minutes to simulate...

Where should we look in the superchain registry to find the OPCM address? I could not find it anywhere when searching the repo except in this test json file https://github.com/ethereum-optimism/superchain-registry/blob/210c8ea3cde825aad0c11a02f37fa94eae47ff59/ops/internal/report/testdata/deployer-state.json#L57

Looks like the oz foundry-upgrades package is running the oz-upgrades npm package under the hood https://github.com/OpenZeppelin/openzeppelin-foundry-upgrades/blob/main/src/internal/Core.sol#L371-L376

This issue should not block mainnet as this is a small refactor/cleanup.

We should come back to the docs and update all the path references to ensure they're right at some point when paths change.