Advisory issuance and distribution mechanism

**As a** *Fire Behavior Specialist* **I want* *to issue a fire behavior advisory/warning from automatically generated content* **So That** *the process is scalable and can reach all field staff across multiple communication platforms in an efficient manner.

**Additional Context**
- Currently, radio dispatchers read out advisories to fire fighters. There may be additional methods to push notifications out such as mobile devices. Our product should support all possible communication mechanisms because they are always available at the same time.

**Acceptance Criteria**
- [ ] Given an advisory is automatically generated, When the distribution mechanism is employed, Then the advisory is issued across across multiple communication platforms, eg.) PDF to radio dispatcher, mobile app, website, etc.
- [ ] Given situations where there is additional context for an advisory, When I add comments within a specified time window, Then they are automatically included with the advisory when it is issued.

**Definition of Done**
- Ready to Demo in Sprint Review
- Does what I have made have appropriate test coverage?
- Documentation and/or scientific documentation exists and can be found
- Peer Reviewed by 2 people on the team
- Manual testing of all PRs in Dev and Prod
- Merged

The issue names no files, tests, or entry points. Begin by locating the existing advisory-generation flow and the current radio-dispatcher output, then determine how mobile, website, PDF, and timed comments are represented. Done means agreeing on the distribution design, implementing each channel, covering the comment window and delivery behavior with tests, and documenting the workflow.

Written by the indexing model from the issue text.