T-F1 — Persisted provenance model

[lightningpixel]

Epic: Epic F — Provenance & re-generation
Priority: P2

Context

The asset library today is effectively a GLB graveyard (IDEAS.md, Infra & comfort section) — no "recipe" is persisted next to an asset. Verified state: workflow_runs.py only does ephemeral job tracking (_jobs in memory, generation status); IDEAS.md wrongly assumes persistence already exists. Direct synergy with Epic A: once mesh ops are centralized in the registry, logging the chain applied to an asset becomes an almost-free byproduct instead of a separate project.

Scope

• On completion of a generation and of every registry op (T-A1), append an entry { type: "generation"|"op", params, timestamp } to a *.provenance.json file next to the asset in the workspace.
• Covers assets generated both via workflow and via the chat agent (T-B2).

Acceptance criteria

Generating then repairing a mesh leaves a readable trace of both the generation and the repair op, with their params.

Depends on: T-A1

---

From ROADMAP_0.5.md.