# Instruction
- You are an expert in cleaning process data descriptions. Given a task, you are provided with a set of annotation description
data for a certain visual LLM related to human user operation videos. Plus, You are provided with full trace of playwright action,
whic includes action and url before and after the action.
- You need to analyze all the descriptive data and ultimately summarize a complete and reasonable user operation description that can accomplish the given task.
- For each strategy, give a clear list of the low level action sequence.

# Task
Draft an email to the shop owner via their contact us function for a coupon as my refund is suppoed to be replaced by a coupon

# Annotation description
## Part 1
In this video segment, I perform the following actions:

1. **Action**: I click on the "Contact Us" link.
   - **Page Changes**: The webpage transitions to a "Contact Us" form page.
   - **Possible Purpose**: The likely intent is to reach out to the website for assistance or information.

2. **Action**: I click inside the "Name" text box.
   - **Page Changes**: The cursor appears in the "Name" text box, indicating it is active and ready for input.
   - **Possible Purpose**: The intent is to enter my name as part of filling out the contact form.

3. **Action**: I type "Emma231 Willow Way, Suite 100, Chicago, IL, 606012EmmaEmmaEn" into the "Name" text box.
   - **Page Changes**: The text I typed appears in the "Name" text box.
   - **Possible Purpose**: The intent is to provide the required name information, though the entered text seems to include an address and repetitive characters, which might be an error or specific test input.

4. **Action**: I click inside the "Email" text box.
   - **Page Changes**: The cursor moves to the "Email" text box, making it active.
   - **Possible Purpose**: The intent is to enter an email address for contact purposes.

5. **Action**: I type "emma.lopez@gmail.com" into the "Email" text box.
   - **Page Changes**: The email address appears in the "Email" text box.
   - **Possible Purpose**: The intent is to provide a valid email address for the website to respond to the inquiry.

6. **Action**: I click inside the "What's on your mind?" text area.
   - **Page Changes**: The cursor appears in the "What's on your mind?" text area, indicating it is active.
   - **Possible Purpose**: The intent is to enter a message or inquiry.

7. **Action**: I type "My refund" into the "What's on your mind?" text area.
   - **Page Changes**: The text "My refund" appears in the text area.
   - **Possible Purpose**: The intent is to communicate a request or inquiry about a refund.

8. **Action**: I hover over the "Submit" button.
   - **Page Changes**: There are no changes to the page, but the "Submit" button is highlighted, indicating it is being targeted for interaction.
   - **Possible Purpose**: The intent is to submit the filled-out form to send the inquiry.

These actions are strictly based on the observations from the provided video segment, focusing solely on the interactions and their immediate effects on the webpage.

---

## Part 2
In this video segment, I perform the following actions:

1. **Action**: I click on the text box labeled "What's on your mind?".
   - **Page Changes**: The text box becomes active, and a blinking cursor appears inside it, indicating that it is ready for input.
   - **Possible Purpose**: The likely intent is to enter a message or inquiry into the text box as part of the contact form.

2. **Action**: I type the text "My refund" into the active text box.
   - **Page Changes**: The text "My refund" appears in the text box.
   - **Possible Purpose**: The purpose is to draft a message related to a refund inquiry, which is a common reason for contacting customer support.

3. **Action**: I continue typing and add the text "is supposed" after "My refund".
   - **Page Changes**: The text in the text box now reads "My refund is supposed".
   - **Possible Purpose**: This action suggests that I am elaborating on my initial message to provide more context about the refund issue.

Throughout these actions, the rest of the webpage remains static, with no other elements changing or interacting. The focus is solely on the text input within the "What's on your mind?" text box.

---

## Part 3
In this video segment, I perform the following actions:

1. **Action**: I click on the text box labeled "What's on your mind?".
   - **Page Changes**: The text box becomes active, and a blinking cursor appears inside it, indicating that it is ready for text input.
   - **Possible Purpose**: The likely intent is to enter a message or query into the text box as part of the contact form submission process.

2. **Action**: I type the message "My refund is supposed to be replaced by a coupon. Please email me a" into the active text box.
   - **Page Changes**: The text appears within the text box as it is typed.
   - **Possible Purpose**: The purpose is to communicate a specific request or issue regarding a refund and a coupon, seeking further action via email.

3. **Action**: I click on the "Submit" button below the text box.
   - **Page Changes**: There is no immediate visible change on the page after clicking the "Submit" button, suggesting that the submission might be processing or that feedback is not instantly displayed.
   - **Possible Purpose**: The intent is to send the filled-out contact form, including the message in the text box, to the intended recipient for review and response.

These actions are performed sequentially and focus on completing the contact form by entering a message and submitting it.

# Playwright action
[
  {
    "action_uid": "link_Contact Us",
    "idx": 0,
    "action_repr": "frame.clickget_by_role(\"link\", name=\"Contact Us\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/"
    }
  },
  {
    "action_uid": "label_What\u2019s on your mind?",
    "idx": 1,
    "action_repr": "frame.clickget_by_label(\"What\u2019s on your mind?\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/contact/"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/contact/"
    }
  },
  {
    "action_uid": "button_Submit",
    "idx": 2,
    "action_repr": "frame.clickget_by_role(\"button\", name=\"Submit\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/contact/index/"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/contact/index/"
    }
  }
]

# Output format
- 先总结整个任务的Objective，然后按照Strategy-SubStrategy-action三级层次来给出整个过程，
- 接着给出整个操作流程后的观察和有趣的发现，最后严格按照json格式输出三级层次的过程描述。
- 最后的输出json应该是包在```{json}```之间，最底层动作需要包含描述、对应的playwright动作指令顺序编号，以及具体指令内容。

# Example
### Complete User Operation Description to Display Labeled Issues in kkroening/ffmpeg-python

**Objective:** Filter and display all issues labeled as "question" in the kkroening/ffmpeg-python repository.

---

#### **Strategy 1: Navigate to the Repository**
**Low-Level Action Sequence:**
1. **Search for the user "kkroening"**
   - Click the global search bar (placeholder: "Search GitLab").
   - Type "kkroening" and press `Enter`.
2. **Select the user from results**
   - Click the "Users" tab in search results.
   - Click on "Karl Kroening @kkroening" in the user list.
3. **Access the repository**
   - Navigate to the "Personal projects" section.
   - Click on the "ffmpeg-python" project.

---

#### **Strategy 2: Filter Issues by Label**
**Low-Level Action Sequence:**
1. **Open the Issues tab**
   - Scroll to the left sidebar menu.
   - Click the "Issues" tab (displaying the count, e.g., "Issues 402").
2. **Apply label filtering**
   - Click the search/filter bar in the issues list.
   - Select the "Label" dropdown from the filter options.
   - Type or select "question" from the label dropdown.
   - Click the search/apply button to confirm the filter.

---

#### **Final Oberservation**
The issues list will refresh to show only issues with the "question" label. The URL will reflect the filter:
`.../ffmpeg-python/-/issues/?label_name[]=question`.

---

### Key Observations from Playwright Trace
- The final URL after filtering:
  `http://ec2-3-135-39-80.../ffmpeg-python/-/issues/?label_name%5B%5D=question`
  confirms the "question" label filter is applied.
- Critical interactions include selecting the "Label" dropdown and explicitly choosing "question" to refine results.

### Final output
```json
[{
  "strategy" : "Navigate to the Repository",
  "substrategies": [
    {
      "substrategy": "Search for the user \"kkroening\"",
      "actions" : [
        {
          "description": "Click the global search bar (placeholder: \"Search GitLab\"). ",
          "playwright_idx" : 18,
          "playwright_instruction" : "frame.pressget_by_placeholder(\"Search GitLab\")Enter"
        }
      ]
    },
    {
      "substrategy": "Select the user from results",
      "actions" : [
      ]
    }
  ]
},
{
  "strategy" : "Filter Issues by Label",
  "substrategies" : [
  ]
}]
```