website: four more notes - first person, the globe's well, the touching tables, the submenu label

1. THE HOME PAGE SPOKE ABOUT THE OPERATOR IN THE THIRD PERSON ("Ha irsz, o valaszol")
   while the page it links to is in the first ("Ha irsz, en valaszolok"). Both home
   pages now read "Nagyfenyvesi Viktor vagyok, a Felhom mogott en allok" / "I am Viktor
   Nagyfenyvesi, and I am the one behind Felhom", and the link after it is "Rolam
   bovebben" / "More about me" rather than repeating the question the sentence has just
   answered. The legal pages keep the formal third-person name, which is their job.

2. 36px OF DEAD SPACE UNDER THE LANGUAGE GLOBE, and most of it was A LEAK GATE 22
   COULD NOT SEE. The old chrome's

       nav { position: fixed; top/left/right: 0; padding: 20px 0;
             backdrop-filter: blur(12px); border-bottom: 1px solid var(--line);
             z-index: 200 }

   is a BARE ELEMENT selector, so it matched <nav class="sidebar"> too - and .sidebar
   declares none of those, so all of them were in force on the sidebar. Scoped
   body:not(.shell); the footer row's own padding went 16px -> ~8px.

   Gate 22's first half compares selectors present in BOTH stylesheets, and `nav` is not
   a selector shell.css ever writes, so this shape was outside its field of view. It now
   has a SECOND HALF: an unscoped bare nav/header/main/aside rule in site.css is a
   failure, because those elements ARE the shell (<nav class="sidebar">,
   <header class="mobile-topbar">, <main class="content">). It convicted a second live
   one on its first run: R-903's `@media (max-width:900px) and (scripting: none)
   nav { position: static }` had been overriding the sidebar's own position on a phone
   with scripting off. `footer` is deliberately NOT on the list, with the reason beside
   it: the shell carries the website's own footer.
   Decoy site/bare-element-rule-reaches-shell, seen to convict.

3. THE COMPARISON TABLE AND THE TWO CARDS under "Miert a sajatod?" were touching: .vs
   ends on its own border and .band opens with a 2px blue rule, so they read as one
   block. 2rem between them.

4. "MINDEN ALKALMAZAS" -> "AZ ALKALMAZASOKROL" / "About the apps" on all 22 pages. Every
   app is on that one page, so the first submenu item is not a filter - it is the top of
   the page, where the intro and the "Fontos tudnivalok" box are. The en-nav-drift decoy
   was re-anchored on the new label.

Checked at 390px and 1440px on all 21 pages: no sideways scrolling, footer inside the
content column, the renamed item on every page. site.css?v=25.

scripts/CHANGELOG.md

@@ -1,3 +1,19 @@
+## 2026-10-12 (afternoon) — gate 22 also refuses an unscoped bare element rule
+
+- `site_gates.py` gate 22 gains a second half: a rule in `site.css` whose selector starts with a bare
+  `nav`, `header`, `main` or `aside` and is not scoped `body:not(.shell)` / `.shell` is a failure,
+  because those elements ARE the shell (`<nav class="sidebar">`, `<header class="mobile-topbar">`,
+  `<main class="content">`). The first half compares selectors present in both stylesheets, which by
+  construction cannot see this: `nav` is not a selector `shell.css` writes.
+- **Why.** The old chrome's `nav { position: fixed; padding: 20px 0; backdrop-filter: blur(12px);
+  z-index: 200 }` was in force on the sidebar — `.sidebar` declares none of those four — and the
+  operator saw the 20px as dead space under the language globe. On its first run the new half
+  convicted a second rule: R-903's `@media … (scripting: none) nav { position: static }`.
+- `footer` is NOT on the list, with the reason beside it: the shell carries the website's own footer.
+- **Decoy** `site/bare-element-rule-reaches-shell`: the `body:not(.shell)` scope taken back off that
+  rule, seen to convict with the gate's own line. `site/en-nav-drift` re-anchored on the renamed
+  submenu label („About the apps").
+
 ## 2026-10-12 — site gate 23: every in-site #fragment resolves
 
 - `site_gates.py` **gate 23** reads every page's ids, maps each in-site href with a `#fragment` to the