Feature: CLI lifecycle Robot alignment
  As a developer
  I want a Behave scenario mirroring the Robot E2E lifecycle flow
  So that unit and integration test expectations stay aligned

  Background:
    Given a robot alignment CLI runner
    And a robot alignment mocked lifecycle service

  Scenario: Full lifecycle action to apply with changeset verification
    Given a robot alignment action "local/lifecycle-action" is created via config
    When I run robot alignment plan use "local/lifecycle-action" on project "proj-a"
    Then the robot alignment plan use should succeed
    When I run robot alignment plan execute for the plan
    Then the robot alignment plan execute should succeed
    And the robot alignment changeset should have 1 entry with operation "create"
    When I run robot alignment plan apply for the plan
    Then the robot alignment plan apply should succeed
    And the robot alignment changeset summary should have total 2

  Scenario: Invalid arg format rejected via CLI
    Given a robot alignment action "local/lifecycle-action" exists
    When I run robot alignment plan use with invalid arg "bad_arg_no_equals"
    Then the robot alignment CLI should reject the invalid arg format

  Scenario: Missing action returns error via CLI
    When I run robot alignment plan use for nonexistent action "local/nonexistent"
    Then the robot alignment CLI should report action not found
