Current state: outline.test.tsx pins an exact hardcoded map of every leaf route, so a plugin page from either plugin root breaks the equality check, while the sibling nav test already composes its expectation from the registry. Proposal: each plugin frontend exports an outline naming its routes and fixtures, and the test composes core plus both plugin roots by glob, keeping the exact equality invariant and giving every plugin page an automatic render test. Trigger: the enterprise tenancy screen's route broke the hardcoded map.
Current state: outline.test.tsx pins an exact hardcoded map of every leaf route, so a plugin page from either plugin root breaks the equality check, while the sibling nav test already composes its expectation from the registry. Proposal: each plugin frontend exports an outline naming its routes and fixtures, and the test composes core plus both plugin roots by glob, keeping the exact equality invariant and giving every plugin page an automatic render test. Trigger: the enterprise tenancy screen's route broke the hardcoded map.