Feature: Config Parser List-Format Route Processing and Template Non-Dict Error Handling
  As a developer
  I want list-format routes to parse from/to fields correctly and template parse errors to raise ValueError for non-dict restored configs
  So that route definitions in list format and template parsing errors are handled correctly
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with list routes using from and to (cpg)
    Then routes and merges should be generated from the list format (cpg)

  Scenario: Parse list-format routes with agent targets
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with list routes targeting agents (cpg)
    Then agent-targeted routes should contain map operators (cpg)

  Scenario: Parse list-format routes with multiple continuation points
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with multiple continuation routes (cpg)
    Then routes should connect via merge sources and cover route_map logic (cpg)

  Scenario: Parse routes without from/to fields
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with list routes lacking from_to fields (cpg)
    Then routes should be stored with index-based names (cpg)

  Scenario: Parse routes where from is an agent without feeding route
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with an orphan agent from source (cpg)
    Then the orphan agent merge source should fallback to agent name (cpg)

  Scenario: Parse routes where from is a non-agent non-input name
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with a non-agent non-input from source (cpg)
    Then the merge source should be the raw from name (cpg)

  Scenario: Template instance routes in list format
    Given a ReactiveConfigParser instance (cpg)
    When I call _build_reactive_config with template instance in list routes (cpg)
    Then template instance route should be stored with template_config (cpg)

  Scenario: Non-dict restored config raises ValueError
    Given a ReactiveConfigParser instance (cpg)
    When parse_files receives a template file yielding a non-dict result (cpg)
    Then a ValueError should be raised for non-dictionary config (cpg)