Add public setup documentation

[jjjhenriksen]

Summary

• add a public /docs route for reading, uploads, evidence labels, API-key setup, deployment, and local validation
• add Docs navigation in the header and a mobile-accessible footer navigation
• add a repository setup/operator guide and connect it from the README
• revise the launch checklist to reflect merged PR Fix repository-wide autoreview findings #19, 120 passing tests, the clean production audit, and the remaining deployment inputs
• add desktop and mobile browser coverage for the docs-to-upload journey and runtime console health

Why

The product was feature-complete enough to configure for deployment, but setup knowledge was spread across the README and launch notes. This gives readers and operators one calm, public entry point before an OpenAI API key is configured, while keeping the secret-handling boundary explicit.

User impact

Readers can understand what works without a key, bring a PDF and optional Lean source, distinguish paper/Lean/curated/AI claims, and follow safe local or hosted setup instructions directly from the site.

Validation

• npm ci
• npm test: 31 files, 120 tests
• npm run typecheck
• npm run lint
• npm run proof:validate
• npm run eval:validate
• npm run build
• npm run build:sites
• npm audit --omit=dev: 0 vulnerabilities
• Playwright docs flow: desktop and Pixel 7 projects passed
• desktop and Pixel 7 full-page visual inspection
• git diff --check

The in-app Browser connection was unavailable, so rendered QA used the repository Playwright setup and screenshots stored outside the repository.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.