fix(schedule): restore calendar refresh and refine account header

[znnnnnnn-wil]

Part of #81

Summary

• Preserves and regression-tests the HomeScreen → refreshSignal → ScheduleCalendarScreen → useScheduleCalendar refresh path so an applied voice schedule command re-runs the existing range and location queries.
• Keeps the internal accountId in account-scoped schedule queries while ensuring it is never rendered as calendar-home text.
• Moves the username and logout action out of the standalone account bar and into the calendar Header as a lightweight avatar pill plus a compact logout icon button.
• Keeps the existing sign-out flow reachable from the SQLite loading and initialization-error states without restoring the global account bar.
• Keeps long usernames on one line with tail truncation and constrains the account controls for narrow phone layouts.

Visual evidence

Mobile — 390 × 844

The screenshot was captured from the current branch with browser device emulation. It shows the username pill and logout icon in the top-right Header while the selected date, month calendar, and daily schedule list retain their existing widths.

Verification

GitHub CI — current head 773999f

• Frontend (lint, types, build) — passed
• Backend (lint, types, tests) — passed
• Backend (migrations) — passed
• Vercel Preview Comments — passed

Executed locally

• npm run lint — passed
• npm run typecheck — passed
• npm run test — passed: 47 Vitest tests and 282 Jest tests
• npx expo export --platform android — passed
• focused Prettier check for all changed source/test files — passed
• git diff --check — passed
• focused AppRoot regression run with --detectOpenHandles — 1 suite / 10 tests passed

Local note: the full Jest command exited successfully after all 282 tests passed, but emitted its non-failing open-handle warning after rebasing onto the latest #243 main. The focused changed-area suites exit cleanly; this scoped PR does not alter the new continuous-voice lifecycle implementation.

Known existing behavior

The existing assistant application tests expect lastAppliedCommand to update even when a local schedule write fails. That can cause a harmless re-query of unchanged local data on the failure path. This PR preserves the established write/ack semantics and covers the successful applied-command refresh path without expanding into assistant business logic.

Scope

This PR is limited to the calendar-home refresh regression coverage, account Header presentation, directly related tests, and the review screenshot.

It does not modify:

• schedule business rules
• schedule models
• SQLite schema, migrations, or sync behavior
• HTTP / WebSocket contracts
• Agent interfaces, including the five existing interface names/inputs/outputs
• ASR / LLM / TTS behavior
• reminder execution semantics
• the style(schedule): redesign schedule detail sheet #240 schedule detail UI
• unrelated screens or global theme tokens

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
timeflow	Ready	Preview	Aug 14, 2026 3:33am

[fennoai]

Found one functional regression in the authenticated loading/error path. Targeted Jest tests (14 tests), TypeScript type-checking, ESLint, Prettier, and git diff --check passed.

View job run