Repository navigation
Reject repeated JSON keys before package identity and parity validation #418
Description
🤖 Generated by the Agentic Engineer
Problem
Current main accepts repeated keys in marketplace manifests, plugin manifests and the persisted rename baseline. Normal jq decoding erases the conflicting value, so normalized parity reports success for ambiguous package identities or compatibility history.
Observed on fresh main during hands-on validation on 2026-10-03. The package cases exercise the production gate against a complete isolated fixture; the catalogue cases exercise its shared parser and native CLI argument contract.
Intended outcome
Require one complete object with unique decoded keys before semantic reads of every package manifest, rename baseline and desired-state resource. Cover nested and escaped duplicate keys and healthy formatting.
Success proxy: a regression fails against current main, then passes with the root-cause repair; healthy packages and normal installation remain usable. No external adoption is claimed.
Size: S. Part of #38.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Effort
Projects
- Status
Activity
chore: agent-claim #418 nonce=c5d72cc5f37944efaf520b6dac310081
devantler commentedon Oct 3, 2026
Delivered in #426 at merged commit 465a84f. The merged tree matches the reviewed final source. The actual merged package passes its production gate; introducing a conflicting repeated declaration into that otherwise healthy package is rejected.
The 39 package boundary cases, 313 existing manifest cases and 25 MCP boundary cases pass, and required CI was green at the final reviewed commit. All review findings were fixed or refuted with evidence before merge.