Core Rule Set: a repository's name passes in the adopt form's id (closes #365)

While bodies are read, the forms that adopt or delete an unadopted
repository were refused when the repository's name held a command, a
system file's name or a shell path, such as alice/python3-app,
alice/.profile or robin/assets. id there now skips 930120, 932120, 932160
and 932260. The paths are gitea's /-/admin/repos/unadopted, Forgejo's
/admin/repos/unadopted, and /user/settings/repos/unadopted, which both
serve.

Model: opus-5-5

README.md

@@ -587,11 +587,11 @@ client's limits by tag. See "Request tags" in [`SPEC.md`](SPEC.md).
 - These apps work out of the box at the default settings, and their recorded
   ordinary requests pass the Core Rule Set:
     - gitea: git over HTTP and sign-in through Git Credential Manager get
-      through. On gitea's own paths, its searches, file names and branch names
-      do too.
+      through. On gitea's own paths, its searches, file names, branch names and
+      repository names do too.
     - Forgejo: git over HTTP and its container and package registries get
-      through. On Forgejo's own paths, its searches, file names and branch names
-      do too.
+      through. On Forgejo's own paths, its searches, file names, branch names
+      and repository names do too.
     - WordPress: saving a post from the block editor gets through. On
       WordPress's own paths, its searches, names and file names do too.
     - Drupal: on Drupal's own paths, the page to return to, its searches and its