EXPERIMENTAL: @signal and @memo TC39 decorators for class-based reactivity in @spearwolf/signalize. Use with caution - the decorator API may change. Prefer manual signal creation (createSignal, createMemo) for production code.

Reactive side effects for @spearwolf/signalize: createEffect, cleanup callbacks, dependency tracking (dynamic and static), effect priority, autorun options, nested effects. Use when creating effects that react to signal changes.

Lifecycle and organizational management for @spearwolf/signalize: SignalGroup for class/object-attached reactivity and logical grouping, parent-child hierarchies, named signals, SignalAutoMap for dynamic signal collections. Use when managing multiple related signals, component lifecycles, or logical units of reactive state.

Signal-to-signal connections for @spearwolf/signalize: link/unlink for one-way data flow, SignalLink class for mute/unmute/touch control, async patterns (nextValue, asyncValues). Use when connecting signals or creating data flow pipelines.

Computed/derived signals for @spearwolf/signalize: createMemo for cached computations that automatically update when dependencies change. Use when creating derived values that depend on other signals.

Testing patterns for @spearwolf/signalize code: assert helpers for counting signals/effects/links, subscription leak detection, cleanup verification patterns. Use when writing tests for signalize-based code.

Utility functions for reactive context control in @spearwolf/signalize: batch (deferred effect execution with priority ordering), beQuiet (suppress dependency tracking), hibernate (complete context isolation). Use for performance optimization and advanced control flow.