[jamescrosswell]

Summary

New style guide rules reach a team only as a MentalDesk.Tui bump that Dependabot opens. Nothing turned that PR into work on the team's board, so once a rule like mentaldesk/tui-style-guide#15's filled buttons shipped, nothing would move TuiCode or a-team onto it. Meanwhile mentaldesk/TuiCode#440 has been sitting red since Oct 5 with nobody looking at it.

• Trigger: triggers lead lists open Dependabot PRs that have no Lead comment from the team's App, and starts a Lead run for each one. A single gh pr list --author app/dependabot covers the whole repo.
• Lead, new step 4: read what the new version brings (release notes, the changes they link to, and new or changed rules when the dependency carries the product's conventions). File an Idea for each change worth adopting, from the user's side as in discover. If the bump needs code changes before it builds (e.g. TuiCode's Terminal.Gui 2.5 move), that work goes inside the Idea. Then comment on the PR listing the Ideas, or saying there's nothing to adopt. That comment is what stops the trigger.
• README gets one bullet under How runs are started.

Notes

• This is a pull model: each Lead reads its own dependencies, so no team opens issues on another team's repo.
• Adoption Ideas carry a-team:idea like discoveries, so they count toward wip.ideas. When you're behind on ranking, discovery pauses; the Dependabot step doesn't.
• The Lead leaves the Dependabot PR itself alone. You merge it when it's green, and if it can't go green on its own, the Idea's task supersedes it.
• Turning a style guide merge into a release automatically is a separate PR (the release setting).

🤖 Generated with Claude Code