Fix preview frontend parity asset detection

This commit is contained in:
rcourtman 2026-04-11 10:59:06 +01:00
parent 6e2b58d555
commit c9cd8cf14b
5 changed files with 35 additions and 16 deletions

View file

@ -185,7 +185,9 @@ dedicated preview service identity instead of defaulting back to the stable
`pulse` instance, and demo deploy/update verification must prove that the
public demo HTML serves the same frontend entry asset as the target service or
freshly built preview artifact rather than treating a passing `/api/health`
response as enough evidence that the public shell actually updated.
response as enough evidence that the public shell actually updated. That proof
must use a deterministic HTML asset parser rather than brittle escaped shell
regex that can fail differently over SSH than it does on the local runner.
Those same governed release workflows also own the operator-facing wording for
that promotion metadata. Human-visible workflow inputs, summaries, and error
messages must describe the path as a prerelease or preview flow rather than