feat(admin): guided tuning editor that sends only the changes
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>
This commit is contained in:
dingo
2026-10-28 12:09:54 -04:00
co-authored by Claude Opus 5.5
parent 8dedde454d
commit 23ea24080e
7 changed files with 464 additions and 71 deletions
@@ -263,6 +263,13 @@ Sections 1-2 are delivered without a new owner format or opening, so running rul
the line, key and kind of a problem, Adopt stores the revision with a reason, the revision
list shows how many regions adopted each, and each region shows which revision its live
rules match (`rules_sha256` in the region view).
- **Guided editor (2026-10-28).** The Tuning page edits by section: each setting as a field
with its unit, a reading in plain units and its comment, changed values listed against the
base. `POST /api/tuning?base=baseline|REV` takes only the changed `key = value` lines and
applies them to the baseline file or to revision REV, which must be the newest (409
`stale_base` otherwise), keeping the base's comments; the result is checked and stored as
any full text. DEV's ingress admits request bodies of about 1 KB, below a whole revamp
file, so the full-text editor (kept as Text mode) reports that proxy refusal plainly.
- **Region page (2026-10-28).** The region view also carries the rules-13 drip
(`drip`: interval, energy and matter bubble caps) and, over every life and deposit whatever
the listing limits, `counts` (players, wildlife, patches, pools, bubbles) and `totals`