#3733 typed-secrets 4.4: persistence and resume hold references: rehydration stops reading the vault, every persisted copy uses the persisted form, and run events are masked

Problem

rehydratePersistedForm still reads the vault to restore values, and toPersistedForm still searches recorded values for the plaintext that data reads bring into CEL. Resume, retry and the last-evaluated replay therefore reproduce old values and read the vault outside a delivery.

Scope (Section 8, Phase 4)

• rehydratePersistedForm issues a sentinel in a new bag for each writtenReferences entry and reads no vault. Resume, retry and the last-evaluated replay load current values under current authorization at delivery, and rerun no completed step.
• swamp workflow evaluate writes its cache through the boundary conversion with zero loads, as swamp behavior evaluate already does.
• toPersistedForm takes entries from sentinels only; the value search goes once typed-secrets 4.2 makes data reads return references. Every persisted copy uses the persisted form: evaluated caches, run records (WorkflowRun.toPersistedData), the run index, output records, the data catalog and control-plane records, and on v3 the commit log, blobs and read model.
• Masking in run events, run records and the run index.
• Existing files keep their encoding on read: json, number and boolean entries restore as Section 8.1 says, and sensitiveFormat does not change.

Exit

Every persistence seam round-trips through writtenReferences (Section 12.1), existing files read back, sentinel-shaped text from another prefix persists as data, and resume loads current values and reruns no completed step.

Depends on typed-secrets 4.2.