feat(filter)!: move the filter components to @flux-ui/filter

[basmilius]

This PR resolves #39. The filter components move out of @flux-ui/components into a new package, @flux-ui/filter.

The reason is the Vite plugin. defineFilter() is a compile-time macro, and its plugin forced a second build entry, @flux-ui/components/vite, into the core package. That entry now ships as @flux-ui/filter/vite, and the core package has one entry again.

What moved

• The nine FluxFilter* components plus FluxFilterBase and FluxFilterWindow, the four Filter* primitives, three private composables, useFilterInjection, defineFilter and the other filter helpers, the injection key, Filter.module.scss and defineFilterMacro.
• The filter components import @flux-ui/components through its public barrel, the way ai does. Two internals they needed were private to components. VNodeRenderer and createLabelForDateRange now live in @flux-ui/internals. VNodeRenderer became a functional component because tsdown's isolated declarations want an explicit type. createLabelForDateRange takes the multi-year label as a string instead of a translate function, so internals doesn't need to know a dictionary key.
• The filter types stay in @flux-ui/types, like the statistics types. I dropped the seven dead ones the issue lists (FluxFilterBase, FluxFilterItem and the five Flux*Entry types), and their section in types.md with them.

Translations

All dictionaries now live in @flux-ui/internals, one file per package under src/data/i18n/, merged into one english. Internals exports a single useTranslate and the FluxTranslate and FluxTranslation types over every key. The per-package useTranslate wrappers are gone.

That has two effects on the filters. The filter bar reuses flux.filter and flux.filterReset from the components file instead of carrying copies. And a defineFilter factory can translate any Flux key, flux.cancel included.

The filter keys keep their flux.* names instead of moving to flux.filter.*. There are two reasons. Existing translations keep working, and flux.filter.* would collide with the flux.filter leaf that FluxActionBar uses in a nested messages file.

The cost is that every app ships all 164 strings, about 2.2 KB gzipped, including those of packages it does not install.

Docs and tooling

• Filter gets its own docs section at /filter/ with an intro, installation, translations, the component pages, useFilterInjection and a helpers page. The examples moved to docs/code/filter/.
• upgrading-v4.md has a new section with the import changes. I also corrected the translation key count and rewrote the section on the translate composable, since it now lives in internals.
• CI, the release workflow, build.sh, transform-dts.mjs, generate-translations.ts and CLAUDE.md all know about the new package.

Checked

• Every package builds, followed by transform-dts.mjs and the docs build. No type errors in the vue-tsc or dts output.
• check-contrast.ts, check-palette-refs.ts and generate-translations.ts --check pass.
• bun install --frozen-lockfile passes. Adding the workspace made bun prune pinia@3.0.4, an orphaned lockfile entry the docs build relied on without declaring it: the bundle of @basmilius/common imports pinia. The first CI run failed on exactly that. Docs now declares pinia@^4 as a dev dependency, the range @basmilius/common asks for.

The review subagent found one regression, and it is fixed. Two filter styles, the badge and the bar button, override a component class at the same specificity. On main they won by sitting later in the same bundle. As separate stylesheets the import order decides. I tried raising their specificity, but that ties them with .secondary-button:active, .is-active and .badge:is(a, button):hover, which win today, so the hover and active states would depend on order instead. The installation page and the upgrade guide now say to import @flux-ui/filter/style.css after the components stylesheet. The ai, flow and application install pages list the sibling stylesheet first. If one of those overrides a component class, it has the same latent problem. I did not check that here.

I did not click through the filter examples in a browser. The docs prerender without errors, but that is all I verified.

Breaking for consumers

• Filter imports move to @flux-ui/filter, and defineFilterMacro to @flux-ui/filter/vite.
• FluxTranslate and FluxTranslation move from @flux-ui/components to @flux-ui/internals.
• Seven dead filter types are removed from @flux-ui/types.

The upgrade guide covers all three.

[basmilius]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[basmilius]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[basmilius]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review skipped: 216 files exceed the limit of 100.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.