fix: prevent plan content loss by blocking subsequent writes to same plan file #1474
+260
−2
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.
Fixes #1363 - When Prometheus creates complex plans that exceed output limits and writes in segments, the Write tool overwrites previous content instead of appending.
Problem?
When creating large plans, Prometheus may need to write content in multiple segments. However:
Solution:
Added plan file overwrite protection to the
prometheus-md-onlyhook:session.deletedandsession.compactedeventsChanges
src/hooks/prometheus-md-only/index.ts:writtenPlanFilesMap to track plan files written per sessionisPlanFile()andnormalizeFilePath()helper functionseventhandler for session cleanupsrc/hooks/prometheus-md-only/index.test.ts:Scope
.sisyphus/plans/*.md.sisyphus/drafts/*.mdError Message Example
Testing
Checklist
devbranchSummary by cubic
Prevents plan content loss by blocking repeated Write calls to the same plan file and guiding the agent to use Edit to append. Applies per session to .sisyphus/plans/*.md; drafts are not affected.
Written for commit 7b2a5d5. Summary will update on new commits.