Repository navigation
chore(config-cascade): call the personal layer the personal override in the contract and shared lib - part 2 of 2 #13188
Description
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
agent-ready
{{ message }}
Work status
Activity
github-actions commentedon Nov 4, 2026
Proposed work class: none
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: #13187
Understood: this is part 2 of 2 of #13182, split at intake. It asks for the release record (version bump and CHANGELOG entries) for the config-cascade contract and for each plugin whose synced copy changed. That record follows the personal-override rename in part 1, so it depends on #13187. This is not a duplicate; it is a sibling split of #13182. Nothing is missing.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 4, 2026
Not admitted to the issue lane yet: blocker #13187 is not closed by a listed human or a merge.
kyle-sexton commentedon Nov 4, 2026
Triage note: where this sub-issue's release record lands.
Agent choice, not an owner answer.
Work class confirmed as
work-class: mechanical: a version bump and a CHANGELOG entry are deterministic, trivially reversible maintenance (the label's own definition). Intake proposed none.The done-when line has two halves, and only one of them can be a separate pull request:
scripts/fragment-plugins.txt, ADR 0048). A pull request that changes a fragment-mode plugin's shipped files must add that plugin's fragment under.changes/<plugin>/in the same pull request (scripts/check-changelog-fragments.sh --check-required). Any pull request other than the release pull request that moves the plugin's version or adds a CHANGELOG heading failsscripts/check-changelog-parity.sh(FRAGMENT-MODE RELEASE, lines 763 and 794). So the plugin half lands in chore\(config-cascade\): call the personal layer the personal override in the contract and shared lib - part 1 of 2 #13187's own pull request as fragments, and the release pull request writes the versions. The lane on this issue checks those fragments exist; it bumps noplugin.jsonand adds no plugin CHANGELOG heading.config-cascadeis not in the fragment list, so itscontract_versionanddocs/contracts/config-cascade/CHANGELOG.mdare written by hand (docs/contracts/config-cascade/README.md, Versioning). That is the work this sub-issue holds, unless chore\(config-cascade\): call the personal layer the personal override in the contract and shared lib - part 1 of 2 #13187's pull request already does it, in which case this issue is done as written.Basis: verified,
scripts/fragment-plugins.txt,scripts/check-changelog-fragments.sh:9,scripts/check-changelog-parity.sh:100,:763,:794,docs/adr/0048-release-plugins-from-changelog-fragments-through-a-bot-maintained-release-pr.md(check table), on origin/main.Blocked by #13187 (native edge). work-unblock labels this issue agent-ready when #13187 closes by a merge. No label change here beyond the class.
[-]chore\(config-cascade\): call the personal layer the personal override in the contract and shared lib - part 2 of 2[/-][+]chore(config-cascade): call the personal layer the personal override in the contract and shared lib - part 2 of 2[/+]melodic-automation-lanes commentedon Nov 4, 2026
The work-resolve-issue run that
agent-readystarted failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.kyle-sexton commentedon Nov 4, 2026
kyle-sexton commentedon Nov 4, 2026
Lane 3 holds this, under the lease above (hub H46). It continues #13187, which merged in #13280.
kyle-sexton commentedon Nov 4, 2026