@tdd_issue @tdd_issue_797 @tdd_issue_4178
Feature: TDD Bug #797 — actor list should not cause a database update

  Bug #797 reports that running ``agents actor list`` on a fresh checkout
  triggers pending-migration prompts and database writes.  The ``list``
  command is read-only from the user's perspective, so it must not call
  ``upsert_actor()`` or any other write operation.

  These scenarios verify that no database writes occur during
  ``actor list``.  The bug has been fixed; these tests serve as
  permanent regression guards.

  Scenario: Actor list does not call upsert_actor for tdd-actor-list-no-db-update
    Given a mock actor service with a fake provider registry for tdd-actor-list-no-db-update
    When the actor list command is invoked for tdd-actor-list-no-db-update
    Then upsert_actor should not have been called for tdd-actor-list-no-db-update

  Scenario: Actor list does not call set_default_actor for tdd-actor-list-no-db-update
    Given a mock actor service with a fake provider registry for tdd-actor-list-no-db-update
    When the actor list command is invoked for tdd-actor-list-no-db-update
    Then set_default_actor should not have been called for tdd-actor-list-no-db-update
