generated from coulomb/repo-seed
feat: resolve graph explorer zones from definitions
This commit is contained in:
@@ -95,7 +95,7 @@ summaries, and conflict diagnostics. Covered the core behavior in
|
||||
|
||||
```task
|
||||
id: RAIL-FAB-WP-0022-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "c89d8d53-72a4-4590-a0e5-67b012c3550c"
|
||||
```
|
||||
@@ -114,6 +114,15 @@ The current operator-facing behavior should remain available:
|
||||
Expected result: existing graph explorer tests continue to pass, with new tests
|
||||
showing that the UI obtains zone rectangles from resolved zone instances.
|
||||
|
||||
Result: Refactored the graph explorer overlay to use explicit default zone
|
||||
definitions and a client-side `resolveZoneInstances()` path. Deployment
|
||||
environment zones now resolve through declarative membership rules with
|
||||
`deploymentEnvironment` normalization for `dev` -> `dev-tegwick`,
|
||||
`test`/`staging` -> `test`, `prod` -> `prod`, and ignored `all` values. Access
|
||||
zone overlays are generated as dynamic definitions from visible graph evidence.
|
||||
The overlay keeps the single-zone visible-node assignment behavior while
|
||||
preserving edge evidence in zone details.
|
||||
|
||||
## Task 4: Add Zone Diagnostics To The Explorer
|
||||
|
||||
```task
|
||||
|
||||
Reference in New Issue
Block a user