docs(server): plain wording in the comments and test titles this change added

Comments and test titles added on this branch cited review labels and
planning documents that do not exist in the repository, and some used
dashes as separators. They now say what the code does and why in plain
sentences, and the Postgres lane's suites share one header format. Test
ids stay as they were.
This commit is contained in:
Maurice
2026-11-18 13:20:09 +01:00
parent e3d195896c
commit 21f4f7d5de
12 changed files with 13 additions and 14 deletions
+1 -1
View File
@@ -50,7 +50,7 @@ import nodeHttp from 'node:http';
* 4b. setupApiDocs — Swagger UI/spec at /api/docs* when TREK_API_DOCS_ENABLED.
* 4c. the named body-parser wrappers — the global 100kb JSON/urlencoded
* parsers, exempting /mcp so the MCP SDK reads the raw stream.
* 4d. nulFreeRequest — drops NUL from the path, query, body and cookies.
* 4d. nulFreeRequest, which drops NUL from the path, query, body and cookies.
* 5. app.init() — every domain controller, including the transport surface
* that used to live pre-init: /api/health (FeaturesController), OAuth
* discovery documents (DiscoveryController), the /oauth/consent COOP