6086cf9a7adbf2a838df96c4543c85a7ed7c0bf5
Apply same composite-FK pattern as 001/002 for migration 003: - resources: add UNIQUE (id, space_id) as FK target. - resource_dependencies: denormalize space_id, composite FKs on both endpoints (enforces both ends of a dep live in the same space at the DB layer). - resource_credentials: denormalize space_id, composite FK to resources. - source_docs.resource_id: NOT NULL (tenancy anchor); resource_id was already absent from the update FIELDS list so docs cannot move resources. Repos derive space_id from the resource on addDependency/addCredential so callers can't fake cross-tenant assignment. 3 regression tests added.
Void 2.0
Homelab orchestrator + canonical knowledge store. Cradle-themed.
Successor to Void 1.x (CT 301). Spec at
/project/docs/superpowers/specs/2026-05-31-void-v2-design.md.
Layout
void-server(this repo) — Node API, MCP, UI, cron, agent runtimevoid-workers— Python ingest workers (separate repo, later plan)
Quick start (dev)
- Provision
void2-dbLXC (seedeploy/README.md) - Install Postgres + pgvector on
void2-db npm installcp .env.example .envand editnpm run migratenpm startcurl -H "Authorization: Bearer $OWNER_TOKEN" http://localhost:3000/health
Description
Languages
JavaScript
87.5%
CSS
6.4%
Python
5.2%
Shell
0.7%
HTML
0.2%