The VPS API now runs staging source ca2fbe5b685700081b3d6e6dd0b2b8c47da548fa, including the sealed alert targets and verified marketplace links from #547. The preceding pricing-only release already contained #549; this deployment removes the remaining gap between runtime and staging.

Validation before rollout: 1,483 API tests passed with SQL fixtures enabled, zero skipped; API typecheck and check-JS passed; 554 ingest tests passed. A separate actual-route/PGlite check reapplied migration 0047 three times, preserved an existing card alert, inserted/updated a sealed alert, isolated another owner, and rejected an unauthenticated read. No paid provider was called. Native PostgreSQL 16 E2E was not run locally.

Image: skns-api:staging-ca2fbe5-20261021. A private alert-table recovery dump was created on the VPS before the additive schema update, which ran in a transaction with a two-second lock timeout and preserved existing alert rows. A temporary candidate used an automatically assigned loopback port and passed health plus catalogue reads before the API service was replaced. An initial candidate smoke request omitted required catalogue filters; the active API remained unchanged until that request was corrected and verification passed.

All active Compose overlays, runtime environment and mounted data were retained. Other running containers kept their IDs and start times. The candidate was removed after promotion. Public health/readiness and catalogue reads passed; the prior API image remains available for rollback. Ten passive ETB reads still returned 399 EUR with the original acquisition date; those reads and two unauthenticated live refusals added zero provider reservations.