fix(ce-proof): update HITL flow for Proof v2#847
Merged
Conversation
Merged
LLMpsycho
pushed a commit
to LLMpsycho/compound-engineering-plugin
that referenced
this pull request
May 21, 2026
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
ce-proofnow teaches agents the Proof v2-native HITL workflow: read only review comments, make narrow content edits through/edit/v2, batch thread replies/resolutions, and reserve whole-document rewrites for true last-resort cases. This should make Proof review loops faster and safer while avoiding the stale-token, duplicate-mark, and full-rewrite habits that came from the v1-era contract.The mutation examples now match Proof v2's stricter contract:
/opsexamples includeIdempotency-Key, successful writes chain the nextmutationBase.token, and retries that rebuild the body with a freshbaseTokenmint a fresh key instead of trippingIDEMPOTENCY_KEY_REUSED.What changed
find_replace_in_docand block-level/edit/v2, withsuggestion.addreserved for visible track-change cases andrewrite.applydocumented as last resort.state?kinds=comment, batched/opsreplies/resolves, andcomment.replywithresolve: true./ops, exact-body retry semantics, and consistentai:compound-engineeringbridge identity.ce-brainstorm,ce-ideate, andce-planhandoff wording so upstream skills no longer promise tracked suggestions as the default HITL edit path.Verification
bun run release:validatebun test tests/frontmatter.test.tsbun test tests/release-metadata.test.tsgit diff --check