SPEC: false statements fixed, repeats removed, dropped requirements restored

The bounds sentence, the blocklist URL sentence, the deny list sentence,
the limit action's scope and the observe mode sentence now say what the
code does. Each of the twenty-one requirements the fourth review found
twice is stated once, with a link from the other place. The request id
header, redirect_uri's case, change 4's reason and the live archive's
InRelease files are back. The biased thresholds are defined where they
are introduced. The docs files apply the fifth README review's findings
and stay identical to the README branch.

Model: fable-5-1

docs/gitea.md

@@ -21,10 +21,10 @@ checked again when gitea or the Core Rule Set changes version.
     - a release attachment.
 
     At the defaults, an upload larger than 100 MiB or taking more than 60
-    seconds is cut off, and no one is banned for it. "Size and time limits" in
-    `SPEC.md` gives the answers the client gets. A gitea that takes large
-    uploads needs `SWWAF_REQUEST_MAX_BYTES`, `SWWAF_CLIENT_REQUEST_TIMEOUT` and
-    `SWWAF_UPSTREAM_REQUEST_TIMEOUT` raised to fit.
+    seconds is cut off ("Size and time limits" in `SPEC.md`). A gitea that takes
+    large uploads needs `SWWAF_REQUEST_MAX_BYTES`,
+    `SWWAF_CLIENT_REQUEST_TIMEOUT` and `SWWAF_UPSTREAM_REQUEST_TIMEOUT` raised
+    to fit.
 
 - Archive download and blame or history pages are what scrapers hammer. The
   request limits do most of the work there.
@@ -63,15 +63,15 @@ toward). The request log names the rule in `waf_rule_ids`, which
 
 ### A query string that reads as an attack
 
-Most often this is a search. Every query parameter is checked against the Core
-Rule Set's lists of system files and commands, except the ten named under
-"Attack detection" in `SPEC.md`. A release attachment uploaded through the API
-as `docker-compose.yml` is refused the same way. Examples:
+Most often this is a search. A search term is a query parameter, which the Core
+Rule Set checks against its lists of system files and commands (see the fourth
+change under "Attack detection" in `SPEC.md`). A release attachment uploaded
+through the API as `docker-compose.yml` is refused the same way. Examples:
 
 - a name on those lists, such as `package.json`, `.gitignore` or
   `docker-compose.yml`;
-- text that starts with a command name, or whose first word has one right after
-  a `/`, such as `python3`, `ssh key` or `feat/docker-support`;
+- text that starts with a command name, such as `python3` or `ssh key`, or has
+  one right after a `/` in its first word, such as `feat/docker-support`;
 - a shell command with its options or a system path (`ls -la`, `sed -i`,
   `/bin/sh`), or a command in backticks;
 - script code (`fetch(`, `${VAR}`, `process.env`), HTML (`<img src=`) or an SQL
@@ -81,15 +81,15 @@ as `docker-compose.yml` is refused the same way. Examples:
 ### A branch, tag or file name that starts with a command name
 
 The Core Rule Set's list of commands (932260) holds names such as `docker-`,
-`python3`, `ansible`, `base64` and `whoami`. A branch, tag or file name that
-starts with one is refused. So is one that has such a name right after a `/`,
-such as `feat/docker-support`, `fix/docker-build` or
+`python3`, `ansible`, `base64` and `whoami`. A query parameter holding a branch,
+tag or file name that starts with one is refused. So is one that has such a name
+right after a `/`, such as `feat/docker-support`, `fix/docker-build` or
 `renovate/docker-build-push-action-6.x`. gitea's own pages send the name in a
 query parameter that 930120, 932160 and 932260 still check:
 
-- `refSubUrl`, the branch or tag of a directory listing. It is sent when the
-  listing asks for its entries' last commits in a second request, which it does
-  whenever gitea takes more than a second to work them out;
+- `refSubUrl`, the branch or tag of a directory listing. A listing sends it when
+  it asks for its entries' last commits in a second request. It does so whenever
+  gitea takes more than a second to work them out;
 - `name`, when a branch is deleted or restored on the branches page;
 - `tag`, when a release is started from a tag;
 - `template`, the file of an issue template, when an issue is opened from it;
@@ -110,9 +110,9 @@ What a visitor sees, for a branch named `docker-build`:
 ### A file name in a query parameter that trips the code rules
 
 The Core Rule Set's rules for Java, script, PowerShell and SQL find what they
-look for in some file names. This holds in the parameters `smallwebwaf` leaves
-out of 930120, 932160 and 932260 too (see the changes to the Core Rule Set under
-"Attack detection" in `SPEC.md`). Examples:
+look for in some file names. This holds too in the ten query parameters that
+930120, 932160 and 932260 do not check (see the fourth change under "Attack
+detection" in `SPEC.md`). Examples:
 
 - `runtime` in OpenJDK's `src/java.base/share/classes/java/lang/Runtime.java`
   (944110);
@@ -129,9 +129,9 @@ For such a file, these requests are refused:
 - the API's call for the contents of files that names it in its query (`body`);
 - the commit graph of that file alone (`file`);
 - the hidden lines of its diff (`path`), which stay hidden;
-- the sign-in page gitea sends a visitor to on the way to a page of the file
-  that needs signing in, such as its edit page (`redirect_to`). The visitor can
-  still sign in by opening the sign-in page itself.
+- the sign-in page, for a visitor who opens a page of the file that needs
+  signing in, such as its edit page (`redirect_to`). The visitor can still sign
+  in by opening the sign-in page itself.
 
 ### A path
 
@@ -143,25 +143,30 @@ For such a file, these requests are refused:
   `process.env.d.ts` does.
 - A path with a directory named `...` (930100, 930110), such as `.../notes.txt`.
 
-For such a file, the page of the file, its raw file, its history, its blame and
-its edit page are refused. The directory that holds it lists it, and a clone
-carries it.
+For such a file, these are refused:
+
+- the page of the file;
+- its raw file;
+- its history and its blame;
+- its edit page.
+
+The directory that holds it lists it, and a clone carries it.
 
 ### A container image push that reuses a layer
 
 A push can reuse a layer of an image docker has pushed to that gitea before.
 docker then asks gitea to take the layer from that image, naming it in the query
 parameter `from`, which 932260 checks. The request is refused when the image's
-owner starts with an entry on the list of commands. So is one whose name after
-the owner does. Examples are `owner/python3-app`, `owner/docker-base`, and any
-image of an owner named `ansible` or `docker-team`.
+owner starts with an entry on the list of commands. It is refused too when the
+image's name after the owner starts with one. Examples are `owner/python3-app`,
+`owner/docker-base`, and any image of an owner named `ansible` or `docker-team`.
 
 What happens next depends on docker's image store. A docker that keeps its
 images in containerd's image store fails the push, and fails each new try the
 same way. A new install of Docker Engine 29 does this. A docker that keeps them
 in its own older image store uploads the layer instead. The push then succeeds
 after one refusal for each layer it reuses, and each of those refusals counts
-toward the error burst.
+toward the error burst ("Attack detection" in `SPEC.md`).
 
 ### Artifact uploads from `actions/upload-artifact@v3`
 
@@ -169,9 +174,9 @@ This action sends the header `Content-Range`, which the Core Rule Set refuses
 (920450). The action sends two files at a time, does not retry a `403`, and
 sends no further file once one is refused. So an upload is refused once or
 twice, however many files it holds, and the step fails. One upload does not ban
-the runner. More than 30 such refusals from its address within a minute, as when
-many jobs upload at once, ban it through the error burst.
-`actions/upload-artifact@v4` does not send the header.
+the runner. The error burst ("Attack detection" in `SPEC.md`) bans it after more
+than 30 such refusals from its address in a minute, as when many jobs upload at
+once. `actions/upload-artifact@v4` does not send the header.
 
 ## What body inspection refuses
 
@@ -193,8 +198,7 @@ Of the requests above, the script sends:
   code rules", the API's list of its commits;
 - for `Runtime.java` alone, the commit graph of that file, the hidden lines of
   its diff, and the API's call for the contents of files that names it;
-- the sign-in page gitea sends a visitor to on the way to the edit page of
-  `document.write.js`;
+- the sign-in page for a visitor who opens the edit page of `document.write.js`;
 - the pages of `java.lang.String.md`,
   `META-INF/services/org.apache.commons.logging.LogFactory`, `process.env.d.ts`
   and `.../notes.txt`;