@cleocode/core 2026.5.133 → 2026.6.0

package/migrations/drizzle-nexus/20260504000001_t1839-fts5-nexus-symbols/migration.sql

@@ -1,68 +0,0 @@
--- T1839: FTS5 virtual table for BM25 search on nexus_nodes.
--- Replaces O(n) LIKE '%pattern%' scans in augment.ts with indexed BM25 MATCH queries.
--- Target: p50 < 50ms (vs 1.8s LIKE baseline on cleocode project).
---
--- Design:
---   - FTS5 standalone table (not content table) — simpler trigger management.
---   - Indexes label + file_path (the two columns searched in augment.ts).
---   - node_id stored UNINDEXED for id resolution post-search.
---   - Triggers maintain the FTS5 table on INSERT/UPDATE/DELETE from nexus_nodes.
---   - Backfill INSERT populates existing rows idempotently.
---
--- Note: node:sqlite does not support the FTS5 content-virtual-table delete
--- syntax `INSERT INTO fts(fts, rowid, ...) VALUES ('delete', ...)`. Triggers
--- use plain `DELETE FROM nexus_symbols_fts WHERE rowid = old.rowid` instead,
--- which works reliably across all supported SQLite versions.
---
--- Safe to re-run: all DDL uses IF NOT EXISTS / DROP IF EXISTS guards.
-
--- 1. FTS5 virtual table: label + file_path indexed, node_id stored for lookup.
-CREATE VIRTUAL TABLE IF NOT EXISTS nexus_symbols_fts USING fts5(
-  node_id UNINDEXED,
-  label,
-  file_path,
-  tokenize = 'unicode61 remove_diacritics 1'
-);
-
---> statement-breakpoint
--- 2a. INSERT trigger.
-DROP TRIGGER IF EXISTS nexus_nodes_fts_ai;
---> statement-breakpoint
-CREATE TRIGGER nexus_nodes_fts_ai
-AFTER INSERT ON nexus_nodes
-BEGIN
-  INSERT INTO nexus_symbols_fts(rowid, node_id, label, file_path)
-  VALUES (new.rowid, new.id, new.label, new.file_path);
-END;
-
---> statement-breakpoint
--- 2b. DELETE trigger.
-DROP TRIGGER IF EXISTS nexus_nodes_fts_ad;
---> statement-breakpoint
-CREATE TRIGGER nexus_nodes_fts_ad
-AFTER DELETE ON nexus_nodes
-BEGIN
-  DELETE FROM nexus_symbols_fts WHERE rowid = old.rowid;
-END;
-
---> statement-breakpoint
--- 2c. UPDATE trigger — delete old entry, insert new entry.
-DROP TRIGGER IF EXISTS nexus_nodes_fts_au;
---> statement-breakpoint
-CREATE TRIGGER nexus_nodes_fts_au
-AFTER UPDATE ON nexus_nodes
-BEGIN
-  DELETE FROM nexus_symbols_fts WHERE rowid = old.rowid;
-  INSERT INTO nexus_symbols_fts(rowid, node_id, label, file_path)
-  VALUES (new.rowid, new.id, new.label, new.file_path);
-END;
-
---> statement-breakpoint
--- 3. Backfill existing nexus_nodes rows into FTS5.
--- The NOT IN guard makes this idempotent across repeated runs.
-INSERT INTO nexus_symbols_fts(rowid, node_id, label, file_path)
-SELECT rowid, id, label, file_path
-FROM nexus_nodes
-WHERE rowid NOT IN (
-  SELECT rowid FROM nexus_symbols_fts
-);

package/migrations/drizzle-nexus/20260507135519_t9163-nexus-is-external/migration.sql

@@ -1,20 +0,0 @@
--- T9163: Add is_external column to nexus_nodes via explicit forward migration.
--- Prior to this migration the column was only created by the ensureColumns()
--- safety net in nexus-sqlite.ts (T1062). Fresh installs that run the full
--- migration chain will now get the column from Drizzle instead of from the
--- safety net, eliminating the "Adding missing column nexus_nodes.is_external"
--- warning on cleo init.
---
--- NOT NULL DEFAULT false (= 0): matches the Drizzle schema definition
--- `integer('is_external', { mode: 'boolean' }).notNull().default(false)`.
---
--- Legacy DBs where ensureColumns already ran the ALTER TABLE will hit a
--- duplicate-column error. migration-manager.isDuplicateColumnError +
--- reconcileJournal Scenario 3 already handles this path (Case A: all ALTER
--- targets already exist → mark journal entry applied and skip re-run).
---
--- The ensureColumns() call in nexus-sqlite.ts is intentionally RETAINED as a
--- repair net for legacy DBs that were upgraded out-of-band.
-ALTER TABLE `nexus_nodes` ADD COLUMN `is_external` integer NOT NULL DEFAULT false;
---> statement-breakpoint
-CREATE INDEX `idx_nexus_nodes_is_external` ON `nexus_nodes` (`is_external`);