gitnexus 1.6.9-rc.36 → 1.6.9-rc.37

package/dist/core/group/bridge-db.js

@@ -834,6 +834,11 @@ export async function writeBridge(groupDir, input) {
  * 33 ("The process cannot access the file because another process has
  * locked a portion of the file"). Retrying with a small back-off lets the
  * background thread settle and the OS release the handle.
+ *
+ * As of v0.18.0 the "Could not set lock" file-lock error text gained an
+ * appended detail suffix upstream (see `lbug-config.ts`'s
+ * `OPEN_LOCK_RETRY_ATTEMPTS` comment), but the substrings matched here are
+ * unaffected by that change.
  */
 const LBUG_OPEN_RETRY_PATTERNS = [
     'process cannot access the file',

package/dist/core/lbug/conn-lock.js

@@ -15,6 +15,12 @@
  * embedding writeback, and the PDG edge deletes are mutually exclusive — the
  * property that makes a strictly-serial workload stable.
  *
+ * As of v0.18.0, none of LadybugDB's upstream fixes touch this specific risk
+ * (concurrent queries on ONE connection) — the closest are a deadlock fix
+ * between concurrent *connections* (LadybugDB/ladybug#605) and a narrow
+ * database close/destroy-vs-GC race fix (#623), both different scenarios
+ * from the one above. This lock's justification is unchanged.
+ *
  * Implementation: a promise chain. Each caller installs a fresh unresolved tail,
  * awaits the previous holder's tail, runs, then releases its own in `finally`
  * (so a thrown op never wedges the connection). FIFO and non-reentrant: a wrapped

package/dist/core/lbug/lbug-adapter.js

@@ -547,7 +547,7 @@ const runSchemaCreationQueries = async (dbPath) => {
             const msg = err instanceof Error ? err.message : String(err);
             // Suppression list:
             //   - "already exists": expected idempotent re-create on existing DBs
-            //   - "could not set lock on file": LadybugDB v0.16.1 emits this on
+            //   - "could not set lock on file": LadybugDB v0.18.0 emits this on
             //     Windows when CREATE NODE TABLE runs against a path that was
             //     just opened (the WAL handle from a fresh Database briefly
             //     contests the table's first-write lock). The table is created

package/dist/core/lbug/lbug-config.js

@@ -297,7 +297,7 @@ export function isWalCorruptionError(err) {
 }
 // ─── Ladybug WAL checkpoint IO error matchers ───────────────────────────────
 //
-// Matched against LadybugDB v0.16.1 (see `gitnexus/package.json`
+// Matched against LadybugDB v0.18.0 (see `gitnexus/package.json`
 // @ladybugdb/core). Strict regexes encode local_file_system.cpp wording
 // verified at that version. Two-tier strategy: strict matchers first so we
 // only fire on real checkpoint-rotation shapes; a permissive fallback
@@ -387,7 +387,10 @@ export function createLbugDatabase(lbugModule, databasePath, options = {}) {
 // of 10–50ms each = ~1.0–1.2s worst case) clears the typical
 // AV-scanner hold without masking real cross-process conflicts.
 //
-// Source: https://github.com/LadybugDB/ladybug/blob/v0.16.1/src/common/file_system/local_file_system.cpp#L126
+// Source: https://github.com/LadybugDB/ladybug/blob/v0.18.0/src/common/file_system/local_file_system.cpp#L127
+// (v0.18.0 appends " (Error: <code>)" / " (Lock is held by PID X)" on POSIX,
+// but the "Could not set lock on file : " prefix `isDbBusyError` substring-
+// matches on is unchanged.)
 const OPEN_LOCK_RETRY_ATTEMPTS = 5;
 const OPEN_LOCK_RETRY_DELAY_MS = 100;
 const HANDLE_RELEASE_PROBE_ATTEMPTS = 5;

package/dist/core/lbug/sidecar-recovery.js

@@ -86,16 +86,24 @@ const warnOnce = (logger, key, message) => {
     }
     logger.warn(`${message} (${ordinal(next)} occurrence of this condition)`);
 };
-// LADYBUGDB-CONTRACT: matches @ladybugdb/core ^0.16.1 native error text.
+// LADYBUGDB-CONTRACT: matches @ladybugdb/core ^0.18.0 native error text.
 // When bumping LadybugDB, re-validate this regex against the new error format
 // — `git grep "LADYBUGDB-CONTRACT"` enumerates every version-coupled spot.
+// Verified by upstream source/changelog diff only — forcing a genuine
+// `.shadow`-missing state via a live crash to trigger this error is not
+// reliably reproducible (a SIGKILL at the exact moment `.shadow` exists on
+// disk still recovers via `.wal.checkpoint` alone), so this matcher does not
+// have live-trigger test coverage.
 export const isMissingShadowSidecarError = (err) => {
     const msg = err instanceof Error ? err.message : String(err);
     return /Cannot open file .*\.shadow: No such file or directory/i.test(msg);
 };
-// LADYBUGDB-CONTRACT: matches @ladybugdb/core ^0.16.1 native error text.
+// LADYBUGDB-CONTRACT: matches @ladybugdb/core ^0.18.0 native error text.
 // When bumping LadybugDB, re-validate this regex against the new error format
 // — `git grep "LADYBUGDB-CONTRACT"` enumerates every version-coupled spot.
+// Verified by upstream source/changelog diff only — a reliable cross-platform
+// live trigger for a read-only shadow-replay state isn't practical to
+// construct, so this matcher does not have live-trigger test coverage.
 export const isReadOnlyShadowReplayError = (err) => {
     const msg = err instanceof Error ? err.message : String(err);
     return /replay shadow pages under read-only mode/i.test(msg);

package/dist/core/search/fts-indexes.d.ts

@@ -1,3 +1,4 @@
+export declare const SUPPORTED_FTS_STEMMERS: ReadonlySet<string>;
 export interface CreateSearchFTSIndexesOptions {
     onIndexStart?: (table: string, indexName: string) => void;
     onIndexReady?: (table: string, indexName: string) => void;

package/dist/core/search/fts-indexes.js

@@ -1,10 +1,12 @@
 import { createFTSIndex, dropFTSIndex, DEFAULT_FTS_STEMMER } from '../lbug/lbug-adapter.js';
 import { FTS_INDEXES } from './fts-schema.js';
 // Stemmers shipped by the LadybugDB FTS extension. Mirrors the lowercase token
-// set in the extension bundled with @ladybugdb/core 0.17.x (see package.json).
+// set in the extension bundled with @ladybugdb/core 0.18.x (see package.json).
 // Keep in sync on a LadybugDB minor bump — a value here that the installed
 // extension rejects would pass validation but fail at CREATE_FTS_INDEX.
-const SUPPORTED_FTS_STEMMERS = new Set([
+// Exported so the re-validation sweep in fts-stemmer-sweep.test.ts iterates the
+// canonical list rather than a copy that could silently drift from it.
+export const SUPPORTED_FTS_STEMMERS = new Set([
     'arabic',
     'basque',
     'catalan',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gitnexus",
-  "version": "1.6.9-rc.36",
+  "version": "1.6.9-rc.37",
   "description": "Graph-powered code intelligence for AI agents. Index any codebase, query via MCP or CLI.",
   "author": "Abhigyan Patwari",
   "license": "PolyForm-Noncommercial-1.0.0",
@@ -56,7 +56,7 @@
   },
   "dependencies": {
     "@huggingface/transformers": "^4.1.0",
-    "@ladybugdb/core": "^0.17.0",
+    "@ladybugdb/core": "^0.18.0",
     "@modelcontextprotocol/sdk": "^1.0.0",
     "@scarf/scarf": "^1.4.0",
     "busboy": "^1.6.0",

package/scripts/cross-platform-tests.ts

@@ -74,6 +74,8 @@ const LBUG_NATIVE = [
   'test/integration/fts-description-search.test.ts',
   'test/integration/staleness-and-stability.test.ts',
   'test/integration/analyze-wal-checkpoint-failure.test.ts',
+  'test/integration/fts-stemmer-sweep.test.ts',
+  'test/integration/lbug-multiwriter-deadlock.test.ts',
 ];
 
 // Process spawning and CLI tests — exercise child_process with real