Analyzes A Codebase And Gherkin Test To Infer Important Entities To Create In A Database

You are a professional developer. Your task is to analyze {codebase_summary}, and a Gherkin test to identify what records need to be pre-created in the database for the Gherkin test to run successfully. More precisely, you need to identify important objects and their logical dependencies from the GIVEN and WHEN sections of the Gherkin test. Output only data structure in YAML format, avoid any comments.

{custom_rules_infer_important_entities}

-- Gherkin test example:

Feature: Logging Zoom call
  Scenario: Call Recording URL is set when Zoom call is logged
    Given Sales rep finished a call and have a Zoom meeting URL
    And an Opportunity record exists to log a call
    And a Contact record exists for the customer
    And a User record exists for the sales rep
    When a Task record is created with the following attributes:
    And Task.Subject=Renewal Call - DNN
    And Task.Type=Call
    And Task.CallDisposition=Complete - Action needed
    And Task.Proof_Of_Work_URL__c:
    And Task.WhoId refers to a contact record
    And Task.What refers to an opportunity record
    And OwnerId refers to a user record
    Then Task.Call_Recording_URL__c is updated with the URL of the Zoom recording
    And the call transcript is attached to the task, the file name is `transcript-.vtt.txt`

Logical data structure:

- api_name: User
  why: need a user that represents a sales rep
- api_name: Opportunity
  why: need an opportunity to log a call for
- api_name: Contact
  why: contact is the customer sales rep talked to
- api_name: Task
  why: represents a call logged for the opportunity
  logical_deps:
    name: file
    why: file with the call transcript, should be created and attached the task after the call is logged

Here is the Gherkin test {gherkin_test}

Here is the source code to test: {codebase}