From 3cd0e7e0eb1ddc3051edb1a36bfec2b1350842bd Mon Sep 17 00:00:00 2001
From: rcourtman <8825017+rcourtman@users.noreply.github.com>
Date: Mon, 5 Oct 2026 02:45:06 +0100
Subject: [PATCH] Restore the vSphere overview incident-table contract note

Re-adds this branch's frontend-primitives note after taking main's file for a clean merge.
---
 .../v6/internal/subsystems/frontend-primitives.md         | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/release-control/v6/internal/subsystems/frontend-primitives.md b/docs/release-control/v6/internal/subsystems/frontend-primitives.md
index b982416db6..13e329be3e 100644
--- a/docs/release-control/v6/internal/subsystems/frontend-primitives.md
+++ b/docs/release-control/v6/internal/subsystems/frontend-primitives.md
@@ -8362,3 +8362,11 @@ regressions preserve their original missing-value and fallback obligations.
 drawer with synthetic APIs in Chromium/WebKit desktop and 390/320-pixel light
 and dark views. This is presentation acceptance, not native backup/QGA safety,
 provider outage attribution, installed recovery or release availability.
+
+### Platform overviews may lead with their own incident table
+
+A platform Overview that leads with its provider's health signals reuses
+that platform's existing incident table rather than a new summary card:
+the vSphere Overview renders `VsphereAlertsTable` with `showToolbar={false}`
+above its hosts table, only when signals exist, matching the TrueNAS
+Overview's health-alert table. Filtering stays on the platform's Health tab.