Resolve "ILT - Lab Update - GitLab DAP - Minor Lab Updates"

1. The session should automatically open in the right panel. You can also navigate to **Automate > Sessions** and find your session.

1. Click the **Details** tab and wait for the session status to change to **Finished**.

1. Click the **Activity** tab and confirm that the activity feed reports a summary of the actions taken to complete the task.

>**Details vs. Activity:** The Details tab shows overall session status and high-level metadata like start time and duration. The Activity tab shows the step-by-step log of every action the agent took, such as which tools it called, what it read, what it created, and in what order. Use Details to confirm completion and Activity to understand what actually happened.

1. Click the session to open it and confirm that the activity feed reports a summary of the actions taken to complete the task.

### Task B.3: Review the Merge Request

    >**Note:** You can also navigate to **Automate > Sessions**, locate the session for the Swag Shop Issue Reviewer, and open it.

1. Click the **Activity** tab and observe the steps executing in real time: issue fetch, data analysis, and comment generation.

1. Click the **Details** tab and wait for the session status to change to **Finished**.

1. Return to the issue and review the comment posted by the flow.

The comment will contain a completeness score out of 6, a "Looks good" section listing criteria that are met, a "Needs attention" section with specific suggestions for each missing criterion, and optionally a "Suggested acceptance criteria" section. The score will vary depending on which issue you chose.

   cursor.execute(secure_query, (search_param, search_param))

   ```

1. Select the **Pipelines** tab. You may notice the pipeline status shows as skipped. This is expected. The commit created by Resolve with AI includes **[ci skip]** by default. A real pipeline will run after the next commit to this branch, which you will make in Task C.

1. Select the **Pipelines** tab. Once the pipeline has finished, open the pipeline details by selecting the **Passed** status. Select the **Security** tab, and check that the **Improper neutralization of special elements used in an SQL Command ('SQL Injection')** for line 214 of `app.py` is no longer reported. 

1. Navigate back to the remediation merge request that you just had open.

### Expected output: Task B

### Task C.1: Introduce the Dependency Error

1. Note the source branch name shown in the remediation merge request header. It will be like `remediate/improper-neutral...`. You will need this in the next step.

1. Note the source branch name shown in the remediation merge request header. It will start with something similar to `duo/fix/...`. You will need this in the next step.

1. In the left sidebar, navigate to **Code > Repository**.