HAL9000
e9bfeca0bc
Extract nodes and edges from the route block as top-level keys in
graph_descriptor within _extract_v3_actor() in config.py. The CLI
layer reads graph_descriptor.get("nodes") / .get("edges") directly,
so those keys must be present at the top level — not nested under route.
Reverts the incorrect CLI-layer workaround (drilling into route) that
broke existing tests relying on flat graph_descriptor structures.
Also fixes two regressions introduced by prior attempts:
- Restored key/value and filter/value table headers in the ACMS
index_data_model_and_traversal feature file
- Reverted the ACMS step name from "the count should be" back to
"idx the index count should be" to eliminate the ambiguous step
conflict with security_audit_steps.py
Adds @tdd_issue @tdd_issue_10860 BDD regression scenarios verifying
that a v3 type:graph actor YAML with route.nodes and route.edges
produces a graph_descriptor with correct top-level node/edge counts.
ISSUES CLOSED: #10860
18 lines
964 B
Gherkin
18 lines
964 B
Gherkin
@tdd_issue @tdd_issue_10860
|
|
Feature: Actor graph_descriptor exposes nodes and edges from route block
|
|
As a developer using graph actors
|
|
I want nodes and edges from the route block to appear as top-level keys in graph_descriptor
|
|
So that 'agents actor add' correctly reports node and edge counts
|
|
|
|
Scenario: v3 graph actor with nodes and edges in route reports correct counts
|
|
Given a v3 graph actor blob with a route containing 2 nodes and 1 edge
|
|
When I parse the actor configuration from the v3 blob
|
|
Then the parsed graph_descriptor node count should be 2
|
|
And the parsed graph_descriptor edge count should be 1
|
|
|
|
Scenario: v3 graph actor route with no nodes or edges defaults to empty lists
|
|
Given a v3 graph actor blob with a route containing no nodes or edges
|
|
When I parse the actor configuration from the v3 blob
|
|
Then the parsed graph_descriptor node count should be 0
|
|
And the parsed graph_descriptor edge count should be 0
|