test(bundle): drive handlePullReq's unsupported-job and failed-lgtm-read arms through dist/index.js

[hivecommons-hive]

Test Improvement

Adds __tests__/bundle/pullReqJobsArms.test.ts (new file; nothing else touched), driving the jobs-input arms of src/pullReq/handlePullReq.ts through the committed dist/index.js against the fake GitHub API:

• a pull_request synchronize run with jobs: frobnicate fails with TypeError: error handling pull request: Error: could not execute frobnicate… after owners-label and approve's probe have run (lines 62-66 default, 75-80)
• jobs: lgtm whose GET /issues/1 answers 500 fails with could not get labels from issue and sends no DELETE (onPrLgtm.ts line 30, handlePullReq.ts 61-63 catch)
• jobs: lgtm frobnicate: the lgtm job removes the label, the unsupported job still fails the run

Measured with npm run test:coverage:e2e on main @ 3fc21f2: handlePullReq.ts 80.76 → 96.15 % lines (only the unreachable line 46 remains), onPrLgtm.ts 83.33 → 91.66 % (only the unreachable line 19 remains). Unit coverage of both files is already 100 %.

Cluster: handlePullReq jobs input / onPrLgtm failure — disjoint from the held bundle PRs (#242 cron jobs, #283–#308 issue_comment commands and plugins).

Related Issue

Closes #309

---

Filed by quality agent (hold-gated mode). Human review required.

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

[hivecommons-hive]

Important

Held for human review by the hive's ACMM level gate.

This PR was opened by the "quality" agent while Hive policy required a human checkpoint for that agent. Non-outreach agents are held at ACMM L3–L5; the outreach agent is always held because it publishes project-facing communication.

Hive will keep the hold label until a human removes it. Operators can make a deliberate one-off release during an ACMM level change with release_level_holds=true, but level changes never release this hold automatically.

[hivecommons-hive]

build-test is red here for a baseline cause this PR's diff does not touch: all 81 test files pass, and the job exits 1 on a single vitest Unhandled Error — assert(err.code !== "ERR_TLS_CERT_ALTNAME_INVALID") originating in __tests__/issueCommentTest/meow.test.ts (runs 37234002533, 37233899279 on 709cb6c). This PR only changes __tests__/bundle/pullReqJobsArms.test.ts.

Tracked as shared incident #294; fix is #287. Deferring — no re-runs or pushes to this branch until that lands.

---

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

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

[jeefy]

• pullReqJobsArms.test.ts:40 and :63: use a fragment, e.g. toContain('could not execute frobnicate'), instead of comparing the whole TypeError: error handling pull request: … string with toEqual.
• Drop :56–65. It reaches the same lines as :36, and removing the lgtm label is already covered at bundle.test.ts:941.
• At :42, :53 and :64, use calls() from helpersFor (routeOwners already comes from it) instead of the inline gh.requests.map(...).

[hivecommons-hive]

Addressed all three: the unsupported-job error is toHaveLength(1) + toContain('could not execute frobnicate'), the two-jobs case is dropped, and the request lists use calls() from helpersFor. Merged main too (it brings #287's meow network fix, which is what build-test was failing on).

---

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

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

[hivecommons-hive]

Addressed in 043a586: fragment checks (toContain('could not execute frobnicate')), the two-jobs case is dropped, and request lists come from calls() via helpersFor.

CI is green on the new head.

---

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

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

[jeefy]

Asks addressed; verified on current main (aa6a0f8) together with the other approved PRs.

[jeefy]

/kind cleanup
/lgtm
/approve
/hold cancel