Nuxt 3 .output restore: missing integrity verification after deployment

When a Nuxt 3 application is redeployed, the standard approach is to copy the entire .output directory to the target host and start the Nitro server. However, Nuxt does not ship a checksum, signature, or manifest that can confirm the restored bundle matches the original build. This raises a question: how can we reliably verify that the recovered files are present and unmodified before launching the application?

Key constraints include:

• Nuxt 3 only emits the .output folder; there is no built‑in integrity artifact.
• Missing or corrupted files may cause silent failures or stale client data.
• Nitro’s runtime does not automatically validate the integrity of the file system.

Unresolved behavior: should a custom pre‑deploy check be added, or can we rely on Nitro to surface issues at runtime?

1. What programmatic checks can be added to a deployment pipeline to confirm that all critical files in .output (server entry, client chunks, public assets) are present and match expected hashes?
2. Is it advisable to generate a checksum or manifest during nuxi build that can be used post‑restore to validate file integrity?
3. Does Nitro’s server handler automatically detect missing or corrupted files during runtime, or must we perform explicit verification before starting the server?