home-widget-registry.test.tsfeat(home): the rail everyone starts with, and a tile that stays where it is
A new user's rail was meetings + agents, and the agents surface is unfinished —
that tile is its only entry point. Defaults become meetings + pipeline +
statistics, the three that are actually ready to be looked at.
Removing the tile outright would take it off the rails already holding it, so
`unlisted` withholds a widget from the picker only: it still resolves, and the
rails that name it go on rendering it. TEMPORARY — shipping the agents surface
is this flag going away.
Co-Authored-By: Claude Opus 5 (1M context) <<email>>Aug 31, 2026, 1:14 AMHomeAgenda.test.tsxfeat(agenda): the instructions button goes to the agent, not a copy of its prose
Clicking "Agenda Agent Instructions" opened a dialog that rendered the prompt
read-only. But the instructions ARE the agent's config — every question the prose
raises (what cadence, which AOP, what it is allowed to touch, when it runs) is
answered by controls the dialog did not have, so it left the reader one click
short of all of them. It now navigates to `/agents/{agentId}?tab=config`, landing
on the config tab rather than the workspace's default.
`getAgendaInstructions` returns the agent id to make that possible. It is
resolved with `resolveSubagentAgentId` over the row's metadata AND frontmatter —
the one place that knows which of the two wins — so the link cannot point
somewhere other than what the cron actually dispatches. The button hides itself
when there is no agent rather than linking nowhere.
`AgendaInstructionsDialog` is deleted; nothing else referenced it.
Co-Authored-By: Claude Opus 5 (1M context) <<email>>Aug 31, 2026, 10:41 PMHomeAgentsWidget.test.tsxfeat(home): widget rail replaces the agents list and collapsible sections
Pre-existing work committed under its own message before starting the
meetings-tab design run, so each design phase lands as one commit.
Co-Authored-By: Claude Opus 5 (1M context) <<email>>Aug 27, 2026, 12:08 AMHomeWidgetRail.test.tsxfeat(home): the rail everyone starts with, and a tile that stays where it is
A new user's rail was meetings + agents, and the agents surface is unfinished —
that tile is its only entry point. Defaults become meetings + pipeline +
statistics, the three that are actually ready to be looked at.
Removing the tile outright would take it off the rails already holding it, so
`unlisted` withholds a widget from the picker only: it still resolves, and the
rails that name it go on rendering it. TEMPORARY — shipping the agents surface
is this flag going away.
Co-Authored-By: Claude Opus 5 (1M context) <<email>>Aug 31, 2026, 1:14 AMwidget-format.test.tsfeat(home): widget rail replaces the agents list and collapsible sections
Pre-existing work committed under its own message before starting the
meetings-tab design run, so each design phase lands as one commit.
Co-Authored-By: Claude Opus 5 (1M context) <<email>>Aug 27, 2026, 12:08 AM