[Upd4ting]

Why

An @antelopejs/* package ships breaking changes in minor releases. A range open to <1.0.0 lets an install resolve one this package was never built against. tooling-configs 0.6.0 adds the dependency:ranges check, which fails such a range. This PR moves to 0.6.0 and caps every @antelopejs/* range. The 0.8.0 release waits for it.

What changes

• @antelopejs/tooling-configs goes to >=0.6.0 <0.7.0. No script here called antelopejs-check-interface-ranges; pnpm run checks now runs dependency:ranges.
• Each interface peer names one minor, the one the tests run against.
• antelopejs-sync regenerated the README compatibility table and the AGENTS.md rule table (new antelopejs/no-unrun-query row).
• Three tests declare their "query" locale parameter as string | true | undefined. interface-api 0.3 types a query parameter that way (?locale alone gives true) and refuses a plain string property.

Ranges

Package	Field	Before	After
@antelopejs/api	dev	^1.7.0	~1.7.0
@antelopejs/core	dev	~1.22.0	~1.23.0
@antelopejs/interface-api	dev	>=0.2.0 <1.0.0	>=0.3.0 <0.4.0
@antelopejs/interface-api-util	dev	^0.3.0	^0.3.0 (unchanged)
@antelopejs/interface-core	dev	^0.5.1	^0.5.1 (unchanged)
@antelopejs/interface-database	dev	^0.4.0	^0.4.0 (unchanged)
@antelopejs/interface-database-decorators	dev	^0.5.2	^0.5.2 (unchanged)
@antelopejs/tooling-configs	dev	^0.5.8	>=0.6.0 <0.7.0
@antelopejs/interface-api	peer	>=0.3.0 <1.0.0	>=0.3.0 <0.4.0
@antelopejs/interface-api-util	peer	>=0.1.3 <1.0.0	>=0.3.0 <0.4.0
@antelopejs/interface-core	peer	>=0.2.4 <1.0.0	>=0.5.1 <0.6.0
@antelopejs/interface-database	peer	>=0.1.10 <1.0.0	>=0.4.0 <0.5.0
@antelopejs/interface-database-decorators	peer	>=0.5.0 <1.0.0	>=0.5.0 <0.6.0

Floors that rose

• interface-api dev, 0.2.0 to 0.3.0. The lockfile resolved 0.2.0 while the peer floor was already 0.3.0, and interface-api-util 0.3 itself peers on interface-api 0.3. Tests now run against 0.3.2, which is what needed the three test type fixes.
• interface-api-util peer, 0.1.3 to 0.3.0. A capped range names one minor, so the floor moves to the newest published minor.
• interface-core peer, 0.2.4 to 0.5.1; @antelopejs/core dev, ~1.22.0 to ~1.23.0. core 1.22 and 1.23, the newest published, depend on interface-core >=0.5.1 <0.6.0, so a lower floor would admit an interface-core the current core refuses.
• interface-database peer, 0.1.10 to 0.4.0. fix(routes): run every database query with .run() for interface-database 0.4 #133 already runs every query with .run(), which needs 0.4.

Every range now starts in the newest minor published on npm today. The already capped ^0.x dev ranges were there already and stay.

Proof

dependency:ranges with tooling-configs 0.6.0, run alone (ANTELOPEJS_CHECKS_SKIP set to every other step), on origin/main's manifest:

[dependency:ranges]
package.json: devDependencies["@antelopejs/api"] is "^1.7.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use "~1.7.0"
package.json: devDependencies["@antelopejs/interface-api"] is ">=0.2.0 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.2.0 <0.3.0"
package.json: peerDependencies["@antelopejs/interface-api"] is ">=0.3.0 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.3.0 <0.4.0"
package.json: peerDependencies["@antelopejs/interface-api-util"] is ">=0.1.3 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.1.3 <0.2.0"
package.json: peerDependencies["@antelopejs/interface-core"] is ">=0.2.4 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.2.4 <0.3.0"
package.json: peerDependencies["@antelopejs/interface-database"] is ">=0.1.10 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.1.10 <0.2.0"
package.json: peerDependencies["@antelopejs/interface-database-decorators"] is ">=0.5.0 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.5.0 <0.6.0"
Checks: 0 passed, 1 failed, 11 skipped.

On this branch:

Checks: 1 passed, 0 failed, 11 skipped.

pnpm run typecheck once interface-api resolves 0.3.2, before the test fix:

src/tests/components/localized_sort.test.ts(81,6): error TS1240: Unable to resolve signature of property decorator when called as an expression.
  Argument of type '"locale"' is not assignable to parameter of type 'never'.
src/tests/components/modifier_key.test.ts(112,6): error TS1240: ...
src/tests/components/partial_edit.test.ts(138,6): error TS1240: ...

After: no output. pnpm run checks with the test step skipped prints Checks: 11 passed, 0 failed, 1 skipped.; the three touched test files pass (17 tests) on core 1.23.0; CI runs the full suite.