ci: move the remaining shared-lib carrier plugins to changelog fragments #6629

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 8, 2026
2. github-actions commented on Oct 8, 2026

   

   github-actionsbot

   on Oct 8, 2026 – with GitHub Actions

   Contributor

   More actions

   Understood as a follow-up to #6543 and #6006: move the remaining plugins that still carry a synced shared-lib copy (per scripts/shared-copies.txt) but bump plugin.json/CHANGELOG.md directly into scripts/fragment-plugins.txt, following the #6414/#6543 precedent (list change plus an ADR 0048 note, no version or CHANGELOG edits). The acceptance criterion is concrete: a lib/ change touching every carrier should add only fragments, with no carrier plugin.json edited. I didn't find an open duplicate; #6006 is the parent problem statement and #6543 already covers the first batch of eight plugins, so this reads as the next increment rather than a repeat. Scope and approach look clear enough to act on without further clarification from the reporter.

   _{Automated triage. A maintainer reviews it.}
3. github-actions

   added

   good first issueGood entry point for new contributors.Good entry point for new contributors.

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   on Oct 8, 2026
4. kyle-sexton

   added the

   Task

   issue type on Oct 12, 2026
5. kyle-sexton

   removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 12, 2026
6. kyle-sexton commented on Oct 13, 2026

   

   kyle-sexton

   on Oct 13, 2026

   ContributorAuthor

   More actions

   Decision recorded. The owner approved applying independently verified recommendations (confirmed, low-risk set) on 2026-10-13.

   • How should the plugins added after chore(release): move the remaining 68 plugins to changelog fragments #6661 get fragment mode? → Add developer-experience, user-experience and display-redaction to scripts/fragment-plugins.txt now with an ADR 0048 phase 4 note
     Basis: scripts/shared-copies.txt:102-103,417-419,458,468 (origin/main); scripts/fragment-plugins.txt (origin/main) lacks the three; PR chore(release): move the remaining 68 plugins to changelog fragments #6661 body ('list names all 87'); docs/adr/0048-...md:276-290 (phase 4 done, phase 5 pending); git log: feat(developer-experience): add developer-experience plugin with setup, build-cli and audit-tools #6668, feat(user-experience): add the user-experience plugin #6669 on 2026-10-09 and feat(display-redaction): mask emails and secrets on screen #7221 on 2026-10-11 added the plugins

   Asks that every plugin carrying a synced shared-lib copy be in fragment mode. #6661 put all 87 plugins of 2026-10-09 in scripts/fragment-plugins.txt, but developer-experience and user-experience (both carriers) and display-redaction were added later and are missing, so the acceptance criterion still fails for two carriers.

   Verified by an independent fresh-context check (confirmed, risk low): gh issue view 6629 (open, 1 triage comment, no owner decision); origin/main scripts/fragment-plugins.txt: developer-experience, user-experience, display-redaction absent; only plugin dirs missing from the list; origin/main scripts/shared-copies.txt:102-103,417-419,458,468 carry user-experience and developer-experience copies; display-redaction carries none; docs/adr/0048:276-290 phase 4 done (87 plugins), phase 5 pending; git log scripts/fragment-plugins.txt: last change #6661; gh pr view 6661 merged 2026-10-09

   Admission to an agent lane stays with the work-class rules and owner ratification.