Runner doesn't get a proper name with new registration method?

I’m testing the new method for registering runners in a test setup. It mostly works, on the runner server:

root@gitlab:~# curl -k -H 'Private-token: <pat-for root>' -X POST ''  | jq .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    68  100    68    0     0    140      0 --:--:-- --:--:-- --:--:--   140
  "id": 2,
  "token": "glrt-Ht29KNg59pMNDrRzrdcf",
  "token_expires_at": null
root@gitlab:~# gitlab-runner register --non-interactive --url --token glrt-Ht29KNg59pMNDrRzrdcf --executor shell
Runtime platform                                    arch=amd64 os=linux pid=10895 revision=436955cb version=15.11.0
Running in system-mode.                            
Verifying runner... is valid                        runner=Ht29KNg59
Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!

but if I then look in /etc/gitlab-runner/config.toml I see:

  name = "gitlab"
  url = ""
  id = 2
  token = "glrt-Ht29KNg59pMNDrRzrdcf"
  token_obtained_at = 2023-06-07T14:51:44Z
  token_expires_at = 0001-01-01T00:00:00Z
  executor = "shell"
    MaxUploadedArchiveSize = 0

(and some global settings and configuration of some runners registered against an old test setup, that I want to replace with this)
And I can see that the name for this new runner is gitlab instead of Test_i_kitchen (that’s danish, but I guess anybody can figure out what it says, even though that’s not important) that I (thought I) specified. Why?

The new runner(s) also don’t seem to be registered on the GitLab server:

root@gitlab:~# curl -k -H 'Private-token: <pat-for-root>' --header 'Content-Type: application/json' --header 'Accept: application/json' -X GET ''

returns an empty array.

I still would like to know where the description I put in the REST API request actually goes (possible it only goes to the GitLab server, on the runner server, I can control what gets put in the name field in config.toml, by adding a --name (the documentation I have from before the new registration method came along, says --name is synonymous to --description) to the gitlab-runner register ... command, so now you can have runners with different descriptions on the runner server and on the GitLab server, but that would probably cause confusion.

That the API request to get the list of runners doesn’t work is probably more a documentation issue, it doesn’t work against (one of) our (old) production servers either, but if I add /all to the request it works. Actually it only says to use the variant with /all further down on

in the “List all runners” section, but at the top it suggests (to me at least) that you can do GET /runners, I have yet to see an instance where that gives something useful.