Document start-automaker.mjs entry point#3636
Merged
mabry1985 merged 1 commit intoMay 23, 2026
Merged
Conversation
|
Warning Review limit reached
Your plan currently allows 2 reviews/hour. Refill in 16 minutes and 22 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, 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 trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
Code Review — ? finding(s)
protoLabs Code Review Report
No findings recorded. |
mabry1985
pushed a commit
that referenced
this pull request
May 23, 2026
- Updates @protolabsai/sdk from ^0.3.0 to ^0.3.1, which ships the hook callback round-trip fix (protoCLI#261). Verified end-to-end via feature dispatch: ProtoProvider → SDK → bundled cli.js → gateway → protolabs/smart, PR #3636 merged cleanly. - CLAUDE.md: adds recovery section for the "stale ESCALATE checkpoint" trap observed during the SDK validation. Filed as P1 bug feature-1779512977020-k125yjmra. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
mabry1985
added a commit
that referenced
this pull request
May 23, 2026
* feat(providers): proto provider captures cli stderr on failure * chore(sdk): bump @protolabsai/sdk to 0.3.1 + document checkpoint trap - Updates @protolabsai/sdk from ^0.3.0 to ^0.3.1, which ships the hook callback round-trip fix (protoCLI#261). Verified end-to-end via feature dispatch: ProtoProvider → SDK → bundled cli.js → gateway → protolabs/smart, PR #3636 merged cleanly. - CLAUDE.md: adds recovery section for the "stale ESCALATE checkpoint" trap observed during the SDK validation. Filed as P1 bug feature-1779512977020-k125yjmra. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 23, 2026
mabry1985
added a commit
that referenced
this pull request
May 23, 2026
… still reconcile (#3642) Closes #3613. Every PR in this session's dogfood loop (#3636, #3637, #3638, #3639) sat in [review] until manual re-dispatch — even though the 60-second PostMergeReconciler poll was firing on schedule (44+ executions, 2ms each, no failures). Root cause: three of the original stuck features (#3593, #3611, #3612) had `prNumber: null` and `prUrl: null` on disk, because the PR-creation write path (PostAgentHook recovery or normal REVIEW) didn't always persist the metadata back to feature.json. The reconciler's filter required both fields, so those features were silently skipped every tick. Fix: PostMergeReconcilerCheck now runs in two phases. Phase 1 (existing): features with `prNumber` + `prUrl` → `gh pr view` direct lookup, transitions to done if merged. Phase 2 (new): features with `branchName` but missing `prNumber` or `prUrl` → `gh pr list --head <branch> --state merged --limit 1`. When a merged PR is found, writes `prNumber`/`prUrl`/`prMergedAt` back to the feature so subsequent ticks short-circuit through Phase 1. This is a safety-net fix — it doesn't remove the underlying need to plug the write-path gap that drops PR metadata, but it eliminates the permanent-stuck case where a feature has no way to be picked up by the reconciler. Tests: 15/15 passing. The two original "skips features without prNumber/prUrl" tests are now "falls back to branchName lookup" covering the new path. The "zero counts" test now requires *also* missing branchName to assert the skip path. Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a one-line JSDoc comment at the top of
start-automaker.mjsexplaining what the file does. The file is the cross-platform launcher that dispatches tostart-automaker.shand orchestrates dev/prod mode selection (see PR #3617 history for context). The comment should be a single short JSDoc that summarizes those responsibilities in plain language. No other changes.Acceptance:
start-automaker.mjshas a top-of-file JSDoc block (3-5 lines) describing the launcher purposeRecovered automatically by Automaker post-agent hook