[feature] every meeting in one list, read down a calendar

[yui0303]

Closes #330.

The problem

The library could only be browsed a folder at a time. LibraryNode had exactly two shapes — a folder, or 還沒歸檔 — so no node meant "everything", and the only other way in was the home screen's six most recent. Finding a recording therefore required remembering which folder you filed it in, which is precisely the thing people forget.

The node

Adds an all node above the folders. It is a view rather than a home: it matches every recording instead of owning any, so ownerNode can never return it and it stays out of the countByNode pass — folding it in would double every recording in the tree total. Its count is simply the number of summaries, so it is still a count of exactly what clicking it opens, which is the invariant #195 established.

Scope is personal recordings only. 組織共享 keeps its own node: a recording shared into an org would otherwise appear twice, and the org scopes load through a different path.

Why a timeline and not the card grid

A folder answers "what is in here", and a card — title, snippet, four stats — is the right shape for that. This node answers "what did I sit through lately", which is a scanning question. Rows read down a column, the date headers give the eye somewhere to stop, and roughly twice as many recordings fit on screen. Nothing about the folder grid changes; the two live side by side on purpose.

Grouping is 今天 / 昨天 / 本週稍早 and then by calendar month, in a pure clock-injected module (lib/library/timeline.ts) so the boundaries are pinned down by tests rather than by waiting until midnight. Two rules worth calling out:

• Yesterday outranks the week boundary. On a Monday, "昨天" is a better answer than "上個月" for something recorded on the Sunday.
• Weeks start Monday. These are work meetings; a Sunday that starts the week orphans the Friday before it.

Rows carry the same four actions as a card (move, share, rename, delete) by reusing CardActions — filing something you have just found is most of the point of a view that spans every folder.

Elsewhere

The home screen keeps its six and gains a way out of them. The ⌘K palette gains the node too, so the two ways of naming a place stay in step.

What it looks like

The timeline rendered from the real component. The app itself could not be launched to shoot it in place — tauri-plugin-single-instance hands off to the installed Parley.app, which was running.

Verification

bunx tsc --noEmit and bunx vitest run (342 tests) both pass. New tests cover the date bucketing (13 cases, including the DST-safe boundaries and the Monday rule) and the all node's behaviour in scope.test.ts — that it takes every recording, that ownerNode can never return it, and that the tree total is not doubled.

The three fixes in the second commit are things that only showed up once the component was rendered and looked at, not caught by types or tests: zh-TW's 12-hour clock wrapped the narrow leading column onto two lines, the folder chip's right alignment made a ragged column, and re-filing from this node dropped the row out of a list it had not actually left.

🤖 Generated with Claude Code

[github-actions]

✅ SonarQube Quality Gate passed — pathorsAI_parley

0 open issues on this PR.