Summary

Regenerate verifiable, signed demo evidence for the two training recipes under the canonical aicr.run predicate type, pushed to the NVIDIA-org registry. Follow-up to #1507, which removed the stale pre-migration pointers that could no longer verify.

Motivation / Context

Addresses @mchmarny's review note on #1507 (#1507 (comment)) asking whether the evidence could be regenerated under a canonical NVIDIA org rather than landing with community: [] + a follow-up. This PR is that regeneration.

#1499 migrated the artifact domain to aicr.run, which bumped PredicateTypeV1 to https://aicr.run/recipe-evidence/v1. The two committed demo evidence pointers had only their predicateType string edited in place, while still pinning the pre-migration, immutable signed OCI bundles — so aicr evidence verify failed on them. #1507 removed them (the correct immediate fix) and left regeneration as a follow-up. This PR is that regeneration.

Each bundle was produced by aicr validate --emit-attestation against a live cluster, then signed keyless (Sigstore) and pushed via aicr evidence publish --push ghcr.io/nvidia/aicr-evidence:

Both carry predicateType: https://aicr.run/recipe-evidence/v1 and verify clean (aicr evidence verify → exit 0: signature-verify, predicate-parse, and manifest-hash all pass).

The signer is unchanged from the original demo evidence (same 7c4c0edc… community source slug), so this PR also restores the community allowlist entry and the allowlist TestClassify "community by slug" case — both had been removed in #1507 when the evidence was deleted.

Fixes: N/A (regeneration follow-up to #1507)
Related: #1507, #1499

Type of Change

• Bug fix (restores verifiable evidence removed in fix(evidence,validator): correct catalog apiVersion examples, drop unverifiable demo evidence (#1499 follow-up) #1507)

Component(s) Affected

• Other: recipes/evidence/ (signed pointers + signer allowlist), pkg/evidence/allowlist (test)

Implementation Notes

• Both clusters' GPU nodes were fully occupied by a standing slinky-slurm NodeSet; freeing it (scale to 0 → validate → restore to 2) let the NCCL all-reduce workers schedule. No recipe/IMEX changes were needed — the earlier performance failures were pure capacity contention.
• The snapshots were captured with the released agent image (pre-migration) and restamped aicr.nvidia.com/v1alpha1 → aicr.run/v1alpha2; the feat: migrate API domain to aicr.run, bump v1alpha2/v1beta2 #1499 bump is signal-only (no schema change), so the restamp is equivalent to a post-migration agent's output.
• Pointers live under the same recipes/evidence/<recipe>/7c4c0edc…/ dirs as the originals (signer identity unchanged); only the digest-named filenames differ.

Testing

go test ./pkg/evidence/allowlist/...                                  # ok
aicr evidence verify recipes/evidence/h100-gke-cos-training/...       # exit 0
aicr evidence verify recipes/evidence/gb200-eks-ubuntu-training/...   # exit 0

Both committed pointers verify end-to-end against their pushed OCI bundles (signature + predicate + manifest hash). Scope is evidence pointers + allowlist + one test; no production Go logic changed.

Risk Assessment

• Low — Restores demo/sample evidence; no production code paths. The pointer-contract gate validates the committed pointers against the allowlist in CI.

Rollout notes: Demo evidence is restored to a verifiable state. No runtime/API impact.

Checklist

• Tests pass locally (allowlist package)
• I did not skip/disable tests to make CI green
• Changes follow existing patterns in the codebase
• Commits are cryptographically signed (git commit -S)