Provide practical day, travel and household assistance

Priority: P2 (later — after core reliability).

Once the core is reliable, compose its existing capabilities into everyday outcomes rather than adding disconnected services.

Acceptance criteria

• Plan a day around confirmed commitments, travel time, weather and working/household preferences.
• Support travel itineraries with source freshness, constraints and clear distinction between suggestions and bookings.
• Maintain shared shopping/errand lists with explicit membership and ownership.
• Track user-requested deliveries, renewals, subscriptions and important dates through existing tasks/events.
• Allow useful single-user operation without joining a social network; sharing remains explicit.
• Deliver the plan/list/tracker as an editable record with links to underlying tasks and events; test conflicts, stale sources and private/shared access.

Dependencies and boundaries

Depends on personal context, connections, permissions, reminders and project records. Implement one validated workflow at a time; purchases/bookings require appropriate authority.

Implementation approach

Audit current main first: some foundations and recent fixes already exist. Close remaining user-visible gaps and preserve working behaviour. This issue records the personal-assistant product backlog, not a claim that every underlying capability is absent. Add focused regression coverage for the behaviour changed.

Begin by auditing the current main and its existing foundations and recent fixes, then select one validated workflow rather than treating this as a single implementation. Trace the relevant personal context, connections, permissions, reminders, tasks and events before defining focused regression coverage. Done means the chosen workflow produces an editable plan, list or tracker linked to underlying records while preserving explicit private/shared access.