chore: prepare API 0.8.0-rc.44

[adrianwebb]

Outcome

Prepare the verified account-deletion concurrency fix for API RC 0.8.0-rc.44.

Work authority

• Work item / Issue: Validate account deletion confirmation before claiming revision #121 and fix(api): preserve account revision on invalid deletion #122
• Proposal / decision: Approved Admin/Core/UI/Reviewer migration plan in the active Codex task
• Assignment / checkpoint: Browser guarantee proof 65, 20/20 passed
• Actor: codex-root
• Human authority: @adrianwedd
• Agent / capacity provider: Codex local development session dev-f9dfe127-231
• Exact base ref: staging a3335d0
• Exact head ref: codex/api-0.8.0-rc.44 0f0a158

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Bump only package release metadata after the verified staging merge, then tag the exact staging merge commit.

Changes and commits

• 0f0a158 prepares 0.8.0-rc.44.

Verification

• I ran the narrowest relevant package verification and documented any checks that could not be run.
• Source PR fix(api): preserve account revision on invalid deletion #122 verify, authorization, and durable-record checks passed.
• Integrated Reviewer browser graph proof 65 passed 20/20.

Risk and rollback

Metadata-only release bump. Roll back by deleting the prerelease tag before consumption or pinning the previous exact RC 0.8.0-rc.43.

Completion summary

Ready to merge to staging and tag the exact merge commit as 0.8.0-rc.44.

AGPL committer authorization

The base-owned workflow checks the provider-authenticated pull-request author against .github/approved-committers.json.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.