# fix\(mobile\): content-accurate inspector identities and isolated subscriber errors · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/401d3c70b6b6090d5a80c5eb408b2e3cf607bffc)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 401d3c70b6b6090d5a80c5eb408b2e3cf607bffc

Requested commit: 401d3c70b6b6090d5a80c5eb408b2e3cf607bffc

Commit: 401d3c70b6b6090d5a80c5eb408b2e3cf607bffc

Tree: 2ea39e749a4166f37725026789cebf6acb9a42db

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): content-accurate inspector identities and isolated subscriber errors

- Review registrations all used `review:changed-files` although the pane
  shows different content per selected section, and files registrations
  keyed only on the relative path, which collides across environments and
  worktrees. Identity builders (reviewInspectorIdentity,
  filesInspectorIdentity) now encode what the user actually sees —
  section, environment, thread-or-cwd, path — so selecting a healthy
  section out of a crashed inspector resets the boundary, while unrelated
  rebuilds still do not. Tests cover both directions.
- recordRenderError/clearRenderErrorRecords isolate each subscriber call:
  a throwing useSyncExternalStore listener can no longer propagate through
  componentDidCatch or starve the subscribers registered after it.

```

## Parents

- [3e01a27d8b5f5ee8e9a02d233a686bacc0e35189](https://git.cafe/pingdotgg/t3code/commit/3e01a27d8b5f5ee8e9a02d233a686bacc0e35189?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/401d3c70b6b6090d5a80c5eb408b2e3cf607bffc?format=markdown)