fix: report skipped and hook-aborted tests in the CLI flow

[kamal-kaur04]

What is this about?

Reports skipped and hook-aborted tests in the CLI (gRPC) flow. Today, tests that never reach beforeTest/afterTest emit no events at all — static it.skip, this.skip() inside before/beforeEach hooks, and suites aborted by a failed before hook. The legacy Listener → api/v1/batch path these flowed through previously is not functional in the CLI pipeline (its own usage stats report skipped: {triggeredCount: N, sentCount: 0, failedCount: N}), so such tests are invisible on the Test Observability dashboard and their Automate sessions are never linked to the build (the dominant generator of session_linking_issue_build in TRA build-stability metrics).

Changes (merged via #55, reviewed there; this PR promotes the staging branch to main):

• cli/skipReporter.ts (new): routes skipped tests through the TestFramework tracker using the same INIT_TEST → TEST PRE → LOG_REPORT POST → TEST POST sequence afterTest uses; serialized through a single chain (wdio doesn't await reporter hooks) with started/reported dedup preventing double-reporting runtime this.skip().
• reporter.ts: onTestSkip CLI branch with resolved spec file (events without a file location are rejected downstream) and suite chain via ctx.
• service.ts: afterHook CLI branch — on a non-passed BEFORE_ALL/BEFORE_EACH/AFTER_EACH hook, reports the suite's undetermined tests as skipped (port of the legacy insights-handler cascade); beforeTest marks started tests.
• cli/frameworks/wdioMochaTestFramework.ts: hook results mapped from real Frameworks.TestResult fields incl. the sync-skip error shape — genuine before-hook failures fail the build, deliberate this.skip() hooks stay green.
• util.ts / testOps/listener.ts: batch-upload failures carry HTTP status + body snippet instead of a misleading Unexpected end of JSON input; listener logs the drop reason.

Validation (live end-to-end, 6-spec matrix, verified via the Observability API): before — build passed, {passed: 3-4}, skipped/aborted suites absent, sessions unlinked. After — {passed: 4, failed: 1, skipped: 8}, all 12 tests reported exactly once, every session attributed, build failed only from the genuinely-thrown hook. Closed-loop proof under TRA stability semantics: 3 without-fix builds FLAGGED as session_linking_issue_build, 3 with-fix builds STABLE. npm run build green; 6 new skipReporter unit tests. Regression coverage in BStackAutomation (SDK/api wdio_mocha, marker sdk_6987). v8 line: #68.

Related Jira task/s

N/A

Release (mandatory for every PR — required for the ready-for-review label)

Version bump: (required — tick exactly one)

• minor (backwards-compatible feature)
• patch (bug fix or other small change)

Release notes type: (optional)

• New Feature
• Bug Fix
• Other Improvement

Release notes (customer-facing): (optional but encouraged)

• Fixed skipped tests (it.skip, this.skip() in before/beforeEach hooks) and suites aborted by a failed before hook not being reported to Test Observability when using the CLI.
• Fixed Automate sessions from skipped/aborted spec files not being linked to the Test Observability build.

Release notes (internal): (required — engineer-facing; what actually changed / why)

• Added cli/skipReporter routing skipped/aborted tests through the gRPC tracker (INIT_TEST → TEST PRE → LOG_REPORT POST → TEST POST), serialized and deduped against started tests; onTestSkip CLI branch + afterHook cascade port the legacy skip paths that are dead against api/v1/batch in CLI mode.
• Hook results map from real TestResult fields (incl. the sync-skip error shape) so failed before-hooks fail the build and deliberate skips don't.
• Batch uploader reads response as text with a response.ok guard (failures carry HTTP status instead of Unexpected end of JSON input); listener logs batch-drop reasons.

Checklist

• Ready to review
• Has it been tested locally?

PR Validations

Run Tests: Comment RUN_TESTS to trigger sanity tests.

🤖 Generated with Claude Code

[kamal-kaur04]

✅ Good to go

File	Status
cli/frameworks/wdioMochaTestFramework.ts	✅ All Clear
cli/skipReporter.ts	✅ All Clear
reporter.ts	✅ All Clear
service.ts	✅ All Clear
testOps/listener.ts	✅ All Clear
util.ts	✅ All Clear
tests/cli/skipReporter.test.ts	✅ All Clear

↻ This verdict comment is the review anchor — it's updated in place on each run (the gate posts its status separately).

— SDK PR Review Agent

[github-actions]

🟢 SDK PR Review gate is green — the SDK PR Review Agent has given a GTG for this PR (the ready-for-review label is present and the latest SDK PR Review Agent run reports success on the current head commit).

A native GitHub reviewer approval is still separately required by branch protection before this PR can merge — this check does not substitute for that.

[kamal-kaur04]

RUN_TESTS

[yashdsaraf]

.includes('sync skip; aborting execution')

I haven't checked this myself -> Is there a better way to check this than asserting error message string? (Asking because string literals might change in the future without us realising the impact)

[kamal-kaur04]

Ideally, skipped check should suffice, if at all string changes, worst case it will marked as failure. Shouldn't be an issues since testResult itself was not a skipped status.