Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/Captcha/Exceptions/CaptchaException.php`:
- Around line 21-24: Update the docblock to accurately reflect the defined class
name: change the line that reads "Class CacheException" to "Class
CaptchaException" in the CaptchaException class file so the docblock matches the
actual class (CaptchaException) and keep the `@package` and other annotations
unchanged.

In `@tests/Unit/App/Exceptions/AppExceptionTest.php`:
- Around line 1-18: Run the project's PHP formatter on the new test file to
apply coding standards fixes: open the AppExceptionTest class
(tests/Unit/App/Exceptions/AppExceptionTest.php) and run the repository's
formatter (e.g., php-cs-fixer fix or composer run format) so the
testMissingAppKeyFactory method and surrounding whitespace/formatting are
adjusted to the project's CS rules; commit the formatted file so CI no longer
reports PHP CS Fixer violations.

In `@tests/Unit/App/Exceptions/BaseExceptionTest.php`:
- Around line 1-61: Run php-cs-fixer on the changed test file (the
BaseExceptionTest and BaseExceptionStub definitions and their test methods such
as testMethodNotSupportedFactory, testAdapterAndDriverFactories,
testLookupAndConnectionFactories, testConfigAndRequestMethodFactories) to
normalize formatting/whitespace according to project rules, apply the fixes it
suggests, stage the updated file and re-run the test/CI pipeline so the PHP CS
Fixer violations are resolved before merging.

In `@tests/Unit/Asset/Exceptions/AssetExceptionTest.php`:
- Around line 1-27: Formatter fixes are required for AssetExceptionTest: run the
project's PHP CS Fixer (or php-cs-fixer fix) and apply its changes to the
AssetExceptionTest class so the file adheres to coding standards; ensure
spacing, imports, and line endings are corrected for the class
AssetExceptionTest and its methods testPositionInUse and testNameInUse and
commit the formatted file.

In `@tests/Unit/Auth/Exceptions/AuthExceptionTest.php`:
- Around line 1-44: Run PHP-CS-Fixer on the test file and commit the formatting
fixes so CI passes: apply PSR-12 formatting (or your project's php-cs-fixer
config) to tests/Unit/Auth/Exceptions/AuthExceptionTest.php — e.g., run
vendor/bin/php-cs-fixer fix (or your project equivalent) and commit the updated
file; ensure the AuthExceptionTest class (and its test methods like
testIncorrectCredentials, testInactiveAccount, etc.) are formatted according to
the fixer rules.

In `@tests/Unit/Config/Exceptions/ConfigExceptionTest.php`:
- Around line 1-18: The test file ConfigExceptionTest (class
ConfigExceptionTest, method testConfigCollision) is failing PHP CS Fixer; run
the project's formatter (e.g., php-cs-fixer fix . or the repository's configured
formatter command) against this file, apply the fixer output, and commit the
reformatted ConfigExceptionTest.php so it complies with PHP CS Fixer rules
before merging.

In `@tests/Unit/Encryption/Exceptions/CryptorExceptionTest.php`:
- Around line 1-36: The file CryptorExceptionTest contains PHP CS Fixer
formatting violations; run php-cs-fixer (or your project's pre-commit formatter)
against this file or the whole repo to normalize formatting, then commit the
updated file so the class CryptorExceptionTest and its test methods
(testPublicKeyNotProvided, testPrivateKeyNotProvided, testInvalidCipher) pass CI
linting; ensure you stage the formatted changes before pushing.

In `@tests/Unit/Hasher/Exceptions/HasherExceptionTest.php`:
- Around line 1-25: This file fails PHP CS Fixer rules; run php-cs-fixer (e.g.,
php-cs-fixer fix) and reformat the test class HasherExceptionTest so it complies
with project coding standards — ensure spacing, indentation, imports and
trailing newlines are fixed for the class and its methods
testAlgorithmNotSupported and testInvalidBcryptCost, then re-run tests/CI to
confirm the style violations are resolved.

In `@tests/Unit/Hook/Exceptions/HookExceptionTest.php`:
- Around line 1-27: Run PHP-CS-Fixer on this test file to normalize formatting
before merging; specifically apply the project's coding style to
HookExceptionTest (affecting methods testHookDuplicateName and
testUnregisteredHookName) and ensure spacing/line breaks and phpdoc/namespace
formatting conform to the fixer rules so the assertions around
HookException::hookDuplicateName and HookException::unregisteredHookName remain
unchanged, then commit the formatted file.

In `@tests/Unit/HttpClient/Exceptions/HttpClientExceptionTest.php`:
- Around line 1-18: Run the project's PHP CS Fixer/formatter and commit the
resulting changes for this test file: format
tests/Unit/HttpClient/Exceptions/HttpClientExceptionTest.php (the class
HttpClientExceptionTest and method testRequestNotCreated) so it adheres to the
repo coding standards; specifically run the configured fixer (e.g., php-cs-fixer
fix or composer run format), review and stage the updated file, and push the
formatted file so CI no longer reports style violations.

In `@tests/Unit/Jwt/Exceptions/JwtExceptionTest.php`:
- Around line 1-18: Run the PHP formatter/CS fixer and apply its changes to this
test file: open the JwtExceptionTest class and the testPayloadNotFound method,
run your project's PHP CS Fixer (e.g., php-cs-fixer fix or composer cs:fix) to
reformat according to the repo rules, review the modified JwtExceptionTest.php
to ensure spacing/imports follow the fixer output, and commit the formatted file
so CI no longer flags the file as non-compliant.

In `@tests/Unit/Lang/Exceptions/LangExceptionTest.php`:
- Around line 1-27: Run the PHP CS Fixer/formatter over the test file and commit
the fixed formatting so CI passes: open the LangExceptionTest class (methods
testTranslationsNotFound and testMisconfiguredDefaultConfig) and apply your
project formatter (e.g., run vendor/bin/php-cs-fixer fix
tests/Unit/Lang/Exceptions/LangExceptionTest.php or the repository's configured
php cbf/php-cs-fixer command), then stage the modified file and push the commit
containing only the formatting changes.

In `@tests/Unit/Logger/Exceptions/LoggerExceptionTest.php`:
- Around line 1-27: The file LoggerExceptionTest (class LoggerExceptionTest with
methods testLogPathIsNotDirectory and testLogPathIsNotFile) fails PHP-CS-Fixer
checks; run the project's php-cs-fixer configuration against this file (or run
the repo-wide fixer) to normalize formatting, then stage the formatted changes
and update the PR so CI passes — ensure you do not change test logic, only
formatting/PSR rules that php-cs-fixer enforces.

In `@tests/Unit/Middleware/Exceptions/MiddlewareExceptionTest.php`:
- Around line 1-18: The file MiddlewareExceptionTest::testMiddlewareNotFound is
failing PHP CS Fixer; run your formatter (e.g., vendor/bin/php-cs-fixer fix
tests/Unit/Middleware/Exceptions/MiddlewareExceptionTest.php or the project's
configured fixer) and commit the resulting changes so the file follows the
project's coding standards (apply PSR-12 spacing, use statement ordering,
trailing newline, and any other fixer edits) before merging.

In `@tests/Unit/Migration/Exceptions/MigrationExceptionTest.php`:
- Around line 1-45: The test file MigrationExceptionTest has PHP CS Fixer
formatting issues; run php-cs-fixer (e.g. php-cs-fixer fix) on the file
containing class MigrationExceptionTest and its test methods
(testWrongDirection, testUnsupportedAction, testNothingToMigrate,
testInvalidMigrationClass), apply the suggested formatting fixes, and commit the
corrected file so CI no longer fails on PHP CS Fixer violations.

In `@tests/Unit/Module/Exceptions/ModuleExceptionTest.php`:
- Around line 1-58: The file ModuleExceptionTest contains PHP CS Fixer style
violations; run php-cs-fixer (or your project's formatting command) against this
file (or the whole repository) and commit the reformatted output so tests pass
CI; specifically reformat the class ModuleExceptionTest and its methods (e.g.,
testModuleRoutesNotFound, testModuleConfigNotFound,
testModuleCreationIncomplete, testMissingModuleTemplate,
testMissingModuleDirectory, testModuleAlreadyExists, testDirectoryListingFailed)
to conform to the project's PHP CS Fixer rules before merging.

In `@tests/Unit/Paginator/Exceptions/PaginatorExceptionTest.php`:
- Around line 1-18: The test file PaginatorExceptionTest (method
testMissingRequiredParams) is failing PHP CS Fixer/formatter checks; run the
project's code formatter (e.g., php-cs-fixer or the repo's preconfigured
formatter) on that file or across the repo and apply the changes so the file
complies with the coding standards — then re-run tests/CI, ensuring
PaginatorExceptionTest and its assertions remain unchanged while only
whitespace/formatting are corrected.

In `@tests/Unit/Router/Exceptions/RouteExceptionTest.php`:
- Around line 10-34: Add assertions that verify the PHP error code (getCode())
for every RouteException factory used in this test: for each call to
RouteException::{incompleteControllerRoute, nestedGroups,
middlewaresOutsideRoute, controllerWithoutModule, cacheableOutsideRoute,
closureHandlerMissing, notClosure, nameBeforeDefinition, paramNameNotValid,
moduleRoutesNotClosure, nonUniqueNameInModule, actionNotFound,
invalidHandlerResponse, paramNameNotAvailable} add an
assertSame(<expected_code>, RouteException::...()->getCode()) following the
existing pattern used for noHttpMethods() and closureWithController(); determine
the correct expected code (E_ERROR or E_WARNING) by checking the corresponding
constants in the RouteException implementation and use that value in the
assertion.

---

Outside diff comments:
In `@tests/Unit/Csrf/Exceptions/CsrfExceptionTest.php`:
- Around line 1-29: This test file isn’t PHP-CS-Fixer compliant; run the
project's PHP CS Fixer (or the configured linter) and apply the automatic fixes
to CsrfExceptionTest (ensure file header spacing, indentation, blank lines
between methods, and PSR-12 conforming braces/whitespace in the class and
methods testTokenNotFound and testTokenNotMatched are corrected) so the file
matches the repo coding standards before merging.

In `@tests/Unit/Di/Exceptions/DiExceptionTest.php`:
- Around line 1-53: Re-run PHP CS Fixer (using the project config) and apply
fixes to this test file so it meets coding standards; run the fixer (e.g.
php-cs-fixer fix . --config=.php_cs.dist) or your repo's configured command,
then re-check and commit the updated DiExceptionTest.php changes (class
DiExceptionTest and its test methods testDependencyFactories,
testAbstractAndCircularFactories, testInvalidCallableFactory) before merging so
CI no longer flags CS violations.

In `@tests/Unit/Environment/Exceptions/EnvExceptionTest.php`:
- Around line 1-29: This test file (EnvExceptionTest class, methods
testEnvironmentImmutable and testEnvironmentNotLoaded) is not PHP CS Fixer
compliant; re-run php-cs-fixer (or the project's fixer command) on this file to
fix formatting/spacing/namespace/import order and ensure it follows PSR-12 so
the file passes CI linting before merging.

In `@tests/Unit/Session/Exceptions/SessionExceptionTest.php`:
- Around line 1-29: Run PHP CS Fixer on the tests file and fix formatting issues
in the SessionExceptionTest class (SessionExceptionTest, testSessionNotStarted,
testSessionNotDestroyed) so it complies with project coding standards; re-run
the fixer until no changes are suggested and commit the formatted file.

In `@tests/Unit/Storage/Exceptions/FileSystemExceptionTest.php`:
- Around line 1-32: Run PHP CS Fixer to make this test file comply with project
coding standards; specifically reformat tests in the FileSystemExceptionTest
class (methods testDirectoryNotExists, testDirectoryNotWritable,
testFileAlreadyExists) by running the project's php-cs-fixer configuration
(e.g., php-cs-fixer fix) and commit the resulting whitespace/formatting changes
so CI passes.

In `@tests/Unit/Storage/Exceptions/FileUploadExceptionTest.php`:
- Around line 1-25: Re-run the project's PHP CS Fixer on the test file and fix
any style issues so it passes CI: run the formatter against the file containing
the FileUploadExceptionTest class (methods testFileTypeNotAllowed and
testIncorrectMimeTypesConfig) and ensure formatting/spacing/braces follow the
repository rules; verify resulting file compiles and assertions referencing
FileUploadException factory methods still match after formatting.

In `@tests/Unit/View/Exceptions/ViewExceptionTest.php`:
- Around line 1-29: Re-run PHP CS Fixer and apply the project coding standards
to this test file (class ViewExceptionTest and its methods testNoLayoutSet and
testViewNotRendered) so it becomes CS-compliant; run the configured php-cs-fixer
command (or your pre-commit formatter) against this file and commit the
resulting formatting changes (spacing, imports, and PSR-12 style fixes) before
merging.

---

Nitpick comments:
In `@src/Loader/Exceptions/LoaderException.php`:
- Around line 21-26: The docblock above the LoaderException class incorrectly
labels it "DatabaseException class"; update the docblock summary to correctly
refer to LoaderException so generated docs match the class. Locate the docblock
for the LoaderException class in LoaderException.php and replace the
"DatabaseException class" text with "LoaderException class" (or an appropriate
description referencing LoaderException) so the class name and docblock are
consistent.