* Add append-only provenance_events log and bd provenance CLI
A generic primitive for capturing work provenance — the base commit a
worktree forked from, which actor touched a bead when, what landed it —
as an append-only event log keyed to an issue. Inert by default: nothing
writes it unless a producer (git hook, orchestrator, CI) opts in.
- Migration 0052: provenance_events (CHAR(36) UUID pk, FK issues
ON DELETE CASCADE ON UPDATE CASCADE, indexes on issue_id/ref/kind).
Sibling to events, per the wisp_events precedent for purpose-specific
event tables rather than overloading the field-mutation audit log.
ON UPDATE CASCADE so a bd rename (which updates issues.id in place)
does not hard-fail the FK, matching the other aux tables (0042).
- Append-only at the event level: only record/log/by-ref operations, no
UPDATE or DELETE of an individual event. An event's lifecycle is bound
to its issue — removed only if the issue is deleted (ON DELETE CASCADE),
identical to the events audit table (0005).
- Opaque actor/ref (bd never interprets them); only kind and ref_kind are
structurally validated (ZFC). occurred_at (event-time) is separate from
created_at (ingest-time). A reserved 'ingest-backfill' source is rejected
so a producer cannot forge a derived event.
- Idempotent record via a content-addressed deterministic id, so a producer
firing twice is harmless; an event with neither a ref nor occurred_at is
rejected at the store boundary (no stable id otherwise). occurred_at is
truncated to whole seconds for both the id basis and the stored value, so
the id stays reproducible from the stored row (the column is bare DATETIME,
second precision) — a sub-second --at records idempotently.
- bd provenance record|log|by-ref; logic shared in issueops, both Dolt
stores delegate (mirrors the events pattern). The record command calls the
exported ValidateProvenanceEvent for early CLI feedback, with the store as
the real boundary.
- ADR-0003 records the rationale (why not extend events, why opaque ids,
event-level append-only vs issue-bound cascade, distributed-merge note).
CGO tests cover round trip, idempotency, sub-second-at idempotency, opaque
field round-trip, and the validation guards.
* Fix provenance CLI lint and review nits
Return JSON output errors from provenance commands, silence Cobra usage/error duplication on the new command group, document deterministic provenance IDs accurately, and add the composite issue/occurred_at index promised by the design.
Agent-Signature: codex-gpt-5.5-high on behalf of matt wilkie
* fix-merge(provenance): renumber to 0063, drop pinned-doc artifacts, stage provenance_events, ADR to engdocs
Maintainer-side rebase tail for PR 4461 after 505 commits of drift; author's
blockers were all fixed on 2026-07-08.
Co-authored-by: sjarmak <sjarmak@users.noreply.github.com>
Agent-Signature: claude-code-sonnet-builder on behalf of maphew
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix-merge(provenance) round 2: backend contract aliases + latest-migration mock shape
Two more surfaces main grew after the 7/27 approval:
- backend public-contract completeness ratchet (#5321) requires aliases
for types reachable from the contract: add ProvKind + ProvenanceEvent
- schema lock tests script sqlmock against the LATEST migration's body
shape; latest is now 0063 (plain CREATE TABLE -> ExecContext), not
0062's bare CALL (-> DrainCall/QueryContext)
---------
Co-authored-by: sjarmak <sjarmak@users.noreply.github.com>
Co-authored-by: matt wilkie <maphew@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Steve Yegge <steve.yegge@gmail.com>