Update shared CI workflows to v0.2.0

[zhongkechen]

Summary

• Pin the shared AI review, issue triage, and Slack notification workflows to the immutable v0.2.0 commit.
• Grant GitHub Models read access for AI-generated Slack summaries.
• Grant the Bedrock issue-triage workflow OIDC and contents access, and inherit the ai-pr-review-runtime environment secret.

Testing

• Parsed the changed workflow files with PyYAML.
• Ran git diff --check.

[github-actions]

Claude AI review

No actionable findings.

This PR is a CI-only change that bumps three reusable-workflow pins from 71259cf476e37255752d8f9445a1a48ec92be1df to ac55d9f4b027e193aba9fa5a69c70bfa1bdc38ed and grants matching least-privilege permissions:

• ai-pr-review.yml — pin bump only; permissions and secrets: inherit unchanged.
• issue-triage.yml — adds contents: read + id-token: write to the triage job and secrets: inherit, matching the described Bedrock OIDC triage runtime.
• notify.yml — adds a job-level permissions block with contents: read + models: read, matching the described GitHub Models Slack-summary feature.

I confirmed the base branch pinned all three files to the old SHA and that the PR moves all three to the same new SHA, so the bump is consistent with no stragglers left behind. All permission scopes used are valid GitHub Actions token scopes and the YAML structure is well-formed. No SDK/runtime code is touched, so replay determinism, serialization, concurrency, and public-API compatibility are not affected.

Residual test risk: the effective behavior depends on the external aws/aws-durable-execution-ci reusable workflows at the newly pinned SHA, which cannot be inspected from this repository. Whether that revision actually corresponds to v0.2.0 and whether it requires exactly this set of permissions/secrets can only be validated by triggering the workflows (or reviewing the upstream CI repo at that commit). The PR notes verification was limited to PyYAML parsing and git diff --check.

Reviewed commit 655600e9054cfd0a119a38fab57028e8f7f2f181. Workflow run

[github-actions]

Codex AI review

No actionable findings. Residual risk is limited to runtime integration with the externally referenced reusable workflows, which is not exercised by repository tests.

Reviewed commit 655600e9054cfd0a119a38fab57028e8f7f2f181. Workflow run