Published HTML artifacts can be checked against rules first and refused outright instead of shipping something unsafe.
The publish-time HTML verifier is present but its gate falls back to false and also requires the surrounding workshop feature check.
What's wrong with this entry?
Artifact publishing can now run the generated HTML through a verifier that refuses to publish when rules are violated, rather than shipping it and relying on later checks.
- publishing accepts a new
verifyWorkshopHtmloption; publishing a plan as an artifact passesverifyWorkshopHtml: "probe"when the gate is on - refusal reports per-rule violations and emits telemetry under
workshop_html_publishandverifier_refusedinstead of publishing - verified slugs accumulate into app state under
workshopVerifiedSlugs - for workshop surfaces, a redeploy must pass
refusedSidecarHistory, sourced from a new AppState keysidecarHistorySlugs, otherwise publishing is refused rather than skipping the sidecar-ordering gate - sidecar files whose content type is not in the inert text or binary allowlists are flagged as renderable or executable
- the gate falls back to false and additionally requires the surrounding workshop feature check; none of these names exist in 2.1.218
refusing rather than skipping the sidecar-ordering gate, verifyWorkshopHtml
Strings lifted out of the shipped bundle, so the claim above can be checked against them.