fix: make historical release recovery actionable

[hatayama]

Summary

• Formalize owner-assisted recovery for historical release targets.
• Guide operators when recovery-target tag or draft-release creation is rejected with GitHub's 403 integration error.

User Impact

• Future release recovery failures identify the cause and point to an executable runbook instead of requiring rediscovery of the workaround.
• The runbook covers native CLI recovery, dispatcher concurrency, runner-first package release sync, and workflow-dispatch cleanup.

Changes

• Add docs/release-recovery-runbook.md with the confirmed reproduction evidence from runs 29459199798 and 29459266044.
• Preserve the existing native release creation and reuse flow; add recovery-only guidance for 403 failures from tag and draft release creation.
• Confirm dispatcher-publish has no historical-target creation path and cover the package sync historical-release path in the runbook.

Verification

• go test ./internal/architecture -run 'TestWorkflowActions|TestPullRequestWorkflow' -count=1 from cli/release-automation
• Ruby YAML parse
• bash -n for the modified native publish step
• git diff --check
• PR fix: make historical release recovery actionable #1799 review: CodeRabbit approved; advisor final review LGTM

The recovery guidance path cannot be fully E2E-tested without an actual historical release recovery. The next real recovery will validate the complete workflow; this PR validates the error handling and documented owner-assisted procedure.

[coderabbitai]

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 88c3bcfd-c415-4ace-be5b-f7e1da30a3a6

📥 Commits

Reviewing files that changed from the base of the PR and between 65326cd and 84fb02a.

📒 Files selected for processing (1)

• scripts/test-native-cli-publish-workflow.sh

📝 Walkthrough

Walkthrough

The publish workflow now captures historical-commit tag and draft-release failures and emits recovery guidance. A runbook documents owner-authenticated commands and follow-up steps for completing native, Unity package, and workflow-dispatch recovery.

Changes

Historical Release Recovery

Layer / File(s)	Summary
Publish error handling .github/workflows/native-cli-publish.yml	Recovery mode is passed into draft release creation, while tag and draft-release API failures are captured and matched against restricted-integration errors.
Manual recovery procedure docs/release-recovery-runbook.md	Documents the historical-commit restriction and procedures for creating tags and drafts, rerunning jobs, handling concurrency, recovering package releases, and completing workflow dispatch recovery.

Estimated code review effort: 2 (Simple) | ~15 minutes

Possibly related PRs

• hatayama/unity-cli-loop#1799: Directly overlaps the workflow error handling and recovery runbook changes.
• hatayama/unity-cli-loop#1790: Modifies the same draft-release and tag handling flow.
• hatayama/unity-cli-loop#1797: Introduces the recovery-target publishing flow refined by these changes.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: making historical release recovery actionable.
Description check	✅ Passed	The description is directly related to the recovery workflow, runbook, and error handling changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/recovery-403-fix-integration

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}