Configuration migration¶
This is a clean breaking change. There are no deprecated API, CLI, environment, or JSON aliases.
Library API¶
Replace flat monitoring keywords with:
CaptureConfigfor core capture;DetailedCaptureConfigonly for individual detailed mechanisms; andAnalysisConfigfor report-time checks.
For the common “capture everything detailed” case:
The removed speculative replay feature is now the displaced-finder check. Its
results use the shared finder_results pipeline.
CLI and environment¶
Use the options and environment names in
Configuration reference. Old MONITOR_*,
SPECULATIVE_REPLAY, --deep-*, and probe names are rejected.
JSON¶
Schema 4.0 uses:
import_searches;finder_resultsandfinder_result_comparisons;checks;program_outcome; and- the event, finding, evidence, and severity vocabularies documented in JSON reports.
Detailed import_mechanism_call payloads now require call_ref and
parent_call_ref. Nested calls contain their exact outcome; the former
unobserved_reentrant outcome has been removed.
Regenerate consumers from the bundled schema. Do not translate old keys inside metapathology; handling migration in the consuming integration keeps schema failures visible.