v0.17.4-0009: Clear Emby Logos feature (GH #475, bd-v9tp7)

[MotWakorb]

Problem

GH #475 (Critical): Emby caches channel logos and keeps serving a stale image even after the logo changes upstream in Dispatcharr, with no way to force a refresh. Channel Identifiarr has a "clear logos" function that deletes the cached image so Emby re-fetches it; this replicates that.

Approach

Reuses ECM's existing Emby connectivity — the saved emby_base_url + emby_api_key with X-Emby-Token auth (what the resolver/cache already use). A static Emby API key authenticates both GET /LiveTv/Channels (enumerate) and per-channel DELETE /Items/{id}/Images/{type} (clear), so no new credentials and no AuthenticateByName username/password login (simpler than CI). Deleting the cached image makes Emby re-download the logo from its source on next channel access.

What's included

Backend

• EmbyClient.get_livetv_channels() (the auth gate — a bad key fails here before any delete) and delete_item_image(id, type), with a Primary / LogoLight / LogoLightColor image-type whitelist.
• New admin-gated routers/emby.py: POST /api/emby/clear-logos → 202 + {job_id} running a supervised background task (a full-lineup sweep — hundreds of channels × up to 3 types — would exceed the 30s ECM_REQUEST_TIMEOUT_SECONDS middleware; same 202+poll pattern as bulk-commit, bd-ggxks), plus GET /api/emby/clear-logos/{job_id}. Clears all Live TV channels (accepts an optional channel_ids filter for a future per-group UI — PO decision), per-channel resilient, validates Emby is configured (400 otherwise) and the image types (400 on unknown).

Progress via the notification system, like stream probe (PO decision)

• The job emits a task_clear_emby_logos progress notification (create → rate-limited updates → finalize success/warning), rendered live by the NotificationCenter — progress bar, deleted/skipped/error counts, current channel name — driven by a new clearing active status.

Frontend

• services/api.ts: clearEmbyLogos + getClearEmbyLogosStatus + EMBY_LOGO_TYPES.
• Settings → Integrations → Emby: a "Clear Cached Logos" block with per-type checkboxes (default all three) and a fire-and-forget button gated on a saved Emby key; live progress shows in the Notifications panel.
• NotificationCenter: clearing added to the progress status union + active list.

MCP

• New clear_emby_logos tool (202+poll), endpoint contract + registration.

Tests

• Backend: 33 (Emby client + clear-logos router incl. the notification create→update→finalize lifecycle, channel filter, per-channel-error resilience, auth-failure-fails-job).
• MCP: 6 tool tests + 129 MCP↔backend contract tests.
• Frontend: 76 (incl. clear-logos UI render, disabled-until-configured, type-filtered call, no-type-selected guard).
• tsc 0, eslint 0.

Pre-existing unrelated failures in test_alert_methods.py (6 SMTP cases — unregistered smtp type in the local test registry) are environment-specific and documented in PR #474; not touched here.

Versioning

All three touchpoints bumped 0.17.4-0008 → 0.17.4-0009 (consistency check passes); CHANGELOG [Unreleased] → Added entry.

Closes GH #475. bd-v9tp7.

🤖 Generated with Claude Code