Add adoption option when submitting a CFD request.

* As an applicant
* I want to indicate that I have been adopted
* so that IAO knows this information ahead of processing my records.

**Assumptions & Scope**
When an applicant applies for their child service records (CS) it may be that they are adopted, however are not requesting their adoption records. Adoption records fall into two categories, identifying and non-identifying, which are severed differently. If an analyst processes a file where it is discovered that a non-identifying adoption has occurred, they will have to re-sever the file from the beginning.

What is IN scope?

What is NOT in scope?

**Acceptance Criteria**

**Scenario 1: Submitting a CFD personal request for CS records."**
* GIVEN An applicant is making a CFD personal request
* WHEN the applicant selects "Your records as a child from a child protection investigation", OR "Your records as a child/youth in care or receiving services" on the "What kinds of records are you looking for?" page
* THEN a modal will appear asking "Are you adopted?"

**Scenario 2: Having the option to select "I am Adopted**
* GIVEN An applicant has chosen "Your records as a child from a child protection investigation", OR "Your records as a child/youth in care or receiving services" on the "What kinds of records are you looking for?" page
* WHEN the "Are you adopted?" Modal has appeared
* THEN "Yes" and "No" response options will be available to choose from.

**Scenario 3: Selecting a response to the "Are you adopted?" modal**
* GIVEN An applicant has chosen "Your records as a child from a child protection investigation", OR "Your records as a child/youth in care or receiving services" on the "What kinds of records are you looking for?" page
* AND the "Are you adopted?" Modal has appeared
* WHEN the applicant chooses "Yes"
* THEN the modal will close and the request will be tagged.

**Scenario 4: Selecting a response to the "Are you adopted?" modal**
* GIVEN An applicant has chosen "Your records as a child from a child protection investigation", OR "Your records as a child/youth in care or receiving services" on the "What kinds of records are you looking for?" page
* AND the "Are you adopted?" Modal has appeared
* WHEN the applicant chooses "No"
* THEN the modal will close and the request will be not be tagged.

**Scenario 5: Not selecting a response to the "Are you adopted?" modal**
* GIVEN An applicant has chosen "Your records as a child from a child protection investigation", OR "Your records as a child/youth in care or receiving services" on the "What kinds of records are you looking for?" page
* AND the "Are you adopted?" Modal has appeared
* WHEN the does not choose "Yes" or "No"
* THEN the applicant will not be able to move to the next stage of the application.

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

No files, tests, entry points, or design are named. Start by locating the CFD personal request flow and the “What kinds of records are you looking for?” page, then trace how request tags and required responses are handled. Done means the modal appears for the two stated choices, enforces a Yes/No response, and applies the tag only for Yes.

Written by the indexing model from the issue text.