pipework 0.8.7 → 0.8.8

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.8.8
+
+- **Fix: pipework's internal tables were never delivered to consumer databases** — configuring `trace: {}` or `audit: {}` in a blueprint left the supporting tables (`trace`, `trace_step`, `trace_retained`, `trace_step_retained`, `audit_record`) absent from the database. The migration generator only walked the consumer's `schema.ts` exports and never saw pipework's own definitions, so the first traced HTTP request or audit emit crashed against a missing table. `pipework generate` now auto-includes the trace tables when `blueprint.trace` is present and `audit_record` when `blueprint.audit` is present. Internal tables only ride on the default database — trace and audit both target it at runtime.
+
 ## 0.8.7
 
 - **Fix: pipework's startup validator rejected its own internal tables** — booting a manifold with pipework-only definitions (`audit_record`, `trace`, `trace_step`) crashed with seven `brand "TraceId"/"TraceStepId" used by both …` errors. `audit_record.traceId`/`traceStepId` are deliberately branded but unreferenced (the audit partition outlives its source trace partition, so an FK would prevent independent retention). The validator's brand-reuse check had no way to express "logical reference without enforced FK" and flagged the columns as conflicting brand definitions. The startup tests missed it because `tests/validation/startup.test.ts` wipes the registry in `beforeEach`, so the validator only ever saw synthetic fixtures.