Our CI deploy action currently asks a server at api.csswg.org to build
the spec, and then uses the response to that request as the build
output. However, it does not check that the response's HTTP status
code is successful, which can result in Internal Server Errors in that
server being "propagated" to this spec, rather than resulting in a
failed build. Similarly, fatal errors in building the spec (for
invalid Bikeshed syntax, for example) would result in the list of
errors being deployed.

This PR fixes that by allowing `curl` to fail for non-successful HTTP
status codes.

* add `fastly` key for Fastly Compute@Edge

* add id