where is `cf.zone.name` documented again? Trying to see what else I can add
where is
cf.zone.name documented again? Trying to see what else I can addcf.zone.name
cf.worker.upstream_zone and cf.zone.name?Identifies whether a request comes from a worker or not.
When a request comes from a worker, this field will hold the name of the zone for that worker. Otherwise cf.worker.upstream_zone is empty.

x- for custom headers is gone/deprecated and the fact those are uppercase also hurtshttp.request.headers["cf-worker"][0], not sure if it would be set that point though hmmx- so these headers stand out, and we don't use x- in any of our applications (so this avoids ever having an accidental conflict of header names)cf.edge.client_port, something you can only get by passing it down.
cf.verified_bot_category is cool too"x-client-port": "0", on my first attemptverified_bot_name?verifiedBotCategory since I do a json.stringify on the cf request objectcf.worker.upstream_zonex-x-x-http.request.headers["cf-worker"][0]cf.edge.client_portcf.verified_bot_category"x-client-port": "0",verified_bot_nameverifiedBotCategorycf