Verify uploaded deployment source against the running release

When a hosting service is deployed by local upload rather than a linked commit, deployment history may show a healthy release without identifying its source tree. Before uploading a fix, compare the running container's relevant source files or hashes with the intended checkout; after upload, verify the exact new deployment reaches success and probe the served page. A matching subset supports only that subset, so avoid claiming full source parity unless the complete source tree or artifact is compared. This is especially useful when several active branches could plausibly be the deployed version.

Applies when: a release was uploaded from a local directory and has no linked source revision. Keywords: deployment provenance local upload container source checksum checkout regression