kubectl content negotiation

Two almost-empty discovery endpoints decide whether kubectl ever reaches your pod handler

A Node reimplementation of the Kubernetes API found that kubectl v1.34.1 negotiates discovery first and then asks the server for a pre-rendered table, which puts most of the compatibility work in headers rather than in resource schemas.