Extract images from PodSpec using Cue

[MPV]

As in:

• Extract images from PodSpec using Cue #28

But now also:

• Use CUE without Central Registry (local schemas), and only Cue to parse Kubernetes resources

[MPV]

Superseded by #83, which is the closest descendant of this one.

This used local schemas with CUE as the only parser — no Central Registry, no typed fallback. #83 keeps both of those choices and changes one thing: the local schemas are generated from k8s.io/api/core/v1 by cue get go (make schema) rather than written by hand, so there is nothing to keep in step with the Kubernetes API.

What that surfaced, which a hand-written schema hides: the real #Container says containerPort is an int32, and manifests decode YAML→JSON→Go where every number is a float64 — so every container declaring a port failed to match until candidates were handed to CUE as JSON instead. A loose hand-written schema never hits this, and also never rejects a lookalike as precisely.

The open question on #83 is cost, not correctness: 2469 ms per 1000 documents against master's 152 ms, ~12× option #82, which validates the same shapes using the same Kubernetes types as Go code.

Closing as superseded rather than rejected — the cue-with-cursor-no-central-registry branch is untouched. #83 is one of four candidates for #26 (#81 #82 #83 #84).

---

Generated by Claude Code