Project page hub redesign

[h4yfans]

Rewrites the project page as a hub. Everything a project holds — tasks, notes, files, events — is reachable from one page, with per-category focus and navigation that lands you in each item's real home view.

What changed

Header — project name, 12/30 done, and an overdue pill that appears only when something is past due. The icon opens the picker; ⋯ edits or archives.

Capture bar — one input. Plain text becomes a task in this project (the existing quick-add parser still handles friday p1); a bare URL becomes a note holding that link, already added to the project; the paperclip imports files and links them.

Five in-page tabs — Overview / Tasks / Notes / Files / Events. Overview previews five of each category with a View all that focuses that tab. None of it opens another app tab: the choice lives in tab.viewState, so it survives tab switches.

Rows behave like their home view — change a task's status or priority from the row, click a note's icon to change it, click any row to open the item. A linked event opens the Calendar on that event's day with its detail showing, instead of dropping you on today. That reuses buildRedirectTab from the canvas rather than re-deriving the viewState.

Details rail — built and wired on all five tabs, collapsible from a toggle that stays in place while closed, so reopening is the same button. Carries the overview note (inline, editable), pinned notes, progress, and details. It ships behind PROJECT_RAIL_VISIBLE = false — the rail, its toggle, and the remembered open/closed state all stay in place, so turning it on for users is a single edit. Progress renders one row per status the project defines — a project with four in-progress statuses gets four rows — plus an overdue row when relevant.

Performance

The old page called tasks:project-list-links four times per load (once by the page, once inside each of the three section components) and then resolved every link with its own IPC round trip: ~74 calls for a project with 70 links. One new tasks:project-list-contents joins project_links against note_metadata and calendar_events in a single pass. The join also drops orphaned links, so the defensive null-filtering each section did is gone.

Schema and sync

One additive migration, 0042_project_link_pinned.sql: project_links.pinned INTEGER NOT NULL DEFAULT 0, for the notes pinned to the overview. Every existing link keeps its current behaviour.

Backward-compat landmine, handled: links reconcile wholesale rather than field-merging, and the update branch wrote a fixed column set. A payload pushed by a client that predates this change carries no pinned key, so it would have wiped every local pin. reconcileLinks now falls back to the existing row's value, with a test that fails if the fallback is removed (verified by mutating it).

No new SyncItemType, no server change. "Updated" in the details panel needed no column at all — projects.modified_at already exists, is stamped by every mutation, and is already field-merged.

Removed

project-home.tsx, project-stats-row, and the project-{notes,files,events}-section components are superseded. projects-tab-content.tsx went with them — it was already unreachable from the app, with only a test importing it. project-selector.tsx stays; project-picker and use-project-quick-create still use it.

Verification

lint (0 errors, 0 new warnings), typecheck, test, ipc:check, check:architecture, check:contracts, i18n:check, docs:impact --strict, docs:build — all green. 49 unit tests cover the new page.

The E2E spec has not run. tests/e2e/project-hub.e2e.ts is new and untested locally: Electron fails to launch on this machine during fixture setup, and a pre-existing spec (tasks-kanban) fails identically at the same point, so this is the known local-launch problem rather than the new spec. CI is its first real run.

Known limitation

The Events section's + opens the Calendar with a create intent; the new event is not linked to the project automatically. Linking still goes through the existing calendar chip menu. Adding a project-side event picker was out of scope here.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

React Doctor found no new issues. 🎉

_{Reviewed by React Doctor for commit cfbfafe.}

[codecov]

Codecov Report

❌ Patch coverage is 71.33550% with 264 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...s/desktop/src/renderer/src/pages/project/index.tsx	0.00%	102 Missing ⚠️
...p/src/renderer/src/pages/project/rail-overview.tsx	0.00%	37 Missing ⚠️
...src/renderer/src/pages/project/project-tab-bar.tsx	0.00%	36 Missing ⚠️
apps/desktop/src/main/ipc/tasks-handlers.ts	16.00%	21 Missing ⚠️
...op/src/renderer/src/pages/project/rail-details.tsx	0.00%	13 Missing ⚠️
...c/renderer/src/pages/project/tabs/overview-tab.tsx	0.00%	12 Missing ⚠️
...ktop/src/renderer/src/components/capture-input.tsx	79.59%	9 Missing and 1 partial ⚠️
...enderer/src/components/capture-bar/capture-bar.tsx	96.73%	6 Missing ⚠️
...rc/renderer/src/pages/project/tabs/hub-section.tsx	50.00%	5 Missing and 1 partial ⚠️
...nderer/src/pages/project/project-capture-input.tsx	91.30%	3 Missing and 1 partial ⚠️
... and 7 more

📢 Thoughts on this report? Let us know!

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Pull request overview

Copilot reviewed 78 out of 78 changed files in this pull request and generated 1 comment.

Suppressed comments (5)

apps/desktop/src/main/ipc/tasks-handlers.ts:280

• Similarly, file imports link files to the project via void domain.linkItemToProject(...), so linking failures won’t be reflected in ImportFilesToProjectResult (and can surface as unhandled rejections). This can cause the UI to show “files added” even when the link step fails.

        return importFilesToProject(
          {
            importFiles: async (sourcePaths) => {
              const result = await importFiles({ sourcePaths })
              return { importedFiles: result.importedFiles, errors: result.errors }
            },
            getIdByPath: async (destPath) => (await getNoteByPath(destPath))?.id ?? null,
            linkToProject: (projectId, fileId) => {
              void domain.linkItemToProject({ projectId, itemType: 'file', itemId: fileId })
            },

apps/desktop/src/renderer/src/pages/project/use-project-hub.ts:167

• In the error path, the hook logs but never updates loaded, which leaves homeNoteId stuck as undefined and can make the overview-note rail render the loading spinner indefinitely. Consider setting an explicit fallback payload (empty contents + homeNoteId: null) so the UI can still render and let the user create an overview note even if the IPC call fails.
  apps/desktop/src/renderer/src/pages/project/project-capture-input.tsx:100
• result.failed can include entries with an empty path (e.g. importer-level errors). Toasting fileError with {name: ''} produces a confusing message, and the more actionable failure.error is never surfaced to the user.
  apps/desktop/src/main/tasks/capture-url.ts:55
• captureUrlToProject treats the page title as link text, but the title is not escaped for markdown. Titles containing ] (or \) will produce malformed markdown like [...] (url) and can render incorrectly in the created note.

  const note = await deps.createNote({
    title: title?.trim() || titleFromUrl(input.url),
    content: `[${title?.trim() || input.url}](${input.url})\n`
  })

apps/desktop/src/renderer/src/pages/project/index.tsx:276

• ProjectOverviewNote calls onHomeNoteChange(noteId) specifically so the parent can update homeNoteId immediately (avoiding the “create” UI staying visible after create/clear until a refetch completes). Here onHomeNoteChange ignores the argument and only triggers hub.refresh(), which can leave a confusing intermediate state.

[Copilot]

Pull request overview

Copilot reviewed 106 out of 106 changed files in this pull request and generated 1 comment.

Suppressed comments (3)

apps/desktop/src/main/tasks/capture-url.ts:64

• The markdown link destination uses (${input.url}). URLs containing spaces or parentheses (common in Wikipedia, Google Docs, etc.) will break markdown parsing (similar to the existing note in vault/attachments.ts about parens breaking links). Wrapping the URL in <...> is a simple way to make the destination robust.

  const linkText = title?.trim() || input.url
  const note = await deps.createNote({
    title: title?.trim() || titleFromUrl(input.url),
    content: `[${escapeLinkText(linkText)}](${input.url})\n`
  })

apps/desktop/src/renderer/src/components/capture-bar/capture-bar.tsx:155

• CaptureBar reads its shortcut/CTA strings from the common namespace (e.g. capture.focusShortcut). Only en/common.json adds these keys in this PR, while other locales already had localized equivalents under inbox.json. As-is, non-English locales will regress to fallback/English for these capture strings (or show missing-key output depending on i18n config).

  const { t } = useT('common')
  const [value, setValue] = useState('')
  const [isFocused, setIsFocused] = useState(false)
  const [isRecording, setIsRecording] = useState(false)
  const [isRecorderMounted, setIsRecorderMounted] = useState(false)
  const fieldRef = useRef<HTMLTextAreaElement>(null)
  const overlayRef = useRef<HTMLDivElement>(null)
  const recorderRef = useRef<VoiceRecorderHandle | null>(null)
  const recorderDismissTimerRef = useRef<number | null>(null)
  // Guards the attach button's pointerdown/click pair (see the button below).
  const attachFiredByPointerRef = useRef(false)

  const disabled = isBusy
  const trimmed = value.trim()

  useKeyboardShortcuts([
    {
      key: 'q',
      action: () => fieldRef.current?.focus(),
      description: t('capture.focusShortcut')
    }
  ])

apps/desktop/src/main/database/drizzle-data/0042_project_link_pinned.sql:1

• PR description calls the migration 0040_project_link_pinned.sql, but the added migration is 0042_project_link_pinned.sql (and the Drizzle journal tag is 0042_project_link_pinned). This makes the PR narrative misleading for reviewers and anyone searching for the migration by name/number.

ALTER TABLE `project_links` ADD `pinned` integer DEFAULT 0 NOT NULL;

[Copilot]

Pull request overview

Copilot reviewed 137 out of 137 changed files in this pull request and generated no new comments.

Suppressed comments (2)

packages/i18n/src/locales/en/common.json:6

• capture.detailHint is displayed as a user-facing label next to the "⌘/Ctrl ↵" hint in CaptureBar. The current English string "detail" reads like a placeholder; consider using a clearer label (e.g. "Details") to match the rest of the UI copy style.
  apps/desktop/src/renderer/src/pages/project/use-relative-time.ts:46
• formatRelative rounds minutes/hours/days, which can overstate age (e.g. 1h31m → "2h"). Relative-time formatting elsewhere in the renderer uses Math.floor, which avoids jumping early; consider switching to floor here so labels only change after the full unit has elapsed.

[Copilot]

Pull request overview

Copilot reviewed 137 out of 137 changed files in this pull request and generated no new comments.

Suppressed comments (2)

packages/i18n/src/locales/zh-CN/common.json:644

• This locale adds common.capture.focusShortcut, but CaptureBar also reads common.capture.focusHint, common.capture.detailHint, and common.capture.submit. With only focusShortcut present, those labels will fall back to another language or render as missing keys in this locale. Add the missing capture.* keys here (and consistently across all locales) so the shared CaptureBar UI is fully localized.
  apps/desktop/src/main/database/queries/projects.ts:653
• setProjectLinkPinned updates by projectId + itemId only. Since project_links.item_id is shared across multiple item types (note/file/calendar_event), this can accidentally pin/unpin an event link if its id matches. Restrict the update to note/file link rows (or explicitly note) so pinned state only applies where the hub expects it.

  db.update(projectLinks)
    .set({ pinned: pinned ? 1 : 0 })
    .where(and(eq(projectLinks.projectId, projectId), eq(projectLinks.itemId, itemId)))
    .run()

[Copilot]

Pull request overview

Copilot reviewed 137 out of 137 changed files in this pull request and generated no new comments.

Suppressed comments (2)

apps/desktop/src/main/database/queries/projects.ts:657

• setProjectLinkPinned updates by (projectId, itemId) only and always bumps projects.modifiedAt, even if no link row matched. This can accidentally pin non-note links (or multiple rows if the same id exists across item types) and will mark the project as modified even when nothing changed.

  db.update(projectLinks)
    .set({ pinned: pinned ? 1 : 0 })
    .where(and(eq(projectLinks.projectId, projectId), eq(projectLinks.itemId, itemId)))
    .run()

apps/desktop/src/main/tasks/capture-url.ts:5

• The header comment claims this avoids leaving a stray note behind if linking fails, but the current implementation can still create the note and then return { success: false, noteId, ... } when linking fails (so the stray note still exists). Either update the comment to reflect the actual behavior or add rollback (delete note) on link failure.

/**
 * Project hub → "paste a link". Creates a note for the URL and links it to the
 * project in one step, so the renderer never has to sequence two mutations and
 * leave a stray note behind if the second one fails.
 */