Repository navigation
Retire mode-run authority from discussion events - #27
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
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.
Outcome
Retire the old mode-run field from governed discussion events while preserving assignment attribution.
Work authority
Contributor mode (select one):
Plan
Integrate existing field removal, add focused parsed-output regression, run required Actions, return clean staging.
Changes and commits
8385d22: removes modeRunId from the existing discussion-event schema; regression preserves assignmentId and rejects exposing retired authority in parsed output. No new schema or storage.
Verification
111 existing tests/32 files passed; new focused content suite three tests passed, ownership checks passed. Required Actions pending. No full golden claim.
Risk and rollback
One retired optional field is no longer projected. Revert through checked staging PR if needed; no data purge, credentials or runtime cutover.
Completion summary
Implementation verified locally and ready for checked staging integration.
Submission checklist