[fosterstack-admin]

One PR with every finished page and the plumbing, for the owner to merge and cold-read live.

Folds (closed with "folded into this PR"): #20, #21, #22, #23, #24, #25, #26, #27, #28, #29, #30, #31, #34, #35, #36, #37, #38, #39, #40, #42, #43, #44, #45, #46, #47.
Not in this PR (held, still open as drafts): #32 launch copy (pricing page, hero, meta/og), #33 Stripe page shells, #41 v0.3.0 draft.
Already live from earlier: #18 (Build Cache Node end of life) and #19 (tagline).

What it adds (24 page folders in total, 22 new): migrate/setup, CI runners, FAQ, how we build, Gradle not working, replacement checklist, long-term support, sizing, air-gapped install, Maven setup, security policy + /.well-known/security.txt, Docker Compose, Kubernetes, changelog, cosign verification, remote-cache safety, Verify a release yourself, monitoring, FIPS, HTTP status codes, reset, Gradle tutorial; plus the refreshed /regulated/ (no tier description; "Paid support tiers are not available yet."), the home page's Security section, Guides list and Maven wording, llms.txt and sitemap.xml covering every page.

Checks run on the combined branch: every internal link resolves to a page in the branch; the full tagline is in every page header; no leftover hedges ("nobody runs it", Maven in-progress), no banned strings; sitemap well-formed with every page; file allowlist passes on all tracked files; _headers, _redirects and robots.txt unchanged (CSP untouched; the FAQ's search markup is a data block).
Tested for real against a v0.2.1 server: #40 verify (13 commands), #42 metrics + statusz, #43 FIPS image, #45 status codes, #46 reset, #47 Gradle tutorial, #30 Maven (two docs bugs found and fixed here), #34 Compose, #29 air-gapped. #35 (Kubernetes) is quoted from the cache docs; a throwaway-cluster test is being run separately.
Review: the independent AI review reviewed each page's PR before folding; a the independent AI review pass on the combined diff (links, CSP, hedges) is recorded below. the independent AI review catch-up owed per rule 8 (no www lane in the wrapper yet).
Known: the home page's Pricing section is untouched (owner framing: "described, not sold").

[cloudflare-workers-and-pages]

Deploying www with    Cloudflare Pages

Latest commit:	2029db1
Status:	✅  Deploy successful!
Preview URL:	https://30bf200e.www-4rw.pages.dev
Branch Preview URL:	https://www-fold-all-pages.www-4rw.pages.dev

View logs

[fosterstack-admin]

Kubernetes page tested for real on a throwaway kind cluster (Kubernetes v1.37.0; own kubeconfig file, every kubectl call with an explicit --context; cluster deleted afterwards, default kubeconfig untouched). The cache doc's Secret, PVC, Deployment and Service manifests (image set to 0.2.1) applied cleanly into a namespace ENFORCING the restricted Pod Security profile: the pod was admitted and ran, replicas=1, strategy Recreate, PVC ReadWriteOnce Bound, requests 100m/128Mi, memory limit 512Mi, no CPU limit, runAsNonRoot 65532, fsGroup 65532, readOnlyRootFilesystem, capabilities drop ALL, allowPrivilegeEscalation false, seccomp RuntimeDefault. From a temporary pod: http://fscache.fscache-ns.svc.cluster.local/healthz ok; PUT without password 401; PUT with the secret's credentials 201. FINDING (fixed on the reset page in this PR; cache docs need the same fix): the documented reset (scale to 0, delete the PVC, scale to 1) leaves the pod Pending with 'persistentvolumeclaim fscache-data not found'; the claim must be re-created (kubectl apply of the PVC manifest) before scaling up, after which statusz shows store_entries 0 and the old key returns 404.