cycle/0007: release prep for 0.1.0#3
Conversation
- bin/graft.js starts MCP stdio server via --import tsx - package.json: version 0.1.0, files field, updated description - tsx moved to runtime dependency (needed by bin entry point) - README: install instructions, MCP config setup, updated tool table - ESLint ignores bin/ (entry script, not linted)
- VISION.md: updated to 7 cycles, 227 tests, 10 tools, 3 legends, added cycles 0003-0007 summaries, CLEAN_CODE legend - CHANGELOG: versioned as 0.1.0, added graft_diff, run_capture, tool descriptions, bin entry point
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 31 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (20)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. 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: 999e36b93e
ℹ️ 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".
| @@ -0,0 +1,11 @@ | |||
| #!/usr/bin/env node --import tsx | |||
There was a problem hiding this comment.
The shebang currently passes node --import tsx as a single argument to env, so the published bin fails to launch on standard Unix setups (in this repo, ./bin/graft.js exits with /usr/bin/env: ‘node --import tsx’: No such file or directory). That makes the advertised npx @flyingrobots/graft entrypoint non-functional until the shebang is changed to a split form (for example using env -S).
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
✅ Fixed in 1fbc598. Shebang now uses #!/usr/bin/env -S node --import tsx for Linux compatibility.
| return Promise.resolve(textResultWithReceipt("run_capture", { | ||
| error: msg, | ||
| stderr: typeof stderr === "string" ? stderr.slice(0, 2000) : "", |
There was a problem hiding this comment.
In the error path, run_capture only returns stderr and drops the command's stdout, even though many failing commands emit the primary diagnostics on stdout; it also omits the normal captured-output payload fields. This makes failure analysis inconsistent with the tool contract of returning tailed command output and can hide actionable output whenever the exit code is non-zero.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
✅ Fixed in 1fbc598. Error path now returns captured stdout (tailed) alongside stderr.
ASAP: - Outline quality audit (if outlines are weak, agents fight the tool) - Live 5-metric study design (burden, completion, churn, recovery, evasion — turns thesis into defensible infrastructure) Up-next: - Non-read burden sources (shell output, search results, subagent bloat — don't overfit to file reads alone) - Token usage comparison updated to reference the full study Key insight: proof requires showing agents don't get WORSE, not just that bytes get smaller.
Two-phase workflow triggered by vX.Y.Z tags on main: Phase 1 (sanity): - Tag version matches package.json version - Lockfile in sync (frozen install) - package.json has required fields (name, version, description, license, repository, bin, files, engines) - Lint, typecheck, tests pass - Dry-run pack verifies publishable contents Phase 2 (release): - Extracts changelog section for the tagged version - Creates GitHub release with changelog notes
- bin/graft.js: use #!/usr/bin/env -S node --import tsx (Linux needs -S to split args) - run_capture: error path now returns captured stdout alongside stderr (commands that produce output before failing)
1 participant
Summary
All pre-release items resolved:
npx @flyingrobots/graftstarts MCP serverTest plan
src/parser/lang.tsAfter merge
Tag
v0.1.0andnpm publish.