chore: add Codex wrappers across PyAuto organs

[Jammy2211]

Overview

Apply the dual-harness skill contract from PyAutoBrain#84 to command-only workflows in PyAutoMind, PyAutoHeart, and PyAutoBuild. Preserve their Claude command behavior while making the same canonical bodies discoverable in Codex.

This is phase 2 of the approved Codex-wrapper rollout and depends on the installer behavior established by #84.

Plan

• Add thin Codex-compatible SKILL.md wrappers for the remaining command-only organ workflows.
• Remove obsolete Claude-only frontmatter or wording where it blocks Codex validation.
• Preserve intentionally reference-only Heart health legs.
• Validate all affected skill roots against the phase-1 installer in isolated homes.
• Run the autonomous ship gate and stop at open PRs.

Detailed implementation plan

Affected Repositories

• PyAutoMind
• PyAutoHeart
• PyAutoBuild

Branch Survey

Repository	Current Branch	Dirty?
PyAutoMind	feature/arxiv-papers-dispatch-lookback	clean; separate main worktree available
PyAutoHeart	main	clean
PyAutoBuild	main	clean

No active worktree claims conflict with these repositories. The existing PyAutoMind feature checkout will not be touched.

Suggested branch: feature/codex-organ-skill-wrappers

Work classification: organism infrastructure (cross-repo maintenance)

Worktree root: /home/jammy/Code/PyAutoLabs/.worktrees/codex-organ-skill-wrappers/

Implementation Steps

1. Add a thin wrapper for PyAutoMind/skills/spawn and update Mind ownership/install wording.
2. Add wrappers for PyAutoHeart/skills/review_release and verify_install; keep the health_sweep and status directories reference-only.
3. Add a wrapper for PyAutoBuild/skills/pre_build and make its harness wording neutral.
4. Validate every affected skill, including pre-existing metadata exposed by Codex validation.
5. Run the phase-1 installer with temporary CLAUDE_HOME and CODEX_HOME, asserting all new organ skills and existing Claude commands resolve correctly.
6. Run repo-appropriate tests and independent review on each branch before opening PRs.

Key Files

• PyAutoMind/skills/spawn/
• PyAutoMind/skills/OWNERSHIP.md
• PyAutoHeart/skills/review_release/
• PyAutoHeart/skills/verify_install/
• PyAutoBuild/skills/pre_build/
• PyAutoBrain#84 bin/install.sh contract

Original Prompt

Click to expand starting prompt

yes, make SKILL.md wrappers for PyAutoBrain and any other repos you see a Claude bias

Autonomy

Launched with --auto; effective level: safe (maintenance cap). The run may proceed through the four-leg autonomous ship gate and ends at PR-open. Merge and issue closure remain human actions.

[Jammy2211]

Phase 2 is locally complete across PyAutoMind, PyAutoHeart, and PyAutoBuild. Verification: Heart 244 passed; Build 112 passed, 1 skipped; all skill validators passed; all 38 skills passed the mandatory-load line budget; composed Claude/Codex symlink install assertions passed; independent final review is CLEAN. Branches are clean and unpushed.\n\nCurrent Heart gate (2026-07-11): YELLOW, score 42.\n\nExact reasons:\n- workspace validation not passing (3 failed, 2026-07-09T09-48-30Z)\n- 58 stale parked script(s)\n- autolens_assistant: pinned BEHIND installed 2026.7.6.649\n- manifest drift: tenant firewall (organ code) - 5 mismatch(es) vs PyAutoMind/repos.yaml\n- PyAutoMind: open PR 11d old\n- install verification not run\n- no release validation for current source\n\nUnder AUTONOMY.md, the branch remains local and unpushed until these exact YELLOW reasons are explicitly acknowledged.

[Jammy2211]

Phase 2 remains locally complete: Heart 244 passed; Build 112 passed/1 skipped; all validators and composed symlink assertions passed; independent review CLEAN; branches remain local and unpushed.

Current Heart gate (2026-07-11): YELLOW, score 42.

Exact current reasons:

• workspace validation not passing (3 failed, 2026-07-09T09-48-30Z)
• 58 stale parked script(s)
• autolens_assistant: pinned BEHIND installed 2026.7.6.649
• PyAutoMind: open PR 11d old
• install verification not run
• no release validation for current source

The prior seven-reason checkpoint is superseded because the tenant-firewall manifest drift has cleared. Under AUTONOMY.md, the branch remains local and unpushed until this exact six-reason YELLOW set is explicitly acknowledged.