chore(deps): update git submodules

[shunkakinoki]

This PR contains the following updates:

Package	Update	Change
dotagents (changelog)	digest	0b92d27 → aee06bf

---

Configuration

📅 Schedule: (in timezone UTC)

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

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate.

---

Summary by cubic

Update the dotagents git submodule to the latest upstream to sync recent changes and fixes. No application code changes; only the submodule pointer was updated.

^{Written for commit 60156c4. Summary will update on new commits.}

[indent-zero]

PR Summary

Routine Renovate-driven submodule bump that advances the dotagents pointer from 0b92d27 to aee06bf, picking up two upstream commits already on shunkakinoki/dotagents main. This lets dotfiles users sync new agent capabilities on next submodule update.

• Bumps dotagents gitlink to include feat(mcp): add Sentry remote MCP server (#154) (adds a Sentry entry to .ruler/mcp.json using mcp-remote against https://mcp.sentry.dev/mcp).
• Bumps dotagents gitlink to include feat(skills): add kitlangton/motel motel-debug skill (#155) (adds kitlangton/motel to SKILLS.txt).
• Indirectly brings in an upstream Makefile change that unpins @intellectronica/ruler (removes RULER_VERSION := 0.3.42); historically that pin existed because 0.3.43 broke the aider MCP merge — worth being aware of, though it's an upstream decision.

Issues

1 potential issue found:

• Upstream submodule bump removes the RULER_VERSION := 0.3.42 pin in dotagents/Makefile and switches ruler-apply-global to unpinned bunx @intellectronica/ruler; the prior pin comment warned that 0.3.43 "dropped the [global] config section and broke aider MCP merge", so future ruler releases could silently regress local-only apply for anyone who syncs this repo. → Autofix

CI Checks

Waiting for CI checks...

---

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 09d7ad48-7365-491a-8a02-a2f71280879a

📥 Commits

Reviewing files that changed from the base of the PR and between d05aa0f and 60156c4.

📒 Files selected for processing (1)

• dotagents

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated internal component dependencies to the latest version.

Walkthrough

The dotagents git submodule reference is updated from commit 0b92d27e8be9d50c2b7e1de2ca85c0fea0941d74 to commit aee06bf7bad91ec0dd98be0df85f98fd0b1fbfed. No other files are changed.

Changes

dotagents Submodule Update

Layer / File(s)	Summary
dotagents submodule repinned dotagents	Submodule pointer is bumped to a new commit hash with no other changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Possibly related PRs

• shunkakinoki/dotfiles#1336: Also updates only the dotagents submodule commit pointer with no other code changes.
• shunkakinoki/dotfiles#1896: Identical change pattern — solely a dotagents git submodule reference bump.
• shunkakinoki/dotfiles#1832: Updates the same dotagents subproject commit pointer in the same repository.

Poem

🐇 Hop, hop, a tiny nudge,
The submodule moves without a grudge.
One hash out, a fresh one in,
A new commit where dots begin.
Such a small but tidy thing! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating git submodules, which is exactly what the PR does.
Description check	✅ Passed	The description is directly related to the changeset, providing a clear table of package updates, the specific commit changes, and context about the automated update process.
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/git-submodules

---

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.}

[gemini-code-assist]

Code Review

This pull request updates the 'dotagents' subproject commit reference from 0b92d27e8be9d50c2b7e1de2ca85c0fea0941d74 to aee06bf7bad91ec0dd98be0df85f98fd0b1fbfed. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[mesa-dot-dev]

Mesa Description

TL;DR

Updated the dotagents git submodule to a new commit digest.

What changed?

• dotagents: Updated submodule reference from 0b92d27 to aee06bf

^{Description generated by Mesa. Update settings}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[mesa-dot-dev]

Performed full review of d05aa0f...60156c4

Analysis

• Git submodule pointer updates provide no visibility into actual code/config changes—the diff only shows a commit hash change, making meaningful review impossible without manual investigation of the submodule diff.

• The dotagents submodule likely contains runtime-loaded agent definitions, configurations, or prompts that bypass static analysis and type checking, creating risk that behavioral changes could slip through with weaker test coverage than compiled code.

• Insufficient verification that CI properly initializes submodules recursively and validates integration contracts—without confirmation that tests actually exercise the updated submodule content, changes could reach production untested.

• No evidence of supply chain verification (commit signing, trusted maintainers, security changes review) or established rollback procedures for submodule updates, leaving the change unverifiable and difficult to recover from if problematic.

Tip

Help

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{0 files reviewed | 0 comments | Edit Agent Settings • Read Docs}