@tdd_issue @tdd_issue_992
Feature: TDD Bug #992 — get_container() caches failed audit subscriber initialization
  As a long-lived process using the shared DI container
  I want get_container() to retry audit subscriber initialization after an initial failure
  So that audit subscriptions are eventually registered once prerequisites become available

  This feature captures bug #992. Previously, get_container() eagerly called
  audit_event_subscriber() only during first container creation. If that first call
  failed, the exception was logged and swallowed, but the global _container remained set.
  Subsequent get_container() calls returned the cached container without retrying the
  subscriber initialization.

  Originally tagged @tdd_expected_fail while the bug was unfixed (see TDD issue
  #1096). The @tdd_expected_fail tag was removed when the fix for #992 was
  implemented so this now runs as a normal regression test.

  Scenario: Bug #992 — get_container retries audit subscriber initialization after first failure
    Given g992- a container whose audit subscriber init fails once then succeeds
    When g992- I call get_container twice
    Then g992- audit subscriber init should have been attempted twice
