@anchrd/intel-api 0.5.0 → 0.5.1

package/dist/adapters/db/db.js

@@ -151,10 +151,14 @@ export function createKnowledgeRepository(deps) {
             try {
                 await deps.db.batch([
                     deps.db
+                        // ⚠️ `context_policy` is dead and is written anyway (#76). The column is NOT NULL
+                        // without a DEFAULT and D1 will not let it be dropped — migration 0009 carries the
+                        // reason. The fixed value is the price; nothing reads it, and the contract no longer
+                        // knows the field. When the column goes (anchrd/intel#86), this line goes with it.
                         .prepare(`INSERT INTO knowledge_nodes (
-            id, parent_id, kind, title, description, owner_id,
+            id, parent_id, kind, title, description, context_policy, owner_id,
             current_version_id, created_at, updated_at, archived_at
-          ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)`)
+          ) VALUES (?, ?, ?, ?, ?, 'relevant', ?, ?, ?, ?, ?)`)
                         .bind(node.id, node.parentId, node.kind, node.title, node.description, node.ownerId, node.currentVersionId, node.createdAt, node.updatedAt, node.archivedAt),
                     deps.db
                         .prepare(`INSERT INTO idempotency_keys (

package/migrations/0009_no_context_policy.sql

@@ -1,51 +1,33 @@
--- #76. `context_policy` leaves the tree. It was written, stored and handed back, and never once
--- read to decide anything — and it could not have been: it instructed a retrieval Intel does not
--- perform. Intel hands out references and the agent fetches what it needs (D24).
+-- #76. `context_policy` leaves the contract, the UI and every MCP answer. The COLUMN stays.
 --
--- ⚠️ SQLite cannot drop a column that a CHECK constraint names, and this one names itself. The
--- table has to be rebuilt, which for `knowledge_nodes` means six foreign keys pointing at it —
--- including one from itself. The order below is SQLite's own twelve-step recipe, and every line of
--- it is load-bearing:
+-- ⚠️ That is not the intent, it is what D1 permits. SQLite cannot drop a column a CHECK names, and
+-- this one names itself. The way around it is a table rebuild, and `knowledge_nodes` carries six
+-- foreign keys, one of them from itself.
 --
---   * `PRAGMA foreign_keys` is turned off first. Without it the DROP below would either fail or
---     cascade into the rows of every referencing table.
---   * The new table is created under a different name and renamed afterwards, rather than the old
---     one being renamed out of the way. Renaming the OLD table would silently re-point every
---     foreign key in the other five tables at `knowledge_nodes_old` — SQLite updates references to
---     follow a rename, and that is exactly what must not happen here.
---   * The indexes are recreated, because dropping the table drops them with it.
---   * `PRAGMA foreign_key_check` is the proof, not the hope. The integration test asserts it comes
---     back empty.
-PRAGMA foreign_keys = OFF;
-
-CREATE TABLE knowledge_nodes_rebuilt (
-  id TEXT PRIMARY KEY NOT NULL,
-  parent_id TEXT REFERENCES knowledge_nodes(id),
-  kind TEXT NOT NULL CHECK (kind IN ('folder', 'document', 'attachment', 'table')),
-  title TEXT NOT NULL CHECK (length(title) BETWEEN 1 AND 240),
-  description TEXT CHECK (description IS NULL OR length(description) <= 2000),
-  owner_id TEXT NOT NULL,
-  current_version_id TEXT,
-  created_at TEXT NOT NULL,
-  updated_at TEXT NOT NULL,
-  archived_at TEXT
-);
-
-INSERT INTO knowledge_nodes_rebuilt (
-  id, parent_id, kind, title, description, owner_id,
-  current_version_id, created_at, updated_at, archived_at
-)
-SELECT id, parent_id, kind, title, description, owner_id,
-       current_version_id, created_at, updated_at, archived_at
-FROM knowledge_nodes;
-
-DROP TABLE knowledge_nodes;
-
-ALTER TABLE knowledge_nodes_rebuilt RENAME TO knowledge_nodes;
-
-CREATE INDEX knowledge_nodes_parent_idx ON knowledge_nodes(parent_id, archived_at, title);
-CREATE INDEX knowledge_nodes_owner_idx ON knowledge_nodes(owner_id, archived_at);
-
-PRAGMA foreign_key_check;
-
-PRAGMA foreign_keys = ON;
+-- Three attempts against the real database, three failures, each with its own lesson:
+--
+--   1. `PRAGMA foreign_keys = OFF` — **ignored** by D1 over its HTTP API. It works locally, because
+--      miniflare honours it, so the integration test was green while production answered
+--      `FOREIGN KEY constraint failed` on the DROP. ⚠️ A green migration test does not prove a D1
+--      migration runs.
+--   2. `PRAGMA defer_foreign_keys = true` — it works, but the self-reference was written as
+--      `REFERENCES knowledge_nodes(id)` and therefore pointed at the table this same migration was
+--      about to drop. SQLite rewrites a self-reference along with the rename, so the temporary name
+--      belongs there.
+--   3. Self-reference fixed → green through `wrangler d1 migrations apply --local`, still red
+--      against `--remote`. The reason is the execution model: D1 commits the statements of a
+--      migration file one at a time, and the deferral only lasts until the next COMMIT. After the
+--      first statement the reprieve is gone and `DROP TABLE` runs unprotected.
+--
+-- A table rebuild with foreign keys is therefore not possible inside a migration file. It needs a
+-- session that drives the transaction itself.
+--
+-- What holds instead: the column sits in D1, nothing reads it, and `db.ts` writes a fixed value on
+-- insert because it is NOT NULL without a DEFAULT. The contract does not know it — for every
+-- consumer it is gone. What remains is one dead column, and that is the price of Intel running.
+--
+-- How it disappears after all is anchrd/intel#86.
+--
+-- This file deliberately does nothing. It is where the above is written down; deleted, it would be
+-- a gap in the numbering that nobody explains.
+SELECT 1;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-api",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {