Applicant Correspondence - Create new Message

* As an IAO user
* I want to be able to send an applicant correspondence
* so that I can notify them of important changes to their request

**Assumptions & Scope**
This story covers the need for IAO users to send applicant correspondence.

Currently, the contact applicant log only appears when a fee estimate is sent - this should now persist through the life of a request, in any state.

This story will cover that new requirement, as well as how a user will get to create a new message to send to an applicant.

To send a message to an applicant, a user needs to select a letter and email template. Letter Templates will be covered in a separate user story - email templates will work consistent with how we have the feature working with fee cover emails.

Messages can be saved as draft to send later, or if a review by a colleague is required prior to sending. Any IAO user that has access to a request will be able to see the sent correspondence, and access any draft correspondence.

Will need designs to handle some of these features like

What is IN scope?
Contact applicant log updates
Creating a message to send
Selecting a letter and email template
Editing the message
Saving as a draft

What is NOT in scope?
Sending the message.
Editing the template letter
Saving the templated letter as a draft

**Acceptance Criteria**

**Scenario 1: xxxxxx**
* GIVEN ... (you or your condition)
* WHEN ... (what you do)
* THEN ... (what you see)

**Scenario 2: xxxxxx**
* GIVEN ... (you or your condition)
* WHEN ... (what you do)
* THEN ... (what you see)

**Scenario 3: xxxxxx**
...

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

The issue does not name files, tests, entry points, designs, or implementation details. Before starting, clarify the acceptance criteria, UI design, dependencies, and which existing fee-cover email flow should guide the feature; completion would require agreed behavior for contact-log persistence, message creation, templates, editing, and drafts.

Written by the indexing model from the issue text.