Task 1.4 — Org-level catalog collections

Seven collections + 3 directus_users custom fields, captured as
snapshots/schema.yaml (53 KB, 2,159 lines).

Collections:
- organizations          — UUID PK, name, slug UNIQUE
- vehicles               — UUID PK, make/model required, year/cc/vin/plate optional
- devices                — UUID PK, imei UNIQUE, model required
- organization_users     — junction with role enum (org-admin, race-director,
                            marshal, timekeeper, participant, viewer)
- organization_vehicles  — junction with registered_at
- organization_devices   — junction with registered_at
- directus_users         — extended with phone, birth_date, nationality

Six M2O relations on the junctions, all ON DELETE RESTRICT (matching
the schema-draft decision: deletion of an org/vehicle/device/user
requires explicit cleanup of dependents).

db-init/004_junction_unique_constraints.sql adds the composite UNIQUE
constraints on the three junctions:
  organization_users  (organization_id, user_id)
  organization_vehicles (organization_id, vehicle_id)
  organization_devices (organization_id, device_id)

Composite uniqueness lives in db-init rather than the Directus snapshot
because Directus's snapshot YAML format only captures single-column
unique constraints (the field-level is_unique flag). The migration file
documents the split inline.

Driven via the directus-local MCP server rather than admin-UI clicking
— programmatic create-collection/create-field/create-relation calls
against the running Directus instance, then `pnpm run schema:snapshot`
to capture the canonical YAML.

Live-verified: db-init/004 applies cleanly on container restart
(0 rows in the empty junctions, no constraint violations); schema-apply
against a snapshot-empty boot still skips correctly; all seven new
collections show up in the admin UI's data model navigation.

Snapshot includes positions and migrations_applied as auto-discovered
ghost entries (Directus introspects all public-schema tables). Harmless
— db-init creates them before schema-apply runs, so snapshot apply just
finds them already present.

ROADMAP marks 1.4 done. Phase 1 progress: 6/9 tasks complete (1.1, 1.2,
1.3, 1.4, 1.6, 1.7); 1.5, 1.8, 1.9 remain.

.planning/ROADMAP.md

@@ -42,7 +42,7 @@ These rules govern every task. Any deviation must be discussed and documented as
 
 ### Phase 1 — Slice 1 schema + deploy pipeline
 
-**Status:** 🟨 In progress (1.1, 1.2, 1.3, 1.6, 1.7 done; 1.4, 1.5, 1.8, 1.9 remaining)
+**Status:** 🟨 In progress (1.1, 1.2, 1.3, 1.4, 1.6, 1.7 done; 1.5, 1.8, 1.9 remaining)
 **Outcome:** A Directus instance with the org-level catalog (orgs, users, organization_users, vehicles, devices and their org junctions) and event-participation collections (events, classes, entries, entry_crew, entry_devices) live and snapshot-tracked. `db-init/` covers the TimescaleDB extension, the `positions` hypertable, and the `faulty` column. Image builds via Gitea Actions with a CI dry-run that catches snapshot drift before deploy. Rally Albania 2026 is registered as the first event in admin UI to dogfood the registration workflow. **This is what Rally Albania 2026 needs.**
 
 [**See `phase-1-slice-1-schema/README.md`**](./phase-1-slice-1-schema/README.md)
@@ -52,7 +52,7 @@ These rules govern every task. Any deviation must be discussed and documented as
 | 1.1 | [Project scaffold](./phase-1-slice-1-schema/01-project-scaffold.md) | 🟩 | pending user commit |
 | 1.2 | [db-init runner script](./phase-1-slice-1-schema/02-db-init-runner.md) | 🟩 | pending user commit |
 | 1.3 | [Initial migrations (extensions, positions hypertable, faulty column)](./phase-1-slice-1-schema/03-initial-migrations.md) | 🟩 | pending user commit |
-| 1.4 | [Org-level catalog collections](./phase-1-slice-1-schema/04-org-catalog-collections.md) | ⬜ | — |
+| 1.4 | [Org-level catalog collections](./phase-1-slice-1-schema/04-org-catalog-collections.md) | 🟩 | pending user commit |
 | 1.5 | [Event-participation collections](./phase-1-slice-1-schema/05-event-participation-collections.md) | ⬜ | — |
 | 1.6 | [Schema snapshot/apply tooling](./phase-1-slice-1-schema/06-snapshot-tooling.md) | 🟩 | pending user commit |
 | 1.7 | [Image build & entrypoint](./phase-1-slice-1-schema/07-image-and-dockerfile.md) | 🟩 | pending user commit |

.planning/phase-1-slice-1-schema/04-org-catalog-collections.md

@@ -126,4 +126,42 @@ Unique constraint: `(organization_id, device_id)`.
 
 ## Done
 
-(Fill in commit SHA + one-line note when this lands.)
+**Implementation landed and live-verified 2026-05-02.** All 7 collections live in Directus, snapshot captured at 53,450 bytes / 2,159 lines.
+
+**Driven via the `directus-local` MCP server** rather than the admin UI — same canonical result (`directus_collections` / `directus_fields` / `directus_relations` rows + actual Postgres tables), captured cleanly by `directus schema snapshot`. This was the API-driven path the spec hinted at; sub-agents can't inherit MCP from the parent conversation, so this work was driven directly without delegation.
+
+**Created:**
+- `organizations` — 5 fields (id UUID PK, name, slug unique, date_created, date_updated).
+- `vehicles` — 10 fields (id UUID PK, make, model, year, engine_cc, vin, plate_number, notes, date_created, date_updated). No ownership fields.
+- `devices` — 7 fields (id UUID PK, imei UNIQUE, model, serial_number, notes, date_created, date_updated).
+- `directus_users` — 3 custom fields added (phone, birth_date, nationality).
+- `organization_users` — 7 fields (id UUID PK, organization_id M2O, user_id M2O, role enum dropdown with 6 values, joined_at, date_created, date_updated).
+- `organization_vehicles` — 6 fields (id UUID PK, organization_id M2O, vehicle_id M2O, registered_at, date_created, date_updated).
+- `organization_devices` — 6 fields (id UUID PK, organization_id M2O, device_id M2O, registered_at, date_created, date_updated).
+- 6 M2O relations on the junctions, all with `ON DELETE RESTRICT`.
+
+**Composite unique constraints landed via `db-init/004_junction_unique_constraints.sql`** because Directus's snapshot YAML format does not capture composite unique constraints (only single-column ones via `is_unique`). The migration adds:
+- `organization_users (organization_id, user_id)`
+- `organization_vehicles (organization_id, vehicle_id)`
+- `organization_devices (organization_id, device_id)`
+
+Boot logs confirm: `[db-init] apply 004_junction_unique_constraints.sql` → `[db-init] done 004_junction_unique_constraints.sql` → assertion block passes.
+
+**Snapshot review (`snapshots/schema.yaml`):**
+- 8 collections registered (the 7 above + `positions` and `migrations_applied` as ghost entries — Directus auto-discovers tables in the public schema and registers minimal metadata for them, even though they're owned by db-init/processor not Directus). The ghost entries are harmless: schema apply against a fresh DB sees them already created by db-init and skips DDL.
+- `directus_users` custom fields round-trip correctly (no need for the spec's fallback `user_profiles` workaround).
+- All 6 M2O relations present in the relations section.
+- File size 53,450 bytes — well under the 200KB sanity threshold.
+
+**Acceptance criteria status:**
+- ✅ All seven collections exist with the fields specified.
+- ✅ Required fields flagged (organizations.name/slug, devices.imei/model, vehicles.make/model, junction org/target/role).
+- ✅ Single-column unique constraints (organizations.slug, devices.imei) enforced.
+- ✅ Composite unique constraints on junctions enforced via db-init/004 (assertion block confirms).
+- ✅ M2O relations clickable in admin UI (Directus auto-resolves the dropdowns from the relation metadata).
+- ✅ No permission policies attached — admin-only by default.
+- ✅ `pnpm run schema:snapshot` produces snapshots/schema.yaml with all 7 collections present.
+- ⏳ End-to-end test (manually create org → user → org_user via admin UI) — pending user.
+- ⏳ Apply-to-fresh-DB roundtrip — pending CI dry-run in task 1.8.
+
+**Phase 5 follow-up note (not blocking):** boot logs still WARN about `positions` lacking a PK. Already documented in task 1.7's Done section.

db-init/004_junction_unique_constraints.sql

@@ -0,0 +1,60 @@
+-- 004_junction_unique_constraints.sql
+-- Composite UNIQUE constraints on the three org-junction tables.
+--
+-- Why this lives in db-init/ rather than being captured by Directus snapshot:
+--   Directus's field-level `is_unique` flag only generates single-column
+--   unique constraints. Junction tables need composite uniqueness on the
+--   pair (org, target) so the same user/vehicle/device cannot be registered
+--   twice within the same org. The snapshot YAML format does NOT capture
+--   composite unique constraints, so Directus cannot round-trip them.
+--   They belong here, in the same place the positions hypertable's DDL lives.
+--
+-- Owned by: task 1.4 (org catalog collections). The constraints are part of
+-- the data model contract, not a separate Phase 1 migration concern.
+--
+-- Idempotency: ALTER TABLE ... ADD CONSTRAINT is NOT idempotent. The
+-- migrations_applied guard table ensures this file runs at most once per
+-- environment. If a constraint already exists (e.g. ad-hoc on an existing
+-- stage DB), the operator must INSERT INTO migrations_applied (filename,
+-- checksum) VALUES ('004_junction_unique_constraints.sql', '<sha256>') to
+-- skip this file on next boot.
+
+ALTER TABLE organization_users
+  ADD CONSTRAINT organization_users_org_user_unique
+  UNIQUE (organization_id, user_id);
+
+ALTER TABLE organization_vehicles
+  ADD CONSTRAINT organization_vehicles_org_vehicle_unique
+  UNIQUE (organization_id, vehicle_id);
+
+ALTER TABLE organization_devices
+  ADD CONSTRAINT organization_devices_org_device_unique
+  UNIQUE (organization_id, device_id);
+
+-- -------------------------------------------------------------------------
+-- Assertion block: verify all three constraints landed.
+-- -------------------------------------------------------------------------
+DO $$ BEGIN
+
+  IF NOT EXISTS (
+    SELECT 1 FROM pg_constraint
+    WHERE conname = 'organization_users_org_user_unique'
+  ) THEN
+    RAISE EXCEPTION 'organization_users composite unique constraint missing';
+  END IF;
+
+  IF NOT EXISTS (
+    SELECT 1 FROM pg_constraint
+    WHERE conname = 'organization_vehicles_org_vehicle_unique'
+  ) THEN
+    RAISE EXCEPTION 'organization_vehicles composite unique constraint missing';
+  END IF;
+
+  IF NOT EXISTS (
+    SELECT 1 FROM pg_constraint
+    WHERE conname = 'organization_devices_org_device_unique'
+  ) THEN
+    RAISE EXCEPTION 'organization_devices composite unique constraint missing';
+  END IF;
+
+END $$;