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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
//! **The one listing row the boundary itself owns** (§8.5) — the
//! [`Query::Workspaces`](crate::boundary::Query::Workspaces) answer's element,
//! split off the [reply roster](super) at §12's per-file budget.
//!
//! Every other listed thing is somebody else's type read back out of its own
//! module — a `ConvRow` is `nav`'s, a `JoinRow` is `projects`', an `OpRow` is
//! `opslog`'s — and this is the one whose *subject* exists only as an answer:
//! a workspace named, classified, rolled up and ranked is a thing no seat and
//! no derivation holds until one is asked for. Its two spellings live in
//! [`rows`](super::rows) beside every other row's, unchanged.
use crateWorkspaceKind;
/// One workspace row (§3.1 classification + the §6 rollups the tab bar shows):
/// the [`Query::Workspaces`](super::Query::Workspaces) answer's element.
///
/// **It names the workspace, it does not locate it** (REMOTE §8, bl-f5f6). It
/// carried the whole [`Workspace`] — path and all — and a path is meaningless
/// on a thin client and a disclosure besides. §3.1 makes the leaf the name, so
/// the `name` this row used to carry *beside* the path became the row's whole
/// identity and the path went.
/// **The altitude-0 chrome, as one answer** (REMOTE §9.7, bl-b4b5) — the
/// [`Query::Workspaces`](crate::boundary::Query::Workspaces) reply: the
/// enumeration, and how current the derivation behind it is.
///
/// The two notes are the §7.2 instrumentation the §11 activity accessory paints
/// above its chip, and they were the last in-process reads in the tail
/// (`AppModel::staleness`, `AppModel::growth_note`). They ride **here** rather
/// than on a question of their own for bl-296f's own rule — a payload grows by
/// a field, never by a near-duplicate question — and the seam is exact: this is
/// the one read every window makes on every frame, so the currency of an answer
/// costs the wire nothing to say.