docs: add glab-axi to community catalog

[karotkriss]

Intent

Rebase the existing upstream PR #99 (docs: add glab-axi to community catalog) onto current kunchenguid/axi main and resolve its conflict. The change adds a single glab-axi entry to the community list in catalog.yaml; README.md and docs/index.html are GENERATED from catalog.yaml via 'pnpm run docs:gen' and must never be hand-merged. The conflict arose only because other catalog entries landed upstream and regenerated those two files. Resolution: took upstream's catalog.yaml, README.md, and docs/index.html wholesale, re-applied the one glab-axi community entry to catalog.yaml, then regenerated README.md and docs/index.html with docs:gen (docs:check reports zero drift; regeneration is idempotent). The final diff against upstream main is exactly one catalog.yaml entry plus its two regenerated outputs (3 files, +20/-0), nothing else. This must UPDATE existing PR #99 in place on the same fork branch karotkriss:fm/axi-catalog-glab-c2 - do NOT open a new PR. The PR body already carries the required 'Updates from git push no-mistakes' signature and must keep it. Note: a prior run on this branch was cancelled after a flaky/failed CI attempt at the pre-rebase head; this is the rebased, revalidated head.

What Changed

• Added a glab-axi entry to the community list in catalog.yaml (author karotkriss, domain GitLab, pointing to github.com/karotkriss/glab-axi).
• Regenerated the corresponding rows in README.md and docs/index.html from catalog.yaml via pnpm run docs:gen, keeping the generated sections in sync.

Risk Assessment

✅ Low: The change is a minimal, well-bounded docs-catalog addition (one YAML entry plus its two regenerated outputs, +20/-0 across 3 files); it matches the append-only convention of the existing catalog, and pnpm run docs:check confirms zero drift between catalog.yaml and the regenerated README.md/docs/index.html.

Testing

Verified via git diff and the project's own docs:check/docs:gen scripts that the rebased head d784f52 (based on current upstream main cc7fb68) changes exactly catalog.yaml plus its two generated outputs by +20/-0 to add a single glab-axi community entry, that docs:check reports zero drift, and that regeneration is idempotent; the generator's unit tests also pass. Confirmed via gh-axi that PR #99 remains open on the same fork branch with the required pipeline signature in its body, and that its still-showing pre-rebase-conflict bot comment is expected since this worktree is the revalidated head awaiting the pipeline's own push step, not something this Test step should push itself. No issues found.

Evidence: docs:check zero-drift verification

$ node scripts/generate-docs.mjs --check
docs:check ok — generated regions match their sources
EXIT_CODE=0

Evidence: docs:gen idempotency verification

$ node scripts/generate-docs.mjs
generated regions already up to date
EXIT_CODE=0
$ git status --porcelain
(empty — no changes produced)

Evidence: Diff scope vs upstream main (cc7fb68..d784f52)

README.md | 1 +
catalog.yaml | 5 +++++
docs/index.html | 14 ++++++++++++++
3 files changed, 20 insertions(+)

Evidence: glab-axi entry content diff

catalog.yaml:
- name: glab-axi
url: https://github.com/karotkriss/glab-axi
author: karotkriss
domain: GitLab
description: "Issues, merge requests, CI/CD pipelines, variables and secrets, releases, and raw API access. Wraps the official glab CLI with agent-ergonomic TOON output."

README.md and docs/index.html each gained exactly one matching table row for glab-axi.

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

⏭️ **Rebase** - skipped

• ⚠️ README.md - merge conflict rebasing onto refs/remotes/no-mistakes-push/fm/axi-catalog-glab-c2
• ⚠️ catalog.yaml - merge conflict rebasing onto refs/remotes/no-mistakes-push/fm/axi-catalog-glab-c2
• ⚠️ docs/index.html - merge conflict rebasing onto refs/remotes/no-mistakes-push/fm/axi-catalog-glab-c2

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

• git diff --stat cc7fb68 d784f52 -- catalog.yaml README.md docs/index.html (confirms exactly 3 files, +20/-0)
• git diff cc7fb68 d784f52 (full content review of the added catalog entry and its two generated table rows)
• node scripts/generate-docs.mjs --check (docs:check — zero drift between catalog.yaml and generated README.md/docs/index.html)
• node scripts/generate-docs.mjs followed by git status --porcelain (docs:gen — confirms regeneration is idempotent, produces no diff)
• node --test scripts/generate-docs.test.mjs (docs:test — 4/4 generator unit tests pass)
• git rev-parse origin/main vs cc7fb68 (confirms base commit is current upstream main)
• grep -c 'name: glab-axi' catalog.yaml and grep for glab-axi across catalog.yaml/README.md/docs/index.html (confirms exactly one consistent entry, no duplicates)
• git show cddff0c --stat (confirms the intervening 'independent evidence' commit only touched policy docs, not catalog schema, so no additional fields are required)
• gh-axi pr view 99 --full and gh-axi api repos/kunchenguid/axi/pulls/99 (confirms PR #99 is open, targets base main, head branch fm/axi-catalog-glab-c2, and carries the 'Updates from git push no-mistakes' signature in its body)
• gh-axi pr view 99 --comments (confirms the visible bot comment is the pre-rebase merge-conflict nudge at 83ca8584, consistent with this worktree being the unpushed rebased revalidation head)

✅ **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#99 at 83ca8584.}

[karotkriss]

@kunchenguid fixed merge conflicts and push, all yours now.

As a fun fact, this axi is actually modeled from your gh-axi and fiirstmate seems to love it.

[kunchenguid]

Thanks @karotkriss - merged! Really appreciate the contribution.