Stop the console's prose arguing from a terminal it no longer ships
Tail of the shop-for-rio swap. The move itself landed in 08f59d0: the schema
went to testdata as a format fixture, schemas/ gained shop's, the rio skel
template went, and the Containerfile started installing the catalog. Three
comments were left still reasoning about rio.
system.rs claimed the Applications side "parses ten schemas". That was never
true at any point, and it is one now. Replaced with what the catalog actually
is, one today against the bounded ten CONSOLE.md scopes for the v0 stack, so
the argument for the System tab's field list being hand-written survives the
correction it was resting on a wrong number.
The other two are the "where is rio" pair in settings.rs, which are load
bearing as rationale rather than decoration: they say why a broken schema
still appears in the list under its app's name. Pointed at shop so the
example is a program the reader can run.
GO alloy 05f6a632.
- Co-Authored-By
- Claude Opus 5 (1M context) <noreply@anthropic.com>
2 files changed,
+5 insertions,
-4 deletions
| 138 |
138 |
|
|
| 139 |
139 |
|
/// One entry in the Applications list: an app, and the form behind it.
|
| 140 |
140 |
|
struct App {
|
| 141 |
|
- |
/// What the list shows. The tool, not the path: someone looking for rio's
|
| 142 |
|
- |
/// config is looking for rio.
|
|
141 |
+ |
/// What the list shows. The tool, not the path: someone looking for shop's
|
|
142 |
+ |
/// config is looking for shop.
|
| 143 |
143 |
|
name: String,
|
| 144 |
144 |
|
/// The `.schema` file this came from, named in the diagnostic when it is
|
| 145 |
145 |
|
/// the thing that is broken.
|
| 1044 |
1044 |
|
self.apps.iter().map(|app| match &app.state {
|
| 1045 |
1045 |
|
Ok(_) => Line::from(text::primary(theme, app.name.clone())),
|
| 1046 |
1046 |
|
// A broken schema is still its app in the list, marked, so
|
| 1047 |
|
- |
// the answer to "where is rio" is never silence. The mark
|
|
1047 |
+ |
// the answer to "where is shop" is never silence. The mark
|
| 1048 |
1048 |
|
// is a character and not only a color, per
|
| 1049 |
1049 |
|
// DESIGN-LANGUAGE.md: state never rides on color alone.
|
| 1050 |
1050 |
|
Err(_) => Line::from(vec![
|
| 8 |
8 |
|
//!
|
| 9 |
9 |
|
//! ## Why the field list is hand-written
|
| 10 |
10 |
|
//!
|
| 11 |
|
- |
//! The Applications side parses ten schemas and will parse more. This side is a
|
|
11 |
+ |
//! The Applications side parses a schema per adopted config, one today and a
|
|
12 |
+ |
//! bounded catalog of about ten at the v0 stack's full extent. This side is a
|
| 12 |
13 |
|
//! handful of rows fronting different CLIs, each with its own vocabulary and
|
| 13 |
14 |
|
//! its own setter, and a schema DSL general enough to describe `timedatectl`
|
| 14 |
15 |
|
//! would be a second language to maintain for no reader. So the table is Rust,
|