Repository Compliance: Track linting workflow adoption across API repositories

[hdamker]

Problem description

There is no automated way to track which API repositories have integrated the linting/validation workflows from tooling. This makes it difficult to:

• Assess adoption progress of standardized workflows
• Identify repositories needing workflow updates
• Report compliance status to TSC

Possible evolution

Two complementary approaches:

1. Reporting workflow update: Extend the Repository Compliance Overview workflow to detect and report linting workflow integration status per repository

   • Check for presence of caller workflows referencing camaraproject/tooling
   • Report which validation workflows are enabled (API linting, release-plan validation, etc.)

2. Campaign for workflow adoption: Create a bulk campaign to update caller workflows in API repositories that haven't yet adopted the latest tooling workflows

Additional context

• Related to Repository Compliance: Define Compliance Check Categories and Requirements #51 (Repository Compliance Reporting)
• Builds on tooling restructure (tooling#46) which established shared-actions pattern
• Could leverage campaign infrastructure from Campaign: Implement release-plan.yaml roll-out to all repositories #99

Success criteria

• Automated detection of linting workflow adoption per repository
• Dashboard or report showing compliance status
• Campaign to roll out central workflow updates to non-compliant repositories