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
//! brazen's on-disk layout **inside one workspace's wall** (DESIGN §5.1 rows
//! 19/22/23, §16.2 as amended), and the two reads that need nothing else.
//!
//! Split off [`super`] at §12's pre-split band on a seam that module's own
//! prose already drew: [`credential_presence`] and [`model_cache_at`] are
//! documented there as *free of the editor* — the §8.3 Login surface, the
//! boundary's `Providers` reply and the §9.4 pick all ask them holding no draft
//! and no Apply pipeline. A layout plus the questions answerable from a layout
//! alone is one subject; the staged-validation editor is another.
use FileIo;
use ProviderRow;
use crateEnv;
use ;
/// brazen's three locations **inside one workspace's wall** (§5.1 rows
/// 19/22/23, §16.2 as amended): the layout is yog's own, so it is the same
/// three leaves on every §10 target and there is no per-OS branch left. This
/// struct is that layout's single home — [`crate::bz_host`] hands the very
/// same paths to the linked brazen's seams, so the file yog's editor writes
/// and the file `bz` reads cannot be two different files.
/// Credential presence for a table of rows, against a credentials dir (§5.1
/// #22): does `<dir>/<provider>.json` exist? Booleans only — contents are never
/// read, never written. Free of the editor because every caller asks the
/// question without one: the §8.3 Login surface and the boundary's own
/// `Providers` reply hold no draft and no Apply pipeline, only the folded dir.
/// `BrazenEditor` used to
/// wrap it at its own path as well; since bl-20cb the §9.1 pane paints no
/// credential column at all, so the wrapper went with the seat and this is the
/// one presence read there has ever been meant to be.
/// The raw model-cache document `bz --list-models` wholesale-wrote for
/// `provider` under `dir` (§5.1 row 23), or `None` where it never ran there.
/// Read-only and forgiving — no parse, no schema coupling.
///
/// Free of the editor for the same reason [`credential_presence`] is: the §9.4
/// pick reads this very file to seed the context window it declares (bl-848f)
/// and holds no `config.toml` draft to ask through. One naming of
/// `<provider>.json`, so the file the picker reads and the file the §9.5 pane
/// shows can never be two different files.