#28082 fix(next): CmuxNextAccounts declares its CmuxNextWakeups dependency

Base red fix. a0ee1353 (cmux team invite) made CmuxNextAccounts/TeamInvite/TeamInviteConsentWindow.swift import CmuxNextWakeups without declaring it in CmuxNextAccounts' dependencies. So "Package dependency lists sorted", inside the cmux-next checks job, fails on base and on every PR's merge ref. An undeclared import also lets an incremental build keep objects compiled against a stale interface.

This adds CmuxNextWakeups to CmuxNextAccounts' dependencies. CmuxNextWakeups depends only on CmuxNextCompat and CmuxNextSignposts, so there is no cycle.

Changelog

none

Observed / Not run

• python3 scripts/cmux-next/check-package-dependency-lists.py: exit 1 at origin/feat-cmux-next, exit 0 with this change. Its test script passes, and prepush-gate finds no new violations.
• Not run: a package build. The edit is one dependency, declared in the manifest of a target that already imports the module.

risk:low

🤖 Generated with Claude Code

Agent session: agent session

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Declares CmuxNextWakeups in CmuxNextAccounts' dependencies so the package dependency list check passes on base. The import was added earlier without the dependency declaration, which also let incremental builds compile against stale interfaces. Adding the dependency introduces no cycle, since CmuxNextWakeups depends only on CmuxNextCompat and CmuxNextSignposts.