Keep PM planning in one canonical doc - #5
Merged
Conversation
JulioMCruz
marked this pull request as ready for review
July 17, 2026 23:32
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
1 participant
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.
What changed
createDoc(type: plan)idempotent for an existing active, unmaterialized plan.Why
In the real Hermes PM E2E, the model sometimes called plan tools out of order or omitted
docId. That split groups, tasks, and proposal state across an empty active plan and a separate PM draft. Reusing the active plan keeps the workflow in one canonical document regardless of call ordering.Impact
PM-created plans no longer drift into duplicate/empty documents, and Platform Tools can publish structured project workflow messages through PerkOS-Chat.
Validation
npm test: 35/35 passing.npm run build: passing.