chore(deps): let the interface range reach UnregisterRoute

[Upd4ting]

The interface dependency read ^0.0.8 — and an npm caret on a 0.0.x version pins that exact patch (>=0.0.8 <0.0.9). Nothing depending on this module could ever resolve interface-api 0.0.10, where UnregisterRoute (AntelopeJS/interface-api#13) ships.

This matters beyond this package: the AntelopeJS loader hands every module of a deployment the implementor's interface copy. The pin here therefore decided the interface version for every consumer — the CMS page teardown calls UnregisterRoute and got TypeError: not a function in any environment where this module supplies the interface.

Widened to >=0.0.10 <1.0.0, the range shape consumers already use for 0.x interfaces. Lockfile resolves 0.0.10; 120 tests passing.

Consumer waiting on this: the CMS fix/release-page-route branch, which releases a page's own layout route on unregistration — the last registry its teardown did not reclaim.

Greptile Summary

Updates @antelopejs/interface-api so consumers can resolve the UnregisterRoute API introduced in version 0.0.10.

• Widens the dependency range from ^0.0.8 to >=0.0.10 <1.0.0.
• Updates the lockfile’s root resolution and utility peer snapshot to interface-api 0.0.10.

Confidence Score: 5/5

The PR appears safe to merge, with the manifest and lockfile consistently enabling interface-api 0.0.10.

The dependency range now reaches the required interface release, and the lockfile consistently resolves the root package and interface utility against version 0.0.10 without an identified current failure.

Important Files Changed

Filename	Overview
package.json	Widens the interface-api dependency range to include version 0.0.10 and subsequent compatible pre-1.0 releases.
pnpm-lock.yaml	Consistently updates the root importer and dependency snapshots to interface-api 0.0.10 while retaining the separately required 0.0.8 snapshot.

_{Reviews (1): Last reviewed commit: "chore(deps): let the interface range rea..." | Re-trigger Greptile}