type: reference title: "Preview alerts fixture evidence" description: "Candidate-bound single-tenant Pro alerts off/on results with retained historical failure and immutable provenance."

Preview alerts fixture evidence

This directory retains the bounded SDK #1954 integration evidence. It covers unpersisted alert draft validation on a dedicated single-tenant Pro fixture, with alerts.geofence explicitly off and on. It does not qualify alert workers, delivery, multi-tenant deployments, Community alerts, GA support, or a full release.

Run 38314349221 executed SDK source 6c2052a5182c2d691392544198fa6294706d1804 against the actual repository-variable image d7a45c87… / server e3ab87ce…. The enabled case passed; the disabled case failed, receiving HTTP 200 instead of 404. Both original Vitest reports and the original metadata are retained byte-for-byte and hashed in receipt.json. The metadata is the workflow's final conformance metadata; the two separate raw reports identify the alerts phases. HTTP statuses are also visible in that run's masked server logs.

The historical server's registry marks alerts as Implemented. Its resolver checks the experimental flag only for Experimental, explaining the failed negative control. The dotted configuration key was valid; the assertion was not weakened.

The self-contained workflow now selects the existing reviewed repository pin, 3ef3bd41… / ff5f5671… / cut 2026-10-04T08:09:54Z, directly for both fixtures. SDK PR #1956 introduced that identity and compatible seed. Successful server run 37188030565 built that exact source; its AOT publisher records the image revision and attestation subject digest. That source explicitly gates the alerts routes. The reviewed-candidate run 38315406627 passed at SDK source cd48c5e752f52be3deebc7b85d151dd3a84558cb: the off phase returned typed HTTP 404, and the on phase validated the draft. Each phase ran one test with no skips. Both workflow jobs succeeded; the combined integration report has 58 passed / 0 failed / 7 existing skips, and conformance has 2 passed / 0 failed / 4 existing skips. Those skips are not claimed as qualified. The original phase reports and metadata are retained byte-for-byte; receipt.json binds their hashes, the immutable artifact, exact evaluated source, and relevant fixture/client source hashes. The subsequent evidence commit changes only this evidence directory; evaluated executable inputs are unchanged. The historical failed run remains a failure.