fix(mobile): guard every hostile read path and catch inspector-callback throws

- describeRenderError/recordRenderError/readErrorStack now read message,
  name, and stack through guarded access: an Error subclass with throwing
  getters can no longer explode inside componentDidCatch and defeat the
  recovery it is part of. The recovery view's Copy details uses the same
  guarded stack read. Tests cover hostile getters and ordinary errors.
- The inspector invokes the route-supplied renderer in a dedicated child
  (InspectorRenderer) inside the boundary. Calling it as a children
  expression ran the callback during the pane's own render, above the
  boundary, where it could not be caught.
- ScreenRenderFallback forwards the captured component stack to all three
  exits, so Copy details keeps the component path on every screen fallback.
aeb3582e79Julius Marminge committed on 9/22/2026, 11:33:44 PMparenta4e849c
5 files changedLine totals unavailable