dsh-client-ui-slots/packages/client/ui-slots官方

English | 中文

Slot registry pure core, slot terminal design: SlotMap declaration merging, the single register composition API on SlotCore, the four-share component-props type family, the store-seat type family, and the renderer installation contract. React types only at runtime — the package is React-free and cordis-free.

One register({ name, children?, store?, inject?, ...kind }, Component) call contributes a component into a declared slot and, in the same breath, declares child slots (declaration = render authorization = runtime spec, one table), a store seat, and the registrant's business face. The component is checked at the call site against ComposedProps — the intersection of four shares, each derived from its single source of truth:

Chain-kind slots invert keyed routing — entries self-nominate instead of the dispatch site picking an entryKey: each registration carries a pure ChainSelect selector (plus optional ascending priority, ties in registration order), the first non-null return elects its entry and becomes the component's matched prop, and all-null falls to the owner's renderSlotChain fallback (ChainRenderOpts).

The standard-kit interfaces (SessionStandardProps, GlobalStandardProps) are declared empty here and merged by the runtime package (same declare-merge pattern as SlotMap keys). The renderer binds the runtime's session and workspace observable sources into selector hooks. Inject factory parameters derive from the declaration (InjectParams): session slots get sessionId, a declared store appends baked actions, nothing else — data access lives in the apply closure's ctx.

The store family (defineStore spec in / StoreHandle<T, A> out) types the store seat: init infers the state schema, actions is the complete draft-transform write set, BakedActions strips the draft parameter into the callbacks components and inject factories receive. The defineStore value implementation lives in the runtime package (the engine's home) and satisfies the DefineStore contract exported here. Engine products and the renderer host contract carry bare snapshot sources (getSnapshot/subscribe), never React hooks — hook binding belongs to the render machinery; only the props-contract hook type (SnapshotSelectorHook) lives here.

SlotCore seeds the a-priori 'root' slot at construction and enforces load-time validation (undeclared-slot registration, duplicate child declaration, one shared handle under two scopes, a chain registration without select — all throw at register). An entry's disposer collapses its declared child slots recursively: ledger rows, contributions, and store mounts die on one lifecycle axis. Each key also carries a declaration epoch that advances only on declaration and collapse; the runtime uses it for ctx.slots.inject, independently from ordinary entry versions. renderer.ts carries the installation contract (SlotRenderer, SlotRendererHost) plus StaleAuthorizationError/SlotOwnershipError; ui-renderer owns both the implementation and its plugin-lifecycle installation.

Model Experience

None, as the slot registry is browser-side UI plumbing; nothing here reaches a model request.

KV Cache effect

None; this package neither assembles nor sends a provider request.

Known Limitations and Deferred Work

• isLive scans all records linearly — fine at UI-plugin registration counts (tens); revisit with an entry→record backref if ledgers ever grow hot.
• The __renders phantom anchor is visible on PropsRenderSlots — the same accepted noise as the type-chain design's __accepts: generic method signatures compare loosely across key unions, so the contravariant marker is what enforces "component key set ⊆ children declaration".