Merge branch 'main' into refactor/localize-google-callback-recovery-1833

Author: tyler-dane

.github/workflows/deploy-production.yml

@@ -0,0 +1,31 @@
+name: Deploy production
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'Release tag being deployed, such as v1.2.3'
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  deploy:
+    name: Deploy to production
+    uses: ./.github/workflows/_deploy-environment.yml
+    with:
+      tag: ${{ inputs.tag }}
+      environment: production
+    secrets: inherit
+
+  health-check:
+    name: Health check production
+    needs: deploy
+    uses: ./.github/workflows/deploy-health-check.yml
+    with:
+      tag: ${{ inputs.tag }}
+      environment: production
+      profile: cloud
+    secrets: inherit

AGENTS.md

@@ -87,6 +87,10 @@ Use a single-context domain-doc layout. See `.agents/config/domain.md`.
   and `user-event`; avoid CSS selectors and `data-*` locators.
 - New web styles should use Tailwind semantic colors from
   `packages/web/src/index.css`, not raw colors like `bg-blue-300`.
+- Prefer canonical Tailwind scale utilities over arbitrary values when an
+  equivalent exists. Treat VS Code Tailwind IntelliSense
+  `suggestCanonicalClasses` warnings as actionable cleanup before finishing
+  changes.
 - Do not test login flows without the required backend setup.
 - Keep React components in their own files.
 - Do not add or use barrel files such as `index.ts` / `index.tsx`. Import from

README.md

@@ -2,7 +2,7 @@
 
 **A daily planner for minimalists. Organize your day and lock-in.**
 
-<https://github.com/user-attachments/assets/ba7b91b9-1984-49f2-afc6-7fcda1100b31>
+<img width="1512" height="860" alt="week-view-2026-06" src="https://github.com/user-attachments/assets/6dcfd741-883d-401c-b8e2-97300b1dd925" />
 
 ## Why Try Compass?
 

docs/CI-CD/workflows.md

@@ -9,6 +9,7 @@ Compass uses GitHub Actions for continuous integration, Docker Hub for image dis
 | Release on main | Push to `main` | Auto-increments patch version, publishes Docker images, then deploys staging |
 | Publish Docker images | Reusable workflow / manual dispatch / manual `v*.*.*` tag push | Builds and pushes Docker images only |
 | Deploy staging | Reusable workflow / manual dispatch | Pulls published images on staging, restarts the stack, then runs deploy health checks |
+| Deploy production | Manual dispatch | Deploys a release tag to production, then runs cloud deploy health checks |
 | Deploy health check | Reusable workflow | Validates the deployed staging stack and alerts Discord on failure |
 | Sync docs to compass-docs | Push to `main` touching `docs/**` | Mirrors this `docs/` directory to docs.compasscalendar.com |
 
@@ -127,3 +128,19 @@ Secrets and variables are split between repository level (shared across workflow
 | `BACKEND_API_URL` | Staging backend API URL |
 | `FRONTEND_URL` | Staging frontend URL |
 | `GOOGLE_CLIENT_ID` | OAuth client ID |
+
+---
+
+## Production Deploy
+
+Source: [`.github/workflows/deploy-production.yml`](../../.github/workflows/deploy-production.yml)
+
+Production deploys are manual-only. Run `Deploy production` from GitHub Actions
+with an existing release tag, such as `v1.2.3`; it is not called by
+`release-on-main.yml` and does not run automatically after PR merges.
+
+The workflow deploys to the GitHub `production` environment through
+`_deploy-environment.yml`, builds an environment-specific web image tagged
+`switchbacktech/compass-web:production-<version>`, then runs
+`deploy-health-check.yml` with the `cloud` profile. Production is expected to use
+external MongoDB and SuperTokens Cloud rather than self-hosted data services.

docs/acceptance/shortcuts.md

@@ -6,7 +6,7 @@ This runbook covers keyboard shortcut parity in Compass. The principle: anything
 
 Use this guide to validate:
 
-- navigating between views with the keyboard (D, W, N)
+- navigating between views with the keyboard (D, W)
 - navigating between days in Day view (J, K, T)
 - navigating between weeks in Week view (J, K, T)
 - opening and using the command palette (Cmd+K)
@@ -20,7 +20,6 @@ Use this guide to validate:
 
 Do not use this guide to validate:
 
-- Now mode navigation shortcuts (see `tasks.md`, Scenarios 10–13)
 - full event CRUD flows (see `events.md`)
 - full task management flows (see `tasks.md`)
 
@@ -45,7 +44,6 @@ Helpful notes:
 | --------------------------- | --------- | --------------------------------- |
 | `D`                         | Global    | Navigate to Day view              |
 | `W`                         | Global    | Navigate to Week view             |
-| `N`                         | Global    | Navigate to Now view              |
 | `R`                         | Global    | Edit personal reminder note       |
 | `Z`                         | Global    | Log out                           |
 | `Cmd+K` / `Ctrl+K`          | Global    | Open command palette              |
@@ -61,8 +59,6 @@ Helpful notes:
 | `Ctrl+Meta+ArrowRight`      | Day view  | Move focused task to next day     |
 | `Ctrl+Meta+ArrowLeft`       | Day view  | Move focused task to previous day |
 | `Cmd+Z` / `Ctrl+Z`          | Day view  | Undo last action                  |
-| `E`                         | Now view  | Edit focused task description     |
-| `Cmd+Enter` / `Ctrl+Enter`  | Now view  | Save focused task description     |
 | `J`                         | Week view | Previous week                     |
 | `K`                         | Week view | Next week                         |
 | `T`                         | Week view | Go to today                       |
@@ -77,23 +73,18 @@ Helpful notes:
 
 ### UX
 
-Pressing `D`, `W`, or `N` from anywhere in the app (while not focused in an input) navigates to Day view, Week view, or Now view respectively.
-
-View shortcuts keep the same meaning in Now mode. `D` still navigates to Day view.
+Pressing `D` or `W` from anywhere in the app (while not focused in an input) navigates to Day view or Week view respectively.
 
 ### Steps
 
 1. Navigate to `/week`.
 2. Press `D`.
 3. Press `W`.
-4. Press `N`.
-5. Press `D` to return to Day view.
 
 ### Expected Results
 
 - `D` navigates to `/day`.
 - `W` navigates to `/week`.
-- `N` navigates to `/now`.
 - Each transition happens without a full page reload.
 
 ---

docs/acceptance/tasks.md

@@ -12,9 +12,6 @@ Use this guide to validate:
 - deleting tasks and undoing deletions
 - reordering tasks by drag and drop
 - moving tasks to adjacent days
-- Now mode — locking in on a single task
-- navigating and completing tasks in Now mode
-- editing a task description in Now mode
 
 Do not use this guide to validate:
 
@@ -218,90 +215,6 @@ Pressing Ctrl+Meta+ArrowLeft moves the focused task to the previous calendar dat
 
 ---
 
-## Scenario 10: Use Now Mode — Lock In On A Task
-
-### UX
-
-Now mode (`/now`) shows all of today's incomplete tasks. Selecting one locks the view to that single task, removing other distractions.
-
-### Steps
-
-1. Create at least two incomplete tasks for today.
-2. Press `N` to navigate to `/now`.
-3. Select a task from the available task list.
-
-### Expected Results
-
-- Now mode opens and displays all incomplete tasks for today.
-- After selecting a task, the view focuses on that single task with a large title display.
-- The other tasks are hidden from view.
-
----
-
-## Scenario 11: Navigate Tasks In Now Mode (J/K)
-
-### UX
-
-In Now mode with a task focused, pressing `J` and `K` cycles through the available incomplete tasks without leaving the view.
-
-### Steps
-
-1. Enter Now mode with at least three incomplete tasks (see Scenario 10).
-2. Select a task to focus it.
-3. Press `K` to move to the next task.
-4. Press `J` to move to the previous task.
-
-### Expected Results
-
-- `K` advances to the next incomplete task (wrapping around at the end).
-- `J` goes back to the previous incomplete task (wrapping around at the start).
-- The currently focused task is displayed prominently.
-
----
-
-## Scenario 12: Complete A Task In Now Mode And Advance To Next
-
-### UX
-
-Pressing Enter in Now mode marks the focused task complete and automatically moves to the next incomplete task. When all tasks are done, a completion state is shown.
-
-### Steps
-
-1. Enter Now mode with exactly two incomplete tasks.
-2. Select the first task.
-3. Press Enter to mark it complete.
-4. Press Enter again to mark the second task complete.
-
-### Expected Results
-
-- After the first Enter, the view advances to the second task automatically.
-- After the second Enter, the "No tasks available" or all-done state is shown.
-- Both tasks appear as completed in Day view.
-
----
-
-## Scenario 13: Edit A Task Description In Now Mode
-
-### UX
-
-Pressing `E` while a task is focused in Now mode opens an inline description editor (max 255 characters). Pressing Cmd+Enter (Mac) or Ctrl+Enter (Windows/Linux) saves the description.
-
-### Steps
-
-1. Enter Now mode and select a task.
-2. Press `E`.
-3. Type a description (keep it under 255 characters).
-4. Press Cmd+Enter (Mac) or Ctrl+Enter (Windows/Linux) to save.
-
-### Expected Results
-
-- An inline editor appears for the description.
-- After saving, the description is displayed below the task title.
-- The description persists after leaving and re-entering Now mode.
-- Characters beyond 255 are not accepted.
-
----
-
 ## Focused Regression Checks
 
 If time is limited, run these checks before shipping task-related changes:
@@ -313,7 +226,3 @@ If time is limited, run these checks before shipping task-related changes:
 5. Cmd+Z / Ctrl+Z restores the deleted task with its original properties.
 6. Drag-and-drop reordering persists after a page reload.
 7. Ctrl+Meta+ArrowRight moves a task to the next day; Ctrl+Meta+ArrowLeft to the previous day.
-8. Now mode shows all incomplete tasks for today and locks focus to a selected task.
-9. J/K navigate between tasks in Now mode without leaving the view.
-10. Enter in Now mode marks the task complete and auto-advances.
-11. D opens the description editor; Cmd+Enter / Ctrl+Enter saves; max 255 characters is enforced.

docs/development/feature-file-map.md

@@ -42,17 +42,14 @@ Use this document to find the first files to inspect for common Compass changes.
 - Drag handle floating placement guard: `packages/web/src/views/Day/components/Task/DraggableTask.tsx`
 - Local storage for tasks: `packages/web/src/common/storage/adapter`
 
-## Day / Week / Now Views
+## Day / Week Views
 
 - Day view route and content: `packages/web/src/views/Day/view`
 - Day view header (includes Planner Sidebar toggle control): `packages/web/src/views/Day/components/Header/Header.tsx`
 - Day keyboard shortcuts (includes `[` toggle): `packages/web/src/views/Day/hooks/shortcuts/useDayViewShortcuts.ts`
 - Day view hooks: `packages/web/src/views/Day/hooks`
 - Week view: `packages/web/src/views/Week`
-- Now view: `packages/web/src/views/Now`
-- Now shortcuts sidebar component: `packages/web/src/views/Day/components/ShortcutsSidebar/ShortcutsSidebar.tsx`
 - Shared responsive sidebar state hook (`xl` breakpoint behavior): `packages/web/src/common/hooks/useSidebarState.ts`
-- Now keyboard shortcuts (includes `[` toggle): `packages/web/src/views/Now/shortcuts/useNowShortcuts.ts`
 - Dedication dialog implementation (native `dialog` + hotkeys): `packages/web/src/views/Week/components/Dedication/Dedication.tsx`
 - Dedication dialog mount points:
   - week view: `packages/web/src/views/Week/WeekView.tsx`

docs/development/testing-playbook.md

@@ -45,8 +45,8 @@ E2E workflow (`test-e2e.yml`) is separate and runs on pull requests to `main` vi
 ## Current Test Strategy
 
 - `bun run test:core` uses `bun test` with a small compatibility preload for the core BSON mock setup.
-- `bun run test:web`, `bun run test:backend`, and `bun run test:scripts` intentionally retain the existing Jest harness while their hoist-heavy module-mocking patterns are migrated.
-- `bun run test:<project>` is the stable CI-facing entrypoint for every package; the root dispatcher chooses the correct runner per project.
+- `bun run test:web` runs `bun test --cwd packages/web` directly. Web tests should be isolated enough to run in one Bun process without batching.
+- `bun run test:backend` and `bun run test:scripts` intentionally retain the existing Jest harness while their hoist-heavy module-mocking patterns are migrated.
 
 ## Retained Jest Layout
 
@@ -116,6 +116,14 @@ Avoid:
 - implementation-detail assertions
 - unnecessary module-wide mocks
 
+Isolation rules:
+
+- Do not use top-level `mock.module` for shared production modules unless the test imports the subject through a local factory and the mock cannot affect later files. Prefer provider wrappers, real stores, explicit dependency factories, or `spyOn` with teardown.
+- Avoid mocking shared UI primitives such as `TooltipWrapper`, `@floating-ui/react`, or session hooks in broad component tests. A mock that only helps one file can change unrelated tests later in the same Bun process.
+- If a test replaces globals (`fetch`, `document.getElementById`, storage, timers, console methods), restore the original value in teardown.
+- Prefer `renderWithStore`, `createStoreWrapper`, or a focused provider harness over mocking `@web/store` or `store.hooks`.
+- `bun test --cwd packages/web` is the acceptance check for web test isolation. A focused test can pass while still leaking into the direct suite.
+
 ### Web Jest Harness Defaults (MSW + Globals)
 
 Primary setup files:
@@ -182,7 +190,6 @@ Files:
 - `packages/web/src/common/hooks/useSidebarState.ts`
 - `packages/web/src/views/Day/components/ShortcutsSidebar/ShortcutsSidebar.tsx`
 - `packages/web/src/views/Day/view/DayViewContent.tsx`
-- `packages/web/src/views/Now/view/NowView.tsx`
 
 Reliable setup pattern:
 

docs/frontend/frontend-runtime-flow.md

@@ -167,35 +167,6 @@ Pitfalls:
 - do not call `dialog.close()` directly in new close handlers unless you intentionally want to bypass the fade/scale exit animation
 - keep imports pointed at `.../Dedication/Dedication` (no barrel file in this folder)
 
-## Now Shortcuts Sidebar Runtime
-
-Files:
-
-- `packages/web/src/common/hooks/useSidebarState.ts`
-- `packages/web/src/views/Day/components/ShortcutsSidebar/ShortcutsSidebar.tsx`
-- `packages/web/src/views/Now/view/NowView.tsx`
-- `packages/web/src/views/Now/shortcuts/useNowShortcuts.ts`
-
-Runtime behavior:
-
-- sidebar state is responsive-first: `useSidebarState` sets open/closed from `window.innerWidth >= 1280` (`xl`) and subscribes to `matchMedia("(min-width: 1280px)")`
-- breakpoint transitions are authoritative: crossing the `xl` boundary re-syncs the sidebar state even if the user manually toggled it earlier
-- users can toggle via:
-  - Now header sidebar button (`Header` tooltip + `SidebarIcon`)
-  - `[` keyboard shortcut in Now view
-- the sidebar is desktop-only in layout (`hidden xl:flex`), so on sub-`xl` widths toggling updates state but the sidebar content remains visually hidden
-- `ShortcutsSidebar` filters out empty sections and returns `null` when no section has shortcuts
-
-Animation and visibility contract:
-
-- opening uses `requestAnimationFrame` to set visible state so entry transition classes apply (`translate-x-0 opacity-100`)
-- closing sets hidden classes (`-translate-x-4 opacity-0`) and unmounts when closed/not visible
-
-Pitfalls:
-
-- `useSidebarState` reads `window` during state initialization and uses `window.matchMedia`; browser-like globals must exist in tests/non-browser runtimes
-- when adding shortcuts sidebar interactions, verify Now view because Day uses the Planner Sidebar instead
-
 ## State Systems
 
 The web app uses multiple state layers:
@@ -350,4 +321,4 @@ Connect-later guardrail:
 - Auth/session issue: read session provider, user provider, router loaders.
 - Event refresh issue: read SSE hooks, sync slice, event sagas.
 - Offline issue: read storage adapter and migration runner.
-- Rendering issue in day/week/now: start at the route view, then its hooks.
+- Rendering issue in day/week: start at the route view, then its hooks.