Add JevForge to research projects

[zwliJay]

Project: https://github.com/zwliJay/jev-forge

Where Jev fits: JevForge is an end-to-end Jev-style structured-decision stack covering auditable data construction, Qwen3.5-0.8B training, fixed Mind2Web/OOD evaluation, preliminary RLCD, local serving, and interactive replay.

• I added one object to data/projects.json and ran npm run validate
• I did not commit README.md or site/index.html (CI regenerates them)
• I am the author, or I linked where the project was announced

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• New Content
  • Added the JevForge project to the project listings.
  • Categorized it under research and identified Python as its primary language.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 95314253-c304-4834-b800-90d8ac238ca4

📥 Commits

Reviewing files that changed from the base of the PR and between 776f499 and 6cd5e8f.

📒 Files selected for processing (1)

• data/projects.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The project catalog now includes the JevForge repository, website, description, research category, Python language, zero stars, and addition date.

Changes

Project catalog

Layer / File(s)	Summary
Add JevForge entry data/projects.json	The projects array now contains the JevForge project with its repository, website, description, category, language, star count, and addition date.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: scald

Merge Risk: ⚪ Minimal · up to 6cd5e

The catalog entry matches the repository's recorded addition date and passes the date-format contract, so no actionable merge risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: adding JevForge to the research projects.
Description check	✅ Passed	The description provides the project URL, explains where JevForge fits, confirms validation, confirms that generated files were not committed, and addresses project authorship or announcement linkage.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[scald]

Landed on main as 2800612 with you as the commit author, so it shows on your contributions. Live at https://awesomejev.com/#benchmarks-research.

Closing the PR rather than merging because the site's data file gets appended to nightly, which makes fork branches conflict faster than they can be reviewed. Landing the entry directly keeps your authorship without force-pushing to your fork. Thanks for the submission.