Gergo Magyar b751418985 fix(test): discover the installed FTS extension version dir instead of assuming it equals lbug.VERSION ... resolveInstalledFtsExtension (extension-binary-real.test.ts) and resolveSeedExtension (fts-extension-e2e.test.ts) both hardcoded the on-disk FTS extension path as .lbdb/extension/<lbug.VERSION>/..., but LadybugDB's native INSTALL/LOAD resolves its own extension-ABI version directory, which does not always track the npm package version. Bumping @ladybugdb/core from 0.18.1 to 0.18.2 in this PR still installs into a 0.18.1 directory, so both hardcoded lookups came up empty and failed hard under GITNEXUS_REQUIRE_FTS=1 in CI (all platforms, shard 3). Add findInstalledFtsExtension() to discover the real installed file by scanning every version subdirectory, and use it from both test files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-07-21 06:06:42 +00:00
..
fixtures	feat(spring): build bean candidate inventory (#2494)	2026-07-20 09:28:23 +01:00
helpers	fix(test): discover the installed FTS extension version dir instead of assuming it equals lbug.VERSION	2026-07-21 06:06:42 +00:00
integration	fix(test): discover the installed FTS extension version dir instead of assuming it equals lbug.VERSION	2026-07-21 06:06:42 +00:00
unit	fix(lbug): raise the adaptive pool floor to a COPY-safe 256 MiB	2026-07-20 16:29:17 +00:00
utils	fix(hook): emit MCP query hint when server owns DB lock (#2396) (#2397)	2026-07-08 18:34:05 +01:00