Session completion notice at batch end

[devjusty]

Parent

#8 — Spec: Session-only scan coordination (ADR-0001)

What to build

Investigators see live Capability status as the Scan Session updates, and a single Session completion notice (toast) when an execute batch finishes. That notice summarizes Scan Session outcome and is suppressed if the batch was superseded. Per-Capability / WordPress-tied success toasts for normal completion are gone. Capability Outcomes from the prior ticket keep firing per terminal Capability.

Acceptance criteria

• One Session completion notice when an execute batch finishes; none mid-batch for normal success.
• Superseded/inactive batch tokens do not fire a completion notice.
• Status UI continues to update as each Capability settles.
• WordPress-tied “scan complete” / per-Capability success toasts for normal completion removed.
• Tests cover once-per-batch notice + token suppression; Outcomes still per Capability.

Blocked by

• Capability Outcomes for settle side effects #11 — Capability Outcomes for settle side effects

[devjusty]

Implemented: one Session completion notice per execute batch (scoped to that batch’s Capability IDs); superseded tokens suppressed; WP-tied normal-completion toasts removed; Outcomes still fire per Capability.