chore(codecov): expand ignores for wiring, locales, and demo packages (RHIDP-15513)

[rostalan]

Changes

• Ignore demo packages/app|app-legacy|backend, generated code, and *-test helper plugins
• Ignore package entry / NFS wiring (src/index.ts(x), plugin.ts, alpha.ts(x)), translations, test-utils, Router/Trans
• Keep constants.ts ignore scoped to orchestrator frontend only
• Sync component_management with overlay metadata (required when touching codecov.yml)

Notes on review feedback

• component_management / intelligent-assistant: Not a product demotion. Overlay metadata still uses the lightspeed workspace path, so the generator cannot map intelligent-assistant into GA. Verified with scripts/generate-codecov-components.sh --check --overlay <overlay>. The workspace remains in flag_management. It will reappear in GA once overlays are renamed/updated.
• **/src/index.tsx: Kept intentionally — those files are NFS/plugin wiring (same class as alpha.tsx / plugin.ts). Comment updated to say so; nested index.tsx under components stay counted.

Split from #3786 (codecov slice).

[rostalan]

/fs-review

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 1:40 PM UTC · Completed 1:52 PM UTC
Commit: 26bd802 · View workflow run →

[fullsend-ai-review]

Review — comment

The ignore-pattern changes are well-reasoned and improve coverage accuracy. The bug fix for the test-helper glob (workspaces/plugins/*-test/** → workspaces/*/plugins/*-test/**) is correct — the old pattern never matched anything. Narrowing **/index.ts to **/src/index.ts correctly preserves coverage for nested index.ts files that contain real logic. The new boilerplate exclusions (translations, alpha wiring, plugin.ts, Router.tsx, Trans.tsx, generated code) are appropriately scoped and well-documented with inline comments. No security issues, no documentation staleness, and no style/convention violations were found.

One concern warrants attention before merge:

component_management manual edit (medium)

The component_management section is marked "GENERATED — do not edit by hand" and has a dedicated sync workflow (.github/workflows/sync-codecov-components.yml) and generation script (scripts/generate-codecov-components.sh). This PR manually removes workspaces/intelligent-assistant/ from the GA component list without regenerating via the script.

Concrete concerns:

• The intelligent-assistant workspace still exists on disk with active plugins and source code, but now appears in no component list (not GA, not tech-preview, not community, not dev-preview). Its coverage data will still be collected via flag_management (line 170) but won't roll up into any component-level dashboard.
• The manual edit may conflict with or be overwritten by the next automated sync run. If the overlay metadata has already changed, regenerating via scripts/generate-codecov-components.sh --write would produce the correct result and maintain process integrity.
• This change is outside the scope of "expand ignores" — it is a workspace reclassification that should ideally follow the established automation path.

Suggestion: Consider splitting the component list change out of this PR and either (a) regenerating via the script if the overlay metadata has already been updated, or (b) deferring until the overlay change lands and triggers the automated sync.

**/src/index.tsx — net-new coverage exclusion (low)

The old config ignored **/index.ts but not **/index.tsx. The PR narrows the .ts exclusion (good) but also adds **/src/index.tsx as a net-new exclusion. At least two src/index.tsx files contain substantive plugin logic rather than simple barrel re-exports:

• workspaces/intelligent-assistant/plugins/intelligent-assistant/src/index.tsx (209 lines: API factories, page blueprints, route refs, drawer configs)
• workspaces/quickstart/plugins/quickstart/src/index.tsx (101 lines: plugin definition, drawer blueprint, init module)

The inline comment says "Package entry barrels only" but these files go beyond re-exports. Whether plugin wiring code should be covered is a judgment call, but the comment is slightly misleading about what these files contain.

---

Positive highlights:

• The *-test glob fix catches a real bug that silently prevented test-helper exclusions
• Comment annotations explaining the rationale for each pattern group are excellent
• Scoping constants.ts to only workspaces/orchestrator/plugins/orchestrator/ (not -common packages) shows good discipline
• The **/generated/** pattern correctly matches only auto-generated OpenAPI client code today

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud