Production artifact and isolated recovery smoke validation

After each production, candidate, or versioned frontend rebuild, verify successful completion, artifact identity, dist/assets, version data, and applicable health endpoints. Preserve the complete output in a referenced log and report notable artifact sizes; known chunk-size, chunking, manualChunks, and source-map advisories are non-fatal when the build succeeds. Then test the exact artifact with a fresh uniquely versioned disposable recovery/restart script under /tmp/opencode/, using isolated server, database, migration, runtime, and session paths with bounded probes. Clean up only spawned disposable processes and preserve required databases.