Phase F10: Validation, Auth Hardening, and Design QA

phase-pal-e-docs-validation-hardening Phase

phase
Goal: Validate all new frontend features with E2E tests, audit design quality, and harden edge cases.
Owner: Betty Sue (coordination) + Dev agent (code)
Repo: forgejo_admin/pal-e-app
Depends on: F6 (private notes), F8 (note editing), F9 (board CRUD) — all COMPLETED

Scope

F10a: Auth E2E Tests + Hardening

  • Playwright tests: signin redirect, role display, FAB visibility, POST /api/notes 401 for anon
  • Auth check verification on PUT /api/notes/[slug], POST/PATCH/DELETE board item proxies
  • Private notes: verify lock icon renders, Quick-Jot private toggle works

F10b: Design Audit + Critique

  • Run /audit on edit form, board CRUD UI, private notes UI
  • Run /critique for UX quality and AI slop detection
  • Lighthouse audit on key pages via Chrome DevTools
  • Screenshot validation of new features

F10c: Hardening + Polish

  • Address audit/critique findings
  • Edge cases: empty states, error handling, text overflow
  • Final spacing/alignment/consistency pass
  • Lock in validated behavior with additional E2E tests
  • plan-pal-e-docs — parent plan
  • phase-pal-e-docs-private-notes — F6, dependency
  • phase-pal-e-docs-note-editing — F8, dependency
  • phase-pal-e-docs-board-item-management — F9, dependency