[xqliu]

What does this PR do?

Adds Orbi (AGPL-3.0, 195 stars, active daily). It's a self-hosted coding agent: you label a GitHub issue ai-ready, it writes the change in an isolated worktree, opens a PR, a separate review session checks the PR against the issue's acceptance criteria, and only the reviewed head is merged and released as a tag. It belongs in Agent Coding next to SWE-Agent and Open SWE, which also work from GitHub issues.

Checklist

• Project added to data/projects.json with correct schema
• node scripts/generate-readme.js was run and README.md is up to date
• node scripts/validate.js passes (node scripts/check-links.js: 121 ok)
• Project meets inclusion criteria (open source, active, documented, 50+ stars or a documented novelty exception)
• Category and cross-list scope are correct; any duplicate listing is justified
• Description is concise, objective, starts with a capital letter, and ends with punctuation
• Links, paper, license, and factual claims were checked against primary sources
• No duplicate entries

Category

• Agent Coding and Software Engineering

Disclosure: I maintain Orbi.

[autogame-17]

Thanks for the submission. The repository, licensing and coding-agent scope are supported. The integration blocker is that GitHub currently reports this head as CONFLICTING / DIRTY against main 48996991a8feb24ec28c8e8b2faa2c22a551b380. Please refresh the branch from current main, preserve the current catalog, resolve the source-data conflict and regenerate README. The current head has no project check/workflow run; that is missing execution, not a test failure.

While refreshing the entry, please also clarify the release condition at data/projects.json:1530 and the generated README.md:157. The upstream README at the audited revision says “Release when you decide” and “When you request a release.” Suggested wording: “…to an independently reviewed, merged pull request and, when requested, a tagged release.” This wording clarification is not a rejection of the project's release capability.

The entry itself passes current-main schema validation in an isolated catalog. That does not resolve the actual branch conflict or supply current CI evidence.

After updating the branch, run:

node scripts/generate-readme.js

node scripts/validate.js

git diff --check

node scripts/check-links.js

Please also wait for the actual validation and link-check workflow jobs to succeed on the updated head. Missing runs or action_required with zero jobs are not successful checks.

[autogame-17]

Verified the refreshed catalog-only diff against current main. The entry correctly qualifies releases as requested, reuses the github-issues tag, and has the current canonical star snapshot. Generated README, validation, and link checks passed locally and in the two current GitHub Actions jobs.