chore: remove non-user-facing changesets

[claude]

Requested by Eric Allam · Slack thread

✅ Checklist

• I have followed every step in the contributing guide
• The PR title follows the convention.
• I ran and tested the code works

---

Testing

N/A — this change only removes two changeset markdown files; there are no code changes to test.

---

Changelog

What changed

Removes two @trigger.dev/core changesets that were added for changes that are not user-facing package changes:

• .changeset/runops-core-residency.md — internal run-ops residency classifier + ksuid mint/decode primitives
• .changeset/telnet-dev-logs.md — dev-only @trigger.dev/core/v3/telnetLogServer module

Why

Per the convention that changesets should only be added when there are actual user-facing package changes, these two do not qualify. Removing them keeps the release (currently the automated v4.5.1 PR #4126) from bumping @trigger.dev/core for internal/dev-only additions.

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1a83496

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

[devin-ai-integration]

Devin Review found 1 potential issue.