HTML responses
A route scaffolded with -response html gets response.HTML(w, r, module, name, title, data) instead of response.JSON. Unlike everything else in the framework, this reads its content file and layout.html straight off disk on every request — not from the embedded binary — so you can edit the page without rebuilding. Content is rendered first (auto-escaped via html/template), then embedded as {{.Content}} inside the layout.
The page data also carries {{.Subject}} (the caller's authenticated subject — always empty for an -auth none app) and {{.Path}} (the request path). layout.html can additionally reference {{.Header}}, {{.Sidebar}}, and {{.Footer}} — three optional partials resolved the same module-then-shared way as content itself; missing anywhere in that hierarchy simply renders as empty, never an error, so a module with no header/sidebar/footer of its own is unaffected.
response.HTMLError(w, r, module, status, title, data) and response.Unauthorised(w, r, module, data) (a fixed 403) render a module's error-content.html/unauthorised-content.html the same way, for an admin page that wants a styled error instead of the plain JSON envelope — falling back to that JSON envelope if the page itself can't be found or rendered.