Drop the document index

README.md

@@ -218,7 +218,7 @@ Full reference: [docs/configuration.md](docs/configuration.md).
 | `agent-bot`              | 4200                       | Proof-of-concept AG-UI Bot.                                                                          |
 | `agent-langgraph`        | 4201                       | LangGraph AG-UI Bot.                                                                             |
 | `supervisor`             | 4500 host / 4300 container | Creates and manages one computer per Bot.                                                        |
-| PostgreSQL with pgvector | 5432                       | Product data, policy, audit, credentials, grants, channels, knowledge, and component metadata.   |
+| PostgreSQL with pgvector | 5432                       | Product data, policy, audit, credentials, grants, channels, and component metadata.              |
 | CopilotKit Intelligence  | external                   | Durable threads and memory.                                                                      |
 
 The server gateway is the product/API path for Bot browser and file tool calls.

docs/architecture.md

@@ -19,7 +19,7 @@ Regenerate it with `bun run diagram` after changing anything it shows.
 | `agent-bot`              | 4200                       | Proof-of-concept AG-UI Bot.                                                                                                                     |
 | `agent-langgraph`        | 4201                       | LangGraph AG-UI Bot.                                                                                                                        |
 | `supervisor`             | 4500 host / 4300 container | Creates, stops, resets, and lists per-Bot computer containers.                                                                              |
-| PostgreSQL with pgvector | 5432                       | Product data, audit rows, credentials, policy, grants, channels, components, connector state, and knowledge records.                        |
+| PostgreSQL with pgvector | 5432                       | Product data, audit rows, credentials, policy, grants, channels, components, and connector state.                                           |
 | CopilotKit Intelligence  | external                   | Durable threads, memory, and realtime gateway.                                                                                              |
 
 `scripts/start.sh` starts PostgreSQL, `agent-computer`, `agent-bot`, `agent-langgraph`, and the supervisor through Docker Compose, then starts `server` and `app` on the host.

server/drizzle/0010_drop_the_document_index.sql

@@ -0,0 +1,26 @@
+-- Drops the document index. THIS DESTROYS DATA AND CANNOT BE ROLLED BACK.
+--
+-- Every row in `documents`, `chunks` and `document_acls` goes, embeddings included. A deployment
+-- that connected a source before the document connector was withdrawn has real rows here, and no
+-- later migration brings them back. There is nothing to migrate them to: the replacement is not
+-- another table, it is asking the vendor at the moment of the question, so there is no shape for
+-- this content to move into. Take a dump first if the corpus is worth anything to you.
+--
+-- Nothing has read or written these since the document connector and the worker's sync
+-- persistence were removed, so no running deployment loses a working feature.
+--
+-- Named in dependency order and dropped without CASCADE on purpose. CASCADE would also remove
+-- whatever a fork had hung off these tables without saying what it took; this way such a
+-- deployment gets a failed migration naming the dependency, which is the outcome it wants.
+DROP TABLE "chunks";--> statement-breakpoint
+DROP TABLE "document_acls";--> statement-breakpoint
+DROP TABLE "documents";--> statement-breakpoint
+DROP TYPE "public"."acl_effect";--> statement-breakpoint
+-- `vector` existed for the `embedding` column on `chunks` and for nothing else. RESTRICT is the
+-- default here and is wanted. A deployment that added a vector column of its own gets a failed
+-- migration rather than losing that column quietly, and because the whole migration is one
+-- transaction, a failure here leaves the three tables in place too: it is all or nothing, not a
+-- half-dropped database. Postgres names the dependent column in the error, though drizzle-kit
+-- does not print it, so read the server log or run the statement by hand to see which it is.
+-- Such a deployment should keep the extension and drop only the three tables above.
+DROP EXTENSION IF EXISTS "vector";