Compute family — first release

Added

Document	What it carries
`reference/compute/compute-engine.md`	the six machine families and their series, the naming grammar, where custom types are allowed
`reference/compute/gke-cluster-modes.md`	Autopilot and Standard, the responsibility split, the two billing dimensions
`reference/compute/cloud-run.md`	the four resource types, the immutable revision, jobs to executions to tasks
`reference/compute/cloud-functions.md`	the renaming, the Cloud Run platform underneath, the four capability differences
`reference/compute/errors.md`	the startup, import, deploy-permission, 429 and 503 strings with cause, check and fix
`guides/compute/deploy-a-container-on-cloud-run.md`	seven steps, ending in a verification that separates 429 from 503
`guides/parity/compute.md`	the one-to-three Cloud Run mapping, and the concurrency row that is a correctness risk

The two headline facts

The product names changed. "Cloud Functions" and "2nd gen" are both old; it is Cloud Run functions,

and a modern function deploys as a Cloud Run service.

A modern function instance serves up to 1000 concurrent requests, where 1st gen served one and AWS

Lambda's execution environment serves one at a time. Code written under the one-request assumption has races on Google Cloud. This is documented as a migration correctness risk, not a tuning note, in guides/parity/compute.md §2.

Absences recorded rather than filled in

The machine-resource page prints no last-updated date, the only page in this release that does not. Series

availability is zonal and is read live rather than written down.

The GKE cluster-mode page describes Autopilot's restrictions at the level of "privileges and configuration

options" and does not enumerate every forbidden field; the document says to check specific Pod specs against Autopilot's own constraints page.

Known missing

Compute Engine and GKE error catalogues. The family's error document covers Cloud Run only, because that

is where a migrated container lands. GKE node-pool and Compute Engine quota failures are not catalogued.

Managed instance groups, autoscaling policies and instance templates.
Sole-tenant nodes, Confidential Computing, Spot VMs and preemptibility.
Artifact Registry, named in the parity table and not documented.
Cloud Run service-to-service authentication and VPC egress settings (partly covered in the networking family).