Step 76, batch 0 of docs/11-UPDATE-2026.md: the two open questions are answered by the owner after probes on the stand and the console, and the baseline of the suite is recorded. A site without sodium or zip still receives every release, and a release no longer overwrites the sitemap and robots.txt a site writes for itself.

Core changes:

1. Decisions (docs/11-UPDATE-2026.md):

2. Without sodium the core verifies the signature with a bundled paragonie/sodium_compat, loaded only when the extension is missing; signing stays on real sodium

3. Without zip the archive is read by PharData; Update walks the central directory itself and applies every refusal to the raw names, the same for both readers

   • PharData drops ../x and /x silently, loses the symlink mode and throws on a backslash, so its names prove nothing

4. The nginx access log of slaed.net goes without the query string for /api/v1/master/, so the privacy note keeps its promise

5. public/sitemap.xml leaves git; public/robots.txt is a site file in files.json, placed only when missing
6. The whole tree ships; nothing beyond the named export-ignore entries leaves the archive
7. Plan sections and steps (docs/11-UPDATE-2026.md):
8. The client, the refusals, the privacy, the help and the tests follow the decisions; steps 3, 6 and 10 carry them

9. "Open questions" becomes "Probes of step 0": stand extensions and opcache, write rights and one device, the speed of sodium_compat, PharData on the tree archive and on hostile entries, the archive size, the suite baseline

10. Roadmap (docs/ROADMAP-2026.md):
11. Step 76 is closed with its decisions

Benefits:

• A site on a host without sodium or zip is not left blind to updates forever
• One set of refusals holds whichever reader opens the archive

Technical notes:

• Plans only; no code, theme or schema change
• Baseline: full phpunit green, 1849 tests, 24477 assertions, 14 skipped

A site learns of an update only by code it already has, so the updater is planned before the release: docs/11-UPDATE-2026.md designs signed releases, the module master on slaed.net and the core page "Обновления", and roadmap steps 77-87 carry it. The admin stand shares the sound engine and the Phoenix scene with the labs.

Core changes:

1. Update plan (docs/11-UPDATE-2026.md, docs/ROADMAP-2026.md):

2. The owner's decisions of 2026-10-15: Ed25519 offline signature, primary and recovery keys, GitHub Releases first and slaed.net second, a full archive and a delta, installation in steps with rollback and rescue

   • the master is the module master, kept in the repository and out of the release archive
   • settings get missing options added, languages and the themes admin and lite are replaced whole
3. Roadmap steps 77-87 are the batches 0-10 of the plan; Close moves to step 88
4. Connector and entry (docs/2027-CONNECTOR.md, docs/2027-VINE-MONITOR.md, docs/ARCHITECTURE.md):
5. The API is the branch /api/ of public/index.php instead of an own public/api.php
6. Steps 1-2 of the connector and the service update move into the update plan; the connector starts at step 3
7. Ideas after the release (docs/2027-IDEAS.md):
8. Numbered raw ideas: automatic security fixes, a public "SLAED in numbers" page, error reports by consent
9. Admin stand (public/demo/admin/*, public/demo/assets/sound.js, public/demo/assets/phoenix-scene.js):
10. The sound engine window.slSound leaves the sound lab for a shared file; the admin stand plays its sounds

11. The Phoenix scene and its rest timer window.slPhoenix move into their own file; the admin stand runs the screensaver after a rest

    • public/demo/phoenix.html, public/demo/snd-01-lab.html and public/demo/assets/phoenix.js load the shared files

Benefits:

• Every 8.0 site can receive 8.0.1 without its owner visiting slaed.net
• One sound engine and one Phoenix scene for every stand page

Technical notes:

• Plans and stand pages only; no core, theme or schema change

Version 1.0.4 of the presentation package. The headings, the texts and the captions take the brand face Magistral instead of Segoe UI and the monospace face, which stays only where code is shown, and the six videos are rendered again from the browser frames with the new face.

Core changes:

1. Face (public/phoenix/vendor/base.css, public/phoenix/player/styles.css, public/phoenix/index.html):
2. base.css gets the token --sl-face-body, Magistral with Arial and sans-serif behind it

3. The stage, the header, the kicker, the archive captions, the continuity row, the editor head, the build bar, the modules, the technology row, the HUD, the history and the controls use --sl-face-body

   • the code of the editors and the continuity listings keep --sl-face-mono
4. index.html stamps base.css ?v=2 and styles.css ?v=4
5. Technology row (public/phoenix/index.html):
6. Every item of the final row carries its Bootstrap icon: release, PHP, MariaDB, core, light and dark
7. Videos (public/phoenix/exports/*.mp4, public/phoenix/presets/production/video-fullhd.json):
8. The dark and light videos in 1080x1920, 1920x1080 and 720p are rendered again with the new face
9. The production preset records the faces and their WOFF2 files
10. Package (public/phoenix/manifest.json, public/phoenix/checksums.json, public/phoenix/README.md):
11. Version 1.0.4 of 2026-10-14; checksums of the changed files

12. README says the texts are set in Magistral, the marks use Bootstrap Icons, and both WOFF2 files match the originals of the lite theme byte for byte

Benefits:

• The presentation speaks in the face of the brand, in the player and in every video

Technical notes:

• The WOFF2 files were already in the package; nothing new is loaded
• No change outside public/phoenix/

Batch 8 of docs/10-URL-2026.md (roadmap step 75): what lasts of the plan moves into the reference, the help of the panel and of the modules, and the plan is deleted. A live check of every address and every printed link on Apache (root on public/ and on the project) and on nginx found a redirect loop, a served dot file and a hard-coded link; all three are fixed.

Core changes:

1. Reference (docs/ARCHITECTURE.md, docs/NODE.md, docs/TEMPLATES.md, docs/VERSIONS.md, docs/TESTS.md, README.md, UPGRADING.md):

2. docs/ARCHITECTURE.md gets "Address Boundary": the address table, the registry _routes and the class Route, the name, when an entity gets and changes its path, migration, parsing, building and the one redirect

   • the bootstrap, the routing keys, the front controller and "What Not To Assume" follow it

3. docs/NODE.md: the permanent type name, Route::checkTypeName(), "Addresses" of a type, the paths of the writers, page in place of num, the 301 of setSeoMove(), the canonical and href on paths

   • the operation attach, which getNodeOps() no longer has, leaves "Public routes"
4. docs/TEMPLATES.md: {{ root }}, the key route of setHead() and "Links In Templates"

5. docs/VERSIONS.md records the addresses of 2026-10-14 with their breaking changes; UPGRADING.md gets "Readable Addresses"; README.md the routing and the cut of the path; docs/TESTS.md the five Route tests

6. Help of the panel and the modules (admin/info//ru.md, modules//admin/info/ru.md):
7. config: page addresses and canonical, 301 and 410, where forcessl and forcehost act
8. security: dot files refused, DirectorySlash Off in the project mode, the front controller required
9. editor, scheduler: the front-controller rule must stay, the sitemap task writes the Sitemap line
10. privat, search: /account/privat/123 and /search; template: {{ root }}

11. categories, node, voting: the field Address; account: a new login moves the profile address, the OAuth redirect URI keeps its query form on purpose

12. Servers (.htaccess, public/.htaccess, nginx.conf.example):

13. The project .htaccess turns off DirectorySlash, which sent /docs to the folder docs/ of the project and back to /docs in an endless loop when the document root is the project

14. public/.htaccess and nginx.conf.example refuse every dot file or folder but .well-known/; nginx served /.htaccess with 200

15. Theme (public/templates/lite/partials/site-footer.html):
16. The ideas button links the path of its forum section instead of forum?cat=95, which answered 301

17. Plan closed (docs/10-URL-2026.md, docs/ROADMAP-2026.md, tests/Unit/Route*Test.php, tests/Support/registry_probe.php, docs/2027-CONNECTOR.md, docs/2027-VINE-MONITOR.md):

18. The plan file is deleted, step 75 ticked; the tests and the 2027 plans point at "Address Boundary"
19. Connector plan (docs/2027-CONNECTOR.md):

20. Full, safe administrator access for AI agents over MCP (owner, 2026-10-14): off by default, a risk class per action with an owner-set policy, short-lived keys, a fixed list of actions no agent gets, an audit trail

    • api_client gains aid and policy, the table api_confirm holds confirmations, config/api.php the key risk
    • a confirm policy answers input_required; a user key stays draft-only

Benefits:

• The reference and the help describe the addresses as they work, with nothing left in a plan
• Apache with either document root and nginx give the same answer to every address

Technical notes:

• Live check: route matrix 57/57 and about 890 printed links on all three configurations, no relative address, no link answering 301, no missing-route warning in the log

• The stand's nginx file .osp/nginx/slaed.loc.conf (outside the repository) got the same dot-file refusal

• Breaking: a dot file in public/ is no longer served; a server whose document root is the project needs DirectorySlash Off, which the shipped .htaccess carries

• No code or schema change besides the server files and one template link

Batches 3 and 4 of the plan of readable addresses before 8.0 (steps 70 and 71 of docs/ROADMAP-2026.md). The migration and the installer give every entity due an address its first path, a request at a path is cut before the database and resolved after it, and the builders of the core print addresses from the root of the site, so a page opened two segments deep finds its styles, scripts and links. The links still read index.php?...; building, the literals and the redirect follow.

Core changes:

1. Migration (core/system.php, public/update.php, public/setup.php):

2. addRouteBacklog() gives types, categories before materials per type, forum sections, topics, users and polls without a module their first path, oldest id first, 500 per transaction; a second call adds nothing

   • A material is due when Published, Disabled or Deleted with published <= NOW() in a type whose ext is not support
3. The second stage of update.php runs it as setMigrateRoutes() on every run and keeps the counts in the manifest
4. setup.php runs it after the Node profiles, so the seed of insert.sql gets its paths
5. Parsing (core/security.php, public/index.php, core/classes/route.php):

6. The block of retired addresses keeps up to five segments of [A-Za-z0-9_-] of a path of index.php in $urlroute, with the flag bent for upper case, a trailing slash or /index.php/ in front; anything else answers 404 before the database, and a path after the script naming only the script keeps its 301

7. public/index.php resolves the segments by one grammar: a type or module is its home, a reserved operation its op, digits after it the id, any other path the registry; a former path opens its entity marked to move, a gone path answers 410, an unknown one 404; the keys replace the same keys of the query in $_GET

8. Route::isRouteReserved() gives a module without a switch no operation instead of those of a Node type
9. getVar() reads a scalar from $_POST and $_GET, so the keys of a path reach every reader

10. Addresses from the root (core/system.php, core/stream.php, core/classes/template.php, core/classes/access.php, core/classes/parser.php, core/classes/editor.php, core/user.php, modules/account/index.php, modules/forum/index.php, modules/node/index.php, public/plugins/editors/toastui/driver.php):

11. HOME_PATH is the path of homeurl with both slashes; the installer and the first stage of update.php take the folder of their script

12. getSeoUrl(), Template::getAssetUrl(), getUploadUrl(), FileAccess::getFileUrl() and the image check of Parser answer from the root; setRedirect() puts the root before a relative target

13. getPublicUrl() also takes an address of the site as a string and answers an absolute one as it is; the canonical address, the feed item and the images of a profile, a topic and a material go through it

14. getImgText(), the image check of Parser and the feed take the root off an address before they use it
15. Three checks of an existing asset ask for ?v= instead of comparing the address with its file

16. Tests (tests/Unit/RouteParseTest.php, tests/Support/route_probe.php, tests/Support/install_probe.php, tests/Unit/UpdateSiteTest.php, tests/Unit/NodeProfileTest.php, tests/Unit/InputVarContractTest.php and others):

17. route_probe.php parse: every row of the decided address table as a path, the grammar, the cut, the keys of a path over those of the query, and a page two segments deep linking its assets from the root

18. The rehearsal of update.php on the clean 6.2 holds the whole registry of the fixture; a clean installation holds the paths of its seed; getVar() scalars are driven from CLI

19. The expectations of assets, uploads, the file route and Node links read from the root; the bootstrap defines HOME_PATH

20. Plan (docs/10-URL-2026.md, docs/ROADMAP-2026.md, docs/PERFORMANCE.md):

21. Batches 3 and 4 recorded; addresses from the root decided by the owner; the batch of the literals runs before the redirect

Benefits:

• A path such as /news/internet opens its page with styles and scripts while every 6.2 address keeps working
• The migrated production base and a fresh installation start with one current path per entity

Technical notes:

• No schema change; the stand's registry was filled once by a direct call of addRouteBacklog()

• Breaking: getSeoUrl(), Template::getAssetUrl(), getUploadUrl() and FileAccess::getFileUrl() answer addresses from the root of the site (/index.php?..., /templates/..., /uploads/...) instead of relative ones

• Breaking: getPublicUrl() accepts array|string; setRedirect() roots a relative target

• Breaking: getVar() no longer reads scalars through filter_input(), so a value the core writes into $_GET or $_POST is read

• Literals of templates, scripts and PHP stay relative until the batch of the links; a page at a path still misses the theme images and the pseudo-cron below the path