@tdd_expected_fail @tdd_issue @tdd_issue_1039
Feature: TDD Bug #1039 — Missing validations/unit-tests.yaml configuration
  As a developer
  I want to verify that the validation configuration file referenced by the
  specification exists and conforms to the expected schema
  So that the bug is captured and will be caught by a regression test

  The specification (Workflow Examples, Example 1, Step 1) references a
  validation configuration file ``validations/unit-tests.yaml`` that is
  used with the ``agents validation add`` command to register a required
  validation named ``local/unit-tests``.  According to the specification
  output, this validation should run ``pytest tests/``, have description
  "Unit tests", mode "required", and timeout 300s (default).

  However, the file ``validations/unit-tests.yaml`` does not exist anywhere
  in the project.  The ``examples/validations/`` directory contains only
  ``required-validation.yaml`` and ``wrapped-validation.yaml``, but not
  the ``unit-tests.yaml`` referenced by the specification.

  This test captures bug #1039 and uses ``@tdd_expected_fail`` until the
  fix is merged.  Once the file is created, the tag will be removed and
  the test will run normally as a regression guard.

  Scenario: The unit-tests.yaml validation config file exists in the project
    Given the project root directory is known for validation yaml test
    When I check for the validation config file "examples/validations/unit-tests.yaml"
    Then the validation config file should exist

  Scenario: The unit-tests.yaml config loads as valid YAML with expected name
    Given the project root directory is known for validation yaml test
    When I load the validation config file "examples/validations/unit-tests.yaml"
    Then the validation config should have name "local/unit-tests"

  Scenario: The unit-tests.yaml config defines a required validation mode
    Given the project root directory is known for validation yaml test
    When I load the validation config file "examples/validations/unit-tests.yaml"
    Then the validation config should have mode "required"

  Scenario: The unit-tests.yaml config includes a description
    Given the project root directory is known for validation yaml test
    When I load the validation config file "examples/validations/unit-tests.yaml"
    Then the validation config should have a non-empty description
