docs(procore): update stage 3 evidence after migration apply

[mcxl]

Summary

• Refreshes Stage 3 Procore evidence after PR docs(procore): refresh stage 3 evidence after hardening #30 and the Supabase migration apply.
• Records applied Supabase migrations 20260618025557 / 007_procore_webhook_deliveries and 20260618025643 / 008_procore_audit for project rpd-pims / nebdpofqglfyfyqqodni.
• Keeps remaining Procore gates explicit: auth/signature scheme, OAuth/DMSA grant/scopes, write-back resource/path/API version, delivery_id/ulid payload location, production env rollout.

Verification

• git diff --check
• python -m pre_commit run --files docs/procore/STAGE3_CERTIFICATION_PLAN_V2.md docs/procore/TRACK_A_COMPLETION_REPORT.md
• pre-push full suite passed

Notes

• Docs only. No app code changed.
• No migrations applied in this PR.
• Supabase runtime smoke is not claimed; it remains an optional explicit-approval checkpoint because it writes synthetic rows.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ec2c707e4a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".