Module assertion_store

Expand description

Run-owned assertion map lifecycle and execution-backed, agent-assessed score.

Structs§

affected_tests: Which of a run’s tests the current checkout’s changes could have reached, from what each test executed and what has changed since, declaration by declaration. A test is affected by a change in code it ran, in its test file, or in a file it ran code in whose declarations changed shape; not by a change confined to code it never ran; not by comments or blank lines. A test that did not pass is listed as affected regardless: it has a result to establish. What this cannot see is a file the run never captured – a file added since – and the run’s dependencies and configuration, which the working-tree check answers for.
assertion: Read authored flows and their assessment from the same map snapshot.
assess
coverage
executions: Each test’s execution, placed in the declarations of the run’s own manifest: for every probe a test fired, the innermost unit holding it. Also which units hold a probe at all, per file, since only a change confined to such units can be said to have missed a test. Sources are needed to place JavaScript columns; without them there is no record.
load
load_inputs
load_manifest
report: Cache derived assessments separately from immutable coverage evidence. Every query still verifies current source, map and managed-state identities.