Ministry Coordinator tag Incompatible Files for Harms

* As a ministry coordinator
* I want to tag a non-PDF file (i.e., incompatible) as a 'Potential Harm'
* so that IAO is aware that the record may need to be withheld

**Assumptions & Scope**
What are the assumptions for this story?

The new Records Review app will be for the redaction of PDFs.

Some, but not all non-PDFs, can be converted to PDF for redaction.

All file types will be uploaded through the Records log into Object Storage.

The Final Package will be generated as a ZIP file from the Records log to be sent to the applicant. This ZIP file will include the redacted PDF and non-PDF files that are deemed to have no harms (i.e., they can be Released in Full).

This story is for the ministry to flag harms for non-PDFs that cannot be converted to PDF for review by IAO.

What is IN scope?
Ministry tagging non-PDF (i.e., incompatible files) for harms.
Filter by 'Potential Harm' tag

What is NOT in scope?
Upload of incompatible file types #3465
Filter by incompatible file #3288
Marking a record as incompatible #3266
Ellipsis for each record #3292

**Acceptance Criteria**

**Scenario 1: Incompatible Ellipsis Options**
* GIVEN a the ministry coordinator is on the Records log
* AND a record is incompatible (non-PDF that cannot be converted)
* WHEN the user clicks the ellipses for the record
* THEN the dropdown will open with these options: Download Original, Delete and Potential Harm will be listed

**Scenario 2: Click 'Potential Harm'**
* GIVEN a ministry coordinator has activated the ellipsis on an incompatible file
* WHEN the user clicks 'Potential Harm'
* THEN the file will be tagged with 'Potential Harm'
* AND a checkmark will show next to 'Potential Harm'
* AND the dropdown will close

**Scenario 3: Filter by 'Potential Harm'**
* GIVEN a ministry coordinator has tagged an incompatible file with 'Potential Harm'
* WHEN the user clicks the 'Potential Harm' filter
* THEN the Records log will be filtered to only display 'Potential Harm' tagged records

**Scenario 4: Click 'Potential Harm' to remove tag**
* GIVEN a ministry coordinator has activated the ellipsis on an incompatible file
* AND a the Potential Harm tag has already been applied to a record
* WHEN the user clicks 'Potential Harm' again
* THEN the 'Potential Harm' tag will be removed from the record
* AND the checkmark next to Potential Harm will go away
* AND the dropdown will close

**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?

Start at the Records log entry point and review the acceptance criteria for incompatible-file ellipsis actions, Potential Harm tagging, and filtering. Confirm the design and existing tag behavior before implementing; done means all four scenarios work, including applying and removing the tag, showing the checkmark, closing the dropdown, and filtering records.

Written by the indexing model from the issue text.