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
use ;
/// Immutable (from the perspective of policies) snapshot of engine runtime state.
///
/// `EngineContext` is the *only structured view of engine control state* independent of:
/// - numerical progress (`Progress`)
/// - event history (`EventBatch`)
/// - solver state (`State`)
///
/// It is passed into the policy layer to support decisions that are not
/// directly derivable from `Progress`, such as:
/// - cancellation
/// - wall-clock timeout
/// - iteration-based scheduling
/// - checkpoint scheduling
///
/// # Design intent
///
/// This type deliberately avoids exposing full engine state. Policies should
/// remain:
/// - deterministic (no hidden mutation)
/// - stateless or explicitly stateful via internal fields
/// - independent of solver implementation details