symfonic.diagnostics.inspection.config_checks¶
config_checks ¶
Configuration inspectors: legacy spellings, conflicts, and unchosen values.
Four questions, one adapter pass:
- What did you write in the legacy dialect? Every supplied key that the T2.2.3 registry knows, mapped to the native target it feeds. Nothing was removed, so these are informational -- but they are the list a migration works through, and nobody could previously get it without reading 139 rows of a table by hand.
- What contradicts what? The cross-capability rules already refuse a contradictory configuration at construction time. Reported here instead of raised, so an adopter sees all of them at once, before deploying.
- What did you never choose? Provenance distinguishes a value that was set from one that arrived by default. Most defaults are fine; a curated few decide whether state survives a restart, whether a skill runs unapproved, and what a turn costs. Those are worth naming, and only those -- a report that listed all 117 defaults would be read by nobody.
capability_conflicts ¶
Cross-capability rules this configuration breaks, reported not raised.
Source code in src/symfonic/diagnostics/inspection/config_checks.py
implicit_defaults ¶
Consequential values that arrived by default rather than by decision.
Source code in src/symfonic/diagnostics/inspection/config_checks.py
legacy_configuration ¶
Legacy keys in use, plus every compatibility diagnostic the adapter raised.
Source code in src/symfonic/diagnostics/inspection/config_checks.py
legacy_pin ¶
Expose a countable legacy-generation-pin verdict from raw data.