Batches 5, 7 and 6 of docs/10-URL-2026.md (roadmap steps 72-74): the builder writes the stored path of an entity, every link, endpoint, form and picture the site prints starts at the root of the site, and a page asked by any other address - a query, a former path, case, a slash, num, the wrong host - lands on its address in a single hop.

Core changes:

1. Building (core/system.php, core/classes/node/*, modules, blocks):

2. getSeoUrl() takes a passed route path, puts operation and id into the path and sorts the query

   • the category map answers the path of a category; a missing route of an entity link is logged with its caller
   • page replaces num on the public lists, the canonical keys and the title; the panel keeps num

3. The readers join the registry: Node lists and views, targets, sitemap, legacy map, forum, users, polls, comments

   • the writer answers the path a publication gives, so the redirect after a submission and the approval mail link it
4. Addresses from the root (templates, core, modules, blocks, lang/, modules/account/lang/):
5. Templates take {{ root }} from Template::getView(); theme pictures getThemeImageUrl()
6. Page links go through getSeoUrl(), mails through getPublicUrl(), endpoints, forms and htmx from HOME_PATH

7. user_info() takes the path of the user; the language constants of the account link carry href="%s"

   • the broken Polish links and the links to op=reg, op=passfor and op=profil are gone
8. One redirect (core/system.php, core/security.php, public/index.php):

9. setSeoMove() answers one absolute 301 for every reason at once, on the forced scheme and host

   • GET and HEAD only; never POST, htmx, an endpoint, a module file, a refusal or another script
   • the material, the topic, the profile and the poll call it right after their read and access check
   • the three callers of getNodeLegacyUrl() answer through it, so a 6.2 address is one hop
10. index.php keeps no 301 of its own: a path that names only the script is the start page
11. The early forcessl/forcehost block keeps the endpoints, the panel and the scripts; the host keeps its port
12. The forum counts a view after the access check; a missing profile answers 404, a members-only one 403
13. robots.txt (public/robots.txt, core/system.php):
14. The Disallow lines of folders outside public/ and the relative Sitemap line are gone
15. addSitemapTask() writes Sitemap: <homeurl>/sitemap.xml after every map, other lines untouched
16. Tests (tests/Unit, tests/Support):
17. RouteBuildTest: the address table built from its entities, list query counts, no relative address at a path
18. RouteMoveTest: each reason alone and mixed in one hop, the kept query, refusals, methods, no view counted
19. The probes follow one 301 on their site; the install router sends every path to index.php

Benefits:

• A search engine moves once, from the query addresses of 6.2 straight to the final paths
• One place decides the address of a page, the redirect and the canonical

Technical notes:

• No schema change; the registry _routes of batch 1 is read only
• Breaking: every GET of a page at index.php?name=... now answers 301 to its path
• RouteRegistryTest::twoWritersRaceForOnePath fails on the MariaDB 11.7 of the work machine, before and after

A review of three 2027 plans brings them in line with what the tree now is: the schema conventions, the reserved names of the readable addresses, the scheduler as it registers jobs today and the settings that are already taken. Nothing is implemented; the plans only stop promising what the code would contradict.

Core changes:

1. Admin UX (docs/2027-ADMIN-UX.md):

2. The status says that the decisions are taken and nothing is built; the dated remarks and the finished fix of the configuration form leave the plan

3. Eight ideas instead of nine, the dark theme of the panel no longer an open check, the dial of the list options left to its own roadmap step

4. The keyboard state of table sorting and the action journal of an undo are described as they are
5. Connector (docs/2027-CONNECTOR.md):

6. The rewrite rule of /api/v1/ stands before the fallback to index.php, and the name api is reserved in docs/10-URL-2026.md

7. Own-site calls of the scheduler keep working over http and loopback; jobs register in the three places the core uses today, or in the module list once docs/2027-CORE.md delivers it

8. Every column takes its domain from the schema conventions of docs/NODE.md

9. The update check keeps upcheck and channel in config/api.php, because config/update.php holds the marks of the 6.3 data updates; the compared version is the leading MAJOR.MINOR.PATCH of $conf['version']

10. The update package accepts only the tracked top-level entries of the release tag
11. Vine monitor (docs/2027-VINE-MONITOR.md):
12. The module stands on the floor of the release it ships with: PHP 8.4, MariaDB 10.5.2+ or MySQL 8.0.16+

13. Every column takes its domain from the schema conventions; moments are DATETIME in the site zone the connection runs on, timers unix seconds

14. An admin action is recorded by the connector audit and by the journal of checkAdminPost(); the public page is /vine; an installed site gets the tables from the step of update.php of its version

Benefits:

• The 2027 plans start from the current tree instead of an older one

Technical notes:

• Documentation only; no code, schema or configuration changes

Batches 0 to 2 of the plan of readable addresses before 8.0 (steps 67 to 69 of docs/ROADMAP-2026.md). The address switch that could never work leaves the panel and the configuration, one table _routes with the class Route holds every path an entity was ever given, and each writer of a material, type, category, topic, account or poll writes its paths inside its own transaction. Links still read index.php?...; parsing, building and the redirect follow.

Core changes:

1. The switch out and the inventory (admin/modules/config.php, config/global.php, core/system.php, public/update.php):

2. rewrite, sep, tsep, title and ctitle leave the panel, the shipped configuration, the 6.2 configuration update.php writes, the language constants of the fields and the help of the settings

3. getSeoUrl() always answers the query address and drops the title keys; the rewrite branches of getSeoRoute(), the sitemap, the panel monitor, NodeView and blocks/center_forum.php are gone

4. The inventory of literals, public operations, num readers, writers and the query baseline stands in docs/10-URL-2026.md; the plan left docs/2027-CORE.md, and no 6.2 path form is parsed

5. Registry and name (core/classes/route.php, storage/update/sql/table.sql, storage/update/sql/table_update6_3.sql):

6. _routes: path, kind, oid, state (current, former, gone) and cur generated from state; unique path and one current path per entity

7. Route finds a path, gives the first one, moves it without a chain, marks every path of a gone entity gone, answers a set in one query and keeps the reserved operations and type names; a write inside an open transaction runs behind a savepoint, a racing writer takes the next suffix

8. Route::setRouteName() is the one rule of the field Address: the given name, else the current name under a new prefix, else the first path from the title

9. filterSlug() transliterates the letters of all six locales from one table, decodes stored entities and cuts to 80

10. Node writers (core/classes/node/service.php, core/classes/node/query.php, core/classes/node/entity.php, core/classes/node/input.php, modules/node/index.php, modules/node/admin/index.php):

11. A material gets its first path where its publication comes, by hand or by the scheduled delivery, never for a type with ext support; the panel form moves it by the field Address once it has one; a deletion marks it gone

12. A type takes its name as its path and loses it on deletion; a new name is refused by Route::checkTypeName() besides RESERVED, so the name of a deleted type is never registered again

13. Categories of a type get, move and lose their paths, the subtree on deletion; Node and the writer read carry the current path as Node::$path

14. A refused path is a storage failure and rolls the whole write back

15. Writers outside Node (admin/modules/categories.php, modules/forum/index.php, modules/account/index.php, modules/account/admin/index.php, admin/index.php, public/setup.php, modules/voting/admin/index.php):

16. Forum categories, new topics, accounts (activation, OAuth sign-up, the panel, the first administrator) and polls write the row and its path in one transaction; deletions mark every path gone

17. A reply the recycle section turns into a topic gets its path; the recycle section keeps the path of a topic
18. The forms of category and poll carry the field Address with the whole path as hint, label _ADDRESS
19. getCategoryMap() joins the registry and carries path under the new cache key catmap/path
20. The reads of the topic, the profile and the poll join the registry for their current path

21. Tests (tests/Unit/RouteRegistryTest.php, tests/Unit/RouteWriterTest.php, tests/Support/registry_probe.php, tests/Support/route_probe.php, tests/Support/guard_probe.php):

22. The registry: transliteration per locale, both cuts, suffixes after current, former and gone paths, no chain, the keys, cur bound to state, a race of two writers, the reserved words held against the switches and the tree

23. The writers over real requests, and a trigger refusing a path leaves neither the entity nor a route row in each of the seven writers

24. The contracts of Node, NodeInput, NodeService, the statement budgets and the reuse of a type name follow

Benefits:

• An address once given stays bound to its entity, so 301 and 410 can be answered from one table
• The index of a search engine moves once, from the 6.2 query addresses straight to the final form

Technical notes:

• New table _routes in table.sql and table_update6_3.sql; the stand got it empty, batch 3 fills it on migration
• Breaking: rewrite, sep, tsep, title and ctitle are no settings any more; filterSlug() lost its separator argument
• Breaking: the name of a deleted Node type cannot be registered again

• Breaking: NodeService::addNodeCategory() and updateNodeCategory() take the field Address as an optional argument, Node and NodeInput end in an optional path

Batch 7 of the schema plan moves what lasts into the permanent reference and deletes the plan. The human-readable addresses leave the 2027 core plan and become a plan of their own before the release: one address per page without an id, held in a registry of routes, so the index of a search engine moves once.

Core changes:

1. Schema reference (docs/NODE.md, docs/ARCHITECTURE.md, docs/VERSIONS.md, docs/TESTS.md, README.md, UPGRADING.md):

2. docs/NODE.md gets "Schema conventions": the column domains, the time rule, the connection contract, the collation as one source, writes that fit their columns, unique addresses with NULL for none, keys that serve the queries

3. docs/ARCHITECTURE.md names the connection contract of Database and points at the conventions and their test
4. docs/VERSIONS.md records the schema of 2026-10-13 with its breaking changes for code outside the tree

5. README.md and UPGRADING.md recommend MySQL 8.4 or MariaDB 10.11 and newer and state the collation; UPGRADING.md lists what code outside the tree must change

6. docs/TESTS.md lists SchemaConventionTest.php
7. Schema plan closed (docs/7-SCHEMA-2026.md, tests/Support/route_probe.php):
8. the plan file is deleted; the comment of the route probe no longer names it
9. Plan of readable addresses (docs/10-URL-2026.md, docs/2027-CORE.md, docs/ROADMAP-2026.md):

10. docs/10-URL-2026.md: addresses without id (/files/adaptivnyi-shablon-pure, /files/moduli, /forum/modul-poiska, /users/eduard), one registry _routes with the current and every former path, an address never reused, 410 for a deleted entity, the type prefix and a fixed /, page in place of num

    • the design: the registry with one current row per entity, the name in six locales, when an entity gets and

changes its path, the migration order, parsing in two stages around the database, building from passed paths,
the query rules, one final redirect after the access check

• seven batches with their tests and the estimate

• docs/2027-CORE.md drops its item 7 and the steps and questions of it, pointing at the new plan
• docs/ROADMAP-2026.md: step 66 ticked, steps 68-74 for the new plan, the close moves to step 75

Benefits:

• The schema conventions live in the permanent reference and are held by a test
• The addresses change once, before the release, in their final form

Technical notes:

• Documentation only; no code, schema or configuration changes
• The address plan is not started; its first step is 68 of the roadmap

Batch 6 of the schema plan rehearses update.php on a clean 6.2 site, which the owner chose over a production dump: the 6.2 path renames the seven source tables of Node again, so any 6.2 site reaches Node, while update.php stays the internal tool of the maintainer. The rehearsal pinned the root cause of the fresh installation that had failed in NodeProfileTest since 2026-10-04: setup.php opened its session a second time.

Core changes:

1. The source tables of Node on the 6.2 path (storage/update/sql/table_update6_3.sql):

2. Batch X renames the 6.2 columns of _news, _pages, _faq, _help, _links, _files and _content to the 6.3 names the migration reads

   • sid, pid, fid and lid become id, catid becomes cid, hometext and bodytext become intro or body
   • ip_sender, date, totalvotes, totalcomments, associated and homepage take their 6.3 names
3. rencol leaves a table already in the 6.3 shape untouched, so the production path is unchanged
4. The installer session (public/setup.php):

5. session_start() runs only when no session is open, as core/security.php does

   • an open session (session.auto_start, a router) printed a notice before the JSON of every part of the run
   • the run then stalled and its first part read a config/db.php that did not exist (2002)
6. Tests (tests/Support/install_probe.php, tests/Unit/UpdateSiteTest.php, tests/SchemaUpdateValidationTest.php):
7. the update probe runs the second stage as the main administrator and reads the materials it made
8. UpdateSiteTest checks that the two news and the file of the 6.2 fixture become materials with intro and body
9. the seven source tables join _modules as legacy tables the schema file may name
10. Plan and reference (docs/7-SCHEMA-2026.md, docs/ROADMAP-2026.md, docs/NODE.md):

11. the decisions "Any 6.2 site migrates" and "The installer starts its session once", the result of batch 6, step 65 ticked

12. NODE.md no longer says that a clean 6.2 stops at the counter step

Benefits:

• A clean 6.2 site of the installer of 6.2 carries all seven old modules with comments, replies and resources
• The fresh installation passes NodeProfileTest again, on MariaDB 11.8, MySQL 8.4 and MariaDB 10.11
• The second stage of update.php is guarded by a test for the first time

Technical notes:

• Rehearsed with tests/Support/install_probe.php over table.sql and insert.sql of 6.2 on MariaDB 11.8, MySQL 8.4.6 and MariaDB 10.11.14: no failed statement in three runs, the schema equal to a clean installation

• UpdateSiteTest stays MariaDB only: MySQL 8.4 refuses the zero-date defaults of its fixture dump
• update.php is still not shipped; UPGRADING.md still says the release updates no 6.2 site