@skyhook-io/k8s-ui 1.12.0 → 1.13.3

package/src/components/resources/renderers/PolicyCoverageSection.tsx

@@ -0,0 +1,939 @@
+import { ShieldAlert, ShieldCheck, ShieldQuestion } from 'lucide-react'
+import { clsx } from 'clsx'
+import { useState } from 'react'
+import { ChevronDown, ChevronRight } from 'lucide-react'
+import { Section } from '../../ui/drawer-components'
+import { SEVERITY_BADGE } from '../../../utils/badge-colors'
+import { isForbiddenError } from '../../../types/fetch-error'
+import { LookupFailureNote } from './LookupFailureNote'
+import {
+  getKyvernoPolicyFamily,
+  getKyvernoEnforcementPosture,
+  getKyvernoResourceRules,
+  getKyvernoEffectiveFailurePolicy,
+  type KyvernoPolicyFamily,
+} from '../resource-utils-kyverno-modern'
+import { getKyvernoPolicyAction } from '../resource-utils-kyverno'
+import type {
+  PolicyCoverageResponse,
+  PolicyCoverageRule,
+  PolicyCoverageSubject,
+  PolicyResourceCounts,
+} from '../../../types/policy'
+
+interface PolicyCoverageSectionProps {
+  /** The policy resource itself — enforcement consequence is a property of the
+   *  policy's spec, not of the report data. */
+  resource: any
+  data: PolicyCoverageResponse | null
+  loading?: boolean
+  error?: Error | null
+  onSelectSubject?: (subject: PolicyCoverageSubject) => void
+  /**
+   * Re-fetch with a higher subject bound. Without it a capped rule ends at a
+   * sentence naming resources the reader cannot open. Hosts that cannot
+   * re-fetch omit it and keep the sentence.
+   */
+  onLoadMore?: () => void
+  loadingMore?: boolean
+}
+
+const TITLE = 'Resources'
+
+// Matches RELATIONSHIP_TRUNCATE_LIMIT in drawer-components: the point at which
+// a list of related resources folds behind "Show all N".
+const SUBJECT_FOLD_LIMIT = 10
+
+interface OutcomeWords {
+  /** Sentence form, e.g. "13 not mutated". */
+  bad: string
+  good: string
+  /** Badge form, e.g. "Not mutated". */
+  badBadge: string
+  goodBadge: string
+}
+
+/**
+ * Kyverno writes `result: fail` for every family and does not mean the same
+ * thing by it: a mutating policy's fail carries "mutation is not applied".
+ * Validating keeps the upstream words verbatim so the screen matches
+ * `kubectl get policyreport`.
+ */
+function outcomeWords(family: KyvernoPolicyFamily | undefined): OutcomeWords {
+  switch (family) {
+    case 'mutating':
+      return { bad: 'not mutated', good: 'mutated', badBadge: 'Not mutated', goodBadge: 'Mutated' }
+    case 'generating':
+      // The subject of a generate result is the TRIGGER, not the object the
+      // rule produced — Kyverno records the resource that caused generation and
+      // never names the target here. "Generated" on that row states the exact
+      // opposite of what happened: it reads as "this ConfigMap was generated"
+      // about the ConfigMap that caused a NetworkPolicy to be generated. The
+      // wording has to keep the subject in its real role.
+      return {
+        bad: 'failed to generate',
+        good: 'triggered generation',
+        badBadge: 'Generate failed',
+        goodBadge: 'Triggered',
+      }
+    default:
+      return { bad: 'failing', good: 'passing', badBadge: 'Fail', goodBadge: 'Pass' }
+  }
+}
+
+function resultTone(result: string, words: OutcomeWords): { badge: string; label: string } {
+  switch (result.toLowerCase()) {
+    case 'fail':
+      return { badge: SEVERITY_BADGE.error, label: words.badBadge }
+    case 'pass':
+      return { badge: SEVERITY_BADGE.success, label: words.goodBadge }
+    // warn / error / skip mean the same thing whatever the family: the rule
+    // flagged it, the engine broke, or the rule declined to look.
+    case 'warn':
+      return { badge: SEVERITY_BADGE.warning, label: 'Warn' }
+    case 'error':
+      return { badge: SEVERITY_BADGE.alert, label: 'Error' }
+    case 'skip':
+      return { badge: SEVERITY_BADGE.neutral, label: 'Skipped' }
+    default:
+      return { badge: SEVERITY_BADGE.neutral, label: result }
+  }
+}
+
+/**
+ * A CREATE-only policy never rejects a change to something that already exists,
+ * so resources failing it are grandfathered until recreated. Verified on 1.18.2:
+ * annotating a failing ConfigMap is admitted, creating an identical one is not.
+ */
+function matchesUpdates(resource: any): boolean {
+  if (isLegacyKyvernoPolicy(resource)) return legacyMatchesUpdates(resource)
+  const rules = getKyvernoResourceRules(resource)
+  if (rules.length === 0) return true
+  return rules.some((r) => r.operations.length === 0 || r.operations.includes('UPDATE'))
+}
+
+/**
+ * Legacy operations live at `spec.rules[].match.any[].resources.operations`, not
+ * `spec.matchConstraints`; reading the modern shape finds no rules and defaults
+ * to "matches updates", stating the consequence backwards. Unset means both.
+ */
+function legacyMatchesUpdates(resource: any): boolean {
+  return legacyRuleUpdateMatches(resource).some(Boolean)
+}
+
+/** One answer per rule, in `spec.rules` order. */
+function legacyRuleUpdateMatches(resource: any): boolean[] {
+  const rules: any[] = resource?.spec?.rules ?? []
+  if (rules.length === 0) return [true]
+  return rules.map((rule: any) => {
+    const blocks = [
+      ...(rule?.match?.any ?? []),
+      ...(rule?.match?.all ?? []),
+      ...(rule?.match?.resources ? [rule.match] : []),
+    ]
+    if (blocks.length === 0) return true
+    return blocks.some((b: any) => {
+      const ops = b?.resources?.operations
+      return !Array.isArray(ops) || ops.length === 0 || ops.includes('UPDATE')
+    })
+  })
+}
+
+/** The consequence sentence is one claim over the whole failing count, so rules
+ *  that disagree about updates make either answer false for some of them. */
+function legacyOperationsAgree(resource: any): boolean {
+  const answers = legacyRuleUpdateMatches(resource)
+  return answers.every((a) => a === answers[0])
+}
+
+/** failureAction is per rule, and the sentence cannot say which rule a failure
+ *  came from — so rules disagreeing on Audit vs Enforce make it a false promise. */
+function legacyActionsAgree(resource: any): boolean {
+  const spec = resource?.spec?.validationFailureAction
+  const answers = (resource?.spec?.rules ?? [])
+    .filter((rule: any) => rule?.validate || rule?.verifyImages)
+    .map((rule: any) => {
+      const declared = [
+        rule?.validate?.failureAction,
+        ...(Array.isArray(rule?.verifyImages)
+          ? rule.verifyImages.map((v: any) => v?.failureAction)
+          : []),
+      ].filter(Boolean)
+      const effective = declared.length > 0 ? declared : [spec]
+      return effective.includes('Enforce')
+    })
+  return answers.every((a: boolean) => a === answers[0])
+}
+
+/**
+ * `results[].rule` is not always an authored rule name: the CEL family writes an
+ * empty one, and the literal `evaluation` when the engine failed (1.18.2 emits
+ * `rule: 'evaluation'` with `result: error`). A name is shown only when the
+ * policy declares it; otherwise the bucket is described by what it holds.
+ */
+function ruleHeading(resource: any, rule: PolicyCoverageRule): string | undefined {
+  const name = rule.rule
+  if (!name) return undefined
+  const declared: string[] = (resource?.spec?.rules ?? [])
+    .map((r: any) => r?.name)
+    .filter(Boolean)
+  if (declared.includes(name)) return name
+  // Not a rule of this policy. If everything in it is an engine error, say so;
+  // anything else keeps the raw name rather than inventing a description.
+  const c = rule.counts
+  if (c.error > 0 && c.fail === 0 && c.pass === 0 && c.warn === 0 && c.skip === 0) {
+    return 'Engine errors'
+  }
+  return name
+}
+
+/** A legacy kyverno.io Policy / ClusterPolicy, as opposed to the modern CEL family. */
+function isLegacyKyvernoPolicy(resource: any): boolean {
+  return typeof resource?.apiVersion === 'string' && resource.apiVersion.startsWith('kyverno.io/')
+}
+
+/** The family a single legacy rule belongs to, read from which block it carries. */
+function legacyRuleFamily(rule: any): KyvernoPolicyFamily | undefined {
+  if (rule?.generate) return 'generating'
+  if (rule?.mutate) return 'mutating'
+  if (rule?.verifyImages) return 'imageValidating'
+  if (rule?.validate) return 'validating'
+  return undefined
+}
+
+/**
+ * The modern API puts the family in the kind; a legacy ClusterPolicy carries any
+ * mix of rules, so reading the kind alone falls back to Pass/Fail and calls a
+ * generate rule "failed". Without a rule name, only a policy whose rules agree
+ * has an answer.
+ */
+function policyFamilyFor(
+  resource: any,
+  ruleName?: string,
+): KyvernoPolicyFamily | undefined {
+  if (!isLegacyKyvernoPolicy(resource)) return getKyvernoPolicyFamily(resource?.kind)
+  const rules: any[] = resource?.spec?.rules ?? []
+  if (rules.length === 0) return undefined
+  if (ruleName) {
+    // Autogen rules carry the source rule's block, but Kyverno names them
+    // `autogen-<rule>` (and `autogen-cronjob-<rule>`), so the report's rule
+    // name does not match `spec.rules[].name` verbatim.
+    const base = ruleName.replace(/^autogen-(cronjob-)?/, '')
+    const rule = rules.find((r) => r?.name === ruleName) ?? rules.find((r) => r?.name === base)
+    if (rule) return legacyRuleFamily(rule)
+  }
+  const families = rules.map(legacyRuleFamily)
+  const first = families[0]
+  return families.every((f) => f === first) ? first : undefined
+}
+
+/**
+ * The families answer from different fields: legacy carries
+ * `spec.validationFailureAction` (or a per-rule `validate.failureAction`), while
+ * `getKyvernoEnforcementPosture` reads `spec.validationActions`, absent on
+ * legacy — which makes an Enforce policy read as audit-only.
+ */
+function blocksAdmission(resource: any, family: KyvernoPolicyFamily | undefined): boolean {
+  if (isLegacyKyvernoPolicy(resource)) {
+    return getKyvernoPolicyAction(resource) === 'Enforce'
+  }
+  return getKyvernoEnforcementPosture(resource, family).blocks
+}
+
+/**
+ * Whether the consequence sentence can be stated at all.
+ *
+ * A legacy ClusterPolicy can carry validate, mutate and generate rules at once,
+ * so "what enforcing does" has no single answer. Rather than pick one and be
+ * confidently wrong, the sentence is withheld and the counts speak for
+ * themselves.
+ */
+function canStateConsequence(resource: any, family: KyvernoPolicyFamily | undefined): boolean {
+  if (!isLegacyKyvernoPolicy(resource)) {
+    return family === 'validating' || family === 'imageValidating' || family === undefined
+  }
+  const rules: any[] = resource?.spec?.rules ?? []
+  if (rules.length === 0) return false
+  // Every rule has to validate AND agree on whether updates are matched AND on
+  // whether failing is blocking; the sentence is one claim about one failing
+  // count and cannot straddle any of the three.
+  return (
+    rules.every((rule) => !!rule?.validate) &&
+    legacyOperationsAgree(resource) &&
+    legacyActionsAgree(resource)
+  )
+}
+
+/**
+ * Both plausible phrasings are false: admission acts on requests, not on the
+ * resources that already exist, and "their next update is rejected" holds only
+ * when the policy matches UPDATE. Exported so the wording is pinned directly.
+ */
+function enforcementConsequence(
+  failing: number,
+  blocks: boolean,
+  matchesUpdate: boolean,
+): string {
+  // Deliberately kind-neutral. A policy can match ConfigMaps, Secrets or
+  // ClusterRoles as readily as Pods, and none of those "run" — the fact being
+  // stated is that the resource already exists, not that it is executing.
+  const one = failing === 1
+  const exists = one ? '1 resource already exists' : `${failing} resources already exist`
+  const it = one ? 'it' : 'them'
+  const itIs = one ? 'it is' : 'they are'
+
+  if (blocks) {
+    return matchesUpdate
+      ? `${exists}, so this policy does not affect ${it} today. The next update to ${one ? 'it' : 'any of them'} will be rejected.`
+      : `${exists} and ${one ? 'stays' : 'stay'} as ${itIs} — this policy only checks creation, so ${itIs} rejected only if recreated.`
+  }
+
+  // "Set to enforce" is the legacy family's vocabulary; the modern API spells
+  // the same thing `validationActions: [Deny]`, and the posture badge above
+  // already says "Deny". Describing the behaviour rather than the field keeps
+  // one sentence correct for both.
+  const target = one ? 'this resource' : `any of these ${failing}`
+  return matchesUpdate
+    ? `Nothing is rejected today. Switching this policy to block would reject the next update to ${target}.`
+    : `Nothing is rejected today. Switching this policy to block would leave ${
+        one ? 'this resource as it is' : `these ${failing} as they are`
+      } — only newly created resources would be rejected.`
+}
+
+export function PolicyCoverageSection({
+  resource,
+  data,
+  loading,
+  error,
+  onSelectSubject,
+  onLoadMore,
+  loadingMore,
+}: PolicyCoverageSectionProps) {
+  if (loading) {
+    return (
+      <Section title={TITLE} icon={ShieldQuestion}>
+        <div className="text-sm text-theme-text-tertiary">Loading policy results…</div>
+      </Section>
+    )
+  }
+
+  if (error) {
+    // Same split as every other lookup on these screens, from the component that
+    // owns it — a denial is expected and reads calm, a fault stays loud. Repeating
+    // the predicate here is how the two drift into disagreeing about the same error.
+    return (
+      <Section title={TITLE} icon={isForbiddenError(error) ? ShieldQuestion : ShieldAlert}>
+        <LookupFailureNote errors={[error]} what="policy results" />
+      </Section>
+    )
+  }
+
+  if (!data || data.status === 'not_installed') return null
+
+  if (!data.evaluated) {
+    return (
+      <Section title={TITLE} icon={ShieldQuestion}>
+        <div className="text-sm text-theme-text-tertiary">
+          {(data.status === 'warmup'
+            ? 'Policy results are still loading from the cluster.'
+            : 'Policy results are unavailable, so nothing has been checked against this policy.') +
+            (data.reasonCode ? ` (${data.reasonCode})` : '')}
+        </div>
+      </Section>
+    )
+  }
+
+  const family = policyFamilyFor(resource)
+  const words = outcomeWords(family)
+  const { counts } = data
+  const examined = counts.pass + counts.fail + counts.warn + counts.error + counts.skip
+
+  if (examined === 0) {
+    const withheld = anythingWithheld(data)
+    return (
+      <Section title={TITLE} icon={ShieldQuestion}>
+        <div className="text-sm text-theme-text-tertiary">
+          {withheld
+            ? 'No results to show here.'
+            : 'Nothing has been checked against this policy yet.'}
+        </div>
+        <ScopeNote data={data} />
+      </Section>
+    )
+  }
+
+  const bad = problemCount(counts)
+  return (
+    <Section title={TITLE} icon={bad > 0 ? ShieldAlert : ShieldCheck} defaultExpanded={bad > 0}>
+      <Headline data={data} words={words} />
+      <ForeignEngines data={data} />
+      <Consequence resource={resource} data={data} family={family} />
+      <div className="mt-3 space-y-3">
+        {data.rules.map((rule, i) => (
+          <RuleBlock
+            key={rule.rule || `unnamed-${i}`}
+            rule={rule}
+            heading={ruleHeading(resource, rule)}
+            partial={anythingWithheld(data)}
+            onLoadMore={onLoadMore}
+            loadingMore={loadingMore}
+            // Per rule, because one legacy policy can validate, mutate and
+            // generate at once and each means something different by "fail".
+            words={outcomeWords(policyFamilyFor(resource, rule.rule))}
+            onSelectSubject={onSelectSubject}
+          />
+        ))}
+      </div>
+      <ScopeNote data={data} />
+    </Section>
+  )
+}
+
+/**
+ * `results[].policy` is producer-defined — Trivy and Falco write their own
+ * identifiers into it — and the lookup keys on that string, so a same-named
+ * producer's results land here. Silent when one engine owns the page.
+ */
+function ForeignEngines({ data }: { data: PolicyCoverageResponse }) {
+  const engines = (data.engines ?? []).filter((e) => e !== 'kyverno' && e !== 'unknown')
+  if (engines.length === 0) return null
+  return (
+    <div className="mt-2 text-sm text-theme-text-secondary">
+      {`Some of these results were written by ${engines.join(', ')}, not by Kyverno — the reports key them under the same name.`}
+    </div>
+  )
+}
+
+/**
+ * Scope before numbers. A total the caller cannot actually see is a lie of
+ * omission, so the sentence names the ground it covers first.
+ */
+function Headline({
+  data,
+  words,
+}: {
+  data: PolicyCoverageResponse
+  words: OutcomeWords
+}) {
+  const { counts } = data
+  const parts: string[] = []
+  if (counts.fail > 0) parts.push(`${counts.fail} ${words.bad}`)
+  if (counts.warn > 0) parts.push(`${counts.warn} warned`)
+  if (counts.pass > 0) parts.push(`${counts.pass} ${words.good}`)
+  if (counts.error > 0) parts.push(`${counts.error} could not be evaluated`)
+  if (counts.skip > 0) parts.push(`${counts.skip} skipped`)
+
+  const scope =
+    data.scopeNamespaces > 0
+      ? `Across ${data.scopeNamespaces} ${data.scopeNamespaces === 1 ? 'namespace' : 'namespaces'}${
+          data.clusterScoped ? ' and cluster-scoped resources' : ''
+        }`
+      : data.clusterScoped
+        ? 'Across cluster-scoped resources'
+        : 'Across the resources you can read'
+
+  // Leading with the examined total bounds the claim to what the engine looked
+  // at, not the cluster.
+  const examined = data.examined || 0
+  const examinedPhrase = examinedSummary(examined, data.subjects ?? examined)
+  return (
+    <div className="text-sm text-theme-text-secondary">
+      {scope}, {examinedPhrase} — {parts.join(', ')}.
+    </div>
+  )
+}
+
+/**
+ * What enforcing this policy would actually do.
+ *
+ * Two claims are tempting and both are false: that enforcing blocks the
+ * resources already failing (it does not — they are left alone), and that their
+ * next update is rejected (only if the policy matches UPDATE). The honest answer
+ * depends on the policy's declared operations, which is why this reads the spec
+ * rather than the report.
+ */
+function Consequence({
+  resource,
+  data,
+  family,
+}: {
+  resource: any
+  data: PolicyCoverageResponse
+  family: KyvernoPolicyFamily | undefined
+}) {
+  const lines: string[] = []
+  // This sentence counts resources — "N already exist", "the next update to any
+  // of them" — so it needs the resources, not the outcomes. One resource failing
+  // two of the policy's rules is one thing that exists and one thing that gets
+  // rejected, however many times it was checked.
+  const failing = data.subjectsFailing ?? data.counts.fail
+
+  if (failing > 0 && canStateConsequence(resource, family)) {
+    lines.push(
+      enforcementConsequence(failing, blocksAdmission(resource, family), matchesUpdates(resource)),
+    )
+  }
+
+  if (data.counts.error > 0) {
+    lines.push(engineErrorLine(data.counts.error, getKyvernoEffectiveFailurePolicy(resource) === 'Fail'))
+  }
+
+  if (lines.length === 0) return null
+  return (
+    <div className="mt-2 text-sm text-theme-text-primary space-y-1">
+      {lines.map((l, i) => (
+        <div key={i}>{l}</div>
+      ))}
+    </div>
+  )
+}
+
+/** An engine error is not a pass — the rule reached no verdict. `skip` stays
+ *  out: a rule that did not apply is not a problem with anything. */
+function problemCount(counts: PolicyResourceCounts): number {
+  return counts.fail + counts.warn + counts.error
+}
+
+/**
+ * Missing results are dropped before counting, so an examined count of zero
+ * means either "nothing was checked" or "something did not arrive". Which one is
+ * ScopeNote's to say; this only decides whether absence can be claimed at all.
+ */
+function anythingWithheld(data: PolicyCoverageResponse): boolean {
+  return (
+    (data.withheldByFamily ?? 0) > 0 ||
+    data.withheldNamespaces > 0 ||
+    !!data.withheldClusterScoped ||
+    (data.deniedGroups ?? []).length > 0
+  )
+}
+
+/**
+ * Whether the cap removed rows that would have been listed. `rule.truncated` is
+ * too blunt (250 passing + 1 failing is capped, yet everything listable
+ * arrived), and rows the view filter withheld are not the cap's doing — counting
+ * those offers a "Load the rest" no higher limit can satisfy.
+ */
+function capWorthMentioning(
+  notableListed: number,
+  notableTotal: number,
+  notableHidden: number,
+): boolean {
+  return notableListed + notableHidden < notableTotal
+}
+
+/** Outcomes and resources are different counts: one resource matched by two
+ *  rules records two outcomes. Named apart only when they differ. */
+function examinedSummary(examined: number, subjects: number): string {
+  const res = (n: number) => `${n} ${n === 1 ? 'resource' : 'resources'}`
+  if (subjects === examined) return `${res(examined)} examined`
+  return `${examined} ${examined === 1 ? 'check' : 'checks'} on ${res(subjects)}`
+}
+
+/** A rule that could not evaluate reached no verdict, so what happens next
+ *  depends on the policy's failurePolicy rather than on the result. */
+function engineErrorLine(n: number, failClosed: boolean): string {
+  if (failClosed) {
+    return `${n} could not be evaluated. This policy fails closed, so ${
+      n === 1 ? 'that admission is' : 'those admissions are'
+    } rejected for an engine error rather than a violation.`
+  }
+  return `${n} could not be evaluated and ${n === 1 ? 'is' : 'are'} being allowed through unchecked.`
+}
+
+/** "Show all N" is a promise the client cannot keep once the server cap bit. */
+function foldLabel(listed: number, total: number, capped: boolean): string {
+  return capped ? `Show ${listed} of ${total}` : `Show all ${listed}`
+}
+
+/**
+ * `counts` describe the cluster, lists describe the view, so the cluster-wide
+ * count cannot label a list. Only non-passing subjects are listed, so everything
+ * withheld that was not notable was a pass — exact, not inferred.
+ */
+function passingInView(passTotal: number, hiddenByFilter: number, hiddenNotable: number): number {
+  return Math.max(0, passTotal - Math.max(0, hiddenByFilter - hiddenNotable))
+}
+
+/** "All" holds only when nothing is outside the view; next to a footer naming
+ *  hidden subjects it invites the count to be read as the total. `partial` is
+ *  the other way the set can be short — a namespace or a report family nobody
+ *  put in front of this caller — which the counts silently exclude, so the word
+ *  would be claiming completeness the footer goes on to deny. */
+function passingLabel(
+  count: number,
+  hiddenByFilter: number,
+  words: OutcomeWords,
+  partial = false,
+): string {
+  const noun = count === 1 ? 'resource' : 'resources'
+  if (hiddenByFilter > 0) return `${count} ${noun} ${words.good} in view`
+  return partial ? `${count} ${noun} ${words.good}` : `All ${count} ${noun} ${words.good}`
+}
+
+function RuleBlock({
+  rule,
+  heading,
+  words,
+  partial,
+  onSelectSubject,
+  onLoadMore,
+  loadingMore,
+}: {
+  rule: PolicyCoverageRule
+  /** Undefined when this bucket has no name worth showing. */
+  heading?: string
+  words: OutcomeWords
+  /** Findings are missing from the whole response, so no rule may claim "All". */
+  partial?: boolean
+  onSelectSubject?: (subject: PolicyCoverageSubject) => void
+  onLoadMore?: () => void
+  loadingMore?: boolean
+}) {
+  // Passing subjects are collapsed, not discarded: a policy matching every pod
+  // in the cluster would bury its failures under a wall of green, but "which
+  // resources satisfy this rule" is half the question the view exists to answer
+  // and a bare count cannot be clicked, checked, or navigated from.
+  const notable = rule.subjects.filter((s) => s.result.toLowerCase() !== 'pass')
+  const passingSubjects = rule.subjects.filter((s) => s.result.toLowerCase() === 'pass')
+  const passing = passingInView(rule.counts.pass, rule.hiddenByFilter ?? 0, rule.hiddenNotable ?? 0)
+
+  // Same shape as RelationshipGroup: fold at a readable length, then expand in
+  // place. The house convention never states a count the reader cannot open.
+  const [showAll, setShowAll] = useState(false)
+  const folded = !showAll && notable.length > SUBJECT_FOLD_LIMIT
+  // Everything the rule flagged, whether or not it survived the server cap.
+  const notableTotal = rule.counts.fail + rule.counts.warn + rule.counts.error + rule.counts.skip
+  const notableCapped = capWorthMentioning(notable.length, notableTotal, rule.hiddenNotable ?? 0)
+  const visible = folded ? notable.slice(0, SUBJECT_FOLD_LIMIT) : notable
+
+  return (
+    <div>
+      {heading && (
+        <div className="text-xs font-medium text-theme-text-tertiary mb-1">{heading}</div>
+      )}
+      {notable.length === 0 ? (
+        /* Two claims to get wrong at once. "All" is only true when the rule
+           has nothing outside the view — with subjects held back it invites
+           the count to be read as the total. And a count of zero is not a
+           statement worth making: "All 0 resources passing" appears exactly
+           when the filter withheld everything, which the footer says properly. */
+        passing > 0 && (
+          <PassingGroup
+            label={passingLabel(passing, rule.hiddenByFilter ?? 0, words, partial)}
+            subjects={passingSubjects}
+            total={passing}
+            words={words}
+            onSelectSubject={onSelectSubject}
+            onLoadMore={onLoadMore}
+            loadingMore={loadingMore}
+          />
+        )
+      ) : (
+        <div className="space-y-1.5">
+          {visible.map((s, i) => (
+            <SubjectRow key={`${s.namespace}/${s.kind}/${s.name}/${i}`} subject={s} words={words} onSelect={onSelectSubject} />
+          ))}
+          {folded && (
+            <button
+              type="button"
+              onClick={() => setShowAll(true)}
+              className="px-2 py-0.5 text-xs rounded border border-theme-border text-theme-text-secondary hover:text-theme-text-primary hover:bg-theme-elevated transition-colors"
+            >
+              {/* "Show all N" is the house wording, but it is only true when the
+                  client holds every subject. Once the server cap has bitten,
+                  the button can only offer what arrived. */}
+              {foldLabel(notable.length, notableTotal, notableCapped)}
+            </button>
+          )}
+          {passing > 0 && (
+            <PassingGroup
+              label={`${passing} other ${passing === 1 ? 'resource' : 'resources'} ${words.good}`}
+              subjects={passingSubjects}
+              total={passing}
+              words={words}
+              onSelectSubject={onSelectSubject}
+              onLoadMore={onLoadMore}
+              loadingMore={loadingMore}
+            />
+          )}
+        </div>
+      )}
+      <RuleFooter
+        rule={rule}
+        notableCapped={notableCapped}
+        words={words}
+        onLoadMore={onLoadMore}
+        loadingMore={loadingMore}
+      />
+    </div>
+  )
+}
+
+/**
+ * The word for what the hidden subjects ARE. Kyverno files engine errors under
+ * a rule of its own, and that bucket holds nothing else — so the family's fail
+ * word ("not mutated" for a mutating policy) names the one thing that did not
+ * happen to them, and the screen ends up claiming more failures than its own
+ * summary counted.
+ */
+function hiddenNotableWord(counts: PolicyResourceCounts, words: OutcomeWords): string {
+  const notable = counts.fail + counts.warn + counts.error + counts.skip
+  return notable > 0 && counts.error === notable ? 'could not be evaluated' : words.bad
+}
+
+/**
+ * What is not on screen. The count describes the rows actually rendered — only
+ * non-passing subjects are listed, so the denominator is that population and a
+ * rule where everything passes announces no truncation over its zero rows.
+ */
+function RuleFooter({
+  rule,
+  notableCapped,
+  words,
+  onLoadMore,
+  loadingMore,
+}: {
+  rule: PolicyCoverageRule
+  /** True when the server cap removed subjects that would have been listed. */
+  notableCapped: boolean
+  words: OutcomeWords
+  onLoadMore?: () => void
+  loadingMore?: boolean
+}) {
+  const hidden = rule.hiddenByFilter ?? 0
+  // Client-side folding is already announced by the "Show all N" button, which
+  // is where the house pattern puts it — repeating it here said the same thing
+  // twice. What the button CANNOT say is that the server capped the list, in
+  // which case "Show all" would be a promise the client cannot keep.
+  if (!notableCapped && hidden === 0) return null
+  const parts: string[] = []
+  if (notableCapped) {
+    parts.push(`only the first ${rule.subjects.length} are available here`)
+  }
+  if (hidden > 0) {
+    // Whether any of the withheld subjects were failing is the part a reader
+    // acts on — it is the difference between a filter trimming noise and a
+    // filter covering a problem.
+    const notableHidden = rule.hiddenNotable ?? 0
+    parts.push(
+      notableHidden > 0
+        ? `${hidden} hidden by your namespace filter, ${notableHidden} of them ${hiddenNotableWord(rule.counts, words)}`
+        : `${hidden} hidden by your namespace filter`,
+    )
+  }
+  return (
+    <div className="flex flex-wrap items-baseline gap-2 pt-1">
+      <span className="text-xs text-theme-text-tertiary">{parts.join(', ')}</span>
+      {/* The cap is the only part of this the reader can do something about,
+          and until there was a way to lift it the sentence was the end of the
+          road. */}
+      {notableCapped && onLoadMore && (
+        <button
+          type="button"
+          disabled={loadingMore}
+          onClick={onLoadMore}
+          className="px-2 py-0.5 text-xs rounded border border-theme-border text-theme-text-secondary hover:text-theme-text-primary hover:bg-theme-elevated transition-colors disabled:opacity-60"
+        >
+          {loadingMore ? 'Loading…' : 'Load the rest'}
+        </button>
+      )}
+    </div>
+  )
+}
+
+/**
+ * The resources that satisfy the rule.
+ *
+ * Collapsed by default — a passing list is usually long and rarely the reason
+ * someone opened the page — but never reduced to a bare number. "34 passing"
+ * with no way to see the 34 answers half the question this view exists for and
+ * leaves the reader no route to any of them; the rows are the same clickable
+ * subjects the failures use.
+ */
+function PassingGroup({
+  label,
+  subjects,
+  total,
+  words,
+  onSelectSubject,
+  onLoadMore,
+  loadingMore,
+}: {
+  label: string
+  /** Passing subjects that arrived. May be shorter than `total` if the server capped. */
+  subjects: PolicyCoverageSubject[]
+  /** Exact count of passing subjects in view, unaffected by the cap — so a
+   *  shortfall against `subjects` is the cap and nothing else. */
+  total: number
+  words: OutcomeWords
+  onSelectSubject?: (subject: PolicyCoverageSubject) => void
+  onLoadMore?: () => void
+  loadingMore?: boolean
+}) {
+  const [open, setOpen] = useState(false)
+  const [showAll, setShowAll] = useState(false)
+
+  // Nothing to open: the count is real but the subjects did not survive the
+  // server cap, so the label stands alone rather than offering an empty drawer.
+  if (subjects.length === 0) {
+    return <div className="text-xs text-theme-text-tertiary pt-0.5">{label}</div>
+  }
+
+  const folded = !showAll && subjects.length > SUBJECT_FOLD_LIMIT
+  const visible = folded ? subjects.slice(0, SUBJECT_FOLD_LIMIT) : subjects
+  const capped = subjects.length < total
+
+  return (
+    <div className="pt-0.5">
+      <button
+        type="button"
+        onClick={() => setOpen(!open)}
+        className="flex items-center gap-1 text-xs text-theme-text-tertiary hover:text-theme-text-secondary"
+      >
+        {open ? <ChevronDown className="w-3 h-3" /> : <ChevronRight className="w-3 h-3" />}
+        {label}
+      </button>
+      {open && (
+        <div className="space-y-1.5 mt-1.5">
+          {visible.map((s, i) => (
+            <SubjectRow
+              key={`${s.namespace}/${s.kind}/${s.name}/${i}`}
+              subject={s}
+              words={words}
+              onSelect={onSelectSubject}
+            />
+          ))}
+          {folded && (
+            <button
+              type="button"
+              onClick={() => setShowAll(true)}
+              className="px-2 py-0.5 text-xs rounded border border-theme-border text-theme-text-secondary hover:text-theme-text-primary hover:bg-theme-elevated transition-colors"
+            >
+              {capped ? `Show ${subjects.length} of ${total}` : `Show all ${subjects.length}`}
+            </button>
+          )}
+          {capped && !folded && (
+            <div className="flex flex-wrap items-baseline gap-2">
+              <span className="text-xs text-theme-text-tertiary">
+                {`only the first ${subjects.length} are available here`}
+              </span>
+              {/* The same offer the failing list gets. A rule where everything
+                  passes is capped just as readily, and without this the count
+                  names resources the reader has no way to reach — which is the
+                  dead end the whole section exists to close, on its quiet half. */}
+              {onLoadMore && (
+                <button
+                  type="button"
+                  disabled={loadingMore}
+                  onClick={onLoadMore}
+                  className="px-2 py-0.5 text-xs rounded border border-theme-border text-theme-text-secondary hover:text-theme-text-primary hover:bg-theme-elevated transition-colors disabled:opacity-60"
+                >
+                  {loadingMore ? 'Loading…' : 'Load the rest'}
+                </button>
+              )}
+            </div>
+          )}
+        </div>
+      )}
+    </div>
+  )
+}
+
+function SubjectRow({
+  subject,
+  words,
+  onSelect,
+}: {
+  subject: PolicyCoverageSubject
+  words: OutcomeWords
+  onSelect?: (subject: PolicyCoverageSubject) => void
+}) {
+  const tone = resultTone(subject.result, words)
+  const label = subject.namespace ? `${subject.namespace}/${subject.name}` : subject.name
+  const body = (
+    <>
+      <span className={clsx('badge shrink-0', tone.badge)} title={`Report result: ${subject.result}`}>
+        {tone.label}
+      </span>
+      <div className="min-w-0">
+        <div className="text-sm text-theme-text-primary truncate">
+          <span className="text-theme-text-tertiary">{subject.kind}</span> {label}
+          {subject.autogen && (
+            <span
+              className="text-theme-text-tertiary"
+              title="Matched through a rule Kyverno generated from your Pod rule"
+            >
+              {' · via controller'}
+            </span>
+          )}
+        </div>
+        {subject.message && (
+          <div className="text-xs text-theme-text-secondary">{subject.message}</div>
+        )}
+      </div>
+    </>
+  )
+
+  if (!onSelect) {
+    return <div className="flex items-start gap-2 min-w-0">{body}</div>
+  }
+  return (
+    <button
+      type="button"
+      onClick={() => onSelect(subject)}
+      className="flex items-start gap-2 min-w-0 w-full text-left hover:bg-theme-hover rounded px-1 -mx-1 py-0.5"
+    >
+      {body}
+    </button>
+  )
+}
+
+/**
+ * Three independent ways this answer can be incomplete: report families the
+ * caller cannot read, namespaces the caller cannot read, and an index that is no
+ * longer updating. Silence on any of them turns a partial view into an implied
+ * all-clear.
+ */
+function ScopeNote({ data }: { data: PolicyCoverageResponse }) {
+  const denied = data.deniedGroups ?? []
+  const unreadable = data.unreadableFamilies ?? []
+  const withheldByFamily = data.withheldByFamily ?? 0
+  if (
+    denied.length === 0 &&
+    unreadable.length === 0 &&
+    data.withheldNamespaces === 0 &&
+    !data.withheldClusterScoped &&
+    data.liveUpdates
+  ) {
+    return null
+  }
+  return (
+    <div className="mt-2 pt-2 border-t border-theme-border text-xs text-theme-text-tertiary space-y-0.5">
+      {data.withheldNamespaces > 0 && (
+        <div>
+          {`${data.withheldNamespaces} ${
+            data.withheldNamespaces === 1 ? 'namespace is' : 'namespaces are'
+          } not shown because you can’t read policy results there.`}
+        </div>
+      )}
+      {data.withheldClusterScoped && (
+        <div>Cluster-scoped results are not shown because you can’t read policy reports at cluster scope.</div>
+      )}
+      {unreadable.length > 0 && (
+        <div>
+          {`You can’t read ${unreadable.join(', ')}, so ${withheldByFamily === 1 ? '1 result was' : `${withheldByFamily} results were`} left out of this list.`}
+        </div>
+      )}
+      {denied.length > 0 && (
+        <div>{`Some policy results could not be read (${denied.join(', ')}), so this list may be incomplete.`}</div>
+      )}
+      {!data.liveUpdates && <div>These results are not updating live.</div>}
+    </div>
+  )
+}
+
+
+/** Internals exposed for tests — family gating is load-bearing and latent
+ *  (a legacy Enforce policy with failures is rare in fixtures, common in the
+ *  field), so it is pinned directly rather than through the DOM. */