Feature: Service Chapters, Governance, and Chapter-Oriented Controls #227
Description
Feature Description
Expand and refine service chapters (governance chapters) so teams can control which governance sections appear, where they appear, and what insights they provide. This includes configurable toggles, ordering/placement controls, and new reporting such as skip-label usage statistics.
Problem / Opportunity
Today, service chapters are not granular enough: teams cannot easily tailor which governance chapters are shown, how they are ordered, or add actionable governance insights. This leads to either hiding all service chapters (losing value) or accepting noisy/poorly ordered output.
Acceptance Criteria
- Users can enable/disable service chapters globally and also toggle individual service chapters.
- Users can control ordering/placement of service chapters relative to user-defined chapters (including making “Closed issues without user defined labels” the first service chapter).
- The action can generate a “skip label stats” governance report (for PRs, issues, issue types, and labels), configurable to show as info/warn/fail.
- Configuration is documented with examples and default behaviors; changes are covered by unit tests.
Proposed Solution
- Add configuration options to toggle service chapters as a group and individually (building on existing service-chapters on/off behavior).
- Introduce ordering/placement controls for service chapters (and ensure “Closed issues without user defined labels” can be positioned as the first service chapter).
- Implement a new service chapter/report: skip-label usage stats (authors, assignees, issue types, and label combinations), with configurable severity.
- Update README/docs with configuration examples and recommended defaults; add/extend unit tests for ordering, toggles, and stats calculations.
Dependencies / Related
Additional Context
These improvements strengthen governance and reporting around release-note hygiene and make service chapters adaptable to different repository standards without forcing a single output layout.