Problem
The exact-artifact PHP conformance runtime launches mysql:8.0 and redis:7-alpine by mutable tags. Candidate plans and retained suite evidence bind the seven Durable Workflow distributions, but do not bind the database and cache image bytes. Retrying or recovering the same plan can therefore execute different infrastructure under the same evidence identity, weakening reproducibility and failure attribution.
Acceptance criteria
- Resolve each required database and cache image to an immutable repository digest before experiment execution.
- Launch runtime dependencies by those exact digests and retain their normalized image identities in experiment and suite evidence.
- Recovery of an existing plan reuses the same dependency identities and fails closed if they are missing, unresolved, or mismatched.
- Contract and aggregation validation reject mutable tag-only evidence and dependency drift.
- Focused coverage proves digest binding, mismatch rejection, and recovery identity continuity.
- Public source qualification and one clean exact-artifact conformance run pass with the retained dependency identities.
Completion
Close when a public conformance release names the immutable MySQL and Redis digests it executed, and replaying the same plan cannot silently consume different dependency images.
Problem
The exact-artifact PHP conformance runtime launches
mysql:8.0andredis:7-alpineby mutable tags. Candidate plans and retained suite evidence bind the seven Durable Workflow distributions, but do not bind the database and cache image bytes. Retrying or recovering the same plan can therefore execute different infrastructure under the same evidence identity, weakening reproducibility and failure attribution.Acceptance criteria
Completion
Close when a public conformance release names the immutable MySQL and Redis digests it executed, and replaying the same plan cannot silently consume different dependency images.