fix(deps): support Core 1.5 canonical interfaces

[Upd4ting]

Before / after

• Before: source main pins @antelopejs/interface-core to ^0.0.6 and @antelopejs/interface-api to ^0.0.8. Those 0.0.x caret ranges reject the canonical 0.0.11 packages selected by the future Core 1.5 stack. The currently published auth-jwt 1.0.1 manifest is narrower still (^0.0.5 for both packages).
• After: keep the proven existing minima and accept the rest of the pre-1.0 contracts:
  • @antelopejs/interface-core: >=0.0.6 <1.0.0
  • @antelopejs/interface-api: >=0.0.8 <1.0.0
  • the playground uses the same Core range
  • the lockfile validates both interfaces at 0.0.11

No auth implementation or hot-path code changes.

Proven contract

• Core usage is limited to ImplementInterface at runtime and defineConfig in test/playground configuration. The existing implementation shape { internal: { Verify, Sign } } is accepted by the real 0.0.11 ImplementInterface; no API #36-style wiring change is needed.
• API-interface usage is limited to new HTTPResult(status, body). The constructor contract is unchanged from interface-api 0.0.8 through 0.0.11.
• Direct strict validation with interface-core/interface-api 0.0.11 created and validated a JWT through SignRaw/ValidateRaw, then rejected an altered token.

Compatibility matrix

Runtime	Canonical interface-core	API stack	Production result
npm @antelopejs/core@1.4.7	0.0.8, one physical copy	@antelopejs/api@1.2.3, interface-api 0.0.11	build + start passed; API listened on loopback; valid JWT accepted; altered JWT rejected; 0 runtime errors, 0 warnings
Core main 6712035fb9ecbb924b5916788d9bc50123f77a8a tarball	0.0.11, one physical copy	@antelopejs/api@1.2.3, interface-api 0.0.11	build + start passed; API listened on loopback; valid JWT accepted; altered JWT rejected; 0 runtime errors

Core-main tarball SHA-256: 43ef73097faa9ddd8e8ede0934463d54b9acbd1c2b2ca6862bc64a34a88f0daa.

Validation

• pnpm install --frozen-lockfile
• pnpm run build
• pnpm run lint
• pnpm run test — 4 passing
• direct real-ImplementInterface JWT create/validate/reject harness on interface-core 0.0.11
• pnpm pack plus tar entry and packed-manifest inspection — 15 expected files
• pnpm publish --dry-run --no-git-checks — completed as a dry run; nothing published
• candidate tarball SHA-256: 6086c270d08b75c349c8ba0cb973b4719ac4660468f0d654baa5103469b200c8
• clean production installations and launches for both matrix rows

Fixtures and limits

• Integration secrets were static, local, non-sensitive test strings.
• API 1.2.3 listened only on 127.0.0.1 ports 55147/55148 and was stopped cleanly after the assertions. No external service, database, or persistent data was used.
• No throughput benchmark was run; scope is manifest resolution, canonical interface wiring, production startup, and one meaningful JWT flow.
• On the exact Core-main commit, API 1.2.3 logs two warnings because Core's provider-route discovery reads the interface-core root export but the API calls named proxies from the /runtime subpath. With strictPort: true on a free production port, startup and endpoint registration fallback complete with 0 [ERROR] logs and the JWT flow passes. This is outside auth-jwt and is not changed here.
• The candidate keeps version 1.0.1 for testing; the release should be a new auth-jwt patch.

Release order

Merge this PR, publish the auth-jwt patch, then cut the Core 1.5 RC so consumers can resolve the compatible auth-jwt manifest first.

Greptile Summary

This PR broadens the supported pre-1.0 ranges for the Core and API interface packages so auth-jwt can resolve the canonical Core 1.5 interfaces.

• Updates the published package’s interface dependency ranges while preserving their existing minimum versions.
• Applies the same Core interface range to the playground.
• Refreshes the lockfile to resolve both interface packages at version 0.0.11.

Confidence Score: 5/5

The PR appears safe to merge, with the manifests and lockfile consistently updated for the intended interface compatibility.

The changed dependency ranges preserve the existing minimum versions, the lockfile resolves a consistent 0.0.11 interface graph, and no concrete build, runtime, or security failure remains.

Important Files Changed

Filename	Overview
package.json	Broadens the interface-api and interface-core dependency ranges to accept compatible pre-1.0 releases; no actionable defect was identified.
playground/package.json	Aligns the playground’s interface-core range with the root package.
pnpm-lock.yaml	Updates importer and package snapshots consistently to interface-api and interface-core 0.0.11.

_{Reviews (1): Last reviewed commit: "fix(deps): support canonical interface p..." | Re-trigger Greptile}