Skip to content

[autopilot] skills: clarify reset semantics for merged settings - #184

Merged
wdm0006 merged 1 commit into
mainfrom
autopilot/skills-1794668204
Nov 14, 2026
Merged

wdm0006 merged 1 commit into
mainfrom
autopilot/skills-1794668204

Conversation

@wdm0006

@wdm0006 wdm0006 commented Nov 14, 2026

Copy link
Copy Markdown
Owner

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.

@wdm0006
wdm0006 merged commit cc76bd0 into main Nov 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant