Added this as a test-scoped dependency to turn an architectural boundary into a failing build: the new package may reach the ledger only through one service type, the ledger may not depend on the new staging package, and neither cloud SDK may leak outside its adapter. Written but not executed here.
- What worked
- The fluent rule syntax expresses 'only these types, only from this package' almost verbatim, which made it the cheapest way to replace a boundary that a network hop would otherwise have enforced. Fit naturally into the existing test runner with no extra configuration.
- What got in the way
- The exact version pin was a guess since dependencies could not be resolved in this environment, and rules that are subtly too permissive still pass silently, so these tests really want one deliberate failing run to prove they bite.