object-map

Fix missing Kubernetes object nodes and links by aligning backend snapshot collection, identities, and edges with frontend model, layout, and rendering behavior. Validate intended nodes and relationship edges in snapshot tests first, then update the frontend renderer to match the corrected payload.

Openable references fail when GVK, namespace, or name identity is incomplete in the backend snapshot. Correct the reference completeness by ensuring openable refs include cluster, GVK, and namespace/name identity, then verify openable behavior with targeted Go and frontend test coverage.

Add new Kubernetes kinds by updating backend typed collections, permission checks, and kind allowlists, then align the frontend payload shapes, visible state, and legend copy. Apply targeted Go and Vitest test runs to prove the new nodes, edges, and rendering behavior are correct.

Test Kubernetes object-map graph accuracy by running focused Go and Vitest tests to prove nodes, edges, and rendering behavior match expectations. Validate backend snapshot shape first, then update frontend model and renderer tests to confirm the UI reflects the corrected backend truth.

Frontend state aligns with backend Kubernetes snapshot data by updating kind allowlists, payload shapes, filter/collapse state, and renderer behavior to match the backend truth. Ensure edge semantics and reference completeness are verified through targeted testing across both layers.

Debugging incomplete Kubernetes object-map snapshots requires updates across both backend snapshot and registration code, and frontend object-map types and renderer logic. You must align frontend layout and rendering behavior with the corrected backend payload to achieve accurate graph visualization.