refactor(config): use schema stripping for persisted fields

This commit is contained in:
Mohamed Boudra
2026-07-02 18:44:17 +02:00
parent 5616c6af6a
commit 9eec33773a
3 changed files with 34 additions and 123 deletions
+2 -3
View File
@@ -195,9 +195,8 @@ Single file, validated with `PersistedConfigSchema`.
All fields are optional with sensible defaults.
Config loading strips unrecognized object keys before validation so a config written by a newer
daemon does not brick older read paths such as `paseo daemon status`. Malformed known fields still
fail validation, and saving remains strict.
Config parsing strips unrecognized object keys so a config written by a newer daemon does not brick
older read paths such as `paseo daemon status`. Malformed known fields still fail validation.
`agents.metadataGeneration.providers` controls the preferred structured-generation fallback order for daemon-side metadata tasks such as commit messages, PR text, branch names, and generated agent titles. Entries are tried first in the configured order, then Paseo falls through to dynamically discovered defaults and finally the current selection when available.