Task: Make release-critical test suites visible in CI output

[RtlZeroMemory]

Parent EPIC: #325

Problem:

Release-critical coverage needs to be visible, not buried inside a large undifferentiated test run.

Scope:

• Define which suites should be surfaced as release-critical.
• Make their status easy to see in CI output and review.
• Keep the signal tied to the critical widget and flow list.

Done when:

• Release-critical suites are visible in CI output.
• Reviewers can see whether the critical path coverage passed.

Notes:

• This task should produce work that is reviewable against expected behavior, not current implementation shape.
• Keep outputs straight to the point and tied to repo code or repo process.

[RtlZeroMemory]

Implemented in PR #368: #368

What changed:

• added a named release-critical suite catalog in scripts/testing-slices.mjs
• added a dedicated fast gate / release-critical suites job in ci.yml
• added matching release-critical visibility in nightly.yml and release.yml
• CI output now shows the package and terminal release-critical suites by name instead of hiding them inside one large generic step

What was verified:

• npm run test:release-critical passed
• npm run test:release-critical:terminal passed
• workflow visibility checks passed in scripts/__tests__/testing-workflows.release-critical.test.mjs

What was intentionally left out:

• no duplicated second terminal-real PR job was added beyond the existing full-gate matrix coverage

Remaining ambiguity:

• terminal-real visibility on pull requests is still clearest in nightly/release output and in the existing full matrix, not as a separate extra PR job