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

Both paths were relative to the current working directory. They run before
vendor/autoload.php, so they use __DIR__ rather than the path constants.

The installer resolved the autoloader, the config check and the step files
relative to the current working directory, and the translation domain relative
to ROOT_PATH. They now come from __DIR__ or from the path constants.

step_3 read the .env file through dirname(__DIR__, 2), a hardcoded depth that
would silently break and drop the database autofill under Docker. step_2 lists
the writable directories as absolute paths and labels them by subtracting
ROOT_PATH; PUBLIC_PATH joins the list, the sitemap and robots.txt are written
there.

Both scripts addressed the upload directory relative to the current working
directory. Once assets and upload move into public/ together, those relative
paths would keep working while ../../../vendor/autoload.php would resolve to
public/vendor and fail.

thumbinal.php did not load the autoloader at all, so it had no constants to
work with.

preview.php accepts the path with or without a leading slash, since one caller
passes each form, and now refuses to serve anything resolving outside of the
document root.

upload/.htaccess only silences PHP under Apache, nginx had no counterpart: a
PHP file placed in the upload directory was executed. The ^~ prefix stops the
regex locations from picking those requests up, while static files keep being
served. The rule matches on the URI, so it holds both before and after the
document root moves.

The dev template also gets the dotfile rule the production one already had.

Both files are fetched over HTTP, so they belong in the document root.
atomicWrite() writes its .tmp file next to the target, which means the public
path has to be writable.

Published assets and language flags are served over HTTP, so they resolve from
PUBLIC_THEMES_PATH. The list of available themes keeps using THEMES_PATH: it is
built from the theme templates, which stay outside the document root.

Assets and avatars are served from the document root, so their URLs are
relative to PUBLIC_PATH rather than to the repository root.

Three independent implementations mapped a filesystem path to a URL. They now
delegate to PublicUrlResolver and keep their signatures.

This also fixes pathToUrl(): it diffed the path segments against the root ones,
so /upload/app/photo.jpg under the /var/www/app root silently lost the app
directory. Paths outside of the base path now resolve to an empty string
instead of a mangled URL.

PUBLIC_PATH marks the web document root. It equals ROOT_PATH for now, so the
values of every constant stay exactly as they were, and ASSETS_PATH,
UPLOAD_PATH and the new PUBLIC_THEMES_PATH are derived from it.

THEMES_PATH keeps pointing at the repository root: most of its usages resolve
templates, which stay outside the document root.

Remove 14 one-off scripts, none of which were referenced from the code:
they were meant to be run manually by URL.

- updaters and converters for 8.0 to 9.9
- module installation scripts for 9.9

The upgrade path is 9.8 -> 9.9 -> 10.0, so these scripts stay available in
the 9.x branch together with their documentation. The install directory is
now a plain web installer.

BREAKING CHANGE: installing a module on an existing database has no tool in
10.x anymore.