Felix Förtsch 51d56a4082 push verified=1 to the UI via a plan_update SSE event ...

the ✓✓ write was landing in the db but never reaching the browser.
job_update fires once at job completion (card renders ✓, verified=0),
then handOffToJellyfin takes ~15s to refresh jellyfin + re-analyze +
UPDATE review_plans SET verified=1. no further sse, so the pipeline
page never re-polled and the card stayed at ✓ until the user
navigated away and back.

new plan_update event emitted at the end of handOffToJellyfin. the
pipeline page listens and triggers the same 1s-coalesced reload as
job_update, so the done column promotes ✓ → ✓✓ within a second of
jellyfin's verdict landing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-14 20:51:47 +02:00

..

api

push verified=1 to the UI via a plan_update SSE event

2026-04-14 20:51:47 +02:00

db

webhook: PascalCase payload + ItemAdded only, switch ✓✓ signal to ffprobe

2026-04-14 17:27:22 +02:00

lib

address audit findings: subtitle rescan decisions, scan limit, parseId, setup gate

2026-04-14 17:41:36 +02:00

services

skip non-extractable subs (dvdsub/dvbsub/unknown), summarise ffmpeg errors

2026-04-14 18:42:05 +02:00

index.tsx

close the jellyfin ping-pong via mqtt webhook subscriber

2026-04-14 08:26:42 +02:00

types.ts

webhook: PascalCase payload + ItemAdded only, switch ✓✓ signal to ffprobe

2026-04-14 17:27:22 +02:00