chore(deps): use shared Renovate config

[Coldaine]

User description

Summary

• Add a minimal Renovate config that extends the shared MooseGooseConsulting preset.
• Use the no-dashboard, low-concurrency, agent-review dependency policy from MooseGooseConsulting/renovate-config.
• No Dependabot config is present in this repo, so this rollout only adds the shared Renovate entrypoint.

Shared config: https://github.com/MooseGooseConsulting/renovate-config

Validation

• Shared preset validated with renovate-config-validator --no-global --strict in MooseGooseConsulting/renovate-config.
• This repo config is the same minimal extends shape validated in MooseGooseWebsite.

---

CodeAnt-AI Description

Use the shared Renovate setup for dependency updates

What Changed

• The repo now uses the shared MooseGooseConsulting Renovate configuration
• Dependency update behavior is now inherited from the common policy instead of a repo-specific setup

Impact

✅ Consistent dependency update behavior across repos
✅ Less manual Renovate maintenance
✅ Faster rollout of shared dependency policies

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

@Coldaine, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes and 31 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 47cb03cf-343a-4e22-ae7e-586da475952a

📥 Commits

Reviewing files that changed from the base of the PR and between 73d6508 and 42ec6c2.

📒 Files selected for processing (1)

• renovate.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/use-shared-renovate-config

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[Coldaine]

Rollout audit note: this PR changes only renovate.json and the JSON is the standard shared-config shape. Current test failures appear unrelated to the Renovate config: Python dependency install fails while building dbus-python because glib-2.0 is missing in the CI image; the 3.12 job was cancelled after the 3.11 failure. Leaving this PR open for dependency-config rollout, but merge is blocked by existing CI environment/dependency setup.

[Copilot]

⚠️ Not ready to approve

The PR description indicates Dependabot is being left in place unless Renovate is confirmed active, but the repo does not currently contain a Dependabot config, so this rollout needs clarification and/or an additional config change to avoid having no active update mechanism.

Pull request overview

Adds a minimal Renovate configuration to this repository by extending the shared MooseGooseConsulting/renovate-config preset, aligning dependency update behavior with the organization’s standardized policy.

Changes:

• Add renovate.json with schema + extends pointing at the shared MooseGooseGooseConsulting preset.

File summaries

File	Description
renovate.json	Introduces Renovate configuration that extends the shared org preset.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

Note

Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• renovate.json — Standard shared Renovate config, no issues

Other Observations — Documentation Health

Per review guidance, the following documentation concerns were noted outside the diff:

File	Issue
docs/plans/StagedImplementation.md	Dated 2025-10-14. Contains execution commands, commit messages, and PR templates for PR-02 through PR-05 — all now completed. Plans that have been executed should be removed or their information consolidated into live docs.
docs/plans/PR-05-overlay-checklist.md	All tasks marked done (✅ Completed as PR #8). This is a completed checklist that no longer represents active planning.
docs/plans/Possible plan.txt	Empty file — abandoned artifact with no content.
README-ShortcutSage-Notion.md	Dated 2025-10-14. One-time Notion import helper. Contains instructions for importing into Notion ("Upload these files directly") that are stale in a living repository.
docs/plans/, docs/updates/, root-level agent docs	15+ markdown files across docs/plans/, docs/updates/, docs/researchReq/, and root. Consider consolidating: agent-prompt-pr-train.md, docs/shortcut_sage_autonomous_agent_prompt_paste_verbatim_into_agent.md, and docs/shortcut_sage_pr_train_operator_handbook_save_only.md all cover similar PR train execution instructions. The status updates (2025-11-08, 2025-11-11) are ~7 months old.

Recommendation: Consider an audit of docs/ to remove executed plans, empty files, and import helpers, and consolidate overlapping agent instructions into a single reference.

---

_{Reviewed by deepseek-v4-flash-20260423 · Input: 72.5K · Output: 7.3K · Cached: 369.2K}