Feature: Context manager coverage
  As a maintainer
  I want context manager edge cases covered
  So reactive context persistence remains reliable

  @coverage
  Scenario: Load stored context JSON files
    Given a context manager storage directory with valid JSON files
    When I initialize the context manager from that directory
    Then the stored context data should be loaded

  @coverage
  Scenario: Ignore invalid JSON files for context storage
    Given a context manager storage directory with invalid JSON files
    When I initialize the context manager from that directory
    Then invalid context files should load as empty defaults

  @coverage
  Scenario: Use default home context path and delete
    Given a temporary home directory for the context manager
    When I initialize the context manager without a context directory
    Then the context manager should use the default home context path
    And deleting the context should remove the directory

  @coverage
  Scenario: Update state and metadata and report existence
    Given a context manager for state and metadata updates
    When I update state and metadata in the context manager
    Then the context manager should return the updated values
    And the context should report it exists on disk

  @coverage
  Scenario: Return last messages and clear context
    Given a context manager with stored messages
    When I request the last message and clear the context
    Then the last message should be returned and the context reset

  @coverage
  Scenario: Export and import a context snapshot
    Given a context manager with exportable data
    When I export and import the context
    Then the imported context should match the exported data