yog 0.0.62

yog: the standalone server for litany loops — the world, the balls and the conversations, behind one wire
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

//! User-message preview extraction.
//!
//! The preview is the **operator's payload**, and the payload's one home on
//! disk is `<workspace>/agents/<agent-id>/goal.md` (DESIGN §3.3) — read by
//! [`super::enumerate`] in the same pass that reads the goal's two stamps.
//! What litany *sent* the model is not that text: an assembled context leads
//! with the §3.7 pinned-instruction frame and wraps a deposit in its envelope,
//! so a request record previews as `<file path="…">` or `---` rather than as
//! anything the operator wrote (bl-368d).
//!
//! What the goal carries is the *composed* goal — yog's own preface above the
//! operator's payload — so the preview is the payload's **headline**: the
//! prefaces come off first (line-wise, each by the compose's own inverse), then
//! the first non-blank payload line, capped at [`PREVIEW_MAX`] chars after
//! whitespace normalization so the render layer can size predictably. That
//! order is what keeps the §3.3 display ladder's first two rungs from being the
//! same string.
//!
//! **Two prefaces, because yog writes two** (bl-e2ad). The legacy identity
//! stamp is one. The other is the path rung's `Working directory: <dir>` +
//! binding sentence, which the seat joins the operator's words *after* — so
//! until this ball every path-rung conversation in a workspace previewed as its
//! own machinery, and the roster, the attention queue and the §3.3 display name
//! were a column of identical absolute paths in the one place that has to tell
//! conversations apart. Coding work always takes the path rung, so that was
//! every worker on the board. The directory is not lost: it rides the fire
//! typed as litany's `--cwd`, it is answered as `working_dir` beside the
//! conversation's files, and it is still line one of the goal verbatim. It just
//! stops being the name.

pub(super) const PREVIEW_MAX: usize = 80;

/// The §3.3 ladder's second rung, at its source: the composed goal with the
/// identity stamp stripped **before** anything collapses (the strip is
/// line-wise — after [`truncate_preview`] there are no lines left to strip),
/// reduced to the payload's headline. Every prefill yog composes leads with one
/// (§3.3: `Ball <id>: <title>`, `Working directory: <dir>`, or the operator's
/// own ask), so the first non-blank line is the preview and the body never runs
/// on into it.
pub(super) fn payload_headline(goal: &str) -> String {
    let payload = crate::start::strip_path_preamble(&crate::start::strip_identity_stamp(goal));
    let headline = payload
        .lines()
        .find(|line| !line.trim().is_empty())
        .unwrap_or_default();
    truncate_preview(headline)
}

pub(super) fn truncate_preview(s: &str) -> String {
    let collapsed: String = s
        .chars()
        .map(|c| if c.is_whitespace() { ' ' } else { c })
        .collect();
    let trimmed = collapsed.trim();
    if trimmed.chars().count() <= PREVIEW_MAX {
        return trimmed.to_string();
    }
    let head: String = trimmed.chars().take(PREVIEW_MAX - 1).collect();
    format!("{head}…")
}