kars-runtime-langgraph-ts image fails to build (OpenTelemetry API drift) — not published

The `langgraph-ts` runtime image does not compile, so it is excluded from the release publish matrix (`.github/workflows/release-public-interim.yml`). The CLI lists it as an OPTIONAL import (`required:false` in `lib/release.ts` / `up/images.ts`), so its absence never breaks a deploy — but the image is unavailable.

**Build failure (release v0.1.21 attempt, since reverted):**
```
src/otel.ts(48,13): error TS2339: Property 'Resource' does not exist on type '...@opentelemetry/resources...'
src/otel.ts(95,20): error TS2339: Property 'addSpanProcessor' does not exist on type 'NodeTracerProvider'
```
The OpenTelemetry SDK APIs changed: `new Resource(...)` → `resourceFromAttributes(...)`/`defaultResource()`, and `provider.addSpanProcessor(...)` → pass `spanProcessors` to the `NodeTracerProvider` constructor.

**To fix:** update `runtimes/langgraph-ts/src/otel.ts` to the current OTel API (or pin the older `@opentelemetry/*` versions), confirm `sandbox-images/langgraph-ts/Dockerfile` builds, then re-add `{ name: langgraph-ts, ghcr: kars-runtime-langgraph-ts }` to the release runtime matrix.

**Context:** discovered during the kars-upgrade-flow fix (#473) — I had added langgraph-ts to the publish matrix assuming it built; it doesn't, so the matrix entry was reverted to keep releases green.

Start with runtimes/langgraph-ts/src/otel.ts and compare its OpenTelemetry usage with the current SDK APIs described in the issue. Build sandbox-images/langgraph-ts/Dockerfile to verify the image compiles, then restore the langgraph-ts entry in .github/workflows/release-public-interim.yml; done means the image builds and is included in the release runtime matrix.

Written by the indexing model from the issue text.