Oliver Kieselbach 5163d7d6a0 refactor(backend): read the request query through req.Query only ...

73 sites in 68 files built the query collection with
HttpUtility.ParseQueryString(req.Url.Query), 15 files used req.Query and five mixed
both. HttpRequestData.Query is that same call, cached per request, and the ASP.NET
Core request type does not override it, so the change is behaviour-neutral.

- QueryParamGuardTests: ParseQueryString in the Functions project is limited to a
  named baseline of three sites that parse something other than the request query.
- A fact pins req.Query against HttpUtility.ParseQueryString (repeated keys, encoded
  values, caching) so a worker update that changes the implementation fails a test.
- Test mocks that set Url answer Query through CallBase; a loose mock returns null.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-21 22:28:11 +02:00

..

Agent

fix(agent): single-instance guard counts a same-named process only in session 0

2026-09-21 15:23:23 +02:00

Backend

refactor(backend): read the request query through req.Query only

2026-09-21 22:28:11 +02:00

McpServer

fix(backend): typed bodies and error envelope for backup, session-restore and delegation wrappers

2026-09-21 22:19:38 +02:00

Shared

fix(backend): typed bodies and error envelope for backup, session-restore and delegation wrappers

2026-09-21 22:19:38 +02:00

Web

fix(backend): typed bodies and error envelope for backup, session-restore and delegation wrappers

2026-09-21 22:19:38 +02:00