chore: sync workflow templates

[stranske]

Sync Summary

Files Updated

• maint-76-claude-code-review.yml: Claude Code review (opt-in) - runs only on labeled PRs or manual dispatch

Files Skipped

• .github/workflows/pr-00-gate.yml: Maintains a fully custom Gate workflow; never overwrite (replaces the hard-coded custom_gate_repos list in maint-68).
• ci.yml: File exists and sync_mode is create_only
• renovate.json: File exists and sync_mode is create_only
• cross-repo-smoke.yml: File exists and sync_mode is create_only
• llm_slots.json: None

---

Review Checklist

• CI passes with updated workflows
• No repo-specific customizations were overwritten

Source: stranske/Workflows
Source SHA: 81ebbaa8d6305afea1f2e882e9bfb3498947dfbc
Template hash: 3c1693c56d44
Sync branch: sync/workflows-3c1693c56d44
Consumer repo: stranske/Manager-Database
Manifest: .github/sync-manifest.yml

Summary by CodeRabbit

• Chores
  • Updated the pinned version of the code review automation used in the repository.
  • Kept the workflow behavior and review process unchanged otherwise.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c9e8e50a-cef1-4781-a554-71754933b274

📥 Commits

Reviewing files that changed from the base of the PR and between 4b9698f and 79c1769.

📒 Files selected for processing (1)

• .github/workflows/maint-76-claude-code-review.yml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• stranske/Workflows (auto-detected)
• stranske/Template (auto-detected)

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (3)

**/.github/workflows/**/!(*.md)

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

For workflow_call reusable workflows, do not use top-level permissions: block as it conflicts with caller permissions (documented in docs/INTEGRATION_GUIDE.md)

Files:

• .github/workflows/maint-76-claude-code-review.yml

**/.github/workflows/*.{yml,yaml}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

For startup_failure in workflows with zero jobs, check for invalid YAML syntax, invalid permission scopes, top-level permissions block on workflow_call, or circular workflow references

Files:

• .github/workflows/maint-76-claude-code-review.yml

.github/workflows/*.yml

📄 CodeRabbit inference engine (CLAUDE.md)

.github/workflows/*.yml: In this consumer repository, keep most workflow logic in stranske/Workflows and only carry repo-specific configuration unless explicitly documented as an exception
First-party consumers should reference reusable workflows with @main unless intentionally pinning to an exact commit SHA for a controlled reason

Reference reusable workflows with @main in first-party consumers unless intentionally pinning to an exact commit SHA for a controlled reason

Files:

• .github/workflows/maint-76-claude-code-review.yml

🔀 Multi-repo context stranske/Workflows, stranske/Template

Linked repositories findings

stranske/Workflows

• docs/HISTORY.md:159 and docs/HISTORY.md:466 mention maint-76-claude-code-review.yml as a consumer-side workflow, which confirms this pinned-action change is meant to flow into consumers rather than alter shared runtime code. [::stranske/Workflows::]
• The repo’s workflow inventory includes no direct maint-76-claude-code-review.yml file, so this repo does not appear to be the template source for the change. [::stranske/Workflows::]

stranske/Template

• .github/workflows/maint-76-claude-code-review.yml exists in the template repo, so this is the template file to compare against for sync drift / pin updates. [::stranske/Template::]
• The workflow inventory also shows this repo contains the same maint-76-claude-code-review.yml, confirming the change is in the shared template surface, not a repo-specific override. [::stranske/Template::]

🔇 Additional comments (1)

.github/workflows/maint-76-claude-code-review.yml (1)

192-192: 🔒 Security & Privacy

Pin is aligned with v1. 74eedf1a1892082d619c3edb66b9402da6520e7f is the commit behind the v1 tag, so the # v1 comment is consistent.

---

📝 Walkthrough

Walkthrough

The pinned commit SHA for anthropics/claude-code-action in the claude-review job's "Run Claude Code Review" step of .github/workflows/maint-76-claude-code-review.yml is updated from one hash to another. No other workflow logic or step inputs are changed.

Changes

Action Pin Bump

Layer / File(s)	Summary
Update claude-code-action commit SHA .github/workflows/maint-76-claude-code-review.yml	The uses: reference for anthropics/claude-code-action in the claude-review job's "Run Claude Code Review" step is updated to a new pinned commit hash. All other step configuration remains unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• stranske/Manager-Database#1163: Updates the same workflow step (maint-76-claude-code-review.yml) by changing the pinned anthropics/claude-code-action commit hash with no other changes.
• stranske/Manager-Database#1242: Updates the same workflow file and the same claude-review job step's pinned commit hash for anthropics/claude-code-action.
• stranske/Manager-Database#1247: Updates a GitHub Actions workflow step to a different pinned commit SHA with no other logic changes.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the PR’s main change: syncing workflow templates from the source repository.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sync/workflows-3c1693c56d44

---

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