Expand description
In-file loop config + state — file-truths persisted through the
substrate’s load_state/store_state as one JSON blob. Carries a schema
version; unknown keys are ignored (serde default), so an older binary opens
a newer file unchanged (proposal §7.3).
Structs§
- Analyzer
Config - Per-analyzer configuration. The file may enable/disable, raise severity floors, override params, and scope namespaces — never raise engine caps.
- Analyzer
Config Update - A partial update to one analyzer’s
AnalyzerConfig— every field absent (None/false) leaves the stored value untouched, so the console can PATCH a single toggle. Deserialized straight from thePOST /api/loop/configbody. - Analyzer
Setting - One analyzer’s effective settings for the Setup view: the manifest facts plus the resolved file-config (override or manifest default).
- Applied
Record - Record of an applied recommendation: how to undo it and what to re-measure.
- Loop
Persisted - The whole loop persisted blob.
- Loop
State - Run state: the watermark that makes repeat runs cheap no-ops.
Constants§
- SCHEMA_
VERSION - Current persisted-state schema version.