svelte-kit-vice/src/uix/langs/components/onion-menu.ts

import type { LangNode } from '$libs/langs';

export const onionMenuLangs = {
	label: {
		es: 'Menú cebolla',
		en: 'Onion menu'
	}
} satisfies LangNode;
feat(eidos): action components — fab, onion-menu, button-group, split-button Ship the four action-cluster components. Per the audit the user requested, the hardcoded magic numbers in their CSS move to recipes (base.ts), so the values live in one place and pass the recipe-CSS contract: - fab: the off-ladder Material size / icon / lift scale → `fab` recipe (named tokens — the canonical control-height / icon-size ladders genuinely can't express 40/56/72 + 20/24/28; documented as the FAB's own scale). - onion-menu: the radial-chrome magics (sector ring widths, glyph bar, trail opacities) → `onion-menu` recipe; the centre trigger's lift + shadow REFERENCE `--fab-*` (it IS a FAB — the two can't drift apart). - button-group: the segmented-divider strength → `button-group` recipe. - split-button: the slim chevron tail's inline padding → `split-button` recipe; DropdownMenu gains `customAnchor` so the menu spans the whole split surface. All four compose the framework primitives (Group / Button / Icon / DropdownMenu), declare a morfo, ship langs + a demo, and pass the recipe-CSS contract test (the only flagged component left is palabras, an active dev track). check 0; onion-menu engine tests 31/31. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 4 months ago			`import type { LangNode } from '$libs/langs';`

			`export const onionMenuLangs = {`
			`label: {`
			`es: 'Menú cebolla',`
			`en: 'Onion menu'`
			`}`
			`} satisfies LangNode;`