chore(submodules): sync BoTZ/DoX gitlinks to hardened baseline

[POWERFULMOVES]

Summary

• update PMOVES-BoTZ gitlink from 94529789 to 4382e270 (includes merged BoTZ PR docs: log m2 automation implementation plan #76)
• update PMOVES-DoX gitlink from 035364ce to 5de730a4 (includes merged DoX hardened updates through 2026-03-04)
• keep scope atomic: no non-submodule file changes

Why

main was behind hardened pointers for these two submodules. This sync aligns superproject gitlinks with the intended hardened baseline before further production validation.

Validation

• git diff --submodule=log confirms only BoTZ/DoX pointer moves
• local tree clean after commit except branch metadata

Summary by CodeRabbit

• Chores
  • Updated internal dependencies with no functional changes to user-facing features.

[coderabbitai]

📝 Walkthrough

Walkthrough

Two submodule references were updated with new commit pointers. PMOVES-BoTZ submodule advanced to a newer commit, and PMOVES-DoX submodule was similarly updated. No functional code changes were introduced.

Changes

Cohort / File(s)	Summary
Submodule Updates PMOVES-BoTZ, PMOVES-DoX	Submodule pointers updated to reference new commits. PMOVES-BoTZ: 94529789f8 → 4382e270..., PMOVES-DoX: 035364ce6... → 5de730a49.... No behavioral or functional code modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Submodules hop to newer ground,
Commit pointers spinning all around,
No code was changed, just refs we bind,
The cleanest update you'll ever find! 🌟

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is missing required sections: Testing section with commands/output and Required Checks checklist. Only Summary and Validation sections are present.	Add a Testing section documenting the validation commands run, and include the Required Checks checklist with appropriate items marked or addressed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: syncing submodule references to a hardened baseline. It is concise, specific, and directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/submodule-gitlink-sync-hardened-2026-03-06

---

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

[coderabbitai]

🧹 Nitpick comments (1)

PMOVES-DoX (1)

1-1: Consider pinning the image build to the commit hash instead of a branch reference.

The image build in pmoves/images.yaml:88-93 currently uses ref: heads/PMOVES.AI-Edition-Hardened, which today resolves to the same commit as the gitlink (5de730a4). However, since the branch reference is not pinned, future updates to that branch could advance independently of the submodule commit, causing drift from the hardened baseline. For maximum safety and clarity, pin the image source directly to 5de730a497eeecf0ab83ed4998e1bb038e6453cc.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@PMOVES-DoX` at line 1, The image source in pmoves/images.yaml currently uses
a branch ref "heads/PMOVES.AI-Edition-Hardened" which can diverge from the
submodule gitlink; update the ref to the exact commit
"5de730a497eeecf0ab83ed4998e1bb038e6453cc" to pin the build to that commit.
Locate the image entry around pmoves/images.yaml lines referencing ref:
heads/PMOVES.AI-Edition-Hardened and replace the branch ref with the full commit
SHA so the image build remains deterministic and aligned with the submodule
gitlink.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@PMOVES-DoX`:
- Line 1: The image source in pmoves/images.yaml currently uses a branch ref
"heads/PMOVES.AI-Edition-Hardened" which can diverge from the submodule gitlink;
update the ref to the exact commit "5de730a497eeecf0ab83ed4998e1bb038e6453cc" to
pin the build to that commit. Locate the image entry around pmoves/images.yaml
lines referencing ref: heads/PMOVES.AI-Edition-Hardened and replace the branch
ref with the full commit SHA so the image build remains deterministic and
aligned with the submodule gitlink.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a28729b8-0042-4dfc-abba-3c6b847ce5cd

📥 Commits

Reviewing files that changed from the base of the PR and between b409835 and 412fe7b.

📒 Files selected for processing (2)

• PMOVES-BoTZ
• PMOVES-DoX