chore: update spec.types.2026-07-28.ts from upstream

[github-actions]

This PR updates packages/core-internal/src/types/spec.types.2026-07-28.ts from the Model Context Protocol specification.

Source file: https://github.com/modelcontextprotocol/modelcontextprotocol/blob/93671a3f2bac3bc11b0eb6327c2d029e272b2871/schema/draft/schema.ts

This is an automated update triggered by the nightly cron job.

---

This change is 

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6ec25c8

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[kilo-code-bot]

[SUGGESTION]: This PR only updates the provenance comment (the Last updated from commit hash) — the generated type definitions below are unchanged.

This is expected for a date-pinned era snapshot that is stable upstream, but it is worth confirming the automated fetch:spec-types run actually regenerated spec.types.2026-07-28.ts and found no content delta. If the upstream schema.ts changed between f68d864… and 93671a3… for this era, only bumping the header while leaving the types stale would silently ship outdated types. Please verify the generated body matches upstream at 93671a3… (or confirm the era content is intentionally frozen).

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
packages/core-internal/src/types/spec.types.2026-07-28.ts	6	PR only bumps the Last updated from commit provenance comment; the generated type definitions are unchanged. Confirm the automated fetch:spec-types run regenerated the file and found no content delta, so types are not silently stale if upstream changed.

Files Reviewed (1 file)

• packages/core-internal/src/types/spec.types.2026-07-28.ts - 1 issue

Fix these issues in Kilo Cloud

---

_{Reviewed by hy3-20260706:free · Input: 57.7K · Output: 6.8K · Cached: 179K}

_{Review guidance: REVIEW.md from base branch main}