Expo config plugin is a no-op but is documented as needed for native crash reporting #206

The Expo config plugin shipped in @exceptionless/react-native 3.2.1 (@exceptionless/react-native/expo-plugin) returns the Expo config unchanged. The README and the agent skill tell users to add it for development and standalone builds, and to check it's present when native crashes don't show up, but adding or removing it has no effect on the generated native project.

Where

• packages/react-native/expo-plugin/withExceptionless.cjs#L3: const withExceptionless = (config) => config;
• packages/react-native/README.md#L41-L49: "Add the config plugin to app.json when using development or standalone builds"
• .agents/skills/exceptionless-javascript/references/client-react-native.md#L107: "verify ... that the config plugin is present before rebuilding the native app"

What happens

npx expo prebuild produces the same ios/ project with or without the plugin in app.json. The native crash reporter is linked by autolinking from exceptionless-react-native.podspec, not by the plugin. Users who follow the troubleshooting advice will be checking for a plugin that doesn't change anything.

Expected

Either the plugin applies the native configuration the SDK needs, or the docs say it's optional (kept for forward compatibility) and point troubleshooting at what actually matters: a development or standalone build, a rebuilt native app, and autolinking of the pod.

Steps to reproduce

1. In an Expo app with @exceptionless/react-native 3.2.1, run npx expo prebuild --clean with "plugins": ["@exceptionless/react-native/expo-plugin"] in app.json, and save the ios/ folder.
2. Remove the plugin entry and run npx expo prebuild --clean again.
3. Diff the two ios/ folders: there is no difference.

Suggested fix

If no native changes are needed, keep the plugin as a harmless placeholder but update the README and skill to say it's optional and remove it from the troubleshooting steps. If native configuration is actually needed, implement it in the plugin with the appropriate @expo/config-plugins mods and add a test that checks the modified config.