Add react-native-edge-glow library details

[aravi365]

📝 Why & how

Adds a new library: react-native-edge-glow — a Siri/Gemini-style animated glow around the screen edges. It runs the animation on the UI thread via Reanimated, reads the device's real display corner radius on Android 12+ (via the public WindowInsets API), and ships with presets, a breathing pulse, and reduce-motion support. Dependencies are only react-native-svg + react-native-reanimated (no Skia).

• npm: https://www.npmjs.com/package/react-native-edge-glow
• Repo: https://github.com/aravi365/react-native-edge-glow

✅ Checklist

• Added library to react-native-libraries.json
• Updated library in react-native-libraries.json

[aravi365]

The data-test-and-validate check is failing on a GitHub API error, not on my entry:

FORBIDDEN — path: ["repository", "stargazers"] — "Resource not accessible by integration"

My repo is public and reachable unauthenticated (stars, raw content, and the npm downloads API all resolve), so this looks like the fork-PR github.token (scoped contents: read) being unable to read repository.stargazers via GraphQL — a CI-token limitation rather than a problem with the submission.

Could a maintainer re-run in a trusted context or merge? My understanding is the authoritative data fetch runs post-merge with a privileged token, so the stars/metadata should populate correctly then. Happy to adjust the entry if anything's actually wrong with it. Thanks!
cc: @Simek

[Simek]

Hey @aravi365, it was failing initially on the lack data in npm API. It usually takes up to 24h for npm API after initial package publish to collect and return the required data.

I will re-run the workflow, by not sure if this would help, let's see, but you might need to recreate the PR. Also, in the current state lint checks will fail on whitespace. And one more thing, please move the new package at the end of the list - we use this order for "Recently added" sort option, see:

• https://github.com/react-native-community/directory#how-do-i-add-a-library

[Simek]

Yeah, re-run does not help (https://github.com/react-native-community/directory/actions/runs/29586792480), the run context have been compromised already. Please re-create the PR.