Run one-time exact-SHA Platform production release

[RollNuts]

Operations-only purpose

This temporary release attempt is complete and intentionally not merged.

The public repository did not have RENDER_API_KEY, so the workflow stopped before any Render mutation. The canonical release later completed from RollNuts/veripsa-dev: preflight, Render promotion, production smoke, and aggregate deployment status all reported success for Platform commit b17d0a03ccf2b282a8bcd6215b4dbba796bb7ca0.

The head branch is being reset to main so no temporary deployment workflow or script remains on the branch.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[veripsa-core]

Veripsa — heading to main

❓ Unknown — not enough signal to call this clear

This PR reserves: .github/workflows/deploy-platform-b17d0a-20260719.yml, .github/workflows/deploy-platform-b17d0a-pr-20260719.yml, scripts/deploy-platform-b17d0a-20260719.py

New paths in this PR — coupling will be computable after merge. These paths are NEW in this PR, so there is no main-side graph to compare against yet (expected, not a warning): .github/workflows/deploy-platform-b17d0a-20260719.yml, .github/workflows/deploy-platform-b17d0a-pr-20260719.yml, scripts/deploy-platform-b17d0a-20260719.py. Veripsa will compute their coupling once this PR lands.

_{Veripsa records what is heading to main and who reserved what — it does not assert correctness. Advisory by default; your branch-protection policy decides what blocks.}