upgrading-runtime-dependencieslisted

# Upgrading Runtime Dependencies This skill teaches the judgment calls needed when upgrading dependencies that power agent runtimes. Unlike routine dependency bumps, runtime SDK upgrades require understanding what new capabilities to adopt, not just what breaks. ## Core Principle Runtime dependencies sit behind abstraction boundaries (e.g., the `AgentRuntime` interface). Changes to the SDK affect a confined set of files, but the _implications_ ripple outward through the features those files enable. Your job is to trace both the direct code impact and the strategic value. ## Changelog Categorization ### Ambiguous Entries Changelog entries are often vague. Use these heuristics: | Entry Pattern | Likely Category | Why | | ---------------------------- | ------------------- | --------------------------------------- | | "refactored X internals" | `internal` | Unless X is a public API you call | | "improved X performance" | `performance` | But check if our usage pattern benefits | | "updated X types" | Could be `breaking` | Type changes can break compilation | | "X now accepts Y" | `feature` | Additive API change | | "X no longer does Y" | `breaking` | Subtractive behavior change | | "deprecated X in favor of Y" | `deprecated` | Even if X still works | | "fixed X when Y" |