[hivecommons-hive]

Description

Adds controlled non-Error rejection scenarios through dist/index.js using a one-shot NODE_OPTIONS=--require preload. A proxied fetch response throws a string from its status getter, after Octokit's fetch catch, while still recording the request against the fake GitHub API.

The four scenarios exercise:

• runEventHandlers on a rejected pull-request read.
• Per-command normalizeError on a rejected milestone listing.
• Label-sync's write catch, including continuation to later labels.
• getErrorDetails through /retitle's collaborator check: one warning with status=unknown and the exact primitive message, a successful action exit, no unhandled rejection, and no issue update.

Fixes #507

The auth scenario supersedes the coverage-ignore approach in #510 once this PR merges: auth.ts now reaches 100% bundle line coverage without adding an ignore or removing its defensive fallback. Other findings formerly folded into #507 have their own canonical PRs; the upstream V8 report is preserved in #550.

Related: #548 adds distinct plugin scenarios using the byte-identical preload. It can remain a separate PR; neither scenario set should be discarded. Truly wrapped/unreachable arms are separately owned by #537, #544 and #549.

Testing

• npx vitest run __tests__/bundle/nonErrorRejectionArms.test.ts — passed: 4 tests.
• npx eslint __tests__/bundle/nonErrorRejectionArms.test.ts __tests__/bundle/nonErrorRejectionPreload.cjs — passed.
• npm run test:coverage:e2e — passed; 100% statements, lines and functions; 99.03% branches (1640/1656). src/utils/auth.ts has 100% lines without an ignore annotation.

Checklist

• I ran npm run all to lint and build my code — used the focused lint/tests and full e2e coverage command above instead.
• I ran npm run pack and committed dist/ — not needed: this PR changes only bundle tests and their preload; committed production source/bundle are unchanged.
• Commits are signed off (DCO)
• Note any new dependencies these changes bring in — none.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation — behavior is unchanged; the test and this PR describe the controlled fault injection.
• My changes generates no new warnings (please describe new warnings if unavoidable)

[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.

[mrbobbytables]

Copilot review performed under the maintainer's explicit authorization to update, review, release reviewed holds, and merge eligible PRs in this cleanup.

Reviewed the shared one-shot preload and four bundle scenarios. The added auth case reaches auth.ts:24, reports the exact primitive warning and denies the title write. Local full e2e coverage passed with 100% lines and 99.03% branches; no auth ignore or production change is needed.

Verified successful build-test, e2e-coverage and DCO results on head f0e2394. Any folded issue findings remain assigned to the canonical destinations in the updated scope tables.