Align CLOMonitor coverage with delivered repository inventory

[yada]

Context

An audit has been conducted and confirmed that SUBPROJECTS.md and the global replication groups now cover all 45 public Microcks repositories consistently.

However, the CNCF CLOMonitor configuration currently covers 20 repositories: 19 delivered components with community + code checks and microcks.io with docs. The current report remains healthy at A / 98.49%.

Four repositories classified as delivered components are missing:

• microcks-mcp-server
• microcks-agent-skills
• api-tooling
• homebrew-tap

There is no existing CLOMonitor issue or pull request covering them.

Decision needed

The existing policy from #16 assigns community + code to delivered components. CLOMonitor also offers code-lite, recommended for secondary code repositories.

@lbroudoux @SebastienDegodez, should we:

1. Add all four repositories with community + code for consistency with the existing policy;
2. Use community + code-lite for selected secondary tooling repositories; or
3. Intentionally exclude any of them, documenting why CLOMonitor coverage is not relevant?

Once agreed, we can submit a separate PR to cncf/clomonitor. No upstream PR should be opened before this decision.

[lbroudoux]

Intentionally exclude any of them, documenting why CLOMonitor coverage is not relevant?

These repositories must be excluded from CLOMonitor. They are either generated, empty (not yet delivered) or not subject to any quality guardrails.

[yada]

Agree and fine with me.

Decision recorded: all four repositories remain intentionally excluded from CLOMonitor, and no upstream PR is required.

For future audits, let's confirm which rationale applies to each repository: generated, not yet delivered, or not subject to quality guardrails, so that we can track and update later on if the status changes:

• microcks-mcp-server -> not yet delivered (to follow, as it may change)
• microcks-agent-skills -> not yet delivered (to follow, as it may change)
• api-tooling -> not subject to quality guardrails (done, fix, no planned changes)
• homebrew-tap -> generated (done, fix, no planned changes)