Q26: knowledge has scope, expiry, and supersession

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/main/database/migrations/063-knowledge-scope.ts

@@ -0,0 +1,9 @@
+export const knowledgeScopeSchema = `
+  alter table knowledge_entries add column scope_type text not null default 'organization';
+  alter table knowledge_entries add column scope_id text;
+  alter table knowledge_entries add column valid_until text;
+  alter table knowledge_entries add column superseded_by text;
+
+  insert into schema_migrations(version, name, applied_at)
+  values (63, 'knowledge_scope', datetime('now'));
+`;

src/main/database/schema.ts

@@ -61,6 +61,7 @@ import { taskHandoffSchema } from "./migrations/059-task-handoff";
 import { chatWakeTextPurgeSchema } from "./migrations/060-chat-wake-text-purge";
 import { taskRunContextSchema } from "./migrations/061-task-run-context";
 import { providerContextWindowSchema } from "./migrations/062-provider-context-window";
+import { knowledgeScopeSchema } from "./migrations/063-knowledge-scope";
 
 interface Migration {
   version: number;
@@ -131,6 +132,7 @@ const MIGRATIONS: Migration[] = [
   { version: 60, name: "chat_wake_text_purge", sql: chatWakeTextPurgeSchema },
   { version: 61, name: "task_run_context", sql: taskRunContextSchema },
   { version: 62, name: "provider_context_window", sql: providerContextWindowSchema },
+  { version: 63, name: "knowledge_scope", sql: knowledgeScopeSchema },
 ];
 
 const SCHEMA_VERSION = MIGRATIONS[MIGRATIONS.length - 1].version;