@consiliency/agent-board-schema

Canonical, immutable, exact-pinnable agent_board schema bundle. Message Board owns the schema bytes, ordering, compatibility rules, and the deterministic adopter tooling; adopters (e.g. the Portal Supabase project) pin an exact release and materialize it — they do not author agent_board DDL.

What's in the bundle

• migrations/ — the ordered, immutable SQL union (frozen baseline + lane migrations + the Message Board-owned endpoint compatibility migration).
• schema-manifest.json — package version, agent_board.schema_version, ordered migration IDs, per-file SHA-256, aggregate digest, source refs + merge base, minimum client version, PostgreSQL/Supabase assumptions, and external dependencies.
• provenance.json — per-file origin/source-ref/digest for every migration + test.
• tests/ — the pgTAP suite + tests/fixtures/ (adopter-base + test/operator prerequisites).
• fixtures/ — plan/check history snapshots.

Adopter CLI (the only supported path)

# Write the exact pinned migrations into an adopter workspace (original IDs,
# exact bytes, provenance marker, receipt). Refuses to overwrite manual edits.
agent-board-schema materialize --target <adopter>/supabase/migrations

# Read-only posture against a supplied migration-history snapshot.
agent-board-schema plan  --history history.json
agent-board-schema check --history history.json     # exit 0 exact / 10 behind / 11 ahead / 12 divergent

# Self-contained smoke: byte-exact + idempotent materialize.
agent-board-schema materialize --check-smoke

agent-board-schema manifest    # print the compatibility manifest
agent-board-schema version

After applying the materialized migrations, the adopter records the install so the authenticated compatibility RPC reports live:

select agent_board.record_bundle_installation(
  '<packageVersion>', '<bundleDigest>', <schemaVersion>, '<sourceCommit>', '<receiptId>'
);
select agent_board.get_bundle_compatibility();  -- authenticated health, no secrets

Rules

• Released migration bytes are immutable. Corrections are forward-only new migrations with new IDs and tests — never edits to shipped SQL.
• SemVer covers SQL, manifest schema, and the materialize/plan/check command/argument/output/exit-code contracts.
• Materialization never mutates database history directly; the adopter operator applies it via the Supabase CLI.