Two notification spammers on the chroot Sovereign Console that produce
noise on every /apps + /app/<name> visit:
D17 — "Deployment id in the URL is malformed":
AppsPage.tsx fires on isDeploymentID(rawDeploymentId)=false. On the
chroot, useResolvedDeploymentId resolves to /api/v1/sovereign/self
which returns the synthesized canonical id `sovereign-<fqdn>` (26
chars, not hex). The notification claims that path-segment is
invalid even though there is no URL segment — the resolution path
is in-process. Suppress on DETECTED_MODE.mode === 'sovereign'.
D18 — "Per-component install monitoring is unavailable":
Fires on state.phase1WatchSkipped. On the chroot, phase1WatchSkipped
is a MOTHERSHIP-only concept (mother's observer pod failed to fetch
the new cluster's kubeconfig). The Sovereign-side catalyst-api runs
IN the cluster it's reporting on — has the in-cluster ServiceAccount
+ bundled sovereignDynamicClient + informer cache watching HelmReleases
natively. Firing this here tells operator to drop to kubectl when
the data is on the page. Suppress on chroot.
Caught on t129 (6cddff7ef4432bdc, 2026-05-16) — DoD D17 + D18.
Co-authored-by: hatiyildiz <hatice.yildiz@openova.io>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2b3888eed5