US41 - Send a block-level liveblog alert

Feature: Send a block-level liveblog alert

Background:
Given the the liveblog contains at least one block
And the author has permission to send notifications

Scenario: Send an app alert for a single block
Given the author has selected a published block
When the author selects "Send alert" on that block
And the author selects at least one communication channel
And the author confirms the alert
Then an alert should be created for that block
And the alert should be linked to the block it was sent from
And the alert status should become "sending"

Scenario: Alert deep-links to the block
Given an alert has been sent for a block
When a recipient opens the alert
Then the recipient should be taken to the liveblog
And the liveblog should be positioned at the block the alert was sent from

Scenario: Block alert is delivered
Given an alert has status "sending"
When delivery to every selected channel succeeds
Then the alert status should become "dispatched"
And the actual dispatch date and time should be recorded
And the block should show that an alert was sent
And the block should show the time the alert was sent

Start by tracing the existing liveblog alert flow from the block’s “Send alert” action through channel delivery and recipient navigation. Use the scenarios as the acceptance checklist: creation must link the block and enter “sending,” delivery must record dispatch details and mark the block, and opening an alert must deep-link to that block.

Written by the indexing model from the issue text.