# 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
Tell me the number of followers of the contributor who has the most commits to branch main

# Annotation description
## Part 1
### Step-by-Step Actions:

1. **Action:** I click on the search bar at the top of the page.
   - **Page Changes:** The search bar becomes active, and a dropdown menu appears below it, suggesting search options related to the current context ("master Switch branch/tag History Commits to master Excluding merge commits. Limit!").
   - **Possible Purpose:** The likely intent is to initiate a search or navigate to a specific section or feature within the GitLab interface by using the search functionality.

2. **Action:** I hover over the "Switch branch/tag" dropdown menu.
   - **Page Changes:** The dropdown menu expands, displaying available branches and tags, with "master" being checked.
   - **Possible Purpose:** The purpose is to review or select a different branch or tag for viewing its commit history or related details.

3. **Action:** I click on the "master" option in the "Switch branch/tag" dropdown menu.
   - **Page Changes:** The page remains focused on the "master" branch, as it was already selected. No significant changes occur since "master" was already active.
   - **Possible Purpose:** This action might be intended to confirm the selection of the "master" branch or to ensure that the correct branch is being viewed.

4. **Action:** I scroll down slightly on the page.
   - **Page Changes:** The view shifts downward, revealing more content such as individual contributor sections with their commit histories.
   - **Possible Purpose:** The intent is to inspect additional information about contributors and their commit activities on the "master" branch.

5. **Action:** I click on the highlighted section for "Henning Leutz" under the "Contributors" list.
   - **Page Changes:** The focus shifts to Henning Leutz's commit details, showing a detailed graph of his commits over time.
   - **Possible Purpose:** The purpose is to examine the specific contributions made by Henning Leutz, including the number of commits and their distribution over different months.

6. **Action:** I move the cursor over the commit graph for "Henning Leutz."
   - **Page Changes:** A tooltip appears, providing specific details about the commits on certain dates (e.g., "2020-10-02" with 5 commits).
   - **Possible Purpose:** The intent is to get precise information about the number of commits made on particular dates by Henning Leutz.

7. **Action:** I click on the "locator" text box at the bottom of the screen.
   - **Page Changes:** The locator text box becomes active, allowing input for navigating or highlighting specific elements on the page.
   - **Possible Purpose:** The purpose is to use the locator tool to find or highlight specific UI elements or sections on the page for further inspection or interaction.

### Summary:
In this video segment, I interact with various elements on a GitLab project page, focusing on the "master" branch and the contributions of specific users, particularly Henning Leutz. My actions include searching, selecting branches, reviewing commit histories, and using a locator tool, all aimed at navigating and analyzing the project's commit data efficiently.

---

## Part 2
### Step-by-Step Actions in the Video Segment

#### 1. **Initial State**
- **Action:** The video begins with a view of a GitLab project page, specifically on the "Contributors" section under the "Repository" tab.
- **Page Changes:** The page displays a graph titled "Commits to master," showing commit activity over time. Below the graph, there are individual contributor sections for "Henning Leutz" and "Jérémie Zarca," each with their respective commit histories and email addresses.
- **Possible Purpose:** The initial state sets the context for reviewing commit contributions within the project.

#### 2. **Hovering Over Contributor Name**
- **Action:** I hover over the name "Henning Leutz."
- **Page Changes:** A tooltip appears, displaying the text "get_by_text('Henning Leutz')".
- **Possible Purpose:** Hovering over the name likely aims to reveal additional information or interactive options associated with the contributor's name. The tooltip suggests that this action might be part of a demonstration or tutorial on how to interact with specific elements on the page using a method like `get_by_text`.

#### 3. **Hovering Over Contributor Email**
- **Action:** I move the cursor to hover over the email address next to "Henning Leutz" (leutz@pcsg.de).
- **Page Changes:** Another tooltip appears, this time displaying the text "get_by_text('51 commits (leutz@pcsg.de)')".
- **Possible Purpose:** Similar to the previous action, hovering over the email address is intended to highlight or demonstrate how to interact with or identify specific textual elements on the page, possibly for automation or testing purposes.

#### 4. **Hovering Over Contributor Section Title**
- **Action:** I then hover over the section title "Henning Leutz" again, but this time it seems more deliberate, as if to emphasize the element.
- **Page Changes:** The same tooltip "get_by_text('Henning Leutz')" reappears.
- **Possible Purpose:** This repeated action reinforces the focus on the contributor's name, perhaps to ensure clarity or to illustrate a point about element identification in a user interface.

#### 5. **Final State**
- **Action:** The video segment ends with the cursor still hovering over the "Henning Leutz" section title.
- **Page Changes:** The tooltip remains visible, maintaining the focus on the highlighted element.
- **Possible Purpose:** The final state serves to conclude the demonstration or explanation related to interacting with the contributor's name element.

### Summary
In this video segment, the primary actions involve hovering over specific elements (the contributor's name and email) to trigger tooltips that display methods for identifying these elements, likely for educational or demonstrative purposes related to UI interaction or testing. There are no clicks or other interactions beyond hovering, and the page content remains static except for the appearance of tooltips.

# Playwright action
[
  {
    "action_uid": "branches-select",
    "idx": 0,
    "action_repr": "frame.clickget_by_test_id(\"branches-select\")",
    "before": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    },
    "after": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    }
  },
  {
    "action_uid": "link_master",
    "idx": 1,
    "action_repr": "frame.clickget_by_role(\"link\", name=\"master\")",
    "before": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    },
    "after": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    }
  },
  {
    "action_uid": "heading_Henning Leutz",
    "idx": 12,
    "action_repr": "frame.clickget_by_role(\"heading\", name=\"Henning Leutz\")",
    "before": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    },
    "after": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    }
  },
  {
    "action_uid": "text_Henning Leutz 51 commits (leutz@pcsg.de) Commits0123456MarMayJulSepNovMarMayJulS",
    "idx": 5,
    "action_repr": "frame.clickget_by_text(\"Henning Leutz 51 commits (leutz@pcsg.de) Commits0123456MarMayJulSepNovMarMayJulS\")",
    "before": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    },
    "after": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    }
  },
  {
    "action_uid": "action_13",
    "idx": 13,
    "action_repr": "frame.clickget_by_placeholder(\"Search GitLab\")",
    "before": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    },
    "after": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    }
  },
  {
    "action_uid": "label_dehenne",
    "idx": 14,
    "action_repr": "frame.clickget_by_label(\"dehenne\")",
    "before": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    },
    "after": {
      "url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:8023/dehenne/awesome-visibility/-/graphs/master"
    }
  }
]

# 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" : [
  ]
}]
```