docs: add codex-axi to community catalog

[kyler505]

Intent

Add codex-axi to the AXI community catalog as an alpha Codex orchestration CLI, preserving its current Codex and SDK compatibility range.

What Changed

• Added a codex-axi entry to catalog.yaml, marked alpha with its current Codex and SDK compatibility range.
• Regenerated the generated:... catalog regions in README.md and docs/index.html from catalog.yaml to include the new entry.

Risk Assessment

✅ Low: Purely additive, mechanical documentation change (README.md, catalog.yaml, docs/index.html) adding one catalog entry; all three generated/single-sourced locations are consistently updated and the entry correctly states alpha status and Codex 0.144.x compatibility per the required intent, with no code or behavior changes.

Testing

docs:check confirms the generated README/docs/index.html tables were regenerated correctly from catalog.yaml (no drift) and the generator's unit tests pass, giving direct evidence the new codex-axi catalog entry — including its alpha status and Codex 0.144.x compatibility note — renders correctly in both end-user-facing docs surfaces.

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

• pnpm run docs:check (via npx pnpm on system Node 25) — confirms README.md and docs/index.html generated regions exactly match catalog.yaml
• pnpm run docs:test (node --test scripts/generate-docs.test.mjs) — 4/4 generator unit tests pass
• Manual diff review of git show HEAD for catalog.yaml, README.md, docs/index.html to confirm the codex-axi entry (alpha, Codex 0.144.x compatibility) is present verbatim in all three files

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[kunchenguid]

Automated reminder: thanks for the PR! This branch currently has a merge conflict with the base branch.

When you get a chance, please rebase onto (or merge) the latest base branch, resolve the conflict, and push. After that, checks will re-run and the PR will get looked at again.

_{Noted for axi#98 at 19057b7f.}

[kunchenguid]

Automated reminder: thanks for the PR! This branch currently has a merge conflict with the base branch.

When you get a chance, please rebase onto (or merge) the latest base branch, resolve the conflict, and push. After that, checks will re-run and the PR will get looked at again.

_{Noted for axi#98 at 11a499ff.}