optative-script: add storage/error boundaries

currently, the whole tree is flattened into a singel reconciler with tagged object types. as long as the order is defined correctly (i. e. dependencesi does not cause issues) this is ok and creates a useful simplification and performance optimization.

but, putting everythign in one reconciler does become a probelm at scale, dpeending on the use case as well, because:
- there are no error boundaries, all errors end up in the same reconciler
- this does not allow for detailed customization for the diff/storage implementation

we should allow the creation of reconciler boundaries which become their own error boundaries and storage boundaries - this shoudl create a nested tree of reconcilers, a "Multiplied" reconciler boundary should actually multiple the storage and all

No files or tests are named. Start by locating the current single reconciler and tracing how errors, storage, and tagged object types flow through it. The work is done when nested reconciler boundaries can provide separate error and storage boundaries, including the proposed multiplied storage behavior.

Written by the indexing model from the issue text.