Two work plans join docs: SETUP-2026 carries the installer of 8.0 in eight batches, of which the schema move, the 6.3 update in update.php and the texts have landed; FILES-2026 plans the closed delivery of forum and message files.

Core changes:

1. Installer plan (docs/SETUP-2026.md):
2. decisions, traps found before the plan, batches with their checks and what each landed batch taught
3. File plan (docs/FILES-2026.md):
4. the closed delivery of forum and private message files, archive links turned into attachments

Benefits:

• Every next run of the installer work starts from the table of batches

Technical notes:

• Both files are deleted by the last batch of their plan

The coming setup.php speaks through 57 constants of the scope SETUP in admin/lang and reuses the globals that already name its words, so the installer and a later update module share one dictionary.

Core changes:

1. Installer texts (admin/lang/*.php):

2. titles, step counter, leads, field labels and hints of the seven stops

   • the Russian wording comes from the stand face demo/setup-09-motion.html and its run rows

3. check and run notes, the refusals of a wrong prefix, panel name, old server, taken prefix, pending journal and an installed site

4. _DELSETUP now names a setup.php that should have deleted itself

Benefits:

• No word of the installer is defined twice: language, site, administrator, password and the buttons reuse globals

Technical notes:

• The constants follow _SESS_T, the six files stay parallel line for line
• They are unused until setup.php is written

A rehearsal of update.php on a copy of the production site found that migrated images rendered as #, that every directly linked file sat twice in the upload folders, that links from the forum and private messages pointed into folders Node closes, and that an attachment in a comment of a Node material answered 403. The migration and the attachment route are fixed, and the stand configuration follows the migrated production data.

Core changes:

1. The migration (update.php):

2. A file has one place: the type folder holds what materials and their comments use, the archive what the site links to directly; a file that is both is copied, a file nothing uses stays outside the site in the working directory

   • getMigrateKeep() lists the attachments of texts, help replies and comments and the local file of every resource
   • setMigrateFile() moves or copies one file, deleteMigrateTree() removes the emptied working folders

3. setMigrateOuter() points the direct addresses of the forum, comments, private messages, newsletters, blocks, signatures and polls at the archive, once, before any file leaves the working directory

4. getMigrateLocal() gives a bare relative [img] or [url] target ./, the local form the safe parser accepts; a rewritten archive address is written as ./uploads/archive/... unless it is absolute or rooted

5. Entity-quoted attributes of old HTML are decoded before conversion; [img alt=...] is recognised
6. Only release guard files stay in a stashed folder, so an old empty placeholder no longer blocks the new type

7. Attachments of comments and help replies keep their tag under the managed name, so a private help request keeps its files private

8. Attachments of comments (core/user.php, core/system.php, core/classes/comment.php, core/classes/node/service.php, modules/node/index.php):

9. A comment of a Node type renders with the id of its material, in the list and in the answer of an edit

10. NodeService::getNodeFile(..., Comment $com) grants the names the published comments of the material carry, every comment not deleted for a moderator, once the material itself is readable

11. Comment::getAttachTexts() reads those bodies, so the comment table stays behind its class

12. The preview of a fresh upload is open to whoever the upload rule of the type lets upload; ownership is checked as before

13. Theme links (templates/lite/partials/menu.html, site-footer.html):
14. The menu and the footer link to docs instead of the removed pages
15. Tests and reference (tests/Support/node_probe.php, tests/Unit/NodeServiceTest.php, docs/NODE.md, docs/VERSIONS.md):
16. Published, pending, deleted and closed comments, and a name asked through another material or type
17. The migration steps, the attach route and the versions of 2026-10-01
18. Stand configuration (config/fields.php, modules.php, node.php, ratings.php, uploads.php):
19. The types, field definitions and upload and rating rules of the migrated production data

Benefits:

• Migrated texts show their images and links on a site of any root
• One copy of each file; private help files stay behind the rights of their request
• A user can attach a picture to a comment of a material again

Technical notes:

• getNodeFile() takes the comment service as a new required argument
• The shipped config stays the stand configuration, as in the previous configuration commit
• config/security.php is not part of this commit: its only change is the secret of the stand

Two inline edits exist - the forum post and the comment - each with its own route, both losing the typed text on a refusal and letting the last write win, while Node has none at all. The plan replaces both with one protocol that Node joins; its batch 0, the forum rights, has landed.

Core changes:

1. Versions (docs/VERSIONS.md):

2. 2026-09-30: the migration of the removed modules into Node with its 301 addresses and the look of the old modules, the escaped code blocks, the forum rights, the thumb burst and the category descriptions

3. The quick edit plan (docs/QUICK-EDIT-2026.md):

4. One QuickEdit protocol over three kinds - node, forum, comment - with an adapter per kind for the source, the write and the view, all read from the stored row

5. A stamp for optimistic locking without a schema change: the version of a node, a hash of the text and its edit time for a post and a comment

6. Two strict routes, getQuickEdit on GET and updateQuickEdit on POST, one status per refusal
7. One fragment and one script: cancel without a request, the typed text kept on a refusal, a conflict window
8. NodeService::updateNodeText() for moderators at any time and for the author within the window of the type
9. Batches 0 to 5; batch 0 is done, the forum trust mode stays an open decision

Benefits:

• The history of the day is readable without the diff
• The next step of the quick edit has a written contract to be measured against

Technical notes:

• The plan file is removed by its last batch, which moves what lasts into docs/ARCHITECTURE.md

The quick edit, the full edit, the reply, the deletion and the moderator actions of the forum read their rights from the category the request named. The moderator of one category could therefore edit, delete, close or move the posts of every other one, which a live request against the stand confirmed before this change.

Core changes:

1. Two rules every handler takes (core/user.php):
2. getForumPlace(int $id) reads the category, the topic with its status and the author of a post from its rows

3. checkForumRight(bool $mod, bool $may, int $uid, int $stat = 3) is the one right over a post: the moderator of its category, or its signed-in author with the category right while the topic is open

   • a guest never matches a post written without an account, which a category open to guests allowed

4. updatePost() takes both, ignores the category of the address, and echoes its refusals instead of returning them into a route that discards them, which left an empty body on the page

5. The handlers of the module (modules/forum/index.php):

6. add(), send() and delete() take the category and the topic of a named post from its row; only a new topic takes the category of the form

7. A reply always answers the topic of the post it names and needs the reply right; the topic right alone used to insert one

8. move() acts only on the topics stored in the moderated category; delete() loses its category argument
9. The edit and delete buttons of view() ask checkForumRight(), so the view never offers what the handler refuses
10. Tests (tests/Unit/ForumRightTest.php, tests/Support/contract_probe.php):
11. The probe forumright compares the place with live rows and asks the right as a guest and as an account
12. The handlers are pinned to getForumPlace() and checkForumRight()

Benefits:

• A category moderator is a moderator of that category and nothing else
• One rule decides both the buttons and the writes

Technical notes:

• Behaviour change: guests no longer edit or delete anonymous posts, authors see no edit button in a closed topic, and a reply without the reply right is refused

• The addresses keep their cat parameter; it no longer decides a right
• Batch 0 of docs/QUICK-EDIT-2026.md