Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 28s
Foundation / server-image (push) Successful in 4m48s
Foundation / image (push) Successful in 5m37s
DEV's ingress refuses request bodies over about 1 KB, so adopting a whole revamp file (5 KB) failed with a 413 the portal misreported as the API's 64 KiB limit. POST /api/tuning?base=baseline|REV now takes only changed `key = value` lines, applies them to the baseline file or the newest revision (409 stale_base for an older one), keeping its comments, then checks and stores as before. The Tuning page becomes a guided editor: sections, a field per setting with its unit, plain reading and comment, a changes list with Check and Apply (or Adopt as is), and loading a past revision or the baseline as changes. The full-text editor stays as Text mode and names a proxy refusal plainly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>