yog 0.0.5

yog: a balls-oriented session manager for lernie loops (egui frontend)
Documentation 
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

//! The **ops-trail** row's badge (§4.2, §11) — the one badge vocabulary painted
//! over `ops.jsonl` rather than over a conversation.
//!
//! Its own file since bl-1296 added the fifth outcome and [`super`] reached
//! §12's cap. The seam is the surface: everything left in the parent describes
//! an agent, a step or a tool result — a conversation's vocabulary — while this
//! one describes an *attempted action yog ran*, which is the activity
//! accessory's subject and nothing else's.

use super::{ASH, BRAZEN, ICHOR, MOONLIT};
use crate::theme::BRAZEN_DIM;

/// Glyph + colour + **the outcome said in words** for an ops-trail row
/// ([`crate::opslog::OpOutcome`]) — the §11 activity accessory's one badge
/// mapping, worn by both its seats: the collapsed chip's live-failure count
/// (`· M failed ⚠`, said outright — the chip has the room) and the per-row
/// marker (a dense repeating row, so it hovers the phrase). The two failure
/// outcomes deliberately share `⚠` (§6: a retired failure keeps its row and its
/// mark, losing only ichor), which is exactly why the words carry the load —
/// the phrase is the outcome's *name*, short enough to read inline in the chip.
///
/// `Detached` (bl-8433) reuses the descent-arrow glyph and brazen hue
/// [`flight_badge`](super::flight_badge) wears for `Flight::Subagents` — "a
/// dispatched child is running", the same fact a handed-off `lernie prompt`
/// states about itself — rather than minting a new glyph/hue pair the palette
/// doesn't already key to this meaning. Its phrase matches
/// `opslog::exit::ExitKind::Detached`'s own wording verbatim, so the collapsed
/// badge and the expanded detail never say two different things about the same
/// row.
///
/// `Notice` (bl-1296) is the same argument one class down, and takes the
/// handoff's own hue **quieted**: [`BRAZEN_DIM`] is the palette's "still warm,
/// no longer bright", which is exactly what a notice is — the same detached
/// spawn, having said something the operator may read past. It may not be
/// [`ICHOR`], the whole point of the outcome being that a benign driver line
/// was painting as a death; and its glyph is neither `⚠` nor the clean bullet,
/// because it is neither.
pub fn op_badge(outcome: crate::opslog::OpOutcome) -> (&'static str, egui::Color32, &'static str) {
    use crate::opslog::OpOutcome;
    match outcome {
        // A live wound: nothing has re-run this verb clean since.
        OpOutcome::Failed => ("⚠", ICHOR, "failed"),
        // §6: superseded, so the fact stays and the prominence retires to ash.
        OpOutcome::Retired => (
            "⚠",
            ASH,
            "failed, retired by a later clean run of the same verb",
        ),
        // Ran clean: a bullet, not an alarm — the moonlit text default.
        OpOutcome::Clean => ("·", MOONLIT, "ran clean"),
        // Handed off: launched, no exit to observe — neither clean nor failed.
        OpOutcome::Detached => ("↳", BRAZEN, "detached — handed off, no exit to observe"),
        // Spoke, and what it said was that it carried on: an operator notice.
        OpOutcome::Notice => (
            "ℹ",
            BRAZEN_DIM,
            "notice — the driver reported something and the branch continued",
        ),
    }
}