fix(agent-core-v2): stop warning on unhandled store.changed events

[7Sageer]

Related Issue

N/A — internal fix, no tracking issue. Problem explained below.

Problem

Every message sent in the CLI prints console noise like
[agent-core] unhandled event "store.changed" in actor "x:271".

The eventStore actor's publish fans each persisted event out two ways:
emit to external .on() subscribers (the real consumer path — works fine)
and a sendBack to the agent machine. The agent machine declares
store.changed in its event types but defines no transition for it, so the
xstate reportUnhandled hook warns on the resulting zero-transition
microstep. Pure noise, no functional impact.

What changed

• Added a noop root-level 'store.changed': {} transition in the agent
  machine (packages/agent-core-v2/src/human/agent/machine.ts), mirroring
  the existing 'store.reset': {} noop in the session machine — the machine
  now explicitly acknowledges the event without reacting to it.
• Added a regression test covering that persisting events no longer produces
  an unhandled-event warning.
• Note: removing the sendBack from the storeActor was tried first and breaks
  xstate waitFor snapshot re-evaluation, so the noop-transition approach
  was chosen instead.

Checklist

• I have read the CONTRIBUTING document.
• I have linked a related issue (external PRs: the issue must have a maintainer's /approve).
• 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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b8e2de6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[7Hanrui]

@codex review

[pkg-pr-new]

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

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

commit: d508d61

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1783894747

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Remove the internal component name from the changeset

When this changeset is rendered into the public CLI release notes, it exposes the internal agent-core component label. Rephrase this as a neutral user-facing description, such as stopping spurious unhandled-event warnings when messages are sent.

AGENTS.md reference: AGENTS.md:L82-L82

Useful? React with 👍 / 👎.

[7Hanrui]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: d508d617cc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".