koala73/worldmonitor

Two independent one-line nits surfaced by a structural review of #5812. Neither is a defect; both are the kind of thing that is cheaper to fix than to re-derive later. Good first issue — each is a single line plus a verification run. 1. isEntitlementActive is public API whose only external consumer is a test seam src/services/entitlements.ts — #5812 extracted this out of isEntitled() so the playback DOM suite could evaluate the real entitlement predicate instead of hand-copying its three conditions into a mock (where they drift silently). That was the right call and is mutation-proven: mutating the predicate now reds 5 tests, where the hand-copied mock survived it. The residual cost is that it is now exported, so it can be called with a hand-built snapshot, bypassing the reactive currentState that every other reader goes through. Nothing does this today. Fix: add an @internal JSDoc tag (or the repo's equivalent convention) documenting that the only intended callers are isEntitled()

Feature area News panels / RSS feeds Description A @username input field in the Telegram Intel panel that lets users add any public Telegram channel to a personal watchlist, persisted in localStorage. The user types a username, sees a preview (channel title + member count), then clicks Add. Their saved channels appear as removable pills and their posts render alongside the curated feed. No user login to Telegram required. The relay's existing authenticated GramJS session already has permission to read any public channel — this only needs two new GET routes on the relay and ~170 lines of frontend/service code. User flow: User types @ukraine_news in a new input in the panel Frontend debounces 800ms → calls GET /telegram/resolve?username=ukraine_news Relay resolves via client.getEntity() → returns title + member count, cached in Redis 24h Panel shows: "Ukraine News · 89k members [+ Add]" User clicks Add → saved to localStorage under telegram:watchlist:v1 Panel calls GET /telegr