Skip to content

Fix skill parity: sync .codex afx skill copies missed by #1143 - #1332

Closed
waleedkadous wants to merge 1 commit into
mainfrom
hotfix/afx-skill-codex-parity
Closed

Fix skill parity: sync .codex afx skill copies missed by #1143#1332
waleedkadous wants to merge 1 commit into
mainfrom
hotfix/afx-skill-codex-parity

Conversation

@waleedkadous

Copy link
Copy Markdown
Contributor

PR #1143 updated .claude/skills/afx/SKILL.md in both trees (the new ### afx cron condition-environment docs) but not the .codex twins. Its 6/6 CI green was from July 6 — predating the skill-parity guards the repo has since grown (1280's T17, 1273's wait-discipline parity test) — so main went red at merge: 3 failures across two parity suites.

Mechanical fix: copy the two .claude files over their .codex twins. md5-verified identical; parity tests green locally.

Gate-check lesson recorded by the architect: a stale CI green must be re-validated against invariants added since the run — zero drift of the touched files is not zero drift of the repo's expectations.

🤖 Generated with Claude Code

…nly update

PR #1143 (cron exitCode) updated .claude/skills/afx/SKILL.md in both trees
but not the .codex twins — its CI green predated the skill-parity tests
(1280 T17, 1273 wait-discipline), so main went red at merge. Mechanical
sync, md5-verified identical, parity suites green.
@waleedkadous

Copy link
Copy Markdown
Contributor Author

Superseded: PR #1320 merged first carrying an identical .codex parity fix (1273's phase-7 tests caught the same #1143 gap independently; both fixes produce byte-identical results — md5-verified on main post-merge, parity suites green). Two independent detections and fixes of one defect within the hour; the cross-tree guards are earning their keep.

@waleedkadous
waleedkadous deleted the hotfix/afx-skill-codex-parity branch August 2, 2026 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant