Repository navigation
Pin SIMAI Framework ui-b4a77681f0a7 with pro-7a2900066a50; remarks R087-R091, «Фоны», C16/C20 cleanup - #18
Merged
Merged
Conversation
…cal) The pair is ui Build b4a77681f (the runtime), bind c62eae925 (the release lock contracts/releases/ui-b4a77681f0a7.lock.json), ui-source a29cc998, ui-builder e87e47d, npm 5.20261109.1121, core.runtime 1.47.0: C16 places and coloured backgrounds, C17 static palette and hues, C23 navigation current page, C27 button height. The Pro package is ui-pro cfad790 (chore/pro-over-b4a77681), archive sha d709316c, builder e87e47d, built over this pair by the Framework take; it is not published as a pro-<12> release yet. Before this is pushed the pin moves to the released pro id (the branch head d4d58aa changes tests only). The version sync moves every pinned value and the CDN examples; the block kit link on Блоки names 5.20261109.1121; the English home is re-accepted. The reference adds Russian text for 10 new manifest strings (C17 hues, C27 height, C28 choice layouts, view templates). Generated sections, the token table (1006 tokens) and property types follow the pair. Reviews recorded: menu contract (the page now states C23: the primary navigation plate, the bar on a closed branch, two levels for a site tree), composition contract (sf-button gains height, additive), smart lessons (loader, smart-base and field renderers byte-identical). Pages: palettes gains «Статическая палитра» with the sixteen hues and the sf-hue roles; buttons replaces «Плотность» (spacing, deprecated by C27) with «Высота» and a height example; segmented links the cycle button (R075); the cycle sections say why the theme cycle does nothing inside a documentation example (R076, the Framework side stays open). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e, button height, segmented - R087: drop the old palette image (live ramp grid instead); new docs:colour-legacy:check fails on C17-retired colour content (tone tokens, avatar tone class/attribute, legacy palette classes, soft chart set, chart generator, palette images); fixed every finding: avatar hue docs/examples, palette sections and examples removed, bg-white/bg-surface-0 replaced. all-tokens skips retired names; updating.md gains a generated "Прежние имена переменных" table from the change journal. - R088: docs:wide-pages:check marks table-heavy pages reading.toc:false (17 pages). - R089: background-color documents the full info role and disabled surface. - R090: class button page documents height (low/default/high/highest), Smart page refers to it. - R091: segmented examples wrap at phone width; theme-switch inertness is Docara booting frames with theme:false (reported, not docs-side). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- New guide page content/ru/guide/colour/surfaces.md («Фоны», order 65): five places (page, area, card, popup, inverse; raised and popup-nested), the translucent layers over them (control fill 16/20/24, state 4/8/12, disabled, scrim 64, glass .sf-surface-media), selected/current = primary-container, status roles and controls on a soft colour place, --sf-surface-place for cut-outs, how to choose, naming scheme. Five live examples under examples/guide/colour/ render light and dark side by side. Linked from the colour guide index, «Поверхность и тень», colour roles, transparency, glossary, design tokens and the AI standards page. - Cleaned C16/C20-retired names on 59 pages and examples (surface-0/1, elevation-N, -transparent-*, outline-<role>, disable, numbered shadows, -background component variables); component defaults now match the release (pager card, table frame and stripe, workspace drawer); contrast table remeasured for on-surface-container-variant neutral-85. - docs:colour-legacy:check also fails on every -c16-/-c20- journal name, the token-aliases component variables and the hand-written placeholder forms; release-derived «Классы»/«Переменные» sections and the coloured shadow pages (no successor) are exempt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Pro package moves from the local build pro-cfad790254d6 to the release pro-7a2900066a50 on simai/ui-pro (ui-pro 7a2900066a50, tree 626060ed, archive sha c74f3ec7, builder e87e47d), built over the same pair ui-b4a77681f0a7; the bytes are also larena-7a2900066a50 on simai/larena-ui. The archive digest was checked against the release asset. Units changed since cfad790: smart.editor 1.2.3, smart.editor-content 1.4.7, smart.view-properties 1.13.2, smart.view-table 1.16.1. The version sync moves the guide's pinned values; the reference sections of the Pro pages follow the package. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Since ui-cb287da78ab1 a Smart action takes a single args object. The pages and
examples of sf-list and sf-list-feed still showed the positional forms
setItems(items, {hasMore}), prependItems/appendItems(items, {hasMore}),
upsert(entry, view, {replaces}), setView(id, view) and
scrollToLatest({instant, focus}); they now read
setItems({items, options: {hasMore}}), upsert({item, view, options:
{replaces}}), setView({id, view}) and scrollToLatest({options: {instant,
focus}}), as the generated reference does. The elements still accept the old
forms.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs pinned to SIMAI Framework pair ui-b4a77681f0a7 (ui Build b4a77681f, bind c62eae925, ui-source a29cc998, ui-builder e87e47d, npm 5.20261109.1121, core.runtime 1.47.0) with the Pro package pro-7a2900066a50 (ui-pro 7a29000, archive c74f3ec7, the published simai/ui-pro release; same bytes as larena-7a2900066a50). Carries the docs work since #17, shown on ui-doc.test.
docs:colour-legacy:checkfails on C17-retired colour content; every finding fixed; updating gains a generated «Прежние имена переменных» table.docs:wide-pages:checkgives table-heavy pages the full width (reading.toc false, 17 pages).--sf-surface-place, naming; five live examples, light and dark.setItems({items, options: {hasMore}}),upsert({item, view, options: {replaces}}),setView({id, view}),scrollToLatest({options})).Checks:
docs:checkexit 0 (smart reference, colour legacy and wide pages included); Smart lessons pass; migration idempotency (CI command) 0 Markdown changes; static build verified (2315 pages, 0 broken references); browser smoke 14 pages, 0 failing. Local release on ui-doc.test checked in headless Chromium: 11 key pages, 3 loads each at 1440 and 390, 0 console errors, runtime ui-b4a77681f0a7 and pro-7a2900066a50 only, no undefined sf- tags. Owner approved publishing (2026-11-09).🤖 Generated with Claude Code