docs(aibom): correct the record left stale by the v1.3.0 re-pin

Two places in the record went stale when #2309 re-pinned k8s-aibom to
chart v1.3.0.

ADR-019's requirement-status table pointed the upgrade-evidence row at
#2282, which closed as the requalification and never carried that
evidence, and pointed the managed-cluster row at the epic rather than the
issue tracking it. Both now point at #2310 and #2311, which have since
closed with that evidence.

The component values described the pinned digest as a v1.2.0 artifact set
after the re-pin moved it to v1.3.0, and stated a Kind-measured resource
envelope that had never been checked against a managed control plane.
#2310 measured it: 67-69MiB and 1-2m steady-state CPU at 1,001 workloads
on GKE, well inside the declared requests. The v1.2.0 Kind figures are
dropped rather than carried forward as a comparison, since the upgrade
validation they existed for is complete.

Signed-off-by: Mark Chmarny <mark@chmarny.com>

Author: mchmarny

docs/design/019-k8s-aibom-runtime-inventory.md

@@ -680,8 +680,8 @@ A third entry is the signal to revisit rather than extend by reflex.
 | Selection and opt-out semantics | Resolved — E |
 | Non-alpha storage API and migration policy | Resolved — A |
 | Concrete user-demand case | Resolved — D |
-| Managed-cluster qualification and measured cost | Planned — [#2271](https://github.com/NVIDIA/aicr/issues/2271) |
-| Upgrade, rollback, uninstall, support evidence | Planned — [#2282](https://github.com/NVIDIA/aicr/issues/2282) |
+| Managed-cluster qualification and measured cost | Planned — [#2310](https://github.com/NVIDIA/aicr/issues/2310) |
+| Upgrade, rollback, uninstall, support evidence | Planned — [#2311](https://github.com/NVIDIA/aicr/issues/2311) |
 
 Decision 4 is unchanged: chart, image, CRDs, and the public status contract
 remain one versioned set, so the graduation release requires full

recipes/components/k8s-aibom/values.yaml

@@ -15,7 +15,8 @@
 # k8s-aibom Helm values
 # Optional runtime AI-workload inventory. Registry-only: no stock recipe
 # selects this component. The digest and defaults below were qualified as one
-# coherent v1.2.0 artifact set under ADR-019.
+# coherent v1.3.0 artifact set under ADR-019, re-pinned from v1.2.0 when
+# upstream graduated the API to v1beta1.
 
 image:
   repository: ghcr.io/googlecloudplatform/k8s-aibom
@@ -58,8 +59,10 @@ securityContext:
   runAsUser: 65532
   allowPrivilegeEscalation: false
 
-# Measured at 0, 250, and 1,000 replicas-zero workloads. At 1,000 workloads,
-# the final v1.2.0 image converged in 14s and remained below 231m CPU / 49MiB.
+# Envelope measured on GKE with the qualified v1.3.0 image (#2310), at 0, 251,
+# and 1,001 workloads, each a Deployment with replicas set to zero. At 1,001
+# workloads memory reached 67-69MiB and steady-state CPU was 1-2m, both well
+# inside the requests below. Convergence completed within 10s.
 resources:
   requests:
     cpu: 50m