test(bundle): serve comment.body and label.name absent to drive the '?? ""' folds through dist/index.js

[hivecommons-hive]

Test Improvement

Files claimed: __tests__/bundle/absentOptionalFields.test.ts (new, test-only). Functions: src/utils/comments.ts createCommentOnce (line 58, comment.body ?? ''), src/plugins/requireMatchingLabel.ts botCommentsWithMarker (line 248, comment.body ?? ''), src/issueComment/trigger.ts okToTestOnPullRequest (line 181, label?.name ?? ''). No src/, dist/ or workflow change.

The REST schema types issue-comment.body as optional and the object form of issue.labels[] with an optional name, but every bundle scenario serves both fields, so at main@1062ce7 npm run test:coverage:e2e reports the three folds with zero hits (coverage-e2e/lcov.info: BRDA:58,2,1,0, BRDA:248,32,1,0, BRDA:181,29,1,0); the unit suite covers all three files at 100 / 100 / 100 / 100.

Four cases, each serving the field absent and driving dist/index.js:

• pull_request synchronize with labels: [{ id: 2 }, { name: 'ok-to-test' }]: the nameless object is skipped, the action_required run on the head is still approved; request sequence asserted.
• the same with labels: [{ id: 2 }] alone: ::debug::trigger: the pull request does not carry ok-to-test, no actions/runs read.
• pull_request labeled lgtm by a bot (no binding) whose GET /issues/1/comments lists one bot comment with no body: the label is stripped and the stale-lgtm notice with its marker is posted once (the bodyless comment is not taken as already carrying it); full request sequence asserted.
• issues labeled kind/bug with needs-kind present whose comments list holds a bodyless bot comment (id 11) and the marker comment (id 12): needs-kind is removed and only comment 12 is deleted.

Verification (local, this branch, main @ 1062ce7)

• npx eslint __tests__/bundle/absentOptionalFields.test.ts clean
• npx vitest run __tests__/bundle/absentOptionalFields.test.ts: 4 passed
• npm run test:coverage:e2e: 79 files / 491 tests pass (was 78 / 487); Branches 97.96 % → 98.14 % (1633 → 1636 / 1667); comments.ts and requireMatchingLabel.ts now 100 % branches; trigger.ts 98.96 % with only line 323 (errorStatus, unreachable through Octokit) left
• Unit suite untouched

Disjoint from the open held PRs: #497 (approve.ts, meow.ts), #498 (tideOptionalFields.test.ts: tide.ts, sweep.ts), #500/#502 (thresholds), #501 (docs YAML), #504 (octokit.ts), #505 (nullIssueUser.test.ts: issueComment/approve.ts, close.ts, reopen.ts).

Related Issue

Refs #507 (needs-human: the issue's own item, dropping or v8-ignoring the getErrorDetails non-object arm at auth.ts:24, is a production-code change the quality lane does not PR; this PR lands the folded finding on that issue — the three ?? '' folds — and ticks its four boxes)
Refs #466 (tracker for every dist/index.js e2e-coverage finding)

---

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. Agent PRs are held at ACMM L3–L5; an outreach PR that targets a repository this hive does not manage is held at every level because it publishes project-facing communication into someone else's project.

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.

[github-actions]

Please add a kind label with /kind feature, /kind failing-test or /kind cleanup.