3.2 KiB
Verification
Verified locally on 24 October 2026 using pinned Bun 1.4.4 and TypeScript 7.0.2:
bun install --frozen-lockfile: committed resolution accepted without changes.bun run check: strict TypeScript check passed for frontend, Bun scripts and tests.bun test: 8 Bun tests passed, including catalog parity, authentication request options, malformed Hub/session checks, avatar-origin validation and encoded preview-path traversal.bun run build: TypeScript browser bundle and static build completed; assets normalized to mode 0644, directories 0755. Source TypeScript and development dependencies are excluded from the release.bun run format:check: Bun's built-in formatter passed.bun audit: no known vulnerabilities across 25 checked lockfile packages; direct dependencies are current.python3 tests/browser_qa.py: passed against both the Bun development preview and the minified productiondist/preview with the workstation's existing Playwright and/usr/bin/chromium; no browser dependency was installed by this project.
The optional browser script requires the loopback preview from bun run dev or bun run preview. It replaces API responses with test fixtures and refuses non-loopback origins. It checks:
- Keyboard-operated illustration tabs and theme selection.
- Runtime RU/EN changes and layouts at 320, 390, 768 and 1440 pixels, including account views.
- Enabled, disabled and unavailable GitHub sign-in; retry after session failure.
- Profile values rendered as text, rejected unsafe avatar URLs and no script execution from hostile profile fixtures.
- CSRF-header/Origin/POST sign-out and expired-session handling.
- Browser storage contains only the UI language; no account tokens are persisted.
Local QA screenshots were visually inspected in /tmp/vnox-web-qa/. Any authenticated profile in those temporary images is explicitly a browser fixture. The repository-hosted README screenshots were captured separately from the live production site using a fresh anonymous context and contain no test profile or private data.
Limits
These frontend tests do not authorize a real GitHub user, verify provider consent or exercise Hub database/session internals. A live end-to-end GitHub authorization requires the account owner to complete provider consent. The loopback preview intentionally has no backend. Production deployment and HTTPS/security-header checks belong to the site's operator and must preserve the Hub's OAuth callback and cookie configuration.
Production verification — 24 October 2026
Published source commit 622f396364bb to central.loki-code.dev, static release 622f396364bb-9b77c9dbd02c. Live Chromium checks passed for desktop landing, anonymous account/GitHub entry, mobile account layout, CSS MIME and JavaScript console. Hub readiness/info, logo assets and authentication endpoints remain available at the same origin. CSP uses self-hosted scripts/styles, no external fonts, same-origin API connections and a specific GitHub avatar image origin. OAuth callback query logging remains disabled. A real user's GitHub consent/code exchange remains a manual verification step.