The browser check of every form before 8.0 ran the panel shell, the site for a guest and a user, the content of the site, the forum with the small modules and the content of the panel on the stand. Each defect it met is fixed in its source function: empty titles and bodies are refused before any write, URL fields no longer start with a bare scheme the browser refuses, rights follow the section they belong to, and the forum counts and titles itself once.

Core changes:

1. Panel shell (admin/index.php, admin/modules/admins.php, public/index.php):

• setAdminOption() refuses an unknown editor instead of storing the default in its place
• The administrator form keeps the stored name, as no loop of the form reuses $name, and starts its URL empty
• go=5 lets a delegated administrator refresh getUserSessionAdminInfo of the admin block

2. Site and cabinet (modules/account/index.php):

• The private rows and the admin menu of a profile need the right account, not any administrator
• An empty feed address of the cabinet is answered with _RSS_PROBLEM, not with nothing
• A saved profile returns to its form with _SUCCSAVE

3. Comments (core/user.php, core/classes/comment.php, modules/node/index.php, docs/NODE.md):

• A moderator is no longer told that his comment waits for a check
• The public form of a material carries no comment mode, so a moderator who sends it gets CommentMode::Open
• Comment::updateBody() refuses an empty body with _CERROR1, as every other edit path does

4. Forum (modules/forum/index.php, modules/forum/admin/index.php, modules/forum/admin/info/ru.md):

• The page titles are given to setHead() as title and ctitle and joined once by getHeadTitle()
• A new topic counts topics+1 only, as delete, move and updateForumSync() count it
• The final delete of a topic takes back the comment points of its replies
• The first tab of the section is _HOME on all three tabs; the help names the sync, the counting and the recycle forum

5. Categories (admin/modules/categories.php):

• addsave() and save() refuse an empty title with _CERROR before the Node writer or the SQL of the forum

6. Node in the panel (modules/node/admin/index.php, modules/node/admin/info/ru.md):

• "Добавить" no longer offers a type of the extension support and its op=add answers 404, as a request is made by a user on the site and the panel keeps it through its card; the help says so

7. Users in the panel (modules/account/admin/index.php):

• A new user starts with an empty site, so the field of type url no longer holds the form

8. Tests (tests/Unit/AdminGuardTest.php, CommentTrustBoundaryTest.php, CommentStateTest.php, FeedTest.php, NodeServiceTest.php, NodeSupportTest.php, UploadIntegrationTest.php, tests/Support/contract_probe.php):

• Each fix is held by its suite; the contract probe saves an empty body by the moderation path and expects _CERROR1

Benefits:

• A refused input writes nothing and says why, on the screen that took it
• The rights of a delegated administrator follow the section it holds

Technical notes:

• No schema, URL or API change; the stand keeps only the traces of the checks
• RouteParseTest still expects the forum title "Форум Talk - Форум" for forum/talk, while getHeadTitle() now gives "Talk - Форум"; its expectation is the next step of the plan

The check "Ошибки PHP" of the home lamp summed error_php.log, error_site.log and error_file.log, and the site journal writes every 404 and 403 at the level error, so the bots probing for files kept the lamp red on a site with no fault; its row led to the monitor, whose own lamp has no error check, so the errors seemed gone after a click. Each journal is now its own check under its true name and opens itself, and a miss of a visitor is no failure.

Core changes:

1. Error count (core/monitor.php):

• getErrorLogCountHours() skips a line whose http_code is under 500, on the lamp and in the count of the monitor
• getSystemSignals() answers sixteen checks: "Ошибки PHP" counts error_php.log alone, the new "Ошибки сайта" and "Ошибки файлов" count error_site.log and error_file.log, each warning from one a day and failing from a hundred
• The four error checks link to logs&op=logview with their journal instead of the monitor and the database tool

2. Database connection (core/classes/pdo.php):

• A refused connection is written by Logger::addSql to error_sql.log instead of the site journal
  • The SQL error checks of the lamp and the monitor and the es figure of the update check now count it

3. Language (admin/lang/*.php):

• _ADM_SIG_SITE and _ADM_SIG_FILE in the six locales

4. Help, docs and demo (admin/info/monitor/ru.md, admin/info/panel/ru.md, docs/ARCHITECTURE.md, docs/TEMPLATES.md, docs/VERSIONS.md, public/demo/admin/admin.js):

• Sixteen checks, the thresholds of each error journal, what is not counted, and the journal each row opens
• The demo lamp lists the two new checks and the new links

5. Tests (tests/Unit/CockpitTest.php, tests/Support/cockpit_probe.php, tests/Unit/JournalNameTest.php, tests/Unit/NodeProfileTest.php, tests/Unit/ApiEntryTest.php, tests/Support/route_probe.php):

• CockpitTest holds the sixteen keys and the thresholds of the site and file errors
• JournalNameTest holds that a 500 counts and a 404 or 403 does not
• NodeProfileTest expects the refused connection of the installer in error_sql.log
• The entry run of route_probe counts the refusal of its lost database in error_sql.log and takes it out, so ApiEntryTest holds it written once while the requests still write no other SQL error

Benefits:

• The lamp fails only on a fault, and every row says what broke and leads to its record

Technical notes:

• No schema, URL or API change; the journals and their lines stay as they are
• The SQL error figure an installation reports grows by its refused connections

The content of the block "Администрация" is written in the Markdown editor since the move away from BB, but its own links were read from <a> tags alone, so a link typed in the editor never showed, and the move of the production texts left the old link as plain text. The block now reads both forms, lets a link name the site, its host and its panel file instead of a fixed address, and keeps its links at hand without the floating menu.

Core changes:

1. Own links (core/system.php):

• getAdminBlockLinks() reads name of Markdown beside the <a> tag, in the order written
  • An image is no link; a hint is optional and falls back to the name
• [homeurl], [host] and [admin] in an address or a hint become the address of the site from its setting, its host and HOME_PATH with the panel file of $afile, so a section link holds on a site whose panel is not admin.php

2. Panel layout (core/admin.php):

• The block stands on every page of the panel while the floating menu is off (dock-off), on the home as before

3. Help and docs (admin/info/blocks/ru.md, admin/info/panel/ru.md, docs/ARCHITECTURE.md, docs/VERSIONS.md):

• The help of the blocks shows how a link is written and what the three marks become
• The help of the panel and ARCHITECTURE.md say where the block stands without the floating menu

Benefits:

• A link typed in the editor is a link of the block and of the floating menu
• One list of links fits the stand and production alike

Technical notes:

• The content of the block row is unchanged in form; an <a> tag and javascript:OpenWindow are read as before
• No schema, URL or API change

The visit counter drawn as a PNG badge and the random banner block belong to the era of link exchanges; the site keeps its statistics in the panel. This change removes both blocks with their pictures, stops a clean install from seeding them, and lets the update switch off a block that still runs one of their files.

Core changes:

1. Blocks and the counter picture (blocks/stat.php, blocks/banner_random.php, core/user.php):

• The file blocks stat.php and banner_random.php are removed
• The switch on index.php?stat=1&img=N that drew today's visits onto a PNG is removed from core/user.php

2. Theme images (public/templates/lite/images/, public/templates/admin/images/ranks/):

• The folder banners/ of lite with its badges and the random banners is removed
• The leftover folders account/ of lite and ranks/ of admin, which nothing reads, are removed

3. Installation and update (storage/update/sql/insert.sql, public/update.php):

• A clean install no longer seeds the blocks "Счетчик посещений" and "Реклама"; "Форум внизу" takes id 6
• update.php switches off an active block that runs stat.php or banner_random.php, as it does with the blocks of the removed modules, and names the files it switched off

4. Probe and test (tests/Support/install_probe.php, tests/Unit/UpdateSiteTest.php):

• The upgrade probe seeds a stat.php block and reads the new report line; the test expects it switched off

5. Demo and docs (public/demo/assets/sb-data.js, docs/TEMPLATES.md, docs/VERSIONS.md):

• The site builder demo drops the two file blocks from its list and its start layout
• TEMPLATES.md no longer names banners among what the panel reads of the site theme

Benefits:

• Two blocks, a GD drawing path and 48 images less to ship and to keep
• An updated site does not run a block whose file is gone

Technical notes:

• Breaking: an outside page that embeds index.php?stat=1 gets the start page instead of a PNG
• No schema change; the update only sets status = 0 on the matching _blocks rows

The rendered page used to be repaired afterwards by a regex normalizer that could not fix the indentation of nested fragments; now the templates of both themes are canonical HTML and the engine keeps that form on the way out, so the page is correct as rendered, with no pass over it.

Core changes:

1. Template engine (core/classes/template.php):

• A line holding only control tags or a note leaves nothing in the output, its indent and line end included
• An insert alone on its line (raw echo, include, freeblock, block) takes the indent of that line on every line
  • getPad() keeps pre, textarea, script and a tag whose attribute spans lines byte for byte
  • An empty insert leaves no line; getPad() is public static so the core can indent late output
• The line end PHP swallows after a closing tag is given back, except after the tag that ends the file
• The hash of an inline snippet carries the engine time, so a changed engine compiles it again
• Companion asset tags are joined without a second line end

2. Page output (core/system.php, core/classes/mail.php):

• getOutputHtml() is removed: the page, the page cache and the queued mail carry what the engine rendered
• The head fragments and the script and stylesheet lists are joined without an extra line end
• getTimedHtml() indents the debug block it substitutes after the render

3. Templates (public/templates/admin, public/templates/lite, modules/presentation/sections):

• Every opening tag stands on one line, a conditional attribute carries its own leading space
• Block elements stand on their own lines with a two-space indent; the root of a fragment starts at column 0
• A multi-line block insert stands alone on its line inside its container
• The inline link and span fragments are one line with no space at their edges
• Whitespace between inline items is kept where it renders; parser fragments stay byte-exact for CommonMark

4. Tests and tooling (tests/, tools/, composer.json, package.json, docs/):

• TemplateOutputTest holds the three output rules; source and markup assertions accept canonical line breaks
• The clean installation, the package installation and the data update form the group release: composer test:fast leaves it out, composer test:release runs it alone
• A class that memoizes its probe keeps the raw answer before any assertion; NodeRouteTest is cut into NodeRouteListTest, NodeRouteFormTest and NodeRouteSeoTest over the base NodeRouteCase
• The unused code audits leave PHPUnit for tools/unused.php, run by hand
• ui:gates and the commit hook rely on ThemeContractTest for the counts instead of a second full audit

5. Presentation (public/plugins/presentation/presentation.js, presentation.css, tools/frame-cost.mjs):

• A part off screen is paused by CSS and its SMIL by script, and the pulse strip reads no layout per frame
• The frame cost rig measures the hero as a page of its own

Benefits:

• The source of a page reads as the templates are written, with no post-processing per request
• A multi-line attribute value and a hidden field reach the browser unchanged
• The fast suite leaves the slow release half out

Technical notes:

• Measured on the stand: getPad() costs about 3.5 ms on the heaviest pages (about 0.4 % of their response), about 1 ms on the news list
• Whitespace inside inline links and spans at their edges is gone; the screenshot rig moved no pixel on the pages it guards
• No schema, URL or API change