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

27 KiB
Raw Blame History

preflight-01: Candidate identity and services

Metadata Value
Status passed
Wave preflight
PR refs #6545
Personas Avery Admin
Boards None
Profiles main-writable, main-readonly, onboarding-fresh, degraded
Primary execution URL http://127.0.0.1:34401
Primary execution port 34401
Primary execution profile main-writable
Primary runtime flags DEMO_MODE=true; DEMO_READ_ONLY=false; UNSAFE_ENABLE_MOCK_INTEGRATION=true
Primary fixture health http://127.0.0.1:37273/health
Chromium viewport desktop-1440 (1440×900)
Zoom 100%
Input mouse, keyboard
Artifact directory /home/habs/.codex/worktrees/8ba8/homarr/.screenshots/release-v2/preflight-01
Candidate SHA f57a660088
Corrected rerun completed 2026-08-31T22:57:16+02:00
Auth Auth-vault profiles used for seeded profiles; no password value read or recorded

Dogfood evidence

Case ID Status Evidence Observed Expected
PF-001-ENVIRONMENT passed all-profile runtime and fixture artifacts main-writable (34401/37273), main-readonly (41589/44267), onboarding-fresh (41775/33549), and degraded (43903/39181) all rendered in named Chromium at 1440×900. Each fixture /health rendered {"status":"ok","fixture":"release-v2-qa"}; / routed to /auth/login for the seeded profiles and /init for onboarding-fresh without a loop. Verify candidate identity, Chromium session, runtime health, fixture reachability, and clean console/network baselines.
PF-001-ACCESS passed profile matrix and onboarding artifacts Avery reached the seeded home on main-writable, main-readonly, and degraded. Read-only Edit board/Add board content remained visibly available and no save/mutation was attempted. The fresh slot reached the expected first-board onboarding boundary with no seeded user or QA board and a normal /auth/login form; onboarding completion/user creation is outside PF-001 scope. Verify assigned profiles, personas, boards, permissions, and read-only boundaries before mutations.
PF-001-EVIDENCE passed timestamped screenshots, snapshots, and diagnostics All four profiles have rendered screenshot evidence plus console/errors/network metadata at the assigned 1440×900 viewport. The onboarding run includes initial /init, explicit /auth/login, fixture health, reload, and a second fresh named session; diagnostics were sanitized and contain no secrets. Capture timestamped viewport/input/zoom evidence and confirm artifacts contain no secrets.

Profile matrix

Profile Status App entry Fixture health Persona/access Reload/session Visible boundary
main-writable passed /auth/login → / {"status":"ok","fixture":"release-v2-qa"} QA v2 · Home · avery-admin with Edit board, Board settings, and three seeded widgets passed Writable affordances visible
main-readonly passed /auth/login → / {"status":"ok","fixture":"release-v2-qa"} QA v2 · Home · avery-admin with three seeded widgets passed Edit board/Add board content remained visible; mutation/save boundary not exercised
onboarding-fresh passed / → /init; explicit /auth/login stayed on /auth/login {"status":"ok","fixture":"release-v2-qa"} Expected first-board onboarding boundary rendered; no seeded user or QA board was visible, and no seeded persona/home access was assigned Reload returned /init; second named session also returned /init Get started/Restore backup visible; completion/user creation is outside PF-001 and was not attempted
degraded passed /auth/login → / {"status":"ok","fixture":"release-v2-qa"} QA v2 · Home · avery-admin with three rendered widgets passed Degraded profile entry and home rendered; no fixture health failure

Console, network, and artifact hygiene

The browser errors captures were empty for all corrected runs, including both onboarding sessions. Console captures contain development HMR/React DevTools information and repeated PostHog initialization warnings, but no uncaught application error. Network metadata shows successful app/auth/home/health responses for the seeded profiles and /init, /auth/login, /health, reload, and new-session responses for onboarding-fresh. Non-blocking dev-only 404s for a Next static chunk/favicon were observed; no redirect loop occurred.

No password, cookies, bearer values, request bodies, or unredacted credential-like values were inspected or recorded. The read-only add-widget dialog was opened and cancelled without submitting a widget or changing product state. Onboarding controls were not submitted, so no user or board was created.

Performance measurements and limitations

No performance timings were requested for PF-001. Onboarding-fresh was verified at its expected initial /init access boundary; completion and user creation are outside PF-001 and were intentionally not attempted. Current authenticated-profile access and all assigned evidence checks were run.

Findings

No tracked finding remains after the successful retest. The previous RV2-P1-001 locale/auth redirect-loop finding was removed because it was not reproduced in fresh sessions for main-writable, main-readonly, or degraded, and onboarding-fresh also showed no redirect loop. The successful retest is recorded in the structured notes above.

Mutations and persistence

No product mutation occurred. Login, fixture navigation, clean reloads, opening/cancelling the read-only add-widget dialog, and exiting edit mode all completed without saving board changes. Avery’s seeded home remained available after reload for all three current authenticated profiles. The onboarding-fresh Get started/Restore backup controls were left untouched; no user or QA board was created.

Artifacts

Corrected desktop-1440 evidence is under the preflight-01 artifact directory. The structured artifact list above is canonical for this report.

Cleanup

The named sessions qa-v2-preflight-01-rerun-onboarding-1440 and qa-v2-preflight-01-rerun-onboarding-new-1440 were closed after capture; earlier seeded-profile rerun sessions were also closed. Existing packet artifacts were preserved. No shared report aggregator or ledger was run.