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
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
//! TermProof: evidence-first verification for TUI and terminal applications.
//!
//! # Layout
//!
//! This crate was merged from three (`termproof-core`, `termproof-terminal`,
//! `termproof-evidence`) before any of them was published, so the shape below
//! is the only one that has ever existed on crates.io.
//!
//! - **The crate root** is what was `termproof-core`: the recipe model,
//! config, schema, validation, the built-in [`steps`] and [`assertions`],
//! [`planner`]/[`runner`]/[`execution`], [`store`]/[`cache`], and the
//! `py*` compatibility shims that keep this port close to the Python
//! oracle. It is flat rather than under a `core` module, both because it is
//! the crate's primary surface and because a module named `core` shadows the
//! `core` crate for every path in its scope.
//! - **[`terminal`]** is what was `termproof-terminal`: PTY, tmux and process
//! sessions, plain and attributed screen state, asciicast recording, idle
//! detection and the [`terminal::SessionBackend`] implementations.
//! - **[`evidence`]** is what was `termproof-evidence`: screenshot and video
//! rendering, Markdown and JUnit reports, visual baselines, diff and upload.
//!
//! The two nested modules keep their own re-exports rather than flattening
//! into the root. `error` is defined by both the root and [`terminal`], so
//! nesting is what keeps [`crate::error`] and [`terminal::error`] apart; the
//! same nesting keeps [`crate::result`] clear of [`evidence::report`], and
//! keeps the reader's sense of which layer a name comes from.
//!
//! Original module notes: models, config, schema, registries, planning,
//! orchestration and execution (RUST-004 + RUST-010 + RUST-016); PTY/process
//! ownership, terminal screen, cast recording, idle and session backends
//! (RUST-005/006 + RUST-012 + RUST-016); and the evidence pipeline.
//!
//! # Features
//!
//! All three are on by default, so a consumer that does not name features gets
//! the whole crate — the shape that has always been published.
//!
//! - **`evidence`** — the [`evidence`] module. Off, the crate does not compile
//! `image`, `quick-junit` or `avt`.
//! - **`json-schema`** — [`validation`], [`pyschema`] and the `json_schema`
//! built-in assertion. Off, the crate does not compile `jsonschema`, and
//! `json_schema` is absent from [`assertions::BUILTIN_TYPES`] rather than
//! present and failing. Implies `schema`, which is where the schema it
//! validates against comes from.
//! - **`schema`** — the [`schema`] module and the `JsonSchema` impls derived on
//! [`Recipe`], [`config::VerifierConfig`] and the types they contain. Off,
//! the crate does not compile `schemars`. This is the one dependency that
//! reaches the public API, so it is the one a consumer cannot deduplicate by
//! pinning; turning it off is how a consumer on a different `schemars` major
//! stops carrying two.
//!
//! [`terminal`] has no feature of its own: the crate root is built on it, and
//! every build drives a terminal, so there is nothing to save.
// Re-exports: config + recipe/schema/validation (RUST-004)
pub use VerifierConfig;
pub use ;
pub use ;
// Re-exports: models/result/store (RUST-010) — models is legacy, result is canonical
// Canonical Recipe is from recipe.rs (serde, plus schemars under `schema`);
// models::Recipe retained as ModelRecipe for back-compat
pub use Recipe as ModelRecipe;
pub use ;
// Canonical RunResult/AssertionResult/StepResult from result.rs (score_from_assertions, BTreeMap artifacts)
pub use ;
pub use ;
// Re-exports: execution/agent (RUST-016/017)
pub use ;
pub use CoreError;
pub use ;
pub use ;
/// Canonical product name used by the CLI and diagnostics.
pub const NAME: &str = "termproof";
/// Canonical crate/product version, inherited from the workspace manifest.
pub const VERSION: &str = env!;
/// Render the canonical `name version` banner used by the CLI greeting.