Repository navigation
Conversation
It claimed daily pstack use and no Cursor in consecutive sentences. pstack is a Cursor plugin, so both cannot be true.
The renamed entry points already keep the two projects apart, so the section told readers to route around a problem the names solved.
Watcher and Azure-testing detail is release-note depth, not README depth. The upstream line moves up next to the divergence pointer.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 35be11e889
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ``` | ||
|
|
||
| Three commands carry their own names so you can always tell which is which. `ronin-mode`, `setup-ronin`, `ronin-review`. Upstream calls them `poteto-mode`, `setup-pstack`, `show-me-your-work`. | ||
| Three commands carry their own names. `ronin-mode`, `setup-ronin`, `ronin-review`. Upstream calls them `poteto-mode`, `setup-pstack`, `show-me-your-work`, so both sets can sit side by side and you always know which one you invoked. |
There was a problem hiding this comment.
Restore the Cursor coexistence warning
When Cursor's pstack plugin and a global ronin installation are both visible to Cursor, only these three entry points are renamed; PORTING.md:27 confirms that the other leaves retain their upstream names and are indistinguishable in Cursor's picker. Commands such as /how, /arena, and /swarm can therefore still collide, so claiming both sets can sit side by side while deleting the host-targeted installation guidance can cause users to invoke the wrong implementation. Restore that guidance or qualify the claim.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 35be11e. Configure here.
|
Superseded by a smaller product boundary. The replacement PR keeps the principles, namespaces every retained skill, and removes the adapter and model-routing layers. |

ronin should trust distinct jobs and reproducible evidence, not model plurality.
This change:
explore,implement,judge,explain, andverifyas behavioral task profilesSingle-model hosts remain complete supported environments. Cross-provider review stays available as an explicit escalation, but reviewer count or model agreement never substitutes for evidence or acceptance verification.
Validation:
bun run checkgit diff --checkReview:
Note
High Risk
This changes core delegation contracts, skill names, install path, and release verification across the whole distribution; consumers and CI must adopt the new
ronin-*commands and skills-CLI install model.Overview
Ronin stops routing on models and host adapters. Delegation is defined by five task profiles (
explore,implement,judge,explain,verify) inskills/ronin-core/task-profiles.json, with subagents inheriting the active model and reviews reported asself-revieworfresh-context-review.HOST_CONTRACT.mdand workflow skills are updated to match; docs and guides drop/setup-ronin,models.yaml, and cross-provider review framing.Public surface is curated and namespaced. Retained skills move to the
ronin-*prefix (43 skills); upstreamarena,automate-me, andsetup-pstackare removed.ronin-architectreplaces parallel arena-style runs with explicitly named structural directions, per-directionexploreworkers, and ajudgesynthesis step.Distribution and verification simplify. The
adapters/tree and Bun globalinstall/uninstallpaths go away; install is documented vianpx skills, andbuildshipsskills+docsonly.verify.mjsadds profile/host-contract semantic checks, expects 43 skills, bans legacy model-role and “manufactured diversity” copy in key docs, and removes isolated-home install lifecycle tests from the gate.Reviewed by Cursor Bugbot for commit 89d6305. Bugbot is set up for automated code reviews on this repo. Configure here.