I've started converting to signal forms and encountered a reactivity challenge that may warrant discussion.

The Conflict:

1. Signal Store state is frozen/immutable - intentional for predictable state management
2. Reactive Forms require mutable objects - forms need to write back to the bound object

Current Workaround:

// Using structuredClone to break the frozen reference
const editableEntity = computed(() => structuredClone(store.selectedEntity()));

// Or with linkedSignal for automatic resync on source changes
const editableEntity = linkedSignal(() => structuredClone(store.selectedEntity()));

I've tried several things, for instance untracked(), which came closest, but it removes reactivity entirely. What's needed is something that reactively updates on read but doesn't attempt to write back to the frozen store object.

With traditional Reactive Forms, we were already mapping store data to FormGroup structures, so the performance cost may be comparable. However, the current approach feels like an unintended workaround rather than a deliberate pattern. Additionally, the error message ("object is not extensible") is difficult to trace back to this root cause.

Questions:

1. Is there a recommended pattern for binding signal store state to forms that we're missing?
2. Would a built-in selectMutable() selector or signalStoreFeature that provides a cloned, writable version of state for form binding be considered?
3. Are there plans to address this in future releases, or is the explicit clone approach the intended design?