fix(kiro): gate diagnostic request-body encoding behind debug flag

[luvs01]

Motivation

• The Kiro adapter was computing bodyBytes by calling new TextEncoder().encode(body).length while building requests, which forced a full UTF-8 encoding (and allocation) of the upstream request body even when diagnostic logging was disabled, creating a resource-exhaustion risk.

Description

• Import isDebugEnabled and move the diagnostic bodyBytes computation and the debugProviderDiagnostic(...) call behind an if (isDebugEnabled()) gate in src/adapters/kiro.ts so expensive encoding only happens when provider debug is enabled.
• Add a focused regression test to tests/kiro-stream.test.ts that spies on TextEncoder.prototype.encode and fails if it is called when diagnostics are disabled to prevent regressions.
• Changes touch src/adapters/kiro.ts and tests/kiro-stream.test.ts and preserve existing runtime request shape and behavior when debug is enabled.

Testing

• Ran the focused Kiro tests with bun test tests/kiro-stream.test.ts and the new regression (buildRequest does not encode the request body for diagnostics when debug is disabled) passed in the targeted runs.
• Ran type checking with bun run typecheck which succeeded.
• Ran privacy checks with bun run privacy:scan which succeeded.
• Ran the full test suite (bun run test) which surfaced unrelated, environment-sensitive failures in management-auth tests (HTTP 403 responses) that are not caused by this change; the failures are outside the scope of this diagnostic-gating fix.

---

Codex Task

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: f3a1cc92-c406-4026-82cb-a743b0daa47d

---

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]

✅ Deterministic PR hygiene checks passed.

[github-actions]

✅ READY

• all PR quality gates passed.

Hygiene

✅ Deterministic PR hygiene checks passed.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e5dc7a8c4d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Explicitly disable all provider-debug sources in this test

When the test suite is launched with the supported OCX_DEBUG=1 environment setting, this test enters the diagnostic branch and the mocked encoder throws; this is reproducible with OCX_DEBUG=1 bun test tests/kiro-stream.test.ts --test-name-pattern 'buildRequest does not encode'. The shared setup only deletes legacy OCX_DEBUG_FRAMES, while isDebugEnabled() also reads OCX_DEBUG and runtime overrides, so explicitly clear/reset those sources (or force the runtime debug setting off) before asserting that diagnostics are disabled.

AGENTS.md reference: AGENTS.md:L228-L230

Useful? React with 👍 / 👎.

[luvs01]

Superseded by upstream lidge-jun/opencodex#3837, which carries this fix forward against current dev.

This PR's head dates from 2026-08-10 and targets src/adapters/kiro.ts plus tests/kiro-stream.test.ts. Upstream has since relocated the Kiro suite to tests/providers/kiro/, so the patch no longer applies as written.

The upstream PR keeps the same defect and the same fix, rebuilt on dev bf85e675484a2391b94b2135bbebe739813a9621:

• wraps the Kiro request diagnostic in isDebugEnabled() so new TextEncoder().encode(body).length no longer runs over the full serialized payload on every request when provider debug is off
• adds the regression in the relocated tests/providers/kiro/kiro-stream.test.ts

Verified there: 418 Kiro tests pass, typecheck, privacy scan, and git diff --check all clean, and the regression was confirmed to fail without the production guard.

Closing this fork PR to keep a single tracked item for the work.