Ship CSS theme bridges and vendor portal-interop recipes

[woksin]

Problem

Components 4 documents coexistence, primitive adaptation, custom composition, unsupported claims, and licensing boundaries. It does not yet ship CSS-only theme bridges or detailed portal/widget recipes from the post-GA L-b plan.

Direction

Deliver this incrementally by licensing class:

Theme bridges

Create optional CSS-only @cratis/components.theme.<id> packages that map a host design language onto semantic --cratis-* tokens. They contain no JavaScript, components, behavior, or vendor code. Their layer ordering must preserve host overrides without !important.

Permissive portal interop

Add a concrete AG Grid Community-style recipe showing an application-owned widget in a Cratis-owned region, with explicit query state, portal/z-index, focus, theme, and ownership boundaries.

Commercial suites

For KendoReact, Syncfusion, DevExtreme, and AG Grid Enterprise, publish documentation/recipes only after counsel confirms redistribution, toolkit/library, trademark, license-validation, and telemetry boundaries. Do not publish adapter packages by inference.

Acceptance criteria

• At least one CSS-only bridge has zero JS and archive/layer/token verification.
• At least one permissive portal recipe is executable and does not relabel a Cratis composite as vendor-native.
• Commercial guidance records counsel-approved boundaries and contains no redistributed vendor code.
• Coexistence/focus/portal/licensing docs remain the source of truth.