chore: record approved pcr set

[0xOsiris]

Records the PCR set approved on the alphanet NitroAttestationVerifier into deployments/alphanet-nitro.json.

Written by just proof-approve-pcrs alphanet when the new enclave measurements were approved on-chain (tx 0x568c78da).

PCR0 5354c41cc47717d3843e9aff37d5b3cbd35d03e219ecce5a1e5498773d4d06df2b22a022a96e542a292ff5c9f01f9a07
PCR1 0343b056cd8485ca7890ddd833476d78460aed2aa161548e4e26bedf321726696257d623e8805f3f605946b3d8b0c6aa
PCR2 44eb23fd7c4c12048b27a4fa3ed157c366603c5e1298f7aaeb184c4b4438040a283a5a112282c6439552faffbd56ec7c

These are the measurements of the enclave EIF at sha-6ed502b. PCR1 is unchanged (same kernel); PCR0 and PCR2 moved because the EIF was rebuilt — the drift pattern #974 exists to detect.

Bookkeeping only, no behaviour change. Without it the deployments file cannot distinguish an approved allowlist from an empty one.

🤖 Generated with Claude Code

---

Note

Low Risk
JSON deployment metadata update only; no application or contract logic changes.

Overview
Adds a new approvedPCRSets entry to pkg/contracts/deployments/alphanet-nitro.json so the repo matches the PCR triple already approved on alphanet’s NitroAttestationVerifier (via just proof-approve-pcrs alphanet).

The new set is for a rebuilt enclave EIF (sha-6ed502b): PCR0 and PCR2 change; PCR1 matches the existing entry (same kernel). The prior PCR set remains in the array.

Bookkeeping only — no runtime or contract behavior changes; the file can now represent multiple approved allowlist entries instead of looking empty relative to chain state.

^{Reviewed by Cursor Bugbot for commit 14019fb. Configure here.}