chore(deps): update stranske/workflows digest to a335f1a

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
stranske/Workflows (changelog)	action	digest	62ed0a8 → a335f1a

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configuration for API client setup.

[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: 3ea3ffe8-6f59-4334-bde4-5c1c6e1d6987

📥 Commits

Reviewing files that changed from the base of the PR and between e0bd603 and 206a152.

📒 Files selected for processing (1)

• .github/workflows/agents-guard.yml

🔗 Linked repositories identified

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

• stranske/Workflows (auto-detected)

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (4)

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

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

{pyproject.toml,.github/workflows/*.{yml,yaml}}: For Python projects with coverage thresholds, ensure both pyproject.toml ([tool.coverage.report] fail_under) and workflow files have matching coverage-min settings, or the lower one will determine the actual threshold
The Manager-Database repository has a coverage threshold of 75%

Files:

• .github/workflows/agents-guard.yml

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

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

For GitHub Actions workflow startup_failure errors, check for invalid YAML syntax, invalid permissions: block in workflow_call reusable workflows, invalid permission scopes, or circular workflow references

Files:

• .github/workflows/agents-guard.yml

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

📄 CodeRabbit inference engine (CLAUDE.md)

Reference reusable workflows in consumer repos with @main unless intentionally pinning to an exact commit SHA for a controlled reason.

Files:

• .github/workflows/agents-guard.yml

.github/workflows/*.yml

📄 CodeRabbit inference engine (AGENTS.md)

First-party consumers should reference reusable workflows with @main unless intentionally pinning to an exact commit SHA for a controlled reason

Files:

• .github/workflows/agents-guard.yml

🔀 Multi-repo context stranske/Workflows

Based on my comprehensive exploration of the stranske/Workflows repository, I have gathered sufficient cross-repository context for the review.

Linked repositories findings

stranske/Workflows [::stranske/Workflows::]

Action Scope and Usage:
The setup-api-client action is a critical, widely-used GitHub composite action deployed across 65+ workflow files in the repository, including:

• Agent automation workflows (agents-63, agents-64, agents-71, agents-72, agents-73, agents-auto-label, agents-auto-pilot, agents-autofix-dispatcher, agents-autofix-loop, agents-bot-comment-handler, agents-capability-check, agents-decompose, agents-dedup, agents-guard, agents-issue-optimizer, agents-keepalive, agents-moderate-connector, agents-pr-meta-v4, agents-verifier, etc.)
• Health check workflows (health-40, health-41, health-44, health-67, health-68, health-70, health-71, health-75, health-78, health-codex-auth-check, health-keepalive-e2e)
• Maintenance workflows (maint-46, maint-50, maint-62, maint-66, maint-69, maint-70, maint-71, maint-72, maint-74, maint-81, maint-coverage-guard, maint-sync-action-versions)
• Reusable workflows (reusable-10 through reusable-70, selftest-reusable-ci)

Action Interface (Stable): [::stranske/Workflows::]

The action definition shows a stable, backward-compatible interface with:

• Inputs: Supports both JSON-based secrets via secrets input and individual fallback inputs (service_bot_pat, actions_bot_pat, owner_pr_pat, agents_automation_pat, plus 8 app credential pairs), plus configuration options (install_dir, skip_deps, verbose)
• Outputs: token_count, available_tokens, setup_contract (machine-readable JSON contract with schema workflows-api-client-setup/v1)
• No signature changes evident between commits — the action.yml file (572 lines) demonstrates a mature, stable interface

PR Impact Assessment: [::stranske/Workflows::]

The PR updates the pinned commit SHA from 62ed0a8 to a335f1a. This is a routine Renovate-managed dependency update. No breaking changes to the action's interface are evident:

• All input parameters remain available
• All output contracts remain defined
• The action continues to serve the same unified API client setup purpose across all 65+ consuming workflows

---

🔇 Additional comments (1)

.github/workflows/agents-guard.yml (1)

114-114: LGTM!

Also applies to: 183-183

---

📝 Walkthrough

Walkthrough

Two lines in .github/workflows/agents-guard.yml are updated to pin the stranske/Workflows/.github/actions/setup-api-client action to a new commit SHA. The change applies to both the pull_request_target fallback step (line 114) and the pull_request fallback step (line 183). No other workflow logic is modified.

Changes

Workflow Action SHA Bump

Layer / File(s)	Summary
Update pinned setup-api-client SHA in both trigger paths .github/workflows/agents-guard.yml	Replaces the previous pinned commit SHA with a new one for stranske/Workflows/.github/actions/setup-api-client in both the pull_request_target (line 114) and pull_request (line 183) fallback steps.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• stranske/Ready#338: Updates pinned GitHub Action commit SHAs in workflow steps, the same pattern as this PR.
• stranske/Ready#362: Modifies the same file (.github/workflows/agents-guard.yml) updating the same stranske/Workflows/.github/actions/setup-api-client SHA in the identical fallback steps.
• stranske/Ready#343: Updates a pinned action SHA in a different workflow file, same change pattern of bumping pinned commit references.

Suggested reviewers

• stranske

🚥 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 and specifically describes the main change: updating the stranske/workflows digest to a new commit SHA (a335f1a), which matches the file changes in the PR.
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 renovate/stranske-workflows-digest

---

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

[github-actions]

Workflow state fingerprint for Agents Gate Followups. Do not edit.

[github-actions]

Workflow state fingerprint for Keepalive Loop Reporter. Do not edit.

[stranske]

Closing as superseded by the latest Workflows sync PR #371; this direct digest update touches Workflows-managed files.