docs: add jira-axi and confluence-axi to community catalog

[emilchristensen]

Intent

The developer wanted to add two tools, jira-axi and confluence-axi, to the community list in the AXI catalog (kunchenguid/axi upstream), following the repo's CONTRIBUTING.md exactly. They specified precise values for both entries (name, url, author, domain, description) using five fields in a fixed order, matching the existing community entries and preserving the file's ordering convention, with both URLs deep-linking into the emilchristensen/atlassian-axi monorepo package directories (to be verified against origin/main, falling back to the monorepo root if a path was wrong). They required regenerating docs via pnpm run docs:gen rather than hand-editing generated regions, so the PR would contain exactly three files (catalog.yaml, README.md, docs/index.html) without touching guarded release files, and validated with git diff --stat and pnpm run docs:check. Finally, they mandated committing with a specific message and shipping through the no-mistakes gate pointed at the captain's fork (never a hand-opened PR), driving the pipeline until a PR into kunchenguid/axi:main was open with green CI.

What Changed

• Added two community: entries to catalog.yaml — jira-axi (domain: Issue tracking) and confluence-axi (domain: Documentation), both authored by emilchristensen and deep-linking into the emilchristensen/atlassian-axi monorepo package directories.
• Regenerated the marked generated:... regions of README.md and docs/index.html via pnpm run docs:gen to reflect the two new catalog rows; generated regions were not hand-edited and no guarded release files were touched.

Risk Assessment

✅ Low: Docs-only catalog addition where the two hand-edited catalog.yaml entries follow the established convention exactly, the generated README/HTML regions pass docs:check with zero drift, and both deep-link URLs were verified to resolve to real package directories on the target repo's main branch.

Testing

Ran the smallest relevant checks for a catalog-plus-generated-docs change: git diff --stat confirmed the 3-file scope with no guarded release files, pnpm run docs:check passed proving README.md and docs/index.html match catalog.yaml, and re-running pnpm run docs:gen produced no diff (generated, not hand-edited). Verified both deep-link URLs resolve on emilchristensen/atlassian-axi main via authenticated gh api (packages jira-axi/confluence-axi present) plus HTTP 200 on the clickable tree URLs against a 404 control. Captured reviewer-visible visual evidence by rendering docs/index.html in Chrome and screenshotting the community table, which shows both new rows (jira-axi / Issue tracking, confluence-axi / Documentation) with correct links, domains, and descriptions appended after glab-axi. All checks passed; worktree left clean with transient screenshots removed.

• Evidence: Rendered community table with jira-axi and confluence-axi entries (local file: /var/folders/ch/2x1ggt6945jf7jjng1rmhyrh0000gn/T/no-mistakes-evidence/01KY82C40GGFK48H7FC2D5K951/community-table-new-entries.png)

Evidence: docs:check result

$ pnpm run docs:check
docs:check ok — generated regions match their sources

Evidence: atlassian-axi packages on main (deep-link targets exist)

$ gh api repos/emilchristensen/atlassian-axi/contents/packages?ref=main --jq '.[].name'
confluence-axi
core
jira-axi

HTTP: jira-axi tree URL 200, confluence-axi tree URL 200, bogus path 404

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.

• git diff --stat d5aa171..25bd175 - confirmed exactly 3 files (catalog.yaml, README.md, docs/index.html), no guarded release files
• pnpm install --frozen-lockfile - deps installed for docs scripts
• pnpm run docs:check - passed: 'generated regions match their sources' (README/index.html match catalog.yaml)
• pnpm run docs:gen then git status --porcelain - idempotent, zero diff vs committed generated files
• gh api repos/emilchristensen/atlassian-axi/contents/packages?ref=main - confirmed jira-axi and confluence-axi package dirs exist on main
• curl HTTP status on both tree URLs (200) vs a bogus path (404) - deep-links resolve
• chrome-devtools-axi opened rendered docs/index.html and screenshotted the community table showing both new entries

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[kunchenguid]

Speaking as Kun's firstmate: I reviewed the diff (catalog.yaml plus generated README.md / docs/index.html only) and independently inspected both packages in the monorepo.

Independent source review at pin bfbbb668b8bc08440bf613a0db4217a8f8ff917f (current main HEAD; tag jira-axi-v1.0.4). Files/paths read at that revision: packages/jira-axi/{package.json,src/bin/jira-axi.ts,src/cli.ts,src/commands/setup.ts,src/commands/home.ts}, packages/confluence-axi/{package.json,src/bin/confluence-axi.ts,src/commands/setup.ts,src/commands/home.ts,src/commands/auth.ts,src/prompt.ts}, packages/core/src/toon.ts, plus both package trees. Direct observations at that revision:

jira-axi (packages/jira-axi, v1.0.4):

• axi-sdk-js runAxiCli; TOON via @toon-format/toon in @atlassian-axi/core; commands workitem / project / board / sprint / filter / dashboard / field / setup; skill present
• principle 7 held: jira-axi setup hooks calls installSessionStartHooks for Claude Code, Codex, and OpenCode
• no-args home is a live acli/open-work-items dashboard
• principle 10 fast path not held: src/bin/jira-axi.ts statically imports ../cli.js (SDK still serves --version)

confluence-axi (packages/confluence-axi):

• same SDK/TOON/setup-hooks pattern; commands include page/space/search plus auth login|status|logout; skill present
• principle 7 held: confluence-axi setup hooks installs Claude Code, Codex, and OpenCode
• no-args home is a live site/auth/spaces dashboard
• OAuth auth login is TTY-gated and fails fast for agents with a structured error pointing at auth login --token (token via stdin) / env; src/prompt.ts is only reached after isInteractiveTTY()
• principle 10 fast path not held: bin statically imports cli.js

Catalog descriptions (Jira work items/boards/sprints via acli, idempotent mutations; Confluence pages/spaces over REST, OAuth 3LO or API-token auth, TOON) are source-backed at this pin.

VISION.md per-rule:

• AXI principles: aligns for a positive admission at this pin for both packages (missing --version fast path is the same observation as other SDK CLIs, not an admission blocker; agent auth is non-interactive).
• Catalog: aligns. Independent source review at bfbbb668b8bc08440bf613a0db4217a8f8ff917f supports admission of both entries.
• SDKs: aligns (docs-only catalog add; no SDK change).

Diff is catalog-only; no security issue. Fork CI is green. The PR is CONFLICTING with main; I will resolve and land if the fork can be updated.

[kunchenguid]

Speaking as Kun's firstmate: catalog-only diff, no security issue. Both packages admitted at the inspected pin (see comment).

[kunchenguid]

Speaking as Kun's firstmate.

This catalog entry landed via last-resort port #159 (squash merge cb8004fd27f6884bf591cfb2f3472ae19c22145b) because #112 stayed CONFLICTING on the fork and we could not fast-forward a resolve there. No rebase was requested. Closing this original as redundant now that jira-axi and confluence-axi are on main.