// `zz top`: the real-time dashboard. Same building blocks as `zz // work`'s view (TabView/LaneList/LiveLog/LadderView), just without an // activity tab since `zz top` isn't itself running an agent -- it's // purely a watcher. Plus Explore, reachable as an ordinary tab at any // time (the plan's own requirement), for finding more repos to watch // without quitting and hand-editing ~/.zz/config.json. import React, { useState, useSyncExternalStore } from "react"; import { TabView } from "./TabView.js"; import { LaneList } from "./LaneList.js"; import { LiveLog } from "./LiveLog.js"; import { LadderView } from "./LadderView.js"; import { Explore } from "./Explore.js"; import { useLaneSnapshots } from "./useLaneSnapshots.js"; import { useLadderTrees } from "./useLadderTrees.js"; import { flattenEvents } from "./types.js"; import { laneListText, liveLogText, ladderText } from "./textExport.js"; // Loose structural shape, not an import of cli/lib/watchedRepos.js's // RepoWatchStore -- see WorkApp.tsx's identical comment for why // (tui/ depends on cli/lib for plain function calls already, e.g. // useLaneSnapshots.ts's callRemoteTool, but a prop TYPE stays // structural so this component doesn't care which store implementation // top.ts actually constructed). interface RepoWatch { get(): { slug: string; repoDir: string; stateDir: string }[]; subscribe(listener: () => void): () => void; } export function TopApp({ watch, remote, local, onTrack, }: { watch: RepoWatch; /** Mirrors WorkApp's own prop: in remote mode, Lane/Ladder state lives on the deployed Worker, not in a local clone's flat files/git notes -- see useLaneSnapshots.ts/useLadderTrees.ts's own `remote` param. */ remote: boolean; /** Picks which Explore variant renders: a search box (remote) or a filesystem browser (local) -- always the logical negation of `remote` today, but threaded through explicitly rather than re-derived, since "remote but acting on local paths" isn't a real combination this prop should ever have to represent. */ local: boolean; /** Explore's "track" action -- top.ts builds this once, closing over whichever of (the track API, ~/.zz/config.json) actually applies, so Explore itself never needs to know the mode-specific rule. */ onTrack: (slug: string) => Promise; }) { const watchedRepos = useSyncExternalStore(watch.subscribe, watch.get); const repos = watchedRepos.map((r) => ({ repo: r.slug, repoDir: r.repoDir, stateDir: r.stateDir })); const snapshots = useLaneSnapshots(repos, 500, remote); const ladders = useLadderTrees(repos, 2000, remote); const [exploreEditing, setExploreEditing] = useState(false); // Explore is always tabs[0] -- reachable the same way regardless of // mode -- but which tab actually opens first depends on whether // there's anything else worth looking at yet: nothing tracked (the // logged-out/no-config empty-dashboard case top.ts can produce) means // Explore IS the useful starting point; anything already being // watched means lanes is. useState only reads this once (React's own // "lazy initial state" semantics), which is exactly right here -- // watchedRepos growing later (a live "track" from Explore) shouldn't // yank the user back to lanes mid-session. const [initialTab] = useState(() => (watchedRepos.length === 0 ? 0 : 1)); return ( }, { label: "lanes", content: (maxRows, scrollOffset) => , getFullText: () => laneListText(snapshots) }, { label: "ladder", content: (maxRows, scrollOffset) => , getFullText: () => ladderText(ladders) }, { label: "protocol", content: (maxRows, scrollOffset) => r.slug)} maxRows={maxRows} scrollOffset={scrollOffset} />, getFullText: () => liveLogText(flattenEvents(snapshots)), }, ]} /> ); }