Bug: Existing tabs receive idle job_status instead of owner job state during active multi-tab scans

[techmore]

Summary

When multiple tabs are already open and a scan or Complete + PDF job starts in one tab, other open tabs may receive live text feedback but still fail to reflect the active button pulse/state.

Expected Behavior

All open tabs should receive the active job state from the owning tab, including the correct pulsing button and running status.

Actual Behavior

Secondary tabs can show live feedback while still rendering the active job as idle, so the initiating button does not pulse.

Root Cause Hypothesis

The job-status fanout path is likely emitting status by looking up the subscriber sid instead of the owner sid, which would send idle for non-owner tabs even while the owner job is running.

Reproduction

1. Open two tabs before starting a scan/report job.
2. Start Quick Scan or Complete + PDF in tab 1.
3. Observe tab 2.
4. Live feedback may appear, but active button state does not match.

Priority

High

[techmore]

Grouping under #161 (Multi-tab scan state consistency). Closing as duplicate to track work in the initiative.

[techmore]

Tracked in #161.