[quality] the status event's success path (tideOnCheckSuite → pullRequestsForSha → merge) and the missing-head-sha arm are never driven through dist/index.js #261

Finding

src/run.ts routes the legacy commit status event to handleCheckSuite → tideOnCheckSuite (src/plugins/tide.ts:510-525), which reads payload.state and payload.sha instead of check_suite.conclusion / check_suite.head_sha, and looks the pull requests up by sha because a status payload has no pull_requests. docs/events.md:16,181 documents this route.

Bundle e2e coverage (__tests__/bundle/bundle.test.ts, dist/index.js against fakeGithub) on main @ c48bd6d drives only the arms that make no API call:

• status with state: pending and check_suite with conclusion: failure (bundle.test.ts:157-166, the hopeless-conclusion short-circuit)
• check_suite success with and without pull_requests (bundle.test.ts:1480-1520)

Never driven through the bundle:

• status success → pullRequestsForSha listing → pull read → binding read → merge (the payload.sha/payload.state read path)
• status success when no open pull request has that head (listing stops, nothing else is called)
• status success under tide.merge_on_events: false (configuration read, no listing)
• the TypeError('github context payload missing head sha: …') arm for a status payload without sha / a check_suite without head_sha, which runEventHandlers must surface as ::error::error handling <event> event: … and exit 1

Evidence

• Unit: __tests__/plugins/tide.test.ts:1000-1020 (status success: looks the prs up by the payload sha, status %s: makes no api call) and __tests__/pullReqTest/handleCheckSuite.test.ts:36 cover every arm in isolation. npx vitest run --coverage on main @ c48bd6d: tide.ts 100 | 94.62 | 100 | 100 (uncovered branch lines unrelated: 30, 361, 424, 543), suite-wide 99.83 | 98.35 | 100 | 99.82.
• E2E: grep -n "'status'" __tests__/bundle/bundle.test.ts → one hit, line 159 (state: 'pending'). None of the open bundle PRs (test(bundle): drive /cc /uncc /unassign /retitle /lock /reopen through dist/index.js #238–test(bundle): drive ok-to-test on pull_request synchronize and in the sweep through dist/index.js #260) add a status payload or a missing-sha payload.
• The two suites cannot be combined at line granularity ([quality] the bundle e2e suite's coverage of src/ is never captured — runBundle.ts drops NODE_V8_COVERAGE and dist/ has no source map #235), so this is stated as unit-covered / e2e-uncovered.

Recommendation

Add __tests__/bundle/statusEvent.test.ts (new file, following #260's one-file-per-cluster layout, so it does not touch the bundle.test.ts hunks held by the open PRs) driving the four arms above through dist/index.js and asserting the exact request sequence and the merge body.

Priority

• Impact: medium — unit-covered, e2e-uncovered (priority 2 under the coverage rules); the status route is the only event whose payload shape differs from the one check_suite tests exercise, so a regression in the payload.sha/payload.state reads would only surface in production.
• Effort: low

Filed by quality agent (hold-gated mode)

🐝 Hive Agent: quality | Instance: hosted-available-lke648397-260827-5q9t | SHA: c48bd6d

— hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88