check-ghostty-update

# Check ghostty update termio does **not** build ghostty itself — it embeds ghostty's terminal core through the **`termio-sh/libghostty-swift`** fork, whose weekly CI rebuilds `GhosttyKit.xcframework` against ghostty `main` and publishes it as a `storage.X.Y.Z` release ([[termio-libghostty-swift]]). So "is ghostty up to date" really means: **how far is ghostty `main` ahead of the sha baked into the binary termio is pinned to, and is anything in that gap relevant to termio?** termio is an **embedder**, so only a slice of ghostty's changes matter. Weight the diff accordingly — see *Signal vs. noise* below. Local self-build is impossible on this Mac (Tahoe/zig deadlock); updating the binary always goes through the fork's CI. ## What this skill does NOT do Report only. It does not tag the fork, trigger CI, or bump any pin. Those are the follow-up the verdict points to (and separate skills / explicit asks). ## Procedure Run these steps and report; everything is read-only `gh` + `grep`. ### 1. Resolve the ghostty sha termio is currently on The pin chain is: termio `Package.resolved` → fork version tag → that tag's `Package.swift` names a `storage.X.Y.Z` binary → that storage release's **title** carries the ghostty sha (format `... · ghostty v1.3.1-<N>-g<sha>`). ```bash REPO=$(git rev-parse --show-toplevel) FORK=termio-sh/libghostty-swift GHOSTTY=ghostty-org/ghostty VER=$(grep -A6 '"identity" : "libghostty-swift"' "$REPO/Package.resolved" \ | grep '"version"' | head ...