/* ============================================================================ СКАРЫНА — LANE 3 : BLOCK BRIDGE Companion to L2's assets/css/skaryna.css. Load AFTER it. WHAT THIS FILE IS, AND WHAT IT DELIBERATELY IS NOT --------------------------------------------------------------------------- L2's CLASS-CONTRACT v1 is authoritative and Lane 3 emits its class names: `sk-tpl-archive` / `sk-tpl-issue` scopes, `sk-grid sk-grid--cards`, `sk-card sk-card--archive`, `sk-card__thumb/__title/__author/__date/__foot`, `sk-tag`, `sk-pill`, `sk-listrow*`, `sk-toc*`, `sk-pager`. Every rule L2 already ships has therefore been DELETED from this lane — the earlier Lane 3 draft carried a full copy of archive.css and a private `--slovo-*` token bridge; both are gone, because a second definition of a token L2 owns is a silent fork. What remains is only the part L2's contract cannot cover: ★ FIVE OF L2's COMPONENT CONTRACTS CANNOT BE EMITTED BY A CORE BLOCK. L2 §1.3/§1.4 specify hand-authored markup (``, `
  • `, `
    `). Core blocks hard-code their own inner class names and expose no attribute to change them, so on a Query Loop page those classes CAN NEVER APPEAR: L2 contract shape core block emits instead ------------------------ --------------------------------------------- a.sk-chip a.tag-cloud-link (core/tag-cloud) a.sk-tab li.cat-item > a (core/categories) .sk-pager__cur/__gap a/span.page-numbers.current/.dots (core/query-pagination-numbers) .sk-pager__edge .wp-block-query-pagination-previous/-next .sk-search input/button .wp-block-search__input/__button (core/search) article.sk-card as the ul.wp-block-post-template > li.wp-block-post grid item (core/post-template) The blocks marked /* L2-DUP */ below restate L2 properties for those DOM shapes so the page is not unstyled. They are duplication and they are labelled as such. HANDOFF TO L2: append the selector on each /* L2-DUP */ block to your existing rule and delete the block here — see L3/REPORT.md §8 for the exact list. ============================================================================ */ /* ── post-template as an L2 grid ───────────────────────────────────────────── core/post-template is the
      , so `sk-grid sk-grid--cards` goes on it and the real card is a core/group INSIDE each
    • . The
    • is a transparent grid cell; without this it collapses and the card loses equal-height. */ .sk-tpl-archive .sk-grid--cards.wp-block-post-template { list-style: none; margin-block: 0; padding-inline: 0; } .sk-tpl-archive .sk-grid--cards > .wp-block-post { display: flex; margin: 0; } .sk-tpl-archive .sk-grid--cards > .wp-block-post > .sk-card { flex: 1 1 auto; } /* ── engraved plate ────────────────────────────────────────────────────────── core/post-featured-image renders NOTHING when a post has no thumbnail (verified: 0 `wp-block-post-featured-image` nodes in the live render of all four posts), so the engraving is the default and retires itself the moment a real image is attached. No placeholder image is invented anywhere. */ .sk-tpl-archive .sk-card__thumb--eng svg { display: block; width: 100%; height: 100%; color: var(--slovo-ink); } .sk-tpl-archive .sk-card:has(.sk-card__thumb--img img) .sk-card__thumb--eng { display: none; } /* Nine refs per card, one revealed on a 9-cycle, so a 4-post archive still shows four DIFFERENT engravings. Only references are added — no symbol geometry is copied, so gate G9 holds (sha256 of all 9 symbols verified identical between comps/archive.html and comps/assets/sprite.svg). */ .sk-eng > use { display: none; } .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+1) .sk-eng > use:nth-child(1), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+2) .sk-eng > use:nth-child(2), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+3) .sk-eng > use:nth-child(3), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+4) .sk-eng > use:nth-child(4), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+5) .sk-eng > use:nth-child(5), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+6) .sk-eng > use:nth-child(6), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+7) .sk-eng > use:nth-child(7), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+8) .sk-eng > use:nth-child(8), .sk-tpl-archive .sk-grid--cards > .wp-block-post:nth-child(9n+9) .sk-eng > use:nth-child(9) { display: inline; } /* ── honest degradation at n=4 ─────────────────────────────────────────────── Three self-suppressing predicates. Each is data-driven: it un-hides by itself the moment the data exists. None of them fabricates anything. */ /* (a) `core/post-terms` renders '' when a post has no tags, but the group's own whitespace text nodes remain, so `:empty` would NOT match. */ .sk-tpl-archive .sk-card__foot:not(:has(a)) { display: none; } /* (b) a "filter by section" strip offering exactly ONE section is a lie about the site's structure (today: 1 category, `Uncategorized`). */ .sk-tpl-archive .sk-filters__sections:has(.wp-block-categories li:only-child) { display: none; } /* (c) core/query-pagination emits an empty