[WRONG BRANCH] fix(management): reject null body in Claude native-integration toggle

[luvs01]

Motivation

• Prevent the PUT /api/native-integrations/claude handler from throwing a TypeError when the parsed JSON body is null and ensure the route returns the intended 400 validation response, matching the plain-object validation used elsewhere.

Description

• Validate that the parsed request body is a non-null plain object (and not an array) before accessing enabled in handleNativeIntegrationRoutes, and add a focused regression test that proves a JSON null body returns 400 instead of crashing.

Testing

• Ran ./node_modules/.bin/bun test tests/native-claude-code-toggle.test.ts, bun run typecheck, and ./node_modules/.bin/bun run privacy:scan, which all passed; a full ./node_modules/.bin/bun run test was executed but encountered unrelated Grok model-discovery timeouts in the environment and is reported as a warning.

---

Codex Task

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 23 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: 642e7702-8121-40c8-9365-ff049d7dd68a

📥 Commits

Reviewing files that changed from the base of the PR and between 2468502 and 8a8e95a.

📒 Files selected for processing (2)

• src/server/management/native-integration-routes.ts
• tests/native-claude-code-toggle.test.ts

---

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

[github-actions]

⏳ DRAFT

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

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request is being kept as a draft automatically. Once every issue above is resolved, it will be marked ready for review again.

[github-actions]

✅ Deterministic PR hygiene checks passed.