The old main module with its slider and carousel gives way to a presentation module whose material lives under uploads/presentation/; the lite theme drops the slider assets. The etalon face of the stand gets real site names and categories, ratings from the thumbnail weight, an autoplaying shuffled strip, one veil treatment for every picture, a rail that follows the page, and radii, spacing and icon sizes snapped onto the theme ladders.

Core changes:

1. Presentation module (modules/presentation/index.php, config/modules.php, lang/*.php, blocks/img.php):
2. main is renamed to presentation in the module registry and the six language files (_PRESENTATION)
3. the screenshot block reads uploads/presentation/sites/thumb instead of uploads/screens/thumb

4. uploads/screens/* move to uploads/presentation/sites/*; brand materials and DNA bands join them under uploads/presentation/brand and uploads/presentation/dna

5. Lite theme (templates/lite/, tests/, tools/ui-*):
6. the main slider, carousel and their fragments, lib.js, the season and slide images are removed
7. the LCP preload keeps only the head-content case; the menu, footer and link fragments follow the new module name
8. the slider tests go, the template test points at menu.html; audit baseline, contract and contrast files are refreshed
9. Etalon block 12, sites (demo/22-dashboard-layout-etalon.html, demo/assets/twentytwo.css, demo/assets/twentytwo.js):
10. 71 cards carry the site name and a category read from the screenshot instead of the address
11. the rating is the thumbnail weight in twenty-byte steps, as the old main module counted it

12. no viewer on site cards; the strip autoplays, pauses under the pointer or focus, shuffles on every load, hides its own scrollbar and resets after the shuffle so scroll anchoring cannot drag it away

13. Etalon block 11, brand archive:
14. pictures fill the tile; logotypes and partner badges stay contain; caption on the image, open and download tools on top
15. the same veil and lifting filter as block 12; the veil also serves the DNA principles of block 10
16. Etalon page order and rail (demo/22-dashboard-layout-etalon.html, demo/assets/twentytwo.css):
17. voices and pulse move to the end, the numbers and the road rail follow
18. the rail loses its label and its search; short uppercase labels at 14 px spread from edge to edge with the track under them
19. the fill ends inside the current label, the rail scrolls the current label into view, anchors land below the sticky rail
20. the security log is born full so the section keeps one height and anchors below it do not drift
21. Etalon standard (demo/22-dashboard-layout-etalon.html, demo/assets/twentytwo.css, demo/assets/demo.js):
22. 192 radii and 481 spacing declarations snap onto --sl-radius-* and --sl-space-*
23. section number and icon share one 34 px height; card title icons and icon boxes grow to the control size
24. --sl-font-micro is 11 px inside the etalon; nothing on the page renders below that
25. the shared DEMO_SITES list carries the same names and categories for the other eighteen faces

Benefits:

• one module name and one upload path for the presentation material across the CMS, the theme and the stand
• the etalon reads as one system: one veil, one caption, one rail behaviour, one ladder for radii and spacing
• the strip and the rail behave deterministically instead of relying on browser scroll anchoring

Technical notes:

• uploads/screens/* are renamed, not re-added; uploads/presentation/brand/* are new binaries (34 files)
• three demo assets are normalised to LF as .gitattributes requires
• no schema, route or API change; index.php?name=main no longer exists, the module is presentation

The Phoenix collection of 2026-09-08 is removed whole and replaced by eighteen presentations of index.php?name=main that share one engine, deck.css and deck.js, and differ in page skeleton, first screen, chart mix and palette rather than in a preset. Six faces develop the leader 00-dashboard-layout.html; twelve reinterpret the dashboard references. A nineteenth face puts the leader into the chrome of the system.

Core changes:

1. Presentation engine (demo/assets/deck.css, demo/assets/deck.js):

2. One palette contract on .p-page, every token in both schemes through light-dark()

   • grid, cards, KPI tiles, tables, rings, bars, heat, logs, ticker, nav, rail, topbar, road, timeline,

calendar, showcase, voices, scenes

• One body of figures, DECK_DATA, and every moving part read from data attributes

  • canvas charts: area, line, spark, bars, hbars, donut, gauge, radar, candles, heat, with periods

and hover tips

• module registry table with search, header sort and section filters
• event streams, flicker figures, CSS bars, heat cells, calendar, written lists
• guard and cache switches, the guard court, the cache route, the PDO bus, walkers, scroll spy
• the real site header and footer fetched around a face unless the gallery opens it bare

1. Faces (demo/01-command-deck.html … demo/18-aeros-horizon.html):

2. 01-06 keep the leader's DNA in six compositions: command deck, observatory wall, ledger with a right column, cockpit with three gauges, one-column flow, module studio

3. 07-18 follow the references: RecehTok neon and exchange, Calltimes rhythm, Vaulto carbon and editorial, Hynex vital, Fobework campus, odds analytics, cyber sentinel, Rinesk lime, Aeros atmosphere and horizon

4. real facts stay fixed, illustrative figures are declared on every page
5. Laboratory face (demo/19-phoenix-laboratory.html, demo/assets/nineteen.css, demo/assets/nineteen.js):
6. the leader shown inside the chrome of the system
7. Stand chrome (demo/assets/demo.js, demo/index.html, demo/README.md):
8. the manifest names the scheme a face was designed in and the gallery opens it in that scheme
9. the README describes the engine, its attributes and the nineteen faces
10. Documentation (docs/CABINET-CONSOLIDATION-2026.md):
11. the finished consolidation plan is removed from the tree

Benefits:

• a new face is markup, a palette and v-* rules, never a script of its own
• eighteen pages cannot disagree about a figure
• both schemes are held by one declaration per token

Technical notes:

• nothing here ships: demo/ is the development stand
• no external resources; icons, photos and screenshots are local
• screenshots keep the two laws of the stand: 260 wide, never taller than natural

The six batches of docs/CABINET-CONSOLIDATION-2026.md land together. Every panel, tile, feed, hub and shelf of the cabinet opens with the same head fragment, every list row is the cabinet row, every fold runs through the toggle mechanic of slaed.js, every icon name PHP writes comes from one map, and the notices of the private-message and favourites pages stand in one slot. Nothing a reader does on these pages changes; what changes is that there is one way to build them.

Core changes:

1. One head (templates/lite/fragments/panel-head.html, theme.css, tools/ui-contract.php):

2. the fragment takes icon, title or title_html, title_id, hint, fold, chips, total_html and live_title and renders div.sl-profile-hub-head > h3 + span.sl-profile-hub-total

   • nineteen heads of three forms are replaced: the settings tile head, the hub head of the

profile and the favourites tiles, and the bare h3 headings of the cabinet home, the
profile panels and the activity feed

• .sl-opt-tile-head, .sl-cab-head and .sl-profile-head leave the CSS; the margin under a

head is contextual to the panel, the feed and the deck

• the shelf head carries fold, hint and its count chip; the profile head carries the

action dial and the share dial as total_html

1. One row (theme.css, fragments/privat-row.html, partials/account-profile*.html):

2. .sl-cab-row is the base; .sl-profile-entry is the modifier that opens the leading track for a date or a count chip; .sl-pmf-item is the modifier of the message row with its own tracks, padding and states

3. .sl-profile-info-row stays a component of its own, a label beside a value
4. .sl-cab-row.sl-profile-hub-row takes the hub-row height the shadowed rule never reached
5. One fold (fragments/privat-focus.html, core/user.php, theme.css):

6. the focus deck folds through data-sl-toggle under the shared head, with the chevron pair and a remembered state; the deck reopens as flex through data-sl-toggle-display

7. the seven summary rules of the details are gone and no <details> is left in the theme

8. One icon map (core/system.php, core/user.php, core/admin.php, modules/account/index.php, admin/modules/modules.php, tests/Support/contract_probe.php):

9. getIconName() beside getModuleName() maps module keys and concept keys to Bootstrap Icons glyphs, falls back to the module config and then to puzzle

10. eighty-two 'icon' => literals in core, modules and admin read the map; getFavoriteIcon() is removed; the glyphs of eleven pages are the same before and after

11. Small safe ones (fragments/opt-lamps.html, fragments/cabinet-notes.html, core/user.php, modules/account/index.php, partials/account-*.html, theme.css):

12. the lamp row of the settings and favourites pages is one fragment; a non-meter lamp carries its value in title

13. the rail chip is the ordinary flex chip again with its label in a span that ellipsises; the block variant and its hand-set icon margin are gone

14. addPrivateMessage() passes one error as a string, an array is for several messages

15. the notice slot is #cabnotes through getCabinetNotes(); the favourites page prints it under the nav, and an emptied list answers the slot out of band instead of an alert in the list

16. Clean-up (core/helpers.php, fragments/pager.html, lang/.php, admin/info//ru.md, tools/ui-audit-baseline.json):

17. the pager summary reads "Страница P из M. Всего: N" through _PAGE, _NUMOF and _OVERALL on every lite pager; _BY and _PAGE_S leave the six locales

18. three duplicate allowances of the contract that named removed rules are dropped
19. the help of private messages and favourites describes the pages as they are
20. the audit baseline is stored: scoped 92 to 89, nothing grew

Benefits:

• a new cabinet panel is a head include and cabinet rows, not a third markup
• theme.css is 62 lines shorter and the head, row and fold rules live in one place each
• an icon is renamed in one line for the whole site and the panel

Technical notes:

• the settings tile head is an h3 now, with the same id for aria-labelledby

• every head has a 34 px floor, so tile and panel heads grew by 8 px; the hub head takes the panel margin and the hub row is 46 px, as its token always said

• the pager data no longer carries by, page_s, perpage or pages; page_label and page_of replace them

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