[ChrisAbner]

Problem

The cycles rule reports each group of mutually reachable modules once, with the shortest cycle through its first module as an example. When the group is larger than that cycle, the message reads as if the example were the whole cycle:

Modules [Admin, Attribute, ... 30 modules] form a dependency cycle: Admin -> Product -> Admin.

Running Cordon on Bagisto (30 modules in the group), advisingapp (29) and LaravelEcomm (25) produced this message in all three.

Change

When the group has more modules than the example cycle, the message now says so:

Modules [Admin, Attribute, ...] are tangled in dependency cycles, such as Admin -> Product -> Admin. Break them one dependency at a time, for example with an event or a contract.

• When the example covers every module (the common two-module case), the message is unchanged, so the README and docs examples stay valid.
• The violation's target is unchanged, so existing baselines still match.
• No contract, config or baseline format change.

Tests

• New unit test for a three-module group whose shortest cycle has two modules (written first, seen failing).
• The existing three-module test now also asserts the unchanged message.
• composer check passes (Pint, PHPStan, Pest: 120 passed, 1 skipped).

Not in this PR

--module and the Pest expectation assign a cycle only to the modules on the example path (ADR 0005), so cordon:verify --module=Sales on Bagisto does not report the cycle Sales is part of. Changing that needs an ADR.