[Refactor] Timestamp-based deployment metadata & automated governance tracking

[clement-ux]

Summary

Replaces the manual proposalExecuted boolean with a timestamp-based metadata system, enabling historical fork replays, automated governance tracking, and removing the need for developers to manually update deployment scripts after governance passes.

Deployment Metadata Format

The Execution struct in DeploymentTypes.sol was redesigned from {name, timestamp} to:

struct Execution {
    string name;
    uint256 proposalId;    // 0 = pending, 1 = no governance needed, >1 = on-chain proposal ID
    uint256 tsDeployment;  // block timestamp when deployment script executed
    uint256 tsGovernance;  // 0 = pending, 1 = no governance needed, >0 = execution timestamp
}

All entries in build/deployments-1.json and build/deployments-146.json migrated to this format with actual on-chain proposal IDs and execution timestamps filled in.

Resolver Changes

Three new mappings added for O(1) lookups: proposalIds, tsDeployments, tsGovernances. The addExecution() signature updated to accept all four metadata fields.

DeployManager Rewrite

• Removed maxDeploymentFiles — now iterates ALL files, using new _canSkipDeployFile() to efficiently skip completed scripts without compilation
• Skip logic based on timestamps: skip if proposalId == 1 (no governance) or tsGovernance != 0 && tsGovernance <= block.timestamp (governance executed)
• _preDeployment() filters historical forks: entries with tsDeployment > block.timestamp are excluded, entries with tsGovernance > block.timestamp are reset to pending
• _postDeployment() serializes the three new fields instead of single timestamp

AbstractDeployScript Changes

• Removed proposalExecuted() virtual function
• Split _storeDeployedContract() into _storeContracts() (persists addresses) and _recordExecution() (records metadata)
• _recordExecution() must be called after _buildGovernanceProposal() — uses govProposal.actions.length to determine sentinel values
• Added public buildGovernanceProposal() for external proposal ID computation (used by UpdateGovernanceMetadata)
• Reordered execution steps: store contracts → build governance → record execution → handle proposal → fork logic

Removed proposalExecuted from All Scripts

The bool public override proposalExecuted = true/false declaration removed from all 19 deployment scripts (14 mainnet + 5 Sonic). Metadata now lives in the JSON files and is automatically maintained.

Automated Governance Metadata Updates

• script/UpdateGovernanceMetadata.s.sol — Standalone script that auto-fills pending governance metadata:
  • Case A (proposalId == 0): Deploys script artifact via vm.deployCode(), calls buildGovernanceProposal() to compute expected proposal ID, verifies it exists on-chain
  • Case B (proposalId > 1 && tsGovernance == 0): Uses FFI to query ProposalExecuted events and find execution timestamp
• find_gov_prop_execution_timestamp.sh — Bash helper using cast logs/cast find-block/cast block to locate proposal execution timestamps
• .github/workflows/update-deployments.yml — CI job running every hour (+ manual trigger), auto-commits updated build/deployments-*.json
• Makefile — New update-deployments target for local execution

Smoke Test Refactor

• Moved initialization from constructor() to setUp() so logs are visible on test failure
• All four concrete smoke tests updated to function setUp() public override with super.setUp() call

Other Changes

• Script 017_UpgradeLidoARMScript.s.sol fixed to use resolver.implementations("LIDO_ARM_IMPL") in governance proposal (works when called externally by UpdateGovernanceMetadata)
• New contract entries: MORPHO_MARKET_ORIGIN and MORPHO_MARKET_ORIGIN_IMPL
• Added missing execution entry for 013_UpgradeOETHARMScript
• Updated OETH_ARM_IMPL implementation address

Test plan

• make test-smoke passes with MAINNET_URL
• make simulate replays deployment history successfully
• make simulate with FORK_BLOCK_NUMBER_MAINNET set to a historical block replays correctly
• make update-deployments resolves pending governance metadata on mainnet fork
• CI workflow update-deployments.yml triggers and auto-commits correctly