@omega.js/desktop 0.53.0 → 0.54.1

package/docs/themes.md

@@ -1,149 +0,0 @@
-# Themes
-
-@omega.js/desktop ships the **classy** theme (built on Bootstrap 5) so consumer apps look polished out of the box. Variables are fully customizable via `@use 'omega-desktop' as * with (...)` — same pattern as UJM and BXM.
-
-## How it works
-
-@omega.js/desktop carries @omega.js/web's FULL theme tree in `<em>/dist/assets/themes/` — vendored from the resolved `@omega.js/web` devDependency at every prepare via the declared-assets channel (C4 cp104/cp109), never hand-copied:
-
-| Theme | Base | Use case |
-|---|---|---|
-| `classy` (default) | Bootstrap 5.3 + OMEGA design system | Polished, modern app shell |
-| `bootstrap` | Plain Bootstrap 5.3 | Minimal, vanilla Bootstrap |
-| `neobrutalism` / `newsflash` | Bootstrap 5.3 | Alternate skins (universal `theme.id`) |
-
-The active theme is selected via `config.theme.id` (default `'classy'`). The `gulp/sass` task adds `<em>/dist/assets/themes/<theme>` to its sass `loadPaths` so the bare `@use 'theme'` import inside `@omega.js/desktop.scss` resolves to the active theme.
-
-## Consumer setup
-
-Your `src/assets/scss/main.scss` becomes:
-
-```scss
-// Generated from `brand.color` in config/omega.json5 by the sass task.
-@use 'brand';
-
-@use 'omega-desktop' as * with (
-  $primary: brand.$primary,
-  // $secondary: #6C757D,
-  // $border-radius: 0.5rem,
-);
-
-// The runtime --omega-accent ramp, AFTER the framework import so it wins the
-// cascade over the token sheet's placeholders.
-@include brand.ramp;
-
-// Custom global styles below...
-main {
-  padding: 2rem;
-}
-```
-
-`$primary` is `brand.color`, not a literal: the sass task writes
-`dist/assets/scss/_brand.scss` from the resolved config before every compile, so
-recoloring the app is a config edit. Want an accent that DIVERGES from the
-brand? Put the literal back in its place: `$primary: #2563EB,`. No `brand.color`
-set at all, and the partial carries the framework default
-([shared/theming.md](shared/theming.md), [#912](https://github.com/Omega-JS-Stack/omega/issues/912)).
-
-That single import gives you:
-- Full Bootstrap 5 (utilities, components, grid, etc.)
-- Classy theme overlays (typography, animations, refined spacing)
-- @omega.js/desktop's `_initialize.scss` (desktop-specific defaults — full-window body, app-region drag classes)
-
-## Per-page CSS
-
-@omega.js/desktop compiles per-page bundles in addition to the shared `main.bundle.css`:
-
-```
-src/assets/scss/main.scss          → dist/assets/css/main.bundle.css            (every page)
-src/assets/scss/pages/main.scss    → dist/assets/css/components/main.bundle.css       (main window only)
-src/assets/scss/pages/settings.scss → dist/assets/css/components/settings.bundle.css   (settings window only)
-src/assets/scss/pages/about.scss   → dist/assets/css/components/about.bundle.css      (about window only)
-```
-
-The page template auto-loads both: `main.bundle.css` is on every HTML page, and `components/<page.name>.bundle.css` is loaded only on its specific page. To add styles for a new page, drop a new file at `src/assets/scss/pages/<view>.scss` — it'll auto-compile and auto-inject.
-
-Per-page bundles can themselves `@use 'omega-desktop' as *;` if they need access to theme variables. Just be aware this means re-emitting some shared CSS — for very small per-page tweaks, prefer plain selectors that ride on the shared `main.bundle.css`.
-
-## Customizable variables
-
-The full classy variable list lives at `<em>/dist/assets/themes/classy/_config.scss`. ~60 variables you can override via the `@use ... with ()` form:
-
-**Colors:** `$primary`, `$secondary`, `$success`, `$info`, `$warning`, `$danger`, `$light`, `$dark`
-**Backgrounds (light mode):** `$classy-bg-light`, `$classy-bg-light-secondary`, `$classy-bg-light-tertiary`
-**Backgrounds (dark mode):** `$classy-bg-dark`, `$classy-bg-dark-secondary`, `$classy-bg-dark-tertiary`
-**Typography:** `$font-family-sans-serif`, `$font-family-base`, `$headings-font-weight`, `$classy-font-mono`, `$classy-font-accent`
-**Border radius:** `$border-radius`, `$border-radius-sm/lg/xl/2xl/pill`
-**Spacing, transitions, shadows** — see `_config.scss`
-
-## Switching themes
-
-Set `config.theme.id` in `config/omega.json5`:
-
-```jsonc
-theme: {
-  id:         'bootstrap',     // 'classy' (default) | 'bootstrap'
-  appearance: 'system',        // 'system' (default) | 'light' | 'dark'
-}
-```
-
-## Appearance (light / dark / system): `omega.theme`
-
-@omega.js/desktop owns appearance at runtime. `config.theme.appearance` is only the **app default**; the resolved appearance is applied and kept live by the theme lib:
-
-- **`'system'` (default)** follows the OS preference **live** — when the OS flips, every page updates without a reload or restart.
-- **`'light'` / `'dark'`** are explicit overrides.
-- A user's runtime choice (`omega.theme.set(...)`) is **persisted in `omega.storage`** (`theme.appearance`) and wins over the config default on every boot.
-
-### How it propagates
-
-Everything rides on Electron's `nativeTheme.themeSource` (same three values). Setting it flips `prefers-color-scheme` in **every renderer of the app — BrowserWindows AND embedded WebContentsViews** — and @omega.js/desktop's preload applier listens via `matchMedia` and rewrites `<html data-bs-theme>` to the **resolved** value (`'light'`/`'dark'`) live. No IPC fan-out, no per-window wiring; native UI (menus, dialogs) follows too.
-
-The applier is **opt-in by presence**: it only manages pages whose `<html>` already carries `data-bs-theme` (stamped by the page template at build). External sites loaded in a consumer's embedded web views get the same preload but are never touched.
-
-### API
-
-```js
-// Main
-omega.theme.get();          // 'system' | 'light' | 'dark'  (the chosen source)
-omega.theme.resolved();     // 'light' | 'dark'             (what's showing)
-omega.theme.set('dark');    // apply + persist (throws on invalid values)
-const unsub = omega.theme.onChange(({ source, resolved }) => { ... });
-
-// Renderer (any page with the @omega.js/desktop preload)
-await window.desktop.theme.get();        // { source, resolved }
-await window.desktop.theme.set('dark');  // → { source, resolved }
-const unsub = window.desktop.theme.onChange(({ resolved }) => { ... }); // matchMedia-powered
-```
-
-Main also broadcasts `desktop:theme:changed { source, resolved }` to BrowserWindows as a courtesy — but renderers should rely on `onChange`/matchMedia, which works in every context.
-
-### Declarative controls
-
-Any element with `data-omega-theme-set` becomes a theme switch (wired by the renderer's `omega.initialize()`, event-delegated, so late-rendered controls work):
-
-```html
-<button data-omega-theme-set="light">Day</button>
-<button data-omega-theme-set="dark">Dusk</button>
-<button data-omega-theme-set="system">Auto</button>
-```
-
-### Build-time stamp
-
-`data-bs-theme="{{ theme.appearance }}"` is still stamped into every page at build. For `'light'`/`'dark'` the stamp is already correct; `'system'` stamps an inert value that the preload applier replaces with the resolved appearance at `DOMContentLoaded` (Bootstrap treats unknown values as light for the instant before that).
-
-## Where the themes live
-
-The SSOT is **`@omega.js/web/themes/`** — one theme tree for web, desktop, and extension (C4 cp109: the classy triplication is dead). @omega.js/desktop declares `omega.vendorAssets` in its package.json, and every `prepare-package` run copies the resolved web package's `themes/` into `<em>/dist/assets/themes/`. Consumers import via the sass `loadPaths` mechanism — **nothing is ever copied into the consumer's tree**. Desktop-specific theme bits (the `.omega-titlebar` component, the `$min-contrast-ratio` knob) were upstreamed INTO the shared classy rather than kept as a fork.
-
-## Updating themes
-
-A theme change lands once in `packages/web/themes/` and rides into desktop + extension on their next prepare. There is no sync step and no version skew — dist is rebuilt from the resolved web package every time. (A standalone `@omega.js/themes` package was considered and rejected for now: the vendor channel gives one-source semantics without another publishable surface.)
-
-## Gotchas
-
-### Sass `@import` deprecation warnings
-Classy's `_theme.scss` uses `@import` (Sass's legacy module system) for its own internal layout. You'll see a deprecation warning during compile. UJM has the same warning. Functional today; will be migrated when classy upgrades to fully-modular `@use`/`@forward`.
-
-### Per-page CSS bundles are 0 bytes by default
-Empty `pages/<name>.scss` produces empty bundles. That's fine — the page template still loads them, the browser just gets a 200 with no rules. Adding any selector populates it.

package/docs/tooltips.md

@@ -1,99 +0,0 @@
-# Bootstrap JS & Tooltips
-
-@omega.js/desktop ships **Bootstrap's JavaScript** (v5.3, Popper inlined) as a prebuilt bundle
-— `assets/js/bootstrap.bundle.js` — loaded by the renderer
-bootstrap. Consumers add **zero setup** and never vendor Bootstrap JS
-themselves.
-
-## Tooltips (auto-initialized)
-
-Bootstrap makes tooltips opt-in (they need a JS instance per element); @omega.js/desktop does
-the opt-in for you. Any element carrying the standard Bootstrap markup gets a
-live tooltip:
-
-```html
-<button class="btn btn-primary" data-bs-toggle="tooltip" data-bs-title="Saves and continues">
-  Save
-</button>
-```
-
-The renderer bootstrap (`renderer.js _wireTooltips`) initializes every
-`[data-bs-toggle="tooltip"]` present at init and watches the DOM:
-
-- elements **inserted later** get their tooltip on arrival,
-- **`data-bs-title` / `title` changes** update the live instance in place
-  (emptying the title disposes it — no tooltip is a valid state),
-- **removed elements** have their instance disposed — no orphaned tips.
-
-Plain-`title` hosts work: Bootstrap's constructor MOVES `title` into
-`data-bs-original-title`, and the observer reads that bookkeeping as a live
-title source. (It must — reading only `title`/`data-bs-title` made the
-observer dispose the instance, dispose restored `title`, re-init removed it
-again: an infinite MutationObserver microtask loop that froze the whole
-renderer. Found by Somiibo's session-limits boot suite; regression-tested in
-the tooltips suite.) One knock-on: a title-only host can't be disposed by
-emptying its title — remove `data-bs-toggle` instead (prefer `data-bs-title`
-for dynamic tooltips).
-
-All the standard Bootstrap `data-bs-*` options work (`data-bs-placement`,
-`data-bs-delay`, …).
-
-### Disabled controls
-
-Bootstrap's own caveat: disabled elements don't fire hover events. Wrap the
-control and put the tooltip on the wrapper:
-
-```html
-<span data-bs-toggle="tooltip" data-bs-title="Requires the Pro plan">
-  <button class="btn btn-primary" disabled>Bulk import</button>
-</span>
-```
-
-## The rest of Bootstrap's JS
-
-The full namespace is exposed at **`window.bootstrap`** (and
-`omega.bootstrap`): `Tooltip`, `Popover`, `Collapse`, `Dropdown`, `Modal`,
-`Offcanvas`, `Tab`, `Toast`, `Alert`, `Button`, `Carousel`, `ScrollSpy`. Only
-tooltips are auto-initialized; the other components' standard **data-api**
-works out of the box on plain Bootstrap markup (e.g.
-`data-bs-toggle="collapse"`), and everything is available for manual control:
-
-```js
-const collapse = window.bootstrap.Collapse.getOrCreateInstance(el);
-collapse.show();
-```
-
-## Rebuilding the bundle
-
-`assets/js/bootstrap.bundle.js` is a COMMITTED prebuilt artifact — no gulp task
-rebuilds it, so a normal build never regenerates it. The checked-in bytes are a
-legacy webpack UMD build, from before [#737](https://github.com/Omega-JS-Stack/omega/issues/737)
-took webpack out of desktop.
-
-Rebuild only when the vendored Bootstrap source is upgraded, with esbuild — the
-one bundler desktop still has. The input is @omega.js/desktop's vendored
-Bootstrap 5.3 source (the vendored themes tree) plus `@popperjs/core` (an
-@omega.js/desktop dependency), and the output has to keep the contract its two
-consumers rely on: `require()` hands back the Bootstrap namespace
-(`renderer.js` reads `.Tooltip` off it and assigns `window.bootstrap` itself),
-so the format is CommonJS:
-
-```bash
-esbuild bootstrap.js --bundle --minify --format=cjs \
-  --outfile=src/assets/js/bootstrap.bundle.js
-```
-
-Use `--format=iife --global-name=bootstrap` only if the bundle is ever loaded by
-a plain `<script>` tag instead — nothing does that today.
-
-Note: the bundle reads `document.documentElement` at import time — the renderer
-bootstrap defers loading it until the document exists (relevant when wiring
-runs from a preload, e.g. the test harness).
-
-## Testing
-
-- `src/test/suites/renderer/tooltips.test.js` — bundle loads, auto-init on
-  insertion, live retitle, dispose-on-removal, tip cleanup. (The harness wires
-  the renderer instance in the preload world: see the suite header for the
-  world-split notes; single-world hover behavior is covered by consumer boot
-  suites.)

package/docs/tray.md

@@ -1,164 +0,0 @@
-# Tray
-
-File-based tray/menubar. @omega.js/desktop looks for `src/integrations/tray/index.js`; if it exists, the exported function is called during boot with a builder API + id-path API. If absent, @omega.js/desktop ships a default tray template (see ids below).
-
-## Config
-
-No config block. Path is conventional: `src/integrations/tray/index.js`. To opt out, call `omega.tray.disable()` from your main entry: idempotent, tears down any existing Tray.
-
-## Definition file
-
-```js
-// src/integrations/tray/index.js
-module.exports = ({ omega, tray }) => {
-  // @omega.js/desktop auto-resolves the tray icon from config/icons/<platform>/tray.png at build
-  // time, so explicit tray.icon() is OPTIONAL. Call it only to override.
-  // Note: on macOS, if you pass your own path, the filename MUST end in
-  // `Template.png` for the OS to auto-invert it in dark mode.
-  // tray.icon('src/assets/icons/my-trayTemplate.png');
-  tray.tooltip(omega.config?.app?.productName);
-
-  // Easiest: start from @omega.js/desktop's default template.
-  tray.useDefaults();
-
-  // Then customize by id (flat — no `tray/` prefix needed):
-  tray.insertAfter('open', {
-    id: 'dashboard',
-    label: 'Open Dashboard',
-    click: () => omega.windows.show('dashboard'),
-  });
-  tray.update('open', { label: 'Show Window' });
-  tray.remove('website');
-  tray.hide('check-for-updates');
-};
-```
-
-## Builder API (during definition)
-
-```js
-tray.icon(path)                // sets the tray icon (relative paths resolved from cwd)
-tray.tooltip(text)
-tray.item(descriptor)          // see "Item descriptors" below
-tray.separator()
-tray.submenu(label, items)
-tray.useDefaults()             // populate with @omega.js/desktop's default template (id-tagged)
-tray.clear()                   // start over
-```
-
-## Id-path API
-
-Same shape across menu / tray / context-menu. Available **during definition** (on the `tray` builder arg) AND **at runtime** on `omega.tray`:
-
-```js
-.find(idPath)                  // live descriptor or null
-.has(idPath)                   // bool
-.update(idPath, patch)         // Object.assign + re-render. returns true if found.
-.remove(idPath)                // splice + re-render. returns true if removed.
-.enable(idPath, bool = true)   // sugar over update({enabled})
-.show(idPath, bool = true)     // sugar over update({visible})
-.hide(idPath)                  // visible:false
-.insertBefore(idPath, item)    // splice in a sibling
-.insertAfter(idPath, item)     // splice in a sibling
-.appendTo(idPath, item)        // push into a submenu (creates submenu if absent)
-```
-
-Tray ids are **flat** — no `tray/` prefix (the lib namespace is implicit). For nested submenus you can address children by `parent/child` paths (the resolver walks `submenu` arrays).
-
-## Default template ids
-
-| ID | Item |
-|---|---|
-| `title` | Disabled label showing the app name |
-| `open` | "Open `<app>`": calls `omega.windows.show('main')` |
-| `check-for-updates` | Wired to `omega.autoUpdater` (label updates dynamically) |
-| `website` | Visit `brand.url` (only present if configured) |
-| `quit` | Quit the app |
-
-## Submenus
-
-Submenus work the same as Electron's. The id-path resolver walks `submenu` arrays so children are addressable as `parent/child`:
-
-```js
-tray.item({ id: 'account', label: 'Account', submenu: [
-  { id: 'sign-in',  label: 'Sign in',  click: () => {} },
-  { id: 'sign-out', label: 'Sign out', click: () => {} },
-]});
-
-omega.tray.find('account/sign-out');
-omega.tray.update('account/sign-out', { enabled: false });
-omega.tray.appendTo('account', { id: 'profile', label: 'Profile' });
-```
-
-## Item descriptors
-
-Mirror Electron's [`MenuItemConstructorOptions`](https://www.electronjs.org/docs/latest/api/menu#menubuildfromtemplatetemplate), with these additions:
-
-| Field | Type | Notes |
-|---|---|---|
-| `id` | string | Used for id-path lookups (`open`, `quit`, `account/sign-out`, …) |
-| `label` | string \| `() => string` | Function form re-evaluated on every `refresh()` |
-| `enabled` | boolean \| `() => boolean` | Same |
-| `visible` | boolean \| `() => boolean` | Same |
-| `checked` | boolean \| `() => boolean` | Same |
-| `click` | function | Wrapped to swallow errors so a bad handler can't kill the menu |
-| `submenu` | array | Recursively resolved with the same conveniences |
-
-## Runtime API on `omega.tray`
-
-```js
-omega.tray.refresh()                   // re-evaluate dynamic state and re-render
-omega.tray.define(fn)                  // replace the whole definition at runtime
-omega.tray.disable()                   // tear down + stop responding (idempotent)
-omega.tray.setIcon(path)
-omega.tray.setTooltip(text)
-omega.tray.addItem(descriptor)         // append (preserves existing items)
-omega.tray.clearItems()
-omega.tray.destroy()                   // tear down (mostly for tests)
-
-// Id-path API — same as listed above.
-omega.tray.find('quit')
-omega.tray.update('quit', { label: 'Goodbye' })
-omega.tray.remove('website')
-omega.tray.insertAfter('open', { id: 'preferences', label: 'Preferences...', click: ... })
-omega.tray.hide('check-for-updates')
-
-// Inspection
-omega.tray.getItems()                  // shallow copy of raw descriptors
-omega.tray.getIcon()
-omega.tray.getTooltip()
-omega.tray.isRendered()
-```
-
-## Common patterns
-
-### Update label after auth state changes
-
-```js
-// in your renderer/main code, after sign-in:
-omega.storage.set('user', { ... });
-omega.tray.refresh();    // dynamic-label functions re-evaluate
-```
-
-### Hide updater item if you ship without auto-update
-
-```js
-// src/integrations/tray/index.js
-module.exports = ({ tray }) => {
-  tray.icon('...');
-  tray.useDefaults();
-  tray.remove('check-for-updates');
-};
-```
-
-### Replace the entire tray at runtime
-
-```js
-omega.tray.define(({ omega, tray }) => {
-  tray.icon('icons/dark-mode.png');
-  tray.item({ id: 'x', label: 'New layout', click: ... });
-});
-```
-
-## Default scaffold
-
-The scaffold every verb runs ships `src/integrations/tray/index.js` calling `tray.useDefaults()` so you start with the same items the framework would supply on its own — plus commented-out examples covering insertAfter, update, remove, hide, enable, and submenus.

package/docs/usage.md

@@ -1,58 +0,0 @@
-# Usage
-
-Tracks app-launch + hours-of-use stats. Sister of legacy @omega.js/desktop's Usage library, but uses `omega.storage` instead of a separate electron-store.
-
-## What's tracked
-
-```js
-omega.usage.opens()              // total app launches
-omega.usage.hoursTotal()         // cumulative hours-of-use across clean exits
-omega.usage.hoursThisSession()   // live, computed from session start
-omega.usage.installedAt()        // ISO timestamp of first launch
-omega.usage.toJSON()             // all of the above as a structured-cloneable object
-```
-
-## How it accumulates
-
-Persisted shape (`storage.usage`):
-
-```js
-{
-  opens: 12,
-  hoursTotal: 4.75,
-  installedAt: '2025-12-01T...',
-  lastLaunchAt: '...',
-  lastQuitAt: '...' | null,
-}
-```
-
-On boot:
-
-1. Read previous snapshot.
-2. If `lastQuitAt` is set, accumulate `(lastQuitAt - lastLaunchAt)` into `hoursTotal`. This is the "previous session ended cleanly" case.
-3. If `lastQuitAt` is null, the previous session crashed — we don't credit any hours. We don't know how long it ran.
-4. `opens += 1`, `lastLaunchAt = now`, `lastQuitAt = null`.
-
-On quit (via `app.on('before-quit')`):
-
-5. `lastQuitAt = now` written to storage.
-6. Next launch's step 2 picks up the duration.
-
-So `hoursTotal` is intentionally a lower bound — it never over-counts crashed sessions.
-
-`hoursThisSession()` is computed live from `(Date.now() - sessionStart) / 3600000`. Never stale.
-
-## Renderer
-
-```js
-const snap = await window.desktop.usage.get();
-// { opens: 12, hoursTotal: 4.75, hoursThisSession: 0.05, installedAt: '...' }
-```
-
-## Why not just use app-state?
-
-`app-state.js` already tracks `launchCount` (= opens). We could fold these in. But `app-state` is concerned with first-launch / crash-sentinel / version-change semantics: `usage` is concerned with telemetry. Keeping them separate keeps each module focused. Both write to disjoint keys in `omega.storage`.
-
-## Tests
-
-- `src/test/suites/main/usage.test.js` — opens-bumps-on-reinit, hoursTotal accumulation from clean prior session, no-credit for crashed sessions, installedAt persistence, IPC handler.

package/docs/verts.md

@@ -1,62 +0,0 @@
-# Verts — the `data-omega-vert` auto-bind
-
-@omega.js/desktop renderers auto-bind the OMEGA verts (ads) system (monorepo
-`docs/web/ads-system.md`, phase 4): drop a `[data-omega-vert]` element into any
-view and the renderer bootstrap hands it to `@omega.js/client`'s verts module —
-zero consumer JS, same element vocabulary as the web `verts/unit` section and
-@omega.js/extension.
-
-```html
-<div data-omega-vert data-omega-vert-size="banner"></div>
-```
-
-## What the wiring does
-
-`renderer.js _wireAds` (runs inside `omega.initialize()`, same liveness
-model as the FontAwesome/tooltip wiring) binds every `[data-omega-vert]`
-element present at init AND inserted later (MutationObserver), marking bound
-hosts `data-omega-vert-bound="house"`. Everything after the bind lives in the
-client module (`@omega.js/client/modules/verts.js`): lazy arming near the
-viewport, a sandboxed iframe to the resolved in-house source's
-`/omega/verts/serve`, origin-validated postMessage, host-owned rotation +
-staleness recovery, and no-fill collapse (the host hides itself).
-
-## House/company lane ONLY — no AdSense
-
-Desktop surfaces never run the AdSense provider lane (policy: no web
-context). The wiring pins `type: 'house'` on every mount — the pin wins over
-the element's `data-omega-vert` type, so even a shared omega.json5 that carries
-`advertising.providers.adsense` (the web target uses it) can only
-ever reach the house/company inventory here. Pinned by the renderer verts
-suite: an AdSense-configured harness must never see an `adsbygoogle` script
-or `<ins>`.
-
-## Config
-
-The shared `advertising` section of `config/omega.json5` flows into the
-renderer via `OMEGA_BUILD_JSON` like every other section:
-
-```json5
-advertising: {
-  providers: {
-    inhouse: { source: 'company' },  // 'self' | 'company' | full URL
-  },
-  tags: ['music', 'audio-tools'],    // contextual targeting inputs
-}
-```
-
-No `advertising` key (or no resolvable inhouse source) → bound units collapse
-quietly. Nothing else to configure.
-
-## Element vocabulary
-
-| Attribute | Meaning |
-|---|---|
-| `data-omega-vert` | binds the element (type value is ignored on desktop — house pin) |
-| `data-omega-vert-size` | size preset (`banner`/`leaderboard`/`rectangle`/…) or raw px max-height |
-| `data-omega-vert-id` | pin a specific vert |
-| `data-omega-vert-tags` | comma-separated contextual tags for this unit |
-| `data-omega-vert-bound` | set by the wiring (`"house"`) once bound — observability/debugging |
-
-Units emit `omega-vert:fill` / `omega-vert:no-fill` / `omega-vert:click` /
-`omega-vert:reload` CustomEvents on the host (bubbling) for app-side hooks.