Files
homarr/qa/release-v2/reports/preflight-01/report.md
T

24 KiB
Raw Blame History

preflight-01: Candidate identity and services

Metadata Value
Status passed
Wave preflight
PR refs #6545
Candidate SHA d3e7cd45a3
Profiles main-writable, main-readonly, onboarding-fresh, degraded
Primary execution http://127.0.0.1:34499 (main-writable)
Primary fixture health http://127.0.0.1:37357/health
Runtime flags DEMO_MODE=true, DEMO_READ_ONLY=false, UNSAFE_ENABLE_MOCK_INTEGRATION=true
Persona Avery Admin
Primary sessions pf01-main-writable-d3e7; fresh pf01-main-writable-d3e7-fresh
Viewport / input 1440x900, zoom 100%, mouse and keyboard
Artifact directory /home/habs/.codex/worktrees/8ba8/homarr/.screenshots/release-v2/preflight-01
Completed 2026-09-01T10:37:30+02:00
Auth Auth-vault profiles used for seeded profiles; no password value was read or recorded

Dogfood evidence

Case ID Status Evidence Observed Expected
PF-001-ENVIRONMENT passed profile matrix and fixture artifacts All four assigned app/fixture pairs rendered in named Chromium at the required desktop viewport. App entries and fixture health endpoints were reachable; the anonymous root reached /init once without a locale loop. Candidate identity, runtime flags, browser setup, fixture reachability, and a clean app baseline.
PF-001-ACCESS passed profile matrix and Weather/reload artifacts Avery reached seeded home and healthy Weather details on main-writable, main-readonly, and degraded. The anonymous profile reached the expected first-board boundary with no seeded persona or QA board. Assigned persona, seeded access, onboarding boundary, reload behavior, and read-only boundary.
PF-001-EVIDENCE passed sanitized diagnostics and artifacts Screenshots cover home, Weather, reload, away/back, fresh sessions, keyboard search, onboarding controls, read-only boundary, fixture statuses, and degraded recovery. Text evidence contains status/path counts only. Timestamped viewport/input/zoom evidence with no secrets, bodies, or credential material.

Profile matrix

Profile App / fixture Flags Result Evidence and boundary
main-writable 34499 / 37357 DEMO_MODE=true, DEMO_READ_ONLY=false, mock integration true passed Authenticated QA v2 · Home · avery-admin; Weather details rendered Clear; reload and Board settings away/back passed; fresh named session and Ctrl+K/Escape passed.
main-readonly 44129 / 46609 DEMO_MODE=true, DEMO_READ_ONLY=true, mock integration true passed Authenticated home and Weather rendered; Edit board and Add widget boundary were inspected and dismissed without save or mutation; reload, away/back, fresh session, and Ctrl+K/Escape passed.
onboarding-fresh 40295 / 33189 DEMO_MODE=false, DEMO_READ_ONLY=false, mock integration true passed Anonymous / → /init once and stably; Get started/Restore backup visible; /auth/login stable through reload; back returned to /init; no seeded user or QA board visible; completion not attempted.
degraded 44059 / 43513 DEMO_MODE=true, DEMO_READ_ONLY=false, mock integration true passed Authenticated home and healthy Weather rendered; reload and Board settings away/back passed; fixture health/slow/empty/malformed/error statuses matched expected classes; scoped slow abort was removed and app/fixture recovered; fresh session and Ctrl+K/Escape passed.

Console, network, and artifact hygiene

Clean app and post-recovery diagnostics recorded zero page-error lines and zero console lines. No app 4xx/5xx, static-missing, locale-loop, appdata, or EACCES signal was observed. The degraded fixture’s intentional error endpoint returned 503, empty returned 204, malformed returned 200, and the fixture-only slow abort produced no response status until its route was removed; these are fixture exercise outcomes, not product findings.

All current-candidate text artifacts were normalized to status/path-classification counts. Fixture response bodies were discarded. No password, cookie, bearer value, token, request header, request/response body, query value, or secret was retained.

Performance measurements and limitations

No performance timings were requested. Visual checks used 1440x900, zoom 100%, with mouse and keyboard input. Onboarding completion and user creation were intentionally not attempted. No product state was changed; the only network interception was a fixture-only slow-path abort that was removed before final app recovery.

Findings

No product finding was opened. The observed fixture 503, 204, malformed response, and scoped route-abort behavior were deterministic fixture exercises and the degraded app remained healthy after recovery.

Mutations and persistence

No product mutation occurred. Login, fixture status checks, Weather expansion, reloads, away/back navigation, keyboard search open/close, and read-only boundary inspection did not save board changes. The onboarding controls were not submitted. The fixture was not stopped, and the temporary slow route was removed before final app recovery verification.

Artifacts

All evidence is under the preflight-01 artifact directory. All paths below are absolute current-candidate artifacts.

Cleanup

All exact named sessions used in this four-profile replay were closed after evidence capture. The artifact directory was preserved. No source, build, test, or shared report aggregator was run.