[simoneNEMO]

generateRegistry takes output and routes: { only, except }, which suggests registering it several times — e.g. one registry for a public SPA without backoffice routes, and one for an Inertia admin app with only those. Today that doesn't work: the hook applies its filter with routesScanner.filter(), and the assembler's scanner holds a single filter (this.#filter = filterFn). The last registered hook wins, and every output gets the same routes.

This change:

• Keeps a set of generators per scanner, and sets a scanner filter that keeps a route if any registry wants it. Single-registry setups still skip scanning the routes they exclude.
• Filters getScannedRoutes() by each generator's own only/except before writing its output.
• Widens filterRoute to take Pick<RoutesListItem, 'name'>, so it accepts scanned routes too.

The new test registers two hooks against a scanner that, like the assembler's, keeps one filter. It fails on main and passes here.

[Julien-R44]

Thanksss Simone

Just added a follow up for the types: both generated registries were still augmenting the same global UserRegistry, causing TS conflicts when used together

each registry now exports its own Route/Path type helpers, and typeAugmentation: false lets secondary registries avoid that global augmentation. default stays true because Inertia's Link, Form and router helpers still depend on UserRegistry. We should get rid of this global augmentation, but thats for later