Phase 1 of the Skills + Revisions + Proposals work. Purely additive — no
existing rows are touched, no tables renamed, no columns dropped.
New tables:
- ResourceRevision — append-only audit + diff log keyed by
(resourceType, resourceId). Both Prompt and Skill produce revisions on
every change. Soft FK so revisions outlive the resources they describe.
Indexed for history viewer (latest-first), semver lookup, and
cross-resource sync diff via contentHash.
- ResourceProposal — generic propose/approve/reject queue. Drop-in
replacement for the prompt-only PromptRequest. Created empty here;
PR-2 will rename PromptRequest → _PromptRequest_legacy and backfill.
- Skill — new resource type that mirrors Prompt for everything CRUD-
shaped. Adds `files` Json (multi-file bundles, materialised onto disk
by `mcpctl skills sync` in PR-5) and `metadata` Json (typed app-layer
in PR-3: hooks, mcpServers, postInstall, …).
New columns on Prompt:
- semver (semver string, default '0.1.0') — auto-bumped patch on save
by PromptService.update once PR-2 wires it. Distinct from `version`,
which stays as the optimistic-concurrency counter.
- currentRevisionId — soft pointer to the latest ResourceRevision row.
DB tests cover scope rules (project XOR agent XOR neither), name
uniqueness across both compound keys, cascade-on-delete, soft-FK
survival of deletion, and JSON column persistence.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
