release: record v0.0.301 cancellation and supersession disposition

[gltanaka]

Context

The release process started for v0.0.301 from commit
49504fc9aa11a9ee70539c93a6f1afe64badad94 after the full cloud gate passed on
rerun (77 passed, 0 failed, 0 errors). The tag exists, but the package release
workflow never started its job steps and was cancelled after waiting for the
pypi-publish environment.

• Tag: v0.0.301
• Release workflow: https://github.com/promptdriven/pdd/actions/runs/29142662507
• Workflow result: cancelled; publish-pypi had no executed steps
• PyPI publish: not performed
• GitHub Release: not created
• Discord release post: not sent

The next release, v0.0.302, contains one additional release-gate fix and
published successfully:

• Release: https://github.com/promptdriven/pdd/releases/tag/v0.0.302
• Workflow: https://github.com/promptdriven/pdd/actions/runs/29182331374
• Commit: 56f1601f5f821a11400b6e03e5c67345501bd2f3

The v0.0.301 release-video attempts also produced no publishable video:

• Initial PDS run: agent_run_82875fb7bf884818be2609abde84338e
  failed at compositions with internal_error.
• Retry PDS run: agent_run_2e7eea7391274071854ae48533b1d255
  failed at compositions after provider HTTP 429 usage-limit failures affected
  13 of 20 components (failure threshold: 3).
• No full video, distribution package, publish result, or YouTube URL exists.

Related defect tracking:

• PDD operator diagnostics: release-video: classify terminal PDS quota and audit-gate failures with actionable hints #1925
• GVS provider-limit lifecycle: https://github.com/promptdriven/Generative-Video-Studio/issues/1238

Decision needed

Confirm that v0.0.301 is intentionally abandoned and superseded by the
successfully published v0.0.302. Publishing v0.0.301 after v0.0.302 would
be an out-of-order package release and should not happen without an explicit
release-owner decision.

The documented make release-video-skip marker cannot be used because no
GitHub Release exists for v0.0.301.

Acceptance criteria

• The release owner records whether v0.0.301 is superseded or must be
  recovered.
• If superseded, the cancelled PyPI workflow is not rerun and no GitHub Release
  or Discord post is fabricated for v0.0.301.
• The retained cloud-test, release, and PDS evidence remains available in the
  release worktree for auditability.
• Quota and delayed-terminal-status defects remain tracked in the linked PDD
  and GVS issues rather than duplicated here.