[docdyhr]

Summary

• Retire the per-repo Claude caller templates. This deletes workflow-templates/caller-claude-dependabot-merge.yml and caller-claude-status-check.yml. Their callers said "Schedule is owned by the cross-repo orchestrator", but the orchestrator never dispatches them: its file names neither caller, and it does the status and Dependabot work itself in one session. So the callers only ran on a push to their own file or by hand. httpcheck's Claude Dependabot Auto-Merge had last run 130 days ago.
• Why retire them instead of wiring the dispatch:
  • The work is covered already. The orchestrator checks all T1+T2 repos weekly, and patch bumps merge natively in each repo.
  • GH_ORG_TOKEN is read-only by design. Dispatching would need Actions: write on every target repo.
  • The merge caller defaulted to dry-run, so a dispatched run merged nothing unless someone chose live.
• MAINTENANCE.md gets a "Retired: per-repo Claude callers" section covering why, which repos changed, how to bring a caller back, and pigame's exception. Its tables and the re-tag procedure no longer assume callers exist. .github/workflows/README.md says the same.
• The reusable workflows stay at v1. pigame (T4, outside the standard and the orchestrator's list) still calls both and is left alone under the T4 rule.

The consumer PRs:

• docdyhr/httpcheck#58, docdyhr/malwarespotter#45, docdyhr/simplenote-mcp-server#1007: delete both callers.
• docdyhr/versiontracker#344: its dispatch-only merger caller (saved as dependabot-auto-merge.yml) becomes the native patch auto-merge, plus a ruff exclusion.

Type of change

• Bug fix
• New feature
• Refactor / code quality
• Documentation
• CI / tooling
• Dependency update

Checklist

• Tests added or updated for new behaviour (n/a: template deletion and docs)
• Full test suite passes locally (orchestrator-guards, changelog-extract: all cases passed)
• Docs updated if user-facing behaviour changed (MAINTENANCE.md, .github/workflows/README.md)
• No secrets or credentials in this PR

Rollout

• No v1 move needed. Templates aren't part of the reusable workflows.
• Merge order: the four consumer PRs first, then this one. Nothing breaks either way, but deleting the templates first would make repo-audit report the remaining callers as CALLER NO-TEMPLATE in between.
• Skills: the local repo-bootstrap fetches these two templates. The updated skills (repo-bootstrap, workflow-migrate, repo-audit) are staged outside this repo. Install them before this merges, or a bootstrap run in between fails at its curl step.
• After merge: ANTHROPIC_API_KEY has no other user in httpcheck, malwarespotter or versiontracker and can be deleted there. simplenote-mcp-server still needs it for evaluation-quality-gate.yml.

Related issues

None; found by /status on httpcheck (the "[driver: docdyhr/.github]" claim).

🤖 Generated with Claude Code

Summary by Sourcery

Retire inactive per-repository Claude callers and align maintenance documentation with the cross-repository orchestrator.

Enhancements:

• Retire unused per-repository Claude maintenance callers while retaining the reusable workflows for pigame and future one-off use.
• Switch versiontracker to the standard native Dependabot patch auto-merge workflow.

CI:

• Remove the obsolete Claude Dependabot merge and status-check caller templates from the shared workflow templates.

Documentation:

• Document the retired callers, orchestrator ownership, remaining pigame exception, and updated workflow maintenance procedures.

[sourcery-ai]

Sorry @docdyhr, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 15 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This PR removes the unused per-repo Claude caller templates, records that T1/T2 maintenance is handled directly by the orchestrator while pigame remains supported, and updates maintenance and workflow documentation to reflect the retirement and future caller/re-tag procedures.

File-Level Changes

Change	Details	Files
Retire unused per-repository Claude caller templates and document the supported workflow ownership model.	Delete the Dependabot merge and status-check caller templates. Clarify that the cross-repository orchestrator performs the T1/T2 maintenance directly, while pigame remains the T4 exception. Document the rationale, affected repositories, restoration procedure, token-permission considerations, and updated re-tag guidance.	workflow-templates/caller-claude-dependabot-merge.yml workflow-templates/caller-claude-status-check.yml MAINTENANCE.md .github/workflows/README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.