[codex] Install plan-to-git from main

[skulidropek]

Summary

• Change generated project Dockerfiles to install plan-to-git from the latest ProverCoderAI/plan-to-git main branch instead of a hard-coded commit SHA.
• Add a remote GitHub commit metadata ADD before the install layer so moving main invalidates Docker cache for the plan-to-git install step.
• Update container template coverage for the floating main install command.

Why

plan-to-git PR #11 is merged and contains the fix for structured Codex update_plan imports and draft PR publishing. docker-git should consume the latest upstream main rather than requiring a new hard-coded revision each time plan-to-git changes.

Mathematical Guarantees

Invariant

• renderDockerfile(config) contains no hard-coded plan-to-git commit SHA.
• plan-to-git installation targets refs/heads/main from ProverCoderAI/plan-to-git.
• Moving plan-to-git/main changes the remote commit metadata input before the install layer.

Postcondition

• New generated project images install a plan-to-git binary that includes the current upstream main behavior at build time.

Complexity

• Template rendering remains O(1) time and O(1) space.

Verification

• bun run --cwd packages/container test
• bun run --cwd packages/container typecheck
• git diff --check
• cargo install --git https://github.com/ProverCoderAI/plan-to-git --branch main --locked --bins --root <tmp> --force plus plan-to-git sync --help check for --pr <PR>

[skulidropek]

AI Session Backup

Commit: 1e3d423
Status: success
Files: 10 (6.23 MB)
Links: README | Manifest

git status

On branch codex/use-latest-plan-to-git-main
Your branch is up to date with 'origin/codex/use-latest-plan-to-git-main'.

nothing to commit, working tree clean

[coderabbitai]

Warning

Review limit reached

@skulidropek, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 41 minutes and 39 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4c8b6ea3-effe-4c3d-aef6-70dd26343d07

📥 Commits

Reviewing files that changed from the base of the PR and between 74b74e5 and 1e3d423.

📒 Files selected for processing (2)

• packages/container/src/core/templates/dockerfile-prelude.ts
• packages/container/tests/core/templates.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}