Repository navigation
[autopilot] skills: clarify reset semantics for merged settings - #184
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a focused section to the application-configuration skill explaining why a compact export of defaults is not necessarily a valid reset payload.
The motivating pattern: allowlist serializers omit inactive optional fields, while merge-based writers preserve omitted fields from existing settings. Passing the exported defaults through that writer can leave an optional feature enabled after a supposedly successful reset.
The guidance distinguishes patch, replacement, and reset semantics, demonstrates explicit clearing values with a nullable schedule pair, and recommends testing the real reset from populated non-default state alongside a partial-update preservation control. Readers can prevent sticky preferences without breaking ordinary patch behavior.
Validation: all 67 tests pass under both pytest and unittest on Python 3.12; scaffold smoke check, skill validation, example assertions, and git diff --check pass. Only the existing skill file changes.