docs: add linear-axi to the community catalog

[pgalka0]

Intent

Add linear-axi to the community catalog so it is listed on axi.md

What Changed

• Added a linear-axi entry to catalog.yaml, the single source for the community catalog.
• Regenerated the catalog regions in README.md and docs/index.html so the new tool is listed on axi.md.

Risk Assessment

✅ Low: A documentation-only catalog addition with consistent entries across the source YAML and both generated HTML/Markdown regions, touching no functional code.

Testing

Installed deps, ran the docs drift check (docs:check passed — the generated README/HTML regions match the edited catalog.yaml) and the docs generator unit tests (all pass), then rendered docs/index.html in headless Chromium to capture a screenshot of the community catalog showing the new linear-axi row (author pgalka0, domain Linear, TOON-output description) exactly as it appears on axi.md. The user intent — linear-axi listed in the community catalog on axi.md — is demonstrated end-to-end; worktree left clean.

• Evidence: Rendered axi.md community catalog with linear-axi row (highlighted) (local file: /var/folders/s_/1_7vjdt96_x4s3bpgwj7fvp40000gn/T/no-mistakes-evidence/01KXDKP4TAN60HT34K84NGP6C5/community-catalog-linear-axi.png)

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.

• node scripts/generate-docs.mjs --check — confirmed generated regions in README.md and docs/index.html match catalog.yaml (no drift; docs-check workflow would pass)
• node --test scripts/generate-docs.test.mjs — 4/4 catalog generation tests pass
• Rendered docs/index.html in headless Chromium and scrolled the community catalog to the new linear-axi row to capture reviewer-visible visual evidence

✅ **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#93 at 0fa4abaa.}

[kunchenguid]

Automated reminder: this PR still looks blocked on a rebase or merge conflict fix.

If you are still interested, please rebase onto the current base branch, resolve the conflict, and push.

If I do not hear back, I may close this as inactive.