1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
//! The altitude-0 navigator view-models (DESIGN §11): the workspace **tab
//! bar** ([`tabs`]) and the focused workspace's **conversation list**
//! ([`convs`]), the §11 context-menu seat roster ([`menu`]), plus the shared
//! row/key types. No egui and no git/ui_state
//! dependency: the caller ([`AppModel`](crate::AppModel)) derives the input
//! facts from the snapshot map + attention + the §3.5 join, and the shell
//! renders the outputs. Every branch is table-tested with plain data.
use Path;
/// One bound ball rendered in the balls section (DESIGN §3.5, §11): its id and
/// the §3.5 join badge (e.g. "delivered"), the caller having resolved both via
/// [`crate::projects::join::badge`]. `badge` is `None` on a state needing none
/// (a plain Bound row).
///
/// The row also carries what **acting on it** needs (§11 ball-row menu): the
/// project its `bl` verbs run in, the claimant they stamp `--as` (§3.2), and the
/// §3.5 state the enablement predicates read. A row that can be right-clicked
/// must name its own object — re-deriving it from the focus is exactly what a
/// pointer-targeted menu may not do.
///
/// **It is `Query::WorkspaceBalls`' answer row since bl-b4b5**, not a
/// frame-side projection: `project` is the §5.1 #1 wire name a `bl` verb takes
/// rather than the clone's path, and the §3.5 [`spend`](Self::spend) figure
/// rides here rather than being asked per row — one workspace's balls and what
/// each has cost are one question, and the seat that paints the strip and the
/// seat that paints the figures were two reads of it.
/// The ui_state key for a workspace (its path) — the pin key, collapse key
/// prefix input, seen key, and focus key, one string everywhere (§4.1).