Every document of the node design moves from a frame to an approved state. The status table of the directory turns from a list of open questions into a list with nothing left blocking approval, and the fifteen documents behind it are filled in to match.

Core changes:

1. Directory status (docs/node/README.md):
2. the plan reads "planning finished, implementation not started"
3. every one of the fifteen documents is marked approved, with no blocker left
4. document 12 is renamed to the boundary of the old data rather than its transfer
5. Contracts filled in:
6. 05-core-api.md: the public contracts and their signatures
7. 06-types.md: the type, field and capability model
8. 03-database.md: the extension tables and the remaining lifecycle transitions
9. 02-naming.md: the names of the remaining classes, methods and lang constants
10. 13-testing.md: what each layer is held by
11. 15-decisions.md: the log grows with the decisions the rest of the pass took
12. The remaining documents follow the same pass:

13. goals, code structure, routing, rendering, integrations, extensions, security and performance, migration boundary and roadmap

Benefits:

• The plan can be executed without reopening the questions it was written to close
• The decision log carries why each answer was chosen, not only what it is

Technical notes:

• Documentation only; no code of the subsystem exists yet
• Written in Russian, as the rest of this directory is

Take the file manager out of the editor plugin and make it the one way the whole system asks for a file. A form row no longer carries a bare file field: it carries a button that opens the same window an editor opens, and what was picked comes back as a chip. The storage of already uploaded files becomes reachable from every place a file is asked for instead of only from inside an editor.

Core changes:

1. Upload places (core/system.php):

2. getUploadPlaceRule() resolves one rule for one place, named with a dot

   • the grammar ^[a-z0-9_]+\.[a-z0-9_]+$ lives here and in no caller
   • three branches: <mod>.attach, files.dist, users.avatar
   • answers every field the routes read, not only the limits
   • the upload right is two settings ANDed: upload && add, upload && addquest
   • users.avatar is a member place: guestupload and guestfiles are hard zero

3. mod is the module a place is moderated as, never the first segment: users.avatar answers account, and no caller splits the place string

4. ops names which of the four routes a place permits; a field place permits editorFiles alone, so a form place can never reach an upload or a deletion

5. getUploadFileArea() replaces getEditorFileArea() and is built from the rule
6. getUploadTakenFile() resolves one client path for both form handlers
7. getUploadPlaceView() answers the module, the rights and the extension list
8. Place routing (index.php, plugins/editors/toastui/driver.php):
9. the go=4 entry guard reads place, raw: filterVar() empties a string with a dot
10. getEditorRouteRule() gates on ops beside its three existing guards

11. every endpoint URL carries place instead of mod, built server side, so both ends of the contract migrate in one step and no shim is needed

12. The window becomes the theme's (core/helpers.php, templates/{lite,admin}):
13. getFileManagerWindow() builds it from the place rule, in either mode

14. getFileManagerField() builds the row: the button, the chip and the three hidden carriers the submit takes to the handler

15. partials/editor-toastui-files.html becomes partials/file-manager.html

16. the window rules move from assets/editors/toastui/skin.css into theme.css under the new root sl-fm-win; the administrative browser owns the bare sl-fm-* names, so the window stays scoped rather than unscoped

17. the shot panel rules move with them: getWindowShot() is already system-wide
18. fragments/file-input.html is deleted; fragments/file-field.html replaces it
19. The runtime leaves the plugin (plugins/system/filemanager.js):

20. editor-upload.js becomes plugins/system/filemanager.js and is delivered by getFileManagerWindow() once per request, so a page with no editor behaves

21. addField(id, node, opt) is the second entry: a box instead of an editor

22. the eleven draw templates the runtime needs move to file-manager-templates.html; the four emoji ones stay with the driver

23. SlaedToastUi keeps tags, emoji and the word lists; editor-tags.js calls the new namespace explicitly and no alias is created

24. The two callers (modules/files/index.php, modules/account/index.php):

25. both read the three outcomes in a fixed defensive order and resolve a stored path through getUploadTakenFile(), which refuses it unless the owner matches

26. the catalogue passes getEditorFileOwner() and never the integer user id, which used to turn every guest token into zero and match one guest against another

27. the avatar keeps plan 2's arbitration: a preset beats anything the window produced, and an avatar failure does not roll back the profile

28. Tooling and tests:

29. tools/upload-route-check.php walks the new place routes; its merge deletion is verified rather than assumed, and the master secret is re-read per call while the last non-empty value is held

30. tools/ui-contract.php follows the rules into the theme

Benefits:

• One door: adding a file is one gesture everywhere, and stored files are reachable from every place a file is asked for

• One rule per place instead of a rule assembled by hand in each module, so a limit and a right are answered in one file and read the same before and after

• The server refuses what the interface does not draw: an interface that draws no button is not a guard, and the ops gate is enforced in one place

• Guest uploads are isolated per session instead of sharing the owner segment 0

Technical notes:

• Breaking: the editor endpoints take place=<mod>.<slot> and no longer accept mod=<mod>; a dot cannot travel through filterVar(), which is why the parameter is new rather than widened. Both ends are built server side and migrate together

• Breaking: _FILE_USER, _AVATAR_USER and _EDITOR_ADD are removed from lang. The first two lost their callers with the rows they captioned; the third was a scoped duplicate of the global _ADD, identical in all six locales

• Breaking: templates/{lite,admin}/fragments/file-input.html is deleted. A theme or module calling it must move to file-field.html through getFileManagerField()

• sl-toastui-upload survives as a second class on the window: it cures the fixed button height the vendor root imposes and belongs where the vendor is

• data-editor is deliberately not renamed: it is read by five producers and a template-only rename would break the editor silently

• Files stored before this change keep the owner segment 0 and are listed to nobody; they are not migrated, which is the correct failure direction

The crawl fails on this stand before any edit, and the record of that was deleted with the plan that measured it. A future reader would meet a red gate and look for the cause in their own work.

Core changes:

1. Label crawl (docs/TEMPLATES.md):

2. the failure is coverage, not violations: 366 stored against 365 rendered

   • three route variants no longer answer, two of them record-bound
   • proved by stashing a whole batch and running the same audit on the committed tree
3. and a warning not to --store over it, which would adopt a regression as the floor

Benefits:

• A red gate that is not yours is recognisable in a minute instead of an hour

Technical notes:

• Documentation only; the loss itself is untouched and still wants an investigation

A sixteen part plan for the content subsystem that is meant to serve several material types at once and retire the same-shaped modules one by one, without growing a second CMS inside SLAED. Status is design; no implementation has started, and nothing in the tree reads any of it yet.

Core changes:

1. Plan set (docs/node/):
2. README names the reading order and the status

3. goals, naming, database, code structure and the public core API

   • types, fields and settings; routing; rendering
4. integrations with SLAED, type extensions, security and performance
5. data migration from the modules being replaced, testing, roadmap
6. a decision journal, so a settled question is not reopened by the next reader

Benefits:

• The design is arguable before it is expensive, while it is still only prose
• A decision journal keeps the reasoning with the plan instead of in a session

Technical notes:

• Documentation only; no code, no schema, no route and no configuration change
• Written in Russian, as the working language of these plans

A member who had once saved a site theme was served an admin panel built from partials no site theme carries, so the login form did not render at all and the log filled with a template-not-found warning. The name reached the cookie from a default the code wrote in as if it were a decision.

Core changes:

1. Theme resolution (core/system.php):

2. getTheme() ignores the member's theme once ADMIN_FILE is defined

   • the panel forces its own theme at bootstrap and the account cookie may not take it back
   • the constant is read only where it is set before the bootstrap, which is the panel entry point
   • index.php declares the same constant for its admin endpoints, but long after this answer is cached
3. Cookie writes (modules/account/index.php):

4. savehome() and savepass() write the theme the member chose and never the site default

   • an empty slot means no preference, which every reader already resolves for itself
   • a name written in now means a decision, which is what the database column already held

Benefits:

• The panel is reachable again for every member who ever picked a theme
• The cookie and the users.theme column stop disagreeing about what empty means

Technical notes:

• No schema change; the column already stored an honest empty string
• Backward compatible: a cookie carrying the old default resolves to the same theme