fix: verify detached deployments

[PerishCode]

What changed

• wait for both detached oneshot completion and the exact target package version
• fail when the upgrade unit, installed version, service, doctor, memory continuity, or health check is not valid
• run doctor with the deployed EnvironmentFile so env:// provider credentials resolve without printing them

Why

The beta.24 deploy exposed a race in the old loop: it interpreted the unit's initial inactive state as completion before the queued oneshot entered activating. The wrapper then printed stale schema/service data and still returned success because doctor and health failures were swallowed.

Validation

• reproduced the premature return against the live beta.24 upgrade
• manually completed and verified the live deployment: package beta.24, schema 23, service active, health OK, memory unchanged, provider budget 120000
• deno fmt --config .runseal/deno.json --check .runseal
• deno lint --config .runseal/deno.json .runseal
• deno check --config .runseal/deno.json .runseal/wrappers/deploy.ts
• flavor check