feat(routes): let a consumer unregister a single route

[Upd4ting]

Routes are only released when their module unloads. Anything with a shorter life than its module therefore keeps answering after the thing that registered it is gone — the case that prompted this is a CMS page unregistered while its module stays loaded: its /pagelayout route kept serving.

routesProxy is exported and RoutesProxy.unregister already does the right cleanup (it prunes routesList as well), but a consumer cannot use it: interface resolution rebinds the export, so the object the consumer imports is not the one holding the live registry. Verified in the AntelopeJS test harness — internal.routesProxy !== routesProxy, and neither removes a route from getRegisteredRoutes().

Hence a real API next to RegisterRoute, taking the id it returns.

const id = RegisterRoute({ ... });
// later, when whatever owns the route goes away
UnregisterRoute(id);

Consumer waiting on this: AntelopeJS/cms#301, where a page now owns and releases everything it registered — every registry but this one.

Greptile Summary

The PR adds a public API for unregistering an individual route using the ID returned during registration.

• Adds UnregisterRoute, which delegates cleanup to the live route proxy.
• Adds lifecycle regression tests covering targeted removal, preservation of unrelated routes, repeated removal, and unknown IDs.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
src/index.ts	Adds the public single-route cleanup API using the existing proxy lifecycle behavior.
src/tests/route-lifecycle.test.ts	Adds focused regression coverage that resolves the prior concern about route cleanup behavior.

_{Reviews (3): Last reviewed commit: "test(routes): cover the route lifecycle" | Re-trigger Greptile}

[Upd4ting]

@greptile review

[Upd4ting]

@greptile review