[Upd4ting]

Why

Put interface-database on @antelopejs/tooling-configs 0.5.1 and make it pass cleanly, not just carry the new version. 0.5.1 adds antelopejs/no-read-then-insert, relaxes no-inherited-key-lookup, and fixes the declared-surface walk that overflowed the stack on this package (tooling-configs#290). Task ANT-1857, parent ANT-1840.

What changed

• @antelopejs/tooling-configs is declared ^0.5.1, and the lockfile resolves 0.5.1.
• pnpm run sync rewrote AGENTS.md (new rule row, three sync notes now enforced by --check) and .agents/skills/verify-interface/SKILL.md (verdict --judgement).
• features/smoke.md no longer blames the stack overflow. every-function and minor-bump now run here but cannot pass, so the gotcha states the two tool-side reasons and through-core stays the smoke journey.

No lint finding came up. no-read-then-insert and no-unknown-parameters report nothing here. The repo has no no-inherited-key-lookup suppression for #291 to retire. guardrails.suppressions.json is unchanged. No published surface changes.

Proof

Before. Main with ^0.5.1 installed, before pnpm run sync:

$ pnpm run sync:check
Drift: AGENTS.md; run antelopejs-sync
Drift: .agents/skills/verify-interface/SKILL.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.
exit 1

$ pnpm run checks
[sync:check]
Drift: AGENTS.md; run antelopejs-sync
Drift: .agents/skills/verify-interface/SKILL.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.
Checks: 10 passed, 1 failed.
 ELIFECYCLE  Command failed with exit code 1.
exit 1

After, at this head:

$ pnpm run sync:check
Guardrails are in sync.
exit 0

$ pnpm run checks
Checks: 11 passed, 0 failed.
exit 0

Verify layer. antelopejs-verify journey <run> --plan ran all 20 features (the diff touches package.json) and passed 31 of 31 journeys.

Attention

Run by hand at this head with smoke naming them, every-function and minor-bump both fail:

• every-function fails 635 checks. 577 are class prototype methods (.:ValueProxy.prototype.gt, and so on). The .d.ts walk lists them and the consumer's runtime walk does not (it returns 65 top-level members), so each reads as "declared but not exported". The other 58 are plain classes and functions that would need interface.calls hooks.
• minor-bump reports 21 added and 21 removed __@asyncIterator@<n> members, whose ids differ between the published 0.3.1 build and head (1858 against 3457). Each signature also embeds its referenced type closure, so fix(selection): accept a getAll key proxy of any SelectionKey type #80's real getAll<K extends SelectionKey> overload marks 630 functions as changed. With symbol ids normalised, 42 still differ, all through that overload. That part is genuine: under the rule, the next release of this package needs at least 0.4.0.