Put players where they actually are on the public map

[CaYatur]

Reported as a placement bug: on the web the players sit beside where they are standing, and in the app they do not.

It is not a placement bug. The public surfaces round positions for privacy and the app does not round at all:

surface	rounds?
desktop app	no
admin panel (/api/servers/:id/map)	no
public site map (/api/public/map)	yes, 64 blocks
map page (/api/map)	yes, 64 blocks

At 64 a player is drawn up to 32 blocks from where they stand. That default made sense when the public map was dots on an empty grid, where half a chunk out was invisible. The map draws real terrain now, and against terrain it is indistinguishable from a bug — which is how it got reported.

What changed

Exact by default, on both public surfaces. The protection is real and stays available; it is now an opt-in.

The field says what it costs. "Round to (blocks)" reads as a display nicety. It actually means every player is drawn up to half of it away from where they are, which is the sentence the hint now says, in EN and TR, on both the website settings and the map page settings.

Not migrating anyones stored value

round: 64 is persisted in site.json, so this default alone changes nothing for an existing install — including the one that reported the bug. That is deliberate: a stored 64 is indistinguishable from a deliberate choice, and rewriting it would publish exact player coordinates on the public website of every operator who meant to round. New configs get the new default; an existing one is one field in Website settings.

Verification

Proved failable — putting the default back to 64 fails with the public map rounds positions by default: 64.

The existing redaction test took its rounding from the defaults, so it started asserting the feature was broken the moment the default changed (the public map published exact coordinates). It now passes round explicitly: "does redaction work when switched on" and "is it on by default" are two questions, and only the first belonged in that block. The field-level protections — no y, no world, no uuid — are now asserted with rounding both on and off, since those have no setting and must hold either way.

Gates green by exit code: MSMS_SMOKE, MSMS_SMOKE_WEB.

[CaYatur]

Self review

Small change, but it moves a privacy default, so the review is about what it does NOT do.

The one that matters: this does not fix the reporter's map. Their site.json has round: 64 written into it, and site.ts:69 merges stored over defaults ({...base.map, ...(raw.map ?? {})}), so the new default never reaches them. I considered a one-time migration keyed on "value equals the old default" and rejected it: there is no marker distinguishing a stored 64 from a deliberate one, because the marker did not exist when those configs were written, so the migration would publish exact coordinates for operators who chose rounding on purpose. That is not a trade I can make on their behalf from a bug report about a different install. Flagged in the release notes and the report instead — it is one field.

Checked: the panel is genuinely unrounded. server.ts:1410 builds its payload from livePlayers directly, server.ts:652 and :2615 both go through redactPlayers. So the "app is right, web is wrong" split in the report is exactly this and nothing else — no second placement bug hiding underneath. I looked for one first: both surfaces place tiles and players through the same mapW2S, so a transform error would have moved the terrain with the players rather than between them.

A test was asserting the bug. The redaction block took its rounding from PUBLIC_MAP_DEFAULTS, so changing the default turned it into the public map published exact coordinates — a green gate that would have blocked a correct change, which is the mirror image of the vacuous fixture from #157. Split into the two questions it was conflating. While there I widened the field-level assertions (y, world, uuid) to run with rounding off as well: those protections have no setting, and the only case that previously exercised them was the rounded one.

heads interaction, checked and unchanged. heads: cfg.heads && cfg.names at server.ts:2619 still gates a face on a name, and redactPlayers still publishes the name when heads are on — a recognisable face identifies a player as well as a name does. Rounding is orthogonal and this PR does not touch it.

Scope. Nothing here addresses the tile retention, the web lag, or the "stays until F5" request — those are the next branch, deliberately separate so this reverts alone.