fix(github-copilot): preserve reasoning ids with encrypted_content

[a410979729-sys]

Summary

Fix GitHub Copilot response replay so that reasoning items with encrypted_content do not have their item ids rewritten by connection-bound id normalization.

Problem

Copilot/OpenAI Responses reasoning items can carry encrypted_content that is bound to the original item id.

The existing connection-bound id normalization rewrites opaque response item ids before replay. For normal items this is fine, but for reasoning items with encrypted_content it creates an inconsistent payload:

• outer reasoning item id is rewritten to a synthetic rs_<hash> id
• encrypted payload still refers to the original upstream item id

This causes provider-side request rejection with errors like:

The encrypted content for item rs_... could not be verified.
Reason: Encrypted content item_id did not match the target item id.

Fix

Skip connection-bound id rewriting for response items where:

• type === "reasoning"
• encrypted_content is present

This keeps the encrypted reasoning block internally consistent while preserving the existing normalization behavior for other item types.

Tests

Added regression coverage for:

• preserving ids for reasoning items with encrypted_content
• continuing to rewrite reasoning ids when encrypted_content is absent

Local verification:

corepack pnpm exec vitest run extensions/github-copilot/connection-bound-ids.test.ts

Related

Addresses #70654

Submitted by Tianji on behalf of the Beidou Five and Joy.

[greptile-apps]

Greptile Summary

This PR adds a targeted guard in rewriteCopilotConnectionBoundResponseIds to skip id rewriting for reasoning items that carry an encrypted_content field, preventing a provider-side verification failure caused by a mismatched item id inside the encrypted payload. Two regression tests are added to cover both the new bypass and the unchanged behaviour for reasoning items without encrypted content.

Confidence Score: 5/5

Safe to merge — minimal, well-scoped fix with direct regression tests.

The change is two guarded lines with a clear precondition (type === 'reasoning' && typeof encrypted_content === 'string'), inserted at the right point in the loop before the id rewrite. Both the new behaviour and the existing behaviour for reasoning items without encrypted content are tested. No logic, security, or type-safety issues found.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(github-copilot): skip id rewrite for..." | Re-trigger Greptile}

[steipete]

Landed via squash merge.

• Gate: pnpm check:changed; pnpm test:contracts:plugins; GITHUB_COPILOT_LIVE_TEST=1 OPENCLAW_LIVE_TEST=1 pnpm test:live extensions/github-copilot/connection-bound-ids.live.test.ts --reporter=verbose --testTimeout=70000
• Source head: f7f4857
• Merge commit: 8fd15ed

Thanks @a410979729-sys!