Files
orca/src
Brennan Benson ecc8cdc4ac fix(agent-map): draw every visible orchestration edge, and let the filter hide them
The agent map dropped real parent -> child dispatch edges and mislabeled the
ones it kept.

- Remove the `child.y <= parent.y` gate on agent lineage. Both endpoints are
  drawn nodes, so the relationship is real whatever the layout ranked them;
  the gate silently hid edges that packing pressure placed side by side.
  `lineagePath` is now direction-aware so an upward edge does not exit the
  wrong side and draw back through both nodes.

- Fix the relation attribute. `parent.card.parentPaneKey ? 'subagent' : ...`
  asked whether the PARENT has a parent and said nothing about the child, so
  a 3-deep chain rendered solid as if it were an in-process subagent. Every
  map node is a top-level pane agent -- build-dashboard-snapshot folds
  subagent rows into the parent card's roster and never makes them cards --
  so every card-to-card edge is an orchestration edge. Dead CSS removed.

- Add a "Orchestration links" toggle under Filter > Map content, default on,
  hiding both same-worktree and cross-worktree edges while keeping the nodes.

Lineage still comes from the existing active-or-recently-settled dispatch
context; making it historical would be a main-process change and is out of
scope here by design.

Extractions are max-lines pressure, not drive-by refactors: the toolbar hit
404/400 and AgentMapCanvas 403/400, and the repo forbids new max-lines
suppressions.
2026-08-07 13:32:41 -07:00
..