Skip to content

[autopilot] skills: clarify concurrent extension settings writes - #177

Merged
wdm0006 merged 1 commit into
mainfrom
autopilot/skills-1793584519
Nov 2, 2026
Merged

wdm0006 merged 1 commit into
mainfrom
autopilot/skills-1793584519

Conversation

@wdm0006

@wdm0006 wdm0006 commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Clarify that re-reading settings immediately before writing narrows a stale-snapshot window but does not make a storage read–merge–write atomic. Explain how to serialize the whole sequence through one owner and test the remaining race with a controlled interleaving.

Motivating pattern: a background worker and popup both save a shared settings object; a delayed whole-object write can overwrite an independent preference change. Awaiting the write proves completion, while synchronous mocks and concurrent saves placed before the fresh read can hide the lost update. Readers gain a precise boundary for the existing example and a regression-test recipe.

Validation: all 67 unittest tests pass; skill validator passes; git diff --check passes. Only the existing browser-extension skill changes.

@wdm0006
wdm0006 merged commit 456ad29 into main Nov 2, 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