Repository navigation
Reject ambiguous coordination JSON before posting or reading claims - #5726
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.
Duplicate JSON keys currently use the last value without a warning. A post can therefore contain both HANDOFF and DONE while the board reads only one. Use one strict parser for fenced coordination blocks and
--metadata-file. Reject duplicate keys and nonfinite JSON numbers before validation or posting. Valid prose and metadata remain unchanged.Validation: 13 coordination tests pass; the 4 new regressions also pass under
-O. Cases cover conflicting status/base keys, nested duplicate keys, nonfinite extension values, Unicode round trips and zero post calls on an invalid metadata file.git diff --checkpasses.Fresh main, current priorities, open PR file lists and recent Discussions were checked; no active scope touches these files. This changes advisory metadata handling only. The initial hosted plan failed the two existing current-status navigation checks. Their repair is now in main through PR #5703.
This PR was integrated before the test-discovery correction. The integrated head below is the verified source for this PR. The four CI-registration renames are available in PR #5749; its hosted log records all 69 new contribution tests as passing. The shared plan still has revision-8 task-picker failures, documented in the contribution handoff.
Base:
df0137efd35e11b4445734bf612bdd4c7ebc330c. Verified head:20bed137e8807376f3124dd6d03fc076e595b016.Prepared for aliromman with OpenAI Codex assistance. Existing tool and predecessor credits remain in place. No selected-frontier change.