[Jaana Dogan (rakyll)]

No description provided.

[Tomer Glottmann (tomergee)]

Heads-up from #77 (Substrate bump to f03327bd): once that lands this branch needs more than a rebase.

• The fields the warm-cache template relies on no longer exist in ateapipb at that pin: onPause / onCommit (SnapshotContentScope_*, replaced by the fidelity ladder in Replace SnapshotContentScope with the SnapshotFidelity ladder and preferred_fidelity substrate#2364 and #2309) and onResume.fromData (OnResumeConfig, ResumeSource_RESUME_SOURCE_GOLDEN, removed in Remove onResume.fromData and the DATA_ON_GOLDEN restore scope substrate#2105). The per-template replacement is snapshotConfig.preferredFidelity (VOLUMES | ROOTFS | MEMORY) plus goldenSnapshotConfig; Bump Substrate to f03327bd: follow the current API and stop sending ate-target-actor twice #77 sets preferredFidelity: MEMORY on the default template. Volume.durableDir itself is still there (capacity, storageClassName).
• Textual conflicts with Bump Substrate to f03327bd: follow the current API and stop sending ate-target-actor twice #77 in cmd/ate-env/manifest.go (template builder: readyz → wakeupProbe, snapshotsConfig → snapshotConfig, shared sandboxConfigName constant) and README.md (quickstart digests and a compatibility note). manifest_test.go auto-merges.

Suggest rebasing onto main after #77 merges and re-expressing the warm-cache settings in terms of preferredFidelity.

[Tomer Glottmann (tomergee)]

This change sets onPause, onCommit and onResume.fromData in cmd/ate-env/manifest.go:306-310. The Substrate version on main does not have these fields, thus the branch does not compile after a rebase.

main sets preferredFidelity: MEMORY and keeps golden snapshots enabled by default (cmd/ate-env/manifest.go:422-427). The nearest equivalent of a data-only snapshot is SNAPSHOT_FIDELITY_VOLUMES with a durableDir workspace volume. Substrate has no replacement for a golden resume source for data.

The change also removes the empty-map check in prune for all keys (cmd/ate-env/manifest.go:341). That is a global change, not a warm-cache change.

Close this PR. If the VOLUMES level is necessary, open a new PR with a fidelity flag and an optional workspace volume.