docs: refresh Jev Social v0.1.10 review

[IRONICBo]

What changes and why?

• refresh the existing Jev Social app entry from v0.1.8 to the current immutable v0.1.10 release
• replace the stale versioned install commands and commit links
• document the v0.1.10 socai child-process privacy default: telemetry stays off unless the exact value SOCAI_TELEMETRY=1 opts in
• keep the guide scoped to Jev Social while describing lowercase socai CLI as its local browser-execution dependency

Canonical project: https://github.com/socai-io/jev-social

Reader benefit: the catalog now gives current, reproducible commands and an explicit provider/telemetry boundary instead of sending readers to the older release.

I maintain Jev Social.

Verification

Reviewed Jev Social release v0.1.10, commit 0ea7be9d2ad4e19d1ae629d9b01bb670a90546b8, on 2026-09-27:

• inspected README, SECURITY.md, LICENSE, package metadata, provider/classifier paths, the socai child environment, benchmark contract, checkpoints, preview logic, and release metadata
• npm ci --ignore-scripts — 0 vulnerabilities
• npm run check
• npm test — 199/199 offline tests passed
• verified the pinned source files and live project site are reachable

Validated this Awesome Jev change:

• npm ci --ignore-scripts — 0 vulnerabilities
• npm run check — Markdown lint, 5,377 local links, 657 community project checks, and all offline test groups passed
• git diff --check

No live Jev request, Chrome automation, or social-platform session was run for this catalog update. The checks establish the documented code paths and offline behavior, not model accuracy or end-to-end speed.

AI assistance

Codex assisted with source inspection, the focused documentation update, and running the recorded checks. I reviewed the resulting diff and remain responsible for the submission.

Checklist

• I read the repository's CONTRIBUTING.md.
• This change makes one focused correction to the existing Jev Social resource.
• The detail page and app directory entry are consistent; the root README has no version-specific fact requiring a change.
• Links work and descriptions are factual; prerequisites and limitations are clear.
• I ran the applicable checks and included no secrets or private data.