История коммитов

.
refactor(album): pass the request as an action argument
Only the actions that actually read the request take it; form and confirmation actions keep their signatures.
.
refactor(profile): pass the request as an action argument
Only the actions that actually read the request take it; form actions keep their signatures.
.
refactor(guestbook): pass the request as an action argument
GuestbookForm::getFormData() now takes the request as a parameter instead of holding it in the constructor: it reads five body fields plus the attached files, which does not reduce to a scalar fact, and a RequestStack in the module's application layer would reintroduce the hidden capture this stage removes.
.
refactor(downloads): pass the request as an action argument
Controllers are container singletons, so a Request injected into the constructor outlives the request it belongs to. Every downloads controller now takes it as the first action argument; private handlers receive it as a parameter, and DownloadPathController forwards it to the controllers it delegates to.

Fixes ImportFileController::handleImport(), which read $category from the caller's scope: a successful import failed with a TypeError in getCategoryUrl(). The helper now takes the category as a parameter, and the matching PHPStan baseline entry is gone.
.
refactor(admin): pass the request as an action argument
Controllers are container singletons, so a Request injected into the constructor outlives the request it belongs to. Every admin controller now takes it as the first action argument; private helpers such as isCsrfValid() receive it as a parameter.
.
refactor(forum): pass the request as an action argument
Controllers are container singletons, so a Request injected into the constructor outlives the request it belongs to. Every forum controller now takes it as the first action argument; private helpers receive it as a parameter.

ForumUtils::topicLink() no longer resolves the request from the container: it needs the host only, which the caller now passes as a string.
.
refactor(http): make the session facade per-request
The shared Session facade now implements ResetInterface, so the kernel drops the bags
of the request it has served before serving the next one. An open session belongs to
the request being served (the FPM boot opens it before the kernel runs) and is left
alone.

Session::save() moves into the finally block of Kernel::handle(): a cycle that throws
no longer leaves its session open for the next one, which is what lets an open session
be read as the current request's.

Also: the console application implements ResetInterface, so the instanceof rule tagged
it as resettable and every HTTP request built the whole CLI application just to reset
it. Its definition now sits before that rule, guarded by a container test.
.
refactor: pass visitor facts into the application layer as a DTO
Introduce Johncms\Security\ClientInfoDTO and Environment::getClientInfo(): controllers
take the visitor address and user agent and hand them down, so use cases and forms no
longer depend on the HTTP-layer Environment service.

- forum: CreateTopic/PostMessage/ReplyMessage use cases take ClientInfoDTO
- registration: RegisterUserUseCase takes ClientInfoDTO
- admin: PrepareIpBanUseCase takes ClientInfoDTO; the admin's own addresses now go
through IpRangeParser, so an unparsable address takes part in no comparison
- contacts: ContactForm::getValidationRules() takes ClientInfoDTO
- fix stale ForumMessage $ip / $ip_via_proxy annotations (int -> string)
.
refactor(security): extract the request-rate log from Environment
The short-term log of who has been hitting the site is a storage, not a fact of the
request: it now lives behind RequestRateLogInterface with a flat-file implementation
(the record format is unchanged). The kernel records the visit, online/GetIpActivityUseCase
reads it, and Environment keeps only the address and the user agent.

Addresses cross the interface as strings — the unsigned-int form stays an implementation
detail, which is what IPv6 support will replace. The online module also stops depending
on Environment altogether: the current address is handed to the use case by its controller.
.
docs: record stages 5a-3 and 5a-4 in the migration plan