Add shared mutation core preview pipeline#40
Merged
Conversation
Owner
Author
This was referenced Apr 18, 2026
Owner
Author
|
Architecture/stack update: this PR is now retargeted to Current intended order: #38 -> #40 -> #41 -> #42 -> #43 -> #44 -> #46. This keeps the write contract first, then the shared mutation core, then individual mutation tools. |
This was referenced Jun 1, 2026
Owner
Author
|
Updated #40 on top of current Current focused diff: shared mutation request/response models, bridge mutation request plumbing, cache invalidation hooks, and tests. Validation:
Merge order note: this should merge after #38 and before #41. |
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.
Summary
Add the shared mutation core that later task/project write tools can build on without bespoke transport code.
Change
OmniFocusCoreOmniFocusServicewith a commonperformMutationentry pointCatalogCacheScope Notes
This PR intentionally stops at plumbing:
Validation
swift testWhy
Issue #29 is about creating one shared mutation pipeline for CLI and MCP before the field-specific write issues begin. This PR gives later issues a stable transport and result envelope without mixing in task/project write behavior.