yog 0.0.8

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

//! Tests for the §9.4 picker's pure half. Split by concern: the generic
//! [`fields`](super::grammar::entry_field) access every rewrite shares, the
//! block [`grammar`](super::grammar) — its `roles:` half and its `models:`
//! half on the seam the production module already has — the roster
//! [`query`](super::query), the
//! composed [`plan`](super::plan) + the sentences the surface paints, the
//! conversation [`header`](super::header) line and its apart clause, the
//! `models.yaml` read-back that judges a declared provider row (`validate`),
//! the [`remedy`](super::remedy) a credential-shaped roster failure routes to,
//! and the protocol-`capability` gate that keeps a row brazen ships but cannot
//! serve a role out of both config files (bl-3d22).

mod capability;
mod fields;
mod grammar_models;
mod grammar_roles;
mod header;
mod plan;
mod query;
mod validate;

/// brazen's effective table as the fixtures need it: one row per name, keyless,
/// on a dialect that **carries tools** (bl-3d22). A fixture of bare names could
/// not exercise the pick gate at all — the gate asks two questions of the table
/// and only one of them is answerable from a name.
pub(crate) fn table(names: &[&str]) -> Vec<crate::config_edit::brazen::ProviderRow> {
    rows_on(names, "openai_chat")
}

/// The same table on a named dialect — the seam the capability tests aim a
/// `claude_code` row, and an unspellable protocol, through.
pub(crate) fn rows_on(
    names: &[&str],
    protocol: &str,
) -> Vec<crate::config_edit::brazen::ProviderRow> {
    names
        .iter()
        .map(|name| crate::config_edit::brazen::ProviderRow {
            name: (*name).to_owned(),
            protocol: protocol.to_owned(),
            auth: "none".to_owned(),
            credential: "not required".to_owned(),
        })
        .collect()
}

/// `providers.yaml` exactly as litany's own `template/providers.yaml` writes
/// it — the shape the grammar is defined over (§9.4). Every rewrite test reads
/// this back, so a template change upstream fails here rather than in the UI.
pub(crate) const TEMPLATE_PROVIDERS: &str = "roles:\n  worker:\n    provider: codex\n    model: gpt-5.4\n    \
     tools: [bash, read_file, load_skill]\n  compactor:\n    provider: codex\n    model: gpt-5.4-mini\n";

/// `models.yaml` carrying the block's **legacy four-field entry** — the shape
/// litany's `install/models.yaml` seeded before it retired the table (bl-35e2),
/// and the shape an operator's file still has on disk. yog writes the id and
/// `context_window` alone since bl-3ffa; every read here is over this fuller
/// shape on purpose, because writing less changed no reader.
pub(crate) const SEEDED_MODELS: &str = "# Global config-root models.yaml (ARCH §4.2).\n\nmodels:\n  \
     gpt-5.4:\n    provider: codex\n    model_id: gpt-5.4\n    capabilities: [tool_use_native, streaming]\n    \
     context_window: 400000\n";