[WRONG BRANCH] fix(logs): preserve apiKeyId, admissionKind, and inboundProtocol when hydrating request logs

[luvs01]

Motivation

• Persisted usage rows already include apiKeyId, admissionKind, and inboundProtocol, but hydrated /api/logs entries lost those fields after restart because the projector did not copy them back.
• The change restores expected attribution in the in-memory request-log ring so GUI and /api/logs show the same attribution as usage.jsonl after a process restart.

Description

• Copy apiKeyId, admissionKind, and inboundProtocol from PersistedUsageEntry into the RequestLogEntry returned by requestLogEntryFromPersistedUsage using the existing validation helpers. (src/server/request-log.ts)
• Add regression assertions to tests/request-log.test.ts to verify the three attribution fields survive the persisted-to-request-log projection. (tests/request-log.test.ts)
• Preserve existing validation and normalization behavior by using isKnownAdmissionKind and isKnownInboundProtocol when restoring fields.

Testing

• Ran the focused request-log tests with the repository test runner (node_modules/bun/bin/bun.exe test --isolate tests/request-log.test.ts) and the hydrated-log tests passed (45 tests in file all passed).
• Ran bun run typecheck and bun run privacy:scan, both of which succeeded.
• Ran the broader test runner (bun run test) in this environment and observed the test suite execute with many passing tests; focused coverage for the changed code is green.
• Noted an environment mismatch where invoking the system bun test tests/request-log.test.ts (system Bun v1.2.14) raised a node:zlib export error, but the repository-managed Bun invocation used for CI reproduced passing results; the failure is environmental and unrelated to the code change.

---

Codex Task

[coderabbitai]

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b73d2206-b467-4b72-adc3-31733044e597

📥 Commits

Reviewing files that changed from the base of the PR and between 121f1ad and f638dbc.

📒 Files selected for processing (2)

• src/server/request-log.ts
• tests/request-log.test.ts

---

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

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev. UI screenshot required.

What to do

• Retarget this PR to dev — all contributions go to dev.
• Add a screenshot of the UI change to the PR description.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.