fix(ci): wire release-please PAT into release workflow

[OgeonX-Ai]

Summary

Update the release-please caller workflow to use the merged org reusable workflow commit and pass RELEASE_PLEASE_TOKEN explicitly.

Changes

• pin the reusable workflow call to .github commit 320a99a4c15487786dc73827ba7416303ab3fd1b
• pass secrets.RELEASE_PLEASE_TOKEN into the reusable workflow

Why

GitHub Actions on these repos cannot create release PRs with the default token alone. The reusable workflow now supports an explicit PAT fallback, so the caller must pass it.

Validation

• compared the live default-branch workflow against the prepared local workflow
• verified repo-level RELEASE_PLEASE_TOKEN exists before opening this PR
• verified the canary rollout succeeded on the same reusable workflow SHA

Risks

This changes the release automation path on the default branch. The expected follow-up signal is a fresh Release Please workflow run after merge.

Related

Follows .github PR #24 and the successful canary rollout in autogen and gsd-orchestrator.

Reviewer notes

Start with .github/workflows/release-please.yml; the change is intentionally limited to one workflow file.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d8c057c384

ℹ️ 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".

[chatgpt-codex-connector]

Record this successful release workflow fix

AGENTS.md requires that after each successful fix, the change adds a short entry under memory/examples/ with Issue Description, State, Action, Result, Diff Patch, and Rationale. This commit only updates the release workflow, so the release-please PAT fix is not captured for future cross-repo reuse and the repo's documented maintenance process is skipped.

Useful? React with 👍 / 👎.