fix: list an agent's runs as the previews they are

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vo7HXMdgqXJhR7p8YyVgjB

frontend/src/lib/components/flows/agentActions.ts

@@ -44,11 +44,11 @@ export function agentMenuItems(agent: {
 			? []
 			: [
 					{
-						// Chat turns are filed under `<path>.chat` (agent_runs.rs) and listed by the agent's
-						// own chat, so this is the form runs.
+						// An agent run is a flow preview, which the runs page hides by default. Chat turns
+						// are filed under `<path>.chat` (agent_runs.rs) and listed by the agent's own chat.
 						displayName: 'View runs',
 						icon: List,
-						action: () => goto(`${base}/runs/${agent.path}`)
+						action: () => goto(`${base}/runs/${agent.path}?job_kinds=previews`)
 					},
 					...(agent.operator
 						? []

frontend/src/lib/components/home/ItemsList.svelte

@@ -900,8 +900,8 @@
 	// each row carries its server fetch ordinal (`ord`), which already reflects the
 	// chosen order, the (path, kind) tiebreaks, full-precision timestamps, the database
 	// collation, and starred-first pinning. Sorting by it can never disagree with the
-	// server, so a later page never jumps above shown rows on "load more". Agents lead the
-	// runnables (see loadAgents) everywhere but among the starred, which all come first. Depends on
+	// server, so a later page never jumps above shown rows on "load more". Starred rows lead
+	// across kinds, agents included. Depends on
 	// `sortOrder` only so its identity changes when the order does (re-grouping the tree,
 	// whose leaves also sort by ord); the actual reordering comes from the reload that
 	// restamps ord.