Superseded by #1435: chore(submodules): bump AgentGym, Archon, BoTZ after 5090 lane PR merges

[POWERFULMOVES]

Summary

Superproject gitlink bumps after 5090 lane PR merges:

Submodule	Old Pointer	New Pointer	Inner PR
PMOVES-AgentGym	f724cfc	d6c0687	POWERFULMOVES/PMOVES-AgentGym#2
PMOVES-Archon	f4bd252	d5383745	POWERFULMOVES/PMOVES-Archon#14
PMOVES-BoTZ	e50d8b6	bf9b372b	POWERFULMOVES/PMOVES-BoTZ#127

All three inner PRs merged via "Create a merge commit" to preserve gitlinks.

⚠️ Merge Note

enforce_admins is now TRUE on main. Merge must use "Create a merge commit" with a signed commit (GPG key required). Squash merge will drop gitlinks.

Village Rule

One scope, one commit, one PR.

Summary by CodeRabbit

• Chores
  • Updated PMOVES-AgentGym, PMOVES-Archon, and PMOVES-BoTZ subprojects to their latest versions.

[coderabbitai]

Warning

Rate limit exceeded

@POWERFULMOVES has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 42 minutes and 59 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 497d4e1a-6f0f-4f93-b0f3-24a28d739f70

📥 Commits

Reviewing files that changed from the base of the PR and between 5a4d1db and 15cb6e8.

📒 Files selected for processing (1)

• pmoves/integrations/archon

📝 Walkthrough

Walkthrough

This PR updates three git submodule pointers in the PMOVES.AI repository: PMOVES-AgentGym, PMOVES-Archon, and PMOVES-BoTZ are each advanced to new upstream commits. No code or configuration changes are present; only submodule commit references are modified.

Changes

Submodule Sync

Layer / File(s)	Summary
Submodule Pointer Updates PMOVES-AgentGym, PMOVES-Archon, PMOVES-BoTZ	Three dependency submodules are updated to new commit references: AgentGym (f724cfc → d6c0687), Archon (f4bd252 → d538374), and BoTZ (e50d8b6 → bf9b372).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• POWERFULMOVES/PMOVES.AI#1059: Updates PMOVES-Archon and PMOVES-BoTZ submodule pointers to different commits.
• POWERFULMOVES/PMOVES.AI#1038: Syncs PMOVES-AgentGym and PMOVES-BoTZ submodule gitlinks to new commits.
• POWERFULMOVES/PMOVES.AI#1300: Updates PMOVES-Archon and PMOVES-BoTZ submodule references.

Poem

🐰 Three submodules dance in sync,
Commits updated in a blink,
AgentGym, Archon, BoTZ aligned—
Dependencies refined! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description includes a summary with detailed submodule changes and links, but lacks the required Testing section with commands/output and does not include the Required Checks checklist.	Add a Testing section documenting verification steps and include the Required Checks checklist from the template, even if marking items as not applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: bumping three submodules (AgentGym, Archon, BoTZ) following their PR merges.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/submodule-bump-agentgym-archon-botz-2026-05-08

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5a4d1dbdae

ℹ️ 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".

[chatgpt-codex-connector]

Sync both Archon gitlinks when bumping Archon

Updating only PMOVES-Archon to d538374... leaves the duplicate mount pmoves/integrations/archon on the old commit (f4bd252...), which introduces a split revision for the same repository. This is a functional regression because local/vendorized Archon builds and the submodule UI compose path read from integrations/archon (see pmoves/services/archon/Dockerfile COPY integrations/archon ... and pmoves/docker-compose.archon-ui.submodule.yml build context), so the intended Archon bump is not actually picked up in those workflows.

Useful? React with 👍 / 👎.

[POWERFULMOVES]

fix(submodules): resolved codex-connector P1 comment

Confirmed the split revision was real — pmoves/services/archon/Dockerfile COPYs from integrations/archon and pmoves/docker-compose.archon-ui.submodule.yml uses it as a build context. Stale gitlink would have silently built old Archon code.

Fixed in commit 15cb6e8d8: bumped pmoves/integrations/archon from f4bd252c → d5383745 to match PMOVES-Archon.

---

Known CI failure: Validate agent-zero (PR) fails due to boring-sys-imp v2.1.0 Rust/BoringSSL compile error inside the agent-zero Docker image. This is a pre-existing upstream dependency issue — not introduced by this PR's gitlink bumps. 20/21 other checks pass. This PR only modifies gitlinks (no code changes) and is safe to merge once the agent-zero build issue is tracked separately.

[POWERFULMOVES]

5090-CLAUDE review — superseded by #1435, pinned SHAs are stale

This PR was opened from pre-merge branch-tip SHAs; the inner PRs were then merged via "Create a merge commit", producing different mergeCommit SHAs.

Submodule	This PR	Actual mergeCommit	Status
PMOVES-AgentGym	d6c0687744	42bcff828	❌ stale branch-tip
PMOVES-Archon	d53837454	d5383745	✅ matches
PMOVES-BoTZ	bf9b372b3	1b90ed8e4	❌ stale branch-tip

The two stale SHAs currently exist in their respective inner repos' object stores (because the original promote branches were just pushed) but are at risk of garbage-collection once those branches are deleted from origin (GitHub's default after merge). The merge-commit SHAs are guaranteed-reachable from the default branches, which is what we want submodule pointers to track.

PR #1435 has the correct merge-commit SHAs and additionally bundles the dirty CODEX parity docs that have been sitting in the working tree. Per repo precedent (#839/#840/#841 superset pattern), recommend closing this PR in favor of #1435.

Lessons-learned for future superproject pointer-bump PRs

When authoring a gitlink-bump PR after inner-repo PRs merge:

1. Wait for the inner PRs to actually merge (not just be approved)
2. Re-fetch each inner repo's default branch
3. Pin to the mergeCommit SHA from the closed inner PR (gh api repos/.../pulls/N -q '.merge_commit_sha'), not to the branch-tip SHA you had locally before merge
4. The two SHAs differ when the operator chooses "Create a merge commit" (the safer strategy for pointer-bump PRs)

— 5090-CLAUDE, 2026-05-08