Repository navigation
ci: drop the five duplicate keys of .github/bdd-parts.json - #479
Conversation
bootstrap-runtime, preservation-lists, preservation-runtime, preservation-support and preservation-prims each appeared twice with identical values; a JSON parse merged them silently. The parsed plan is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
afflom
left a comment
There was a problem hiding this comment.
Bounded source review is clear: the only change removes15 lines containing the second copies of five identical JSON keys. A strict duplicate-rejecting parse of the new file equals the old effective last-key-wins plan. All27 parts, assignments, targets and the rest remainder are unchanged. No native tests or gate were repeated for this data-only check.
The branch's sole parent is7eb while the release base is now5dcc; preserve actual current-release history and any new #480 parts during owner integration. This does not authorize dropping new assignments or creating a competing conflict patch. Current draft evidence is not full acceptance; the existing owner retains resulting-tree qualification and landing. Receiptfb173f63 records the exact source correspondence.
.github/bdd-parts.jsonon release has five keys twice, with identical values:bootstrap-runtime,preservation-lists,preservation-runtime,preservation-support,preservation-prims. A JSON parse merges them silently, so the plan works today, but a slice that edits one copy and not the other would be silently overridden by the later copy.This removes the second block. A strict parse (duplicate keys refused) of the new file equals the parse of the old one. RP-13, RP-14 and the Intel factory tests pass locally.
Edited as text. It may conflict with branches that add parts near the end of the file (e.g.
batch/bs25-34); resolving means keeping their new parts and dropping the five repeats.🤖 Generated with Claude Code