@session
# Regression tests for bug #570 — verifies that the DI container fix for
# session create command works correctly.  The @tdd_expected_fail tags have
# been removed now that the fix has landed.
Feature: Session create command resolves DI container wiring
  As a developer using the agents CLI
  I want "agents session create" to work after a fresh init
  So that I can create interactive sessions without a DI container error

  Background:
    Given a session-create-error CLI runner using the real DI path

  @tdd_issue @tdd_issue_570

  Scenario: Session create produces a new session
    When I invoke session-create-error create with no arguments
    Then the session-create-error command should exit successfully
    And the session-create-error output should contain "id:"

  @tdd_issue @tdd_issue_570

  Scenario: Created session persists and can be retrieved
    When I invoke session-create-error create with no arguments
    Then the session-create-error command should exit successfully
    When I invoke session-create-error list to verify persistence
    Then the session-create-error list should show at least one session

  @tdd_issue @tdd_issue_570

  Scenario: Session create with custom actor succeeds
    When I invoke session-create-error create with actor "openai/gpt-4"
    Then the session-create-error command should exit successfully
    And the session-create-error output should contain "openai/gpt-4"
    And the session-create-error output should contain "id:"

  @tdd_issue @tdd_issue_570

  Scenario: Session create with arbitrary actor name succeeds
    When I invoke session-create-error create with actor "nonexistent/bogus-actor-999"
    Then the session-create-error command should exit successfully
    And the session-create-error output should contain "nonexistent/bogus-actor-999"
