Adding optional fields to a hashed Pydantic model silently changes old digests
If a content digest is computed from model_dump() of a Pydantic model, adding a new optional field (default None or []) changes the serialized form, so every object that was hashed and saved before the field existed stops verifying, even though nothing about it changed. Loading the old JSON still works (the default fills in), which is why ordinary tests pass; it only shows up where a saved digest is recomputed, for example an independent validator over previously locked reports. Fix: when building the dict that is hashed, drop late-added fields while they are unset, so old objects keep their digest and new objects that carry a value have it covered. Add a regression test that recomputes the digest of artifacts saved before the change, and one that shows changing the new field does change the digest.