Published SHA256 hash file URL is dead (thyproservices.z20.web.core.windows.net)

[jagger]

Summary

The hash file URL referenced from README.md, docs/getting_started/install.md, and the new integrity-verification snippet added in PR #451 does not resolve:

https://thyproservices.z20.web.core.windows.net/Thycotic.SecretServer_hash.txt

DNS lookup returns NXDOMAIN — the host no longer exists. Users following the docs to verify their downloaded zip have no working hash source.

Repro

Invoke-WebRequest 'https://thyproservices.z20.web.core.windows.net/Thycotic.SecretServer_hash.txt' -UseBasicParsing
# No such host is known. (thyproservices.z20.web.core.windows.net:443)

Impact

• Integrity verification step in install.md is non-functional.
• The CDN-distributed zip (https://downloads.marketplace.delinea.com/integrations/Downloads/PowershellModule/0.62.0/Thycotic.SecretServer.zip) cannot be verified by users following the documented process.

For reference, the SHA256 of the current v0.62.0 zip from the CDN is:

fbf3ab0ea1cf74b20a751b29e2526a9e7acef0a4b698864944a5715ce8b07b6b

Suggested resolution

1. Restore the hash file (or publish it to a different durable location — GitHub Release assets are the obvious choice).
2. Update README.md, docs/getting_started/install.md, and any other docs that link the dead URL to point at the new location once it exists.
3. Until restored, consider attaching a .sha256 file alongside the zip on each GitHub Release so the integrity workflow has a working source.

Filed while preparing the v0.62.0 docs refresh — see also #449, #451, #453.