feat: record model response id in wire logs

[liruifengv]

Related Issue

No related issue.

Problem

Session wire logs did not retain the provider response id for model requests, making it hard to correlate a recorded step with the upstream chatcmpl-... response when debugging provider issues.

What changed

• Propagate the provider response id from the LLM response into the recorded step.end wire event as messageId.
• Keep the field optional so providers that do not return an id omit it.
• Add tests for the new field and update affected wire snapshots.

Checklist

• I have read the CONTRIBUTING document.
• I have linked a related issue, or explained the problem above.
• I have added tests that prove my feature works.
• Ran gen-changesets skill, or this PR needs no changeset.
• Ran gen-docs skill, or this PR needs no doc update.

Verification

• pnpm --filter @moonshot-ai/agent-core test
• pnpm --filter @moonshot-ai/agent-core typecheck
• git diff --check

[changeset-bot]

🦋 Changeset detected

Latest commit: 5cf5feb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@moonshot-ai/kimi-code	Patch
@moonshot-ai/kimi-code-sdk	Patch
@moonshot-ai/agent-core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

pnpm dlx https://pkg.pr.new/@moonshot-ai/kimi-code@5cf5feb

npx https://pkg.pr.new/@moonshot-ai/kimi-code@5cf5feb

commit: 5cf5feb