Readers, the reference, and a policy that names things

Fixed

Every documentation page renders again. Reader pages were answering 200 while the browser showed "This page could not be loaded". The reader's Trusted Types policy refused a script URL by throwing, and the throw propagated into rendering, so one unexpected script origin took the whole document with it. A refused script is now substituted rather than thrown, so it can never do that again, and the mismatch that triggered it is closed.

The API reference is complete. 1,499 pages, none of them empty. The importer addressed operation pages by one slug rule and keyed their content by another, so 1,247 pages were published blank; an import that cannot say what a page contains now fails instead of writing an empty one.

Operation pages read like English. "List pages in a space", "Publish the page", "RSS feed of posts" — composed from the method and the path, instead of the handler's class name.

Web app manifests for every section. A blog, a forum, an FAQ, a status page and a legal register each answered 404 for the manifest their own page named. Only documentation had one.

A 404 says it is one. The tab used to read like a page that had loaded.

Changed

The reader's Content-Security-Policy is a list of names, not https:. Scripts, fonts, stylesheets, frames and the API a reference documents are each named. Where an address cannot be resolved the wider policy still stands — a header we cannot compute must not take a feature away.

External pictures are served from your own origin. A page of documentation references pictures from wherever its author keeps them, and loading them directly told every one of those hosts the IP and user agent of every reader of your documentation. They are fetched once into our storage and served from there instead.

The console's own policy carries a nonce, so inline script is no longer allowed wholesale.

Corrected

Dead .md links in the guides, two published lead-ins that promised a table and stopped, four answers that published their own writing prompt, the page count and rate limits in the reference, and the Deprecation header's format — it is an RFC 9745 date, not true.