The shared-wallet shim's fan-out in the data context fed the ORM subscriptions
this provider used to open: readGraphs, writeGraphs, protectedScope,
protectedGraph and the effect that filled them from storeRegistry. Every entity
reads through a Refine backend now, which takes no graph list, so none of it was
reachable. Same for findNg, mapUser and mapParticipation -- reading a record
into a domain type belongs to a backend's binding, not here. storeRegistry
itself stays: the @data multistore scenarios drive it directly.
This is debt the migration created, not debt it inherited, which is why it goes
rather than waiting for a tidy-up.
What the removal COSTS is written where it happened: placement by scope no
longer narrows what the app reads. The backend's declaration is
where that belongs and nothing honours it yet; applyIsolation is the only
narrowing left.
And setLike.delete is now marked as the defect it is. It is a no-op lifted from
a branch where the fixture seed is off, so nothing needs deleting before it --
false here, where the step that empties the wallet therefore does nothing.
Fixing it needs a decision the comment states, because the app exposes no
deleteEvent.
Sylvain Duchesne
8cdd146c81
