Artifact pinning

trigora deploy stores an artifact and a hash. Starting an Execution records programVersionId and artifactHash.

On resume the host runs that stored artifact. A caller-supplied artifact is only a check. If the hash differs, resume fails with an artifact mismatch. A newer deploy does not silently retarget a waiting Execution.

That pin is part of recovery. The continuation’s control position is meaningful for the artifact that produced it. Mixing a new blob with an old continuation is not a resume.

See Versions and How recovery works.