The settings page is brought to the bridge variant of the stand with the mechanics the theme already carries, and what the page taught is folded back into the cabinet: one box, one head, one form row and one file window for every page under the account. The screenshot rig, which was the slowest gate of the work, walks its two modes side by side and stops waiting for a page that could never settle.

Core changes:

1. Settings page (modules/account/index.php, partials/account-settings.html):

2. the lamps, the rail, the tiles, the save bar and the gallery follow set-10-bridge

   • the rail marks stand at even fractions of the width, the first flush left and

the last flush right, and the road walked is a width the script writes

• the lamps paint their figure in the tone of a category, warning through the new

--sl-warning-strong step, because the base step fails AA for large bold type

• a preset picked in the gallery saves itself over htmx through setavatar() and the toast confirms it; the form bar does not rise for a control that saved itself

• the journal tile and the profile ring are gone, the password tile takes the width

• getFieldsInRows() gives the extra fields as data, and getTplFieldsIn() is that list folded into form rows for its five other callers

• sixteen constants came and six went again: the hints under the questions and the heads of the tiles stay, the short rail captions did not

• Form rows (theme.css, base.css):

• the caption column of a form is one column per form: .sl-form and .sl-opt-tile lay fit-content(--sl-form-label-width) and minmax(0, 1fr), and a row standing directly in them takes subgrid, so the captions line up on one edge and the fields on another; a browser without subgrid keeps the quarter

• a row holding an editor folds on the mount point and no longer only after the script arrives, and a hint asks for no width of its own, so the caption column is not sized by either for the moments the parser stands on the editor scripts

• the track of an editor row has a floor of zero: a bare 1fr could not shrink below the toolbar and made every page with a comment form scroll sideways at 768

• Cabinet and profile (partials/account-home.html, account-profile.html, account-profile-feed.html, fragments/account-nav.html, theme.css):

• the panel of the cabinet and of the profile is the settings tile, and every heading is the tile head with the chip of tone, joined by selector list

• the inner pages carry the full-size cabinet tiles, each with its subtitle

• the activity feed's tabs wear the chip, the cabinet rows share the entry's metrics, and the hub of the profile is a scrolling feed of entries

• the spinning indicator freezes with any hovered feed, and the scroll walks translateY(-50%) of the doubled feed instead of a distance measured before the avatars had loaded

• the card and the deck wear the tile's box, the RSS field is the field, the empty badge is hidden, and a button carries a gap between its icon and its label

• Layout (layouts/app.html, home.html, theme.css):

• the layout names the sides it rendered on #container as sl-has-left and sl-has-right, and the CSS reads them instead of :has(#sidebar): the aside stands after the content, and a first frame painted before the parser reached it laid the content over the full width and then pulled it back

• File manager window (partials/file-manager.html in both themes):

• the window opened for a form field carries data-sl-window like the one opened from an editor: it drags, expands and stacks the same way; the two copies stay identical

• Screenshot rig (tools/ui-shots.mjs, tools/ui-shots.json, docs/TEMPLATES.md):

• the two modes of the manifest walk side by side in contexts of their own, a full capture takes about five minutes instead of ten

• --only takes a comma list, so a change is re-compared on the pages it touched

• the ticking counter of a live box is masked; it was why the article page never settled

• Stand (demo/fav-01..04, demo/assets/demo.js, demo/README.md):

• a fourth series proposes four faces for the favourites page out of the parts the cabinet already has: shelves, tabs, bays and the table told what it lacked

• Node plan (docs/node/*):

• the working list and the review of the package, and the plan documents adjusted after the review

Benefits:

• One box, one head and one form row across settings, cabinet and profile, and the two file windows become one

• Every cabinet page arrives without a layout shift; measured zero on messages, settings and favourites

• The rig costs half the wall clock and reports a page that moved instead of one that never settled

Technical notes:

• Two tokens join the API: --sl-warning-strong and --sl-form-label-width; the template-written --sl-d-at, --sl-d-of and --sl-d-spy are registered under data and --sl-d-distance leaves it

• tools/ui-contrast.json is regenerated from the walk after the palette changed

• The constants _ACCOUNT_LOG, _ACCOUNT_FILLNOTE, _ACCOUNT_LINKED, _ACCOUNT_SIGNIN and _ACCOUNT_GALLERY are removed; a theme or a language file that named them will not find them

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