Create the manifest before upload
Generate the release manifest from the final build directory before any upload begins. Record at least each relative path, file size, and content digest, then validate the manifest once locally. The upload stage consumes a fixed version set. If the build directory changes afterward, validation fails before files from two versions can be mixed.
Remote verification should read the same manifest and confirm every listed file and digest. The manifest then defines both the release input and its acceptance evidence, instead of treating an existing directory or a reachable home page as proof of a complete version.
Make timeout ownership include descendants
Ending only the outer process can leave behind a builder, compressor, or transfer program that it started. Treat one command as the timeout boundary and retain its process-group or equivalent tree identity. At the deadline, terminate the complete process tree with the platform-specific mechanism, then wait for the outer process to exit before reporting the timeout.
On Windows this uses taskkill /T /F; on POSIX systems it sends SIGKILL to the process group. A graceful request followed by a grace period could be added later as a separate two-stage design, but it does not describe the current strategy.