@tdd_issue @tdd_issue_980
Feature: TDD Issue #980 — skill add cross-process persistence
  As a developer
  I want to verify that `agents skill add --config <file>` persists
  skills across separate CLI process invocations
  So that the bug is captured and will be caught by a regression test

  Bug #980 reports that skills registered via `agents skill add` in one
  CLI process are not visible when `agents skill list` is run in a
  separate CLI process.  Existing persistence tests pass because they
  verify round-trip within the same Python process (creating two
  SkillService instances sharing the same in-memory database).

  This TDD test captures the regression by using real subprocess
  invocations — the skill is added via one CLI invocation and listed
  via an independent CLI invocation, both sharing the same on-disk
  SQLite database.  Originally tagged @tdd_expected_fail while the bug was unfixed;
  tag removed after fix in #980.

  @tdd_issue @tdd_issue_4287
  Scenario: skill add in one process is visible to skill list in another
    Given a cross-process skill persistence environment
    When I add a skill via a CLI subprocess
    And I list skills via a separate CLI subprocess
    Then the cross-process skill list should contain the added skill

  @tdd_issue @tdd_issue_4287
  Scenario: skill add persists config path across processes
    Given a cross-process skill persistence environment
    When I add a skill via a CLI subprocess
    And I show the skill via a separate CLI subprocess
    Then the cross-process skill show output should contain the skill name
