refactor(nitro): drop the dead !ctx operand in the v3 response hook

[evlogai]

Summary

In the nitro-v3 response hook (packages/evlog/src/nitro-v3/plugin.ts), the guard

if (ctx?._evlogEmitted || ctx?._evlogEmitting || !ctx?._evlogShouldEmit) return

const log = ctx?.log as RequestLogger | undefined
if (!log || !ctx) return

already returns when ctx is undefined: with ctx undefined, !ctx?._evlogShouldEmit is true, so control never reaches the second guard. The !ctx operand is therefore dead, and once it is gone the ?. on ctx?.log is dead with it (TypeScript narrows ctx past the compound guard, confirmed by pnpm run typecheck). The same shape already exists in the error hook two functions below, which reads ctx.log after if (!ctx?._evlogShouldEmit) return.

-    const log = ctx?.log as RequestLogger | undefined
-    if (!log || !ctx) return
+    const log = ctx.log as RequestLogger | undefined
+    if (!log) return

Behavior is preserved. The nitro-v3 integration suite (test/nitro-v3/nitro-v3.test.ts) is the matching test: it drives the response hook through h3 v2's real request driver, including the filtered-out and already-emitted branches this guard serves.

Checks

• pnpm --filter evlog exec vitest run test/nitro-v3/: 5 files, 29 tests passed with the edit.
• pnpm run lint, pnpm run typecheck, pnpm run test: all exit 0 with the edit (96 files, 2,014 tests). Typecheck is the load-bearing one here: it proves ctx is narrowed so the non-optional ctx.log and the later ctx._evlogStartTime read inside emitSuccessResponse stay valid.
• No changeset: dead-code removal with no observable consumer change (per AGENTS.md).

Found by the repo-health sweep at revision 54dcc504; confirmed by the workflow's verifier and reproduced in the sandbox.

Note: this touches plugin.ts lines 246-247, just above the region PR #795 refactors; if #795 merges first this rebases cleanly, and vice versa.

ELI5

One safety check in the v3 request logger asked the same question twice in a row, and the second ask could never fail because the first had already handled it. Removing the repeated check makes the code read straight through; the automated tests confirm nothing changed at runtime.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
evi	Ready	Preview	Oct 9, 2026 8:22am UTC
evlog-telemetry	Ready	Preview	Oct 9, 2026 8:22am UTC

3 Skipped Deployments

Project	Deployment	Actions	Updated
evlog-docs	Skipped	v0	Oct 9, 2026 8:22am UTC
evlog-render-lab	Skipped		Oct 9, 2026 8:22am UTC
just-use-evlog	Skipped		Oct 9, 2026 8:22am UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 175f7f0a-ddd6-416d-a757-498b4f7b22fa

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thank you for following the naming conventions! 🙏

[pkg-pr-new]

@evlog/cli

npm i https://pkg.pr.new/@evlog/cli@796

evlog

npm i https://pkg.pr.new/evlog@796

@evlog/nuxthub

npm i https://pkg.pr.new/@evlog/nuxthub@796

@evlog/signals

npm i https://pkg.pr.new/@evlog/signals@796

@evlog/telemetry

npm i https://pkg.pr.new/@evlog/telemetry@796

commit: 92e5acc