jeroen/cartopolis

Watch

Fork 0

QA: what #197 shipped — Rijkswaterstaat water levels: is it worth wiring in? #243

New issue

Closed

opened 2026-08-31 01:36:44 +00:00 by viberfox-agent · 2 comments

viberfox-agent commented

2026-08-31 01:36:44 +00:00

Collaborator

Issue #197 (“Rijkswaterstaat water levels: is it worth wiring in?”) was built and merged by the unattended lane, and nobody has used it. Walk what it delivered as a player would meet it.

This is a QA pass, not a build. Change no code and open no pull request on this
ticket — the deliverables are findings.

Exercise it for real. Run what a player would touch, headlessly: cargo run -p cartopolis_simulator with a client or a wire/HTTP probe for anything online, the
loopback tests, cargo run -p cartopolis -- --shot … --dump-state for anything with
geometry. CLAUDE.md lists every harness. If part of this genuinely needs a screen, a
phone or a microphone, verify the half a machine can reach and name the half it cannot.
Walk the user's journey, not the happy path. At each step ask what a real user
would obviously expect to be able to do next — then try exactly that. A refusal or an
absence that would surprise a user is a finding even when every implemented piece
works: registration worked, claiming a house worked, and a registered account still
could not claim a house. No test failed; a user hit a wall.
File each real gap as its own issue: title starting gap:, label qa-gap, with
what you did, what happened, what a user would expect instead, and where in the code
the seam is. Use the Forgejo API with the FORGEJO_TOKEN in your environment. Do not
label them autonomous — a person decides which gaps become work.
Report and close. Your final message: what you exercised, what held, what you
filed. Nothing found after a genuine pass is a good outcome — say what you checked.
Then close this ticket through the API; a QA pass has no branch to merge.

Decide it yourself. Nobody is watching this ticket; a question asked here is a
ticket that stops. Judge by what a reasonable player would expect, verify before
claiming, and never post credentials or file contents from outside the repository.

_{Filed by the autopilot.}

Issue #197 (“Rijkswaterstaat water levels: is it worth wiring in?”) was built and merged by the unattended lane, and nobody has used it. Walk what it delivered as a player would meet it. **This is a QA pass, not a build.** Change no code and open no pull request on this ticket — the deliverables are findings. 1. **Exercise it for real.** Run what a player would touch, headlessly: `cargo run -p cartopolis_simulator` with a client or a wire/HTTP probe for anything online, the loopback tests, `cargo run -p cartopolis -- --shot … --dump-state` for anything with geometry. CLAUDE.md lists every harness. If part of this genuinely needs a screen, a phone or a microphone, verify the half a machine can reach and name the half it cannot. 2. **Walk the user's journey, not the happy path.** At each step ask what a real user would obviously expect to be able to do next — then try exactly that. A refusal or an absence that would surprise a user is a finding even when every implemented piece works: registration worked, claiming a house worked, and a registered account still could not claim a house. No test failed; a user hit a wall. 3. **File each real gap as its own issue**: title starting `gap:`, label `qa-gap`, with what you did, what happened, what a user would expect instead, and where in the code the seam is. Use the Forgejo API with the `FORGEJO_TOKEN` in your environment. Do not label them `autonomous` — a person decides which gaps become work. 4. **Report and close.** Your final message: what you exercised, what held, what you filed. Nothing found after a genuine pass is a good outcome — say what you checked. Then close this ticket through the API; a QA pass has no branch to merge. **Decide it yourself.** Nobody is watching this ticket; a question asked here is a ticket that stops. Judge by what a reasonable player would expect, verify before claiming, and never post credentials or file contents from outside the repository. Filed by the autopilot.

viberfox-agent added the

agent

autopilot

labels

2026-08-31 01:36:44 +00:00

viberfox-agent added this to the Viberfox project

2026-08-31 01:36:47 +00:00

viberfox-agent added the

agent:running

label

2026-08-31 01:36:47 +00:00

viberfox-agent commented

2026-08-31 01:36:50 +00:00

Author

Collaborator

🤖 Picked this up — working on branch feat/243-qa-what-197-shipped in a fresh worktree on the VPS. I'll report back here when I'm done.

_{Label an issue agent:skip to keep me off it, or driven to keep it in a session you are driving.}

🤖 Picked this up — working on branch `feat/243-qa-what-197-shipped` in a fresh worktree on the VPS. I'll report back here when I'm done. Label an issue `agent:skip` to keep me off it, or `driven` to keep it in a session you are driving.

viberfox-agent referenced this issue

2026-08-31 01:44:45 +00:00

gap: the water-levels note points at hidden_tiles, which does not exist #244

viberfox-agent closed this issue

2026-08-31 01:45:06 +00:00

viberfox-agent commented

2026-08-31 01:45:40 +00:00

Author

Collaborator

QA pass done — no code changed, one gap filed, ticket closed.

#197 shipped documentation only. No crate is touched, so there is nothing a player can click. What it delivered is a decision — do not wire Rijkswaterstaat water levels in — plus the measurements behind it. So the QA became: do those claims still hold? I re-ran every measurement the note publishes and checked every code reference it makes.

Filed one gap: #244

The note's closing section — the part written for whoever later wants to reopen the decision — tells them to look at hidden_tiles in map_stream.rs. There is no such thing in this repository and there never was, including at the note's own commit. The function is occluded_by_finer. The sentence describing it is accurate; only the name is wrong. A one-word documentation fix, filed rather than fixed because this ticket says to change no code.

What held

Re-running the note's own commands against the live service today:

Old host still answers 301 to the migration notice.
Catalogue: 200, 1,573,954 bytes — the exact byte count recorded, with no API key sent.
2,498 locations, of which 705 carry water height.
A station record has exactly the seven fields listed, with no water-body identifier — so the "every level would be a nearest-station guess" argument stands.
All six rows of the city-centre distance table reproduce exactly: nearest station and all three count columns.
One station-hour: 200, 3,374 bytes, 7 measurements at 10-minute spacing, centimetres relative to Dutch ordnance datum, −91 cm.
Licence page still states CC0 word for word.

Against the code: water sits at −0.0035 m on a ladder spanning 8 mm, the finest basemap layer rests at −0.03 m (a gap of 2.65 cm), and the basemap is eight opaque layers deep with nothing cutting holes in it — all as cited.

I also reproduced the elevation measurement, which is the one carrying the conclusion. Writing a small reader for the height service's compressed floating-point rasters, the 100-metre box over the Grote Markt gives a median of +7.57 metres with 36% of samples missing — matching the note to the centimetre. My own boxes along the Diepenring put the banks at +0.95 to +6.06 metres against a water level of −0.91, so the drop is two to six metres; the note says two to five. Either way it is metres against a stack that can hold 8 millimetres.

Two things that could have contradicted the note and did not: buoys and houseboats are built as ground-plane furniture, so they sit level with the drawn water rather than the real water — the world is self-consistent; and all seven cross-referenced notes exist.

Not verified

Nothing was rendered. The decision was to change nothing, so there is no visual change to photograph — this is an absence of work, not an untested claim.

Branch has no commits, as the ticket asked.

No commits were made.

_{🤖 viberfox issue agent on the VPS — 46 turns · $3.73 · session aad19c99-7046-4856-9cc2-b20337b0dc04. Reply with @agent to continue this session.}

QA pass done — no code changed, one gap filed, ticket closed. **#197 shipped documentation only.** No crate is touched, so there is nothing a player can click. What it delivered is a decision — do not wire Rijkswaterstaat water levels in — plus the measurements behind it. So the QA became: do those claims still hold? I re-ran every measurement the note publishes and checked every code reference it makes. ## Filed one gap: #244 The note's closing section — the part written for whoever later wants to reopen the decision — tells them to look at `hidden_tiles` in `map_stream.rs`. There is no such thing in this repository and there never was, including at the note's own commit. The function is `occluded_by_finer`. The sentence describing it is accurate; only the name is wrong. A one-word documentation fix, filed rather than fixed because this ticket says to change no code. ## What held Re-running the note's own commands against the live service today: - Old host still answers 301 to the migration notice. - Catalogue: 200, **1,573,954 bytes** — the exact byte count recorded, with no API key sent. - **2,498** locations, of which **705** carry water height. - A station record has exactly the seven fields listed, with **no water-body identifier** — so the "every level would be a nearest-station guess" argument stands. - All six rows of the city-centre distance table reproduce exactly: nearest station and all three count columns. - One station-hour: 200, **3,374 bytes**, 7 measurements at 10-minute spacing, centimetres relative to Dutch ordnance datum, −91 cm. - Licence page still states CC0 word for word. Against the code: water sits at −0.0035 m on a ladder spanning 8 mm, the finest basemap layer rests at −0.03 m (a gap of 2.65 cm), and the basemap is eight opaque layers deep with nothing cutting holes in it — all as cited. I also reproduced the elevation measurement, which is the one carrying the conclusion. Writing a small reader for the height service's compressed floating-point rasters, the 100-metre box over the Grote Markt gives a median of **+7.57 metres** with 36% of samples missing — matching the note to the centimetre. My own boxes along the Diepenring put the banks at **+0.95 to +6.06 metres** against a water level of −0.91, so the drop is two to six metres; the note says two to five. Either way it is metres against a stack that can hold 8 millimetres. Two things that could have contradicted the note and did not: buoys and houseboats are built as ground-plane furniture, so they sit level with the drawn water rather than the real water — the world is self-consistent; and all seven cross-referenced notes exist. ## Not verified Nothing was rendered. The decision was to change nothing, so there is no visual change to photograph — this is an absence of work, not an untested claim. Branch has no commits, as the ticket asked. _No commits were made._ --- 🤖 viberfox issue agent on the VPS — 46 turns · $3.73 · session `aad19c99-7046-4856-9cc2-b20337b0dc04`. Reply with **@agent** to continue this session.

viberfox-agent added

agent:done

and removed

agent:running

labels

2026-08-31 01:45:40 +00:00

viberfox-agent referenced this issue

2026-09-01 00:33:04 +00:00

Autopilot log #181

viberfox-agent referenced this issue

2026-09-02 00:24:32 +00:00

Autopilot log #257