Security, for a visitor
/security says in plain words what this forge enforces for every app and every visitor with no
setting (egress refused by name, code in a cell, sandboxed agents, the sign-in cookie, the
cross-site refusal, the response headers) and how to report a problem with no account: the
security contact, a sealed security issue, /<owner>/<name>/report and an app's own
/__forge/report. Each row names the file that enforces it.
Try it: signed out, follow Security in the foot of any page, or open /security.
The terminal: open the palette and choose Security; the same rows scroll with j/k, q
closes. Both read src/view/security.ts.
Every claim names its source and its proof, and test/security-page.test.ts fails when a source
no longer says what the claim leans on or the proof is gone. Machines read
/.well-known/security.txt; the admin's side is /settings/security.