docs: README + ROADMAP for v0.8 shipped (audit, orchestrate, verify, babysit) + fork retarget#7
Conversation
…babysit) + fork retarget Updates the docs to reflect what shipped in PRs #1 + #6 and decouples the URLs from the upstream chorus-codes/chorus slot now that this fork lives on its own at crypticpy/chorus. README: - Templates section: new rows for audit-* and pr-babysit + three explainer subsections (audit + orchestrate, verify + TDD loop, PR-babysit) - Commands section: chorus quickstart + chorus babysit subcommand group - Roadmap mini-summary: v0.8 marked done - Repo/issue/clone/discussion URLs: chorus-codes/chorus → crypticpy/chorus (badges + npm install left alone — those wait for the rebrand PR) ROADMAP: - Status tracker: 4 new shipped rows (audit phase, orchestrate phase, verify phase + TDD loop, PR-babysit) - chorus-codes/chorus migration items marked MOOT — fork is its own project, no contribution-back planned - Section 7 (migration) collapsed to a short MOOT note - "Where we are" footnote updated to 2026-05-17 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
crypticpy has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @crypticpy, you have reached your weekly rate limit of 2500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughREADME.md and ROADMAP.md are updated to migrate the repository to the crypticpy/chorus organization, mark v0.8 as complete, expand feature documentation (MCP tools, code review walkthrough, templates, commands), reformat governance sections into tables, and refine product messaging with emphasis adjustments. ChangesDocumentation Updates for v0.8 and Organization Migration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5d67dd1459
ℹ️ 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".
|
|
||
| ### PR-babysit | ||
|
|
||
| Once you've got a PR open and the review bots are starting to comment, `chorus babysit register <pr-url>` puts that PR on an autonomous loop. The daemon polls the PR, judges each new bot comment (apply-trivial / apply-targeted / apply-architectural / reply-disagree / reply-ack / defer-to-human), pushes fixes or posts replies, runs verify on each fix, and squash-merges when CI is green and two quiet ticks have passed. Inspect with `chorus babysit show <id>`; pause with `chorus babysit pause <id>`. |
There was a problem hiding this comment.
This overstates what the shipped babysit loop does: in the current state machine, quiet_check only returns merged after fetchPrMetadata reports the PR is already merged, and repo-wide search under src/daemon/babysit shows no gh pr merge/CI-green gate implementation. In a real babysat PR this will keep cycling in quiet_check until a human or another system merges it, so telling users it squash-merges after quiet ticks can lead them to leave PRs unattended expecting Chorus to finish the merge.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Good catch — you're right. The in-app daemon (src/daemon/babysit/state-machine.ts) only transitions quiet_check -> merged after fetchPrMetadata reports the PR is already merged externally; there's no gh pr merge call and no CI gate.
Fixed in 48f0f88 — both the README "PR-babysit" section and the ROADMAP v0.8 row now say the daemon settles in quiet_check after two quiet ticks and waits, and that the /babysit-pr Claude Code skill (which wraps this loop) is what actually performs the squash-merge.
The in-app `chorus babysit` daemon (src/daemon/babysit/state-machine.ts) sits in `quiet_check` after two quiet ticks and waits for an external merge — it does not call `gh pr merge` itself and does not gate on CI. The README and ROADMAP both overstated this, implying the daemon squash-merges on its own. Update both to point to the `/babysit-pr` Claude Code skill (this loop) as the surface that actually performs the merge. Caught by ChatGPT Codex review on PR #7. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
crypticpy has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 14-15: The two badge lines use empty link targets
(`[]()` and `[]()`), which violates MD042; fix by
removing the empty link wrapper or supplying valid URLs: either change to plain
images `` and
`` or replace the
empty `()` with the intended target URLs (e.g., project status page or node
compatibility docs) so the nested badge image links are not dead.
In `@ROADMAP.md`:
- Line 69: The ROADMAP row for "Runner decoupling from SSE — background runChat
+ event bus replay" currently conflicts with other entries that mark it shipped;
update this table row's status from "⏳ TODO" to the shipped state used elsewhere
(e.g., the same phrasing used for the shipped entries referencing v0.7 /
"surgical fix" and "fire-on-POST so MCP flows") so the roadmap consistently
reflects that the surgical v0.7 fix has landed and the proper fix is considered
shipped; ensure the cell text matches the exact shipped wording used in the
other rows to avoid contradictions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 352885d9-18d3-4a61-a2e9-c7401dfa9bd7
📒 Files selected for processing (2)
README.mdROADMAP.md
…ing contradiction - README: Status/Node badges had empty `()` link targets (MD042) and the Status badge still said v0.7. Point Status -> ROADMAP.md (now v0.8) and Node -> nodejs.org so both have real targets. - ROADMAP: "Runner decoupling from SSE" row was still marked TODO for v0.8 even though lines 48 and 267 record it as shipped in PR chorus-codes#21 (2026-05-02). Align row to the v0.7 DONE status used elsewhere. CI URL badge and `npm i -g chorus-codes` install line still intentionally untouched — those wait for the rebrand PR. Caught by CodeRabbit on PR #7. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
crypticpy has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
1 participant
Summary
chorus quickstartand thechorus babysitsubcommand group, Roadmap mini-summary marks v0.8 as done.chorus-codes/chorustocrypticpy/chorussince this fork is now its own project. Badges andnpm i -g chorus-codesdeliberately untouched — those wait for the rebrand PR (new project name + new npm package).chorus-codes/chorusmigration items are marked MOOT, section 7 collapsed to a short MOOT note, "Where we are" footnote refreshed to 2026-05-17.Docs-only change. No code, no tests, no behaviour.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
chorus quickstartand “Babysit a PR” docs; updated bug reporting, telemetry example, and roadmap v0.8 status