@synopackageland/ui 0.19.11 → 0.20.0

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.20.0 (2026-11-04)
+
+- `PageContent height="fill"` gives its height to a `SectionTabs fill` or a `SettingsPage` however deeply the App wraps it: every element between the page body and that component becomes a flex column that takes the room its siblings leave, so an App needs no CSS of its own to pass the height through its page wrappers. A hidden wrapper (`v-show`, `hidden`) stays hidden.
+- In such a page, a `SectionTabs fill` tab that is not a `SettingsPage` scrolls under the fixed strip instead of running past the page's bottom; a `SettingsPage` tab still scrolls only its own body over its footer.
+- [Layout rules](docs/layout-rules.md) describe the current page layout: no page title under a sidebar that names the page, the page's buttons in a bar above it, and only the content scrolling. A migration section lists the CSS an App can drop.
+- Fix long `Select` and `Combobox` lists showing no scrollbar, so a list that scrolls no longer looked cut off. Reka hides the native bar inside its list viewports; the DSM scrollbar is drawn there again, in light and dark, while `ScrollArea` keeps hiding its own bar.
+
 ## 0.19.11 (2026-11-03)
 
 - `Progress` draws its track as a faint tint of its own tone (`--ui-primary-soft`, `--ui-success-soft`, `--ui-warning-soft`, `--ui-danger-soft`) instead of the grey border colour, so a bar never sits on a grey track.

package/README.md

@@ -437,6 +437,12 @@ under its sticky header, with the pager always in view. Pages that are not
 `fill` in the same layout scroll as before. In the SDK's `AppShell`, the same
 is a page's `fill: true`.
 
+A settings page fills the same way: `PageContent height="fill"` gives the
+height to a `SectionTabs fill` or a `SettingsPage` through the App's own
+wrapper elements, with no CSS of their own. The tab strip and the footer stay,
+only the sections scroll, and a tab that is not a `SettingsPage` scrolls under
+the strip. The SDK's `AppShell` fills such a page by itself.
+
 ```vue
 <AppLayout height="fill" min-height="0">
   <template #sidebar>…</template>
@@ -964,8 +970,8 @@ Use the pnpm version specified in `package.json`.
 ```bash
 pnpm story       # component workbench
 pnpm dev         # rebuild dist when library source changes
-pnpm check       # production build, then lint, typecheck and tests in parallel, then the package audit
-pnpm check:fast  # as check, but only the tests the changes since origin/master reach (vitest --changed)
+npm run gates   # basic build, lint, typecheck, unit tests, notices and package audit
+npm run gates:full # optional browser/workbench/registry integrations, only when requested
 pnpm story:build # build the component workbench
 pnpm check:host  # after pnpm build: DSM host simulation screenshots (Chrome)
 pnpm check:date-picker # after pnpm build: app-local calendars, Dialog Escape and full-bleed pages (ego-browser)
@@ -973,8 +979,9 @@ pnpm check:switch # after pnpm build: Switch knob geometry and click toggling (C
 pnpm check:topology # after pnpm build: ConnectionTopology motion, keyboard and narrow layout (Chrome)
 ```
 
-Use `pnpm check:fast` while developing (`SYNOPKGLAND_GATE_BASE` sets the base),
-and `pnpm check` once before a release: the full run is the release gate.
+Use `npm run gates` for development and release. Extended checks require an
+explicit `npm run gates:full`; full is optional. `pnpm check` and `check:fast`
+are basic aliases. See [release checks](docs/release-checks.md).
 `check` prints one line per passing task and a failing task's whole log.
 
 With `SYNOPKGLAND_DOCKER_SSH=<ssh host>`, `pnpm check`, `check:fast` and
@@ -1044,12 +1051,11 @@ See the [documentation](https://www.varvis.me/docs/) for usage.
 
 ### CI and tag releases
 
-GitHub Actions runs on Ubuntu for pushes to `master` and `ci/**`, pull requests,
-and manual dispatch. Both workflows share `.github/actions/verify`: a frozen
-pnpm install from npmjs, `pnpm check` (build, lint, typecheck, unit tests and the
-package-content audit), `notices:check`, responsive/host/switch/layout/motion
-browser checks, and the Histoire workbench build. pnpm and Playwright Chromium
-are cached. Browser screenshots and measurements are retained for seven days.
+Automatic CI runs basic checks. The disabled CI/release workflow templates
+share `.github/actions/verify`: frozen dependency installation and
+`npm run gates` (build, lint, typecheck, unit tests, notices and package audit).
+Browser integrations, workbench builds and registry consumer smoke require
+`npm run gates:full` only when explicitly requested.
 
 To release the package:
 
@@ -1066,8 +1072,8 @@ To release the package:
    ```
 
 The release workflow checks the exact tag/version, default-branch ancestry,
-nonempty changelog section and npm version availability. It runs the same full
-CI gates, stages the package into an empty directory, packs it, and audits
+nonempty changelog section and npm version availability. It runs the same basic
+checks, stages the package into an empty directory, packs it, and audits
 the actual tarball (every exported dist file, MIT license, notices, bundled Reka,
 package name and no `publishConfig`). A separate job rechecks the artifact and
 registry before publishing with `NPM_TOKEN`, then creates a GitHub Release from
@@ -1077,7 +1083,7 @@ If npm publication succeeds but GitHub Release creation fails, create the Releas
 from the changelog separately; rerunning publishing intentionally refuses the
 already published version.
 
-On branches and PRs, the release workflow performs the full pipeline through
+On branches and PRs, the release workflow performs basic validation through
 `npm publish <tgz> --dry-run --access public --ignore-scripts`, without npm
 credentials or creating a GitHub Release. An existing npm version is allowed only
 in dry-run mode and is reported explicitly; npm 11 also rejects duplicate versions