jeroen/cartopolis

Watch

Fork 0

QA: what #180 shipped — NWB road network: is it worth wiring in? #255

New issue

Closed

opened 2026-09-01 02:23:14 +00:00 by viberfox-agent · 2 comments

viberfox-agent commented

2026-09-01 02:23:14 +00:00

Collaborator

Issue #180 (“NWB road network: 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 #180 (“NWB road network: 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-09-01 02:23:14 +00:00

viberfox-agent added this to the Viberfox project

2026-09-01 02:23:32 +00:00

viberfox-agent added the

agent:running

label

2026-09-01 02:23:32 +00:00

viberfox-agent commented

2026-09-01 02:23:34 +00:00

Author

Collaborator

🤖 Picked this up — working on branch feat/255-qa-what-180-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/255-qa-what-180-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-09-01 02:27:29 +00:00

gap: the WEGGEG frontier row omits the city-coverage limit #180 already measured #256

viberfox-agent closed this issue

2026-09-01 02:28:05 +00:00

viberfox-agent commented

2026-09-01 02:28:27 +00:00

Author

Collaborator

#180 shipped no code. It checked the Rijkswaterstaat road network (NWB) against the live government service, decided it wasn't worth wiring in, and wrote down why — a note plus a row in docs/direction.md. So there was nothing for a player to touch. The thing to QA is whether that written verdict is true and useful, because its whole purpose is to stop the next person redoing the check.

I re-ran every measurement it documented. All of them held, three days on.

Claim	Result
Licence CC0 1.0	holds
Two collections, no polygon anywhere	holds — road sections are lines, hectometre posts are points
60 properties, none carrying width or lane count	holds — 60 exactly; `rel_hoogte` is the only structure-related one
`rel_hoogte` empty in 363 of 400 features at Knooppunt Oudenrijn	holds, exactly
`rel_hoogte` empty in 969 of 1000 over Groningen centre	holds, exactly
1,392 features, 2,033,782 bytes, 2 requests	holds, byte for byte
Paging cap of 1000; `offset` rejected with 400	holds, same error text
Geometry "largely BGT-derived"	holds — 700 of 1000 features

Both code references it leans on still say what it claims. No code anywhere mentions NWB, which is right — nothing was wired.

The table it invented for "checked and not taken" has since been reused by six more sources, and both loose ends it left were picked up: the bridge-deck one became a ticket (already covered by #242).

What I filed

#256 (qa-gap) — one real gap. The note measured that WEGGEG, the lane-count service it points at, covers motorways only. Two days later that became the top candidate in docs/direction.md, described as "the measured answer to a width this client derives from a road's class" — with only a motorway cell's numbers and no link back to the note. I re-measured: 0 lane features in Amsterdam, Utrecht and Rotterdam centres, 2 in Groningen, 136 at one motorway interchange. Someone picking up that row would wire it and find the change invisible on every city street — the exact repeat that the "checked and not taken" table exists to prevent.

For you to decide

One thing I chose not to file: the note cites road_texture.rs:164 for the road-width table, which has since moved to line 181. The reader lands 17 lines off in the right file with the function visible just below, so I judged it too small for the board — say the word if you'd rather citation drift always got a ticket, since #248 is the same species.

No commits, no branch pushed, nothing built — a QA pass has no code to verify, and I changed none. #255 is closed.

No commits were made.

_{🤖 viberfox issue agent on the VPS — 27 turns · $2.65 · session 688ad15b-ce39-4ed4-990e-309b2276d4da. Reply with @agent to continue this session.}

**#180 shipped no code.** It checked the Rijkswaterstaat road network (NWB) against the live government service, decided it wasn't worth wiring in, and wrote down why — a note plus a row in `docs/direction.md`. So there was nothing for a player to touch. The thing to QA is whether that written verdict is true and useful, because its whole purpose is to stop the next person redoing the check. I re-ran every measurement it documented. **All of them held, three days on.** | Claim | Result | |---|---| | Licence CC0 1.0 | holds | | Two collections, no polygon anywhere | holds — road sections are lines, hectometre posts are points | | 60 properties, none carrying width or lane count | holds — 60 exactly; `rel_hoogte` is the only structure-related one | | `rel_hoogte` empty in 363 of 400 features at Knooppunt Oudenrijn | holds, exactly | | `rel_hoogte` empty in 969 of 1000 over Groningen centre | holds, exactly | | 1,392 features, 2,033,782 bytes, 2 requests | holds, byte for byte | | Paging cap of 1000; `offset` rejected with 400 | holds, same error text | | Geometry "largely BGT-derived" | holds — 700 of 1000 features | Both code references it leans on still say what it claims. No code anywhere mentions NWB, which is right — nothing was wired. The table it invented for "checked and not taken" has since been reused by six more sources, and both loose ends it left were picked up: the bridge-deck one became a ticket (already covered by #242). ## What I filed **#256** (`qa-gap`) — one real gap. The note measured that WEGGEG, the lane-count service it points at, covers motorways only. Two days later that became the *top* candidate in `docs/direction.md`, described as "the measured answer to a width this client derives from a road's class" — with only a motorway cell's numbers and no link back to the note. I re-measured: **0 lane features in Amsterdam, Utrecht and Rotterdam centres, 2 in Groningen, 136 at one motorway interchange.** Someone picking up that row would wire it and find the change invisible on every city street — the exact repeat that the "checked and not taken" table exists to prevent. ## For you to decide One thing I chose *not* to file: the note cites `road_texture.rs:164` for the road-width table, which has since moved to line 181. The reader lands 17 lines off in the right file with the function visible just below, so I judged it too small for the board — say the word if you'd rather citation drift always got a ticket, since #248 is the same species. No commits, no branch pushed, nothing built — a QA pass has no code to verify, and I changed none. #255 is closed. _No commits were made._ --- 🤖 viberfox issue agent on the VPS — 27 turns · $2.65 · session `688ad15b-ce39-4ed4-990e-309b2276d4da`. Reply with **@agent** to continue this session.

viberfox-agent added

agent:done

and removed

agent:running

labels

2026-09-01 02:28:27 +00:00

viberfox-agent referenced this issue

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

Autopilot log #257