Family Login — Daedalus Handoff

Date: 2026-04-24
Status: Frontend delivered, needs backend route registration + tunnel

What I Built

/home/hoffmann_admin/.openclaw/shared/project-docs/dashboard/templates/family_login.html
- Standalone HTML (no Jinja2 dependency for initial delivery)
- Matches dashboard design tokens: dark theme, indigo accent, warm charcoals
- House icon, "Family Dashboard" branding, "Welcome home" tagline
- Full form validation, error states, loading state on submit
- Auto-focus on username field, clears password on failure
- Redirects client-side to ?redirect= param after successful login

Dashboard Router Updates

/home/hoffmann_admin/.openclaw/workspace-socrates/hoffdesk-api/dashboard/router.py

1. Added RedirectResponse to imports
2. Added GET /family/login/ route — serves family_login.html, redirects if already authenticated
3. Updated GET / and GET /dashboard/ — now redirect to /family/login/?redirect= instead of /auth/login

# New route
@router.get("/family/login/", response_class=HTMLResponse)
async def family_login_page(request: Request):
    if is_authenticated(request):
        return RedirectResponse(url="/", status_code=302)
    login_path = DASHBOARD_TEMPLATES_DIR / "family_login.html"
    return HTMLResponse(content=login_path.read_text())

Auth Router Bug (Socrates — Not Mine)

In auth/router.py, the POST /auth/login handler references redirect_url before it's assigned:

# Default redirect based on role  ← comment says this
if "family" in user.get("roles", []):  ← `user` not defined yet, `redirect_url` not defined
    redirect_url = redirect_url or "/"

This crashes on valid login. The JSON response still works (session cookie is set, success: true), so my client-side redirect handles the flow. But the server-side redirect logic is broken — worth fixing when you touch that file.

Remaining Items

Test Plan

1. Visit family.hoffdesk.com → should redirect to /family/login/
2. Login with aundrea / hoffdesk-aundrea-2026
3. Should land on dashboard, see calendar/weather/health cards
4. Logout → session cleared, back to login