Summary
Follow-up hardening for the regression guard added in #882 (fix for #881).
The #882 test pins only the two tool descriptions that carried the stale "Requires altimate_core.init() with API key" claim, and uses a length-bounded regex. Two small gaps remain:
- Bounded regex.
/requires?\b[^.]{0,40}\bapi key\b/ caps the gap at 40 chars, so a variant like "requires an API key for authentication and access" could slip through.
- Two-tool coverage. Only
column_lineage / track_lineage are guarded. A newly added altimate-core-* tool could reintroduce the false claim and go uncaught.
Proposed change (test-only)
- Loosen the regex to
/requires?\b.*?\bapi key\b/ (still does not false-positive on the legitimate "no API key required" copy).
- Add a source sweep over every
altimate-core-*.ts tool asserting none contains the unambiguous altimate_core.init marker (no native engine tool calls a dispatcher method by that name, so any occurrence is a regression).
Type
Test hardening — no runtime/behavior change.
Summary
Follow-up hardening for the regression guard added in #882 (fix for #881).
The #882 test pins only the two tool descriptions that carried the stale "Requires
altimate_core.init()with API key" claim, and uses a length-bounded regex. Two small gaps remain:/requires?\b[^.]{0,40}\bapi key\b/caps the gap at 40 chars, so a variant like "requires an API key for authentication and access" could slip through.column_lineage/track_lineageare guarded. A newly addedaltimate-core-*tool could reintroduce the false claim and go uncaught.Proposed change (test-only)
/requires?\b.*?\bapi key\b/(still does not false-positive on the legitimate "no API key required" copy).altimate-core-*.tstool asserting none contains the unambiguousaltimate_core.initmarker (no native engine tool calls a dispatcher method by that name, so any occurrence is a regression).Type
Test hardening — no runtime/behavior change.