fix(triage): persist project-local Planfile tickets before success - #93
Merged
Merged
Conversation
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.
triage --feed-planfilereported success without creating tickets and selected the MONAG store for other projects. It now calls native Planfile in each owning checkout, uses stable dedupe labels and reads back persisted IDs. Missing stores, invalid paths and partial failures return an error; JSON output retains per-project results.Validation: 343 pytest tests passed, including 19 triage/feed regressions. A live installed Planfile fixture persisted tickets in two projects and returned the same IDs after a repeated feed. Governance and Ruff passed.
Planfile PLF-027 mapped and independently verified as Issue94.
Closes #94