transformation registry, transformation runs, and derived artifact lineage

docs/asset-registry-implementation.md

@@ -63,6 +63,8 @@ and SQLite repositories are adapters behind those ports.
 - Relationship changes create source-asset version records and audit events.
 - Idempotency records for safe asset creation retries.
 - Idempotency-key reuse with a different payload raises a validation error.
+- Transformation run and derived lineage persistence for traceable derived
+  artifact creation.
 - In-memory repository for deterministic tests.
 - SQLite repository for local-first durable asset registry state.
 - SQLite foreign-key enforcement for representation and metadata asset
@@ -84,11 +86,15 @@ and SQLite repositories are adapters behind those ports.
 - `audit_events`
 - `retrieval_feedback`
 - `idempotency_records`
+- `ingestion_jobs`
+- `transformation_runs`
+- `derived_lineage`
 
 Payloads are stored as compact JSON envelopes while indexed columns carry
 stable lookup fields such as asset ID, lifecycle, representation kind, digest,
-sequence, relationship source/target, actor ID, target, correlation ID, and
-idempotency key.
+sequence, relationship source/target, actor ID, target, correlation ID,
+idempotency key, transformation status, operation ID, and derived output asset
+ID.
 
 ## Not Yet Implemented