docs(catalog): add forgejo-axi to the community catalog - #123
Conversation
|
Speaking as Kun's firstmate: I reviewed the diff ( #150 already proposed the same package ( Independent source review at pin
VISION.md per-rule:
CI (no-mistakes, docs-check, generated-files) is green. The PR is CONFLICTING with main; I am not resolving conflicts because it is not otherwise auto-merge-ready. If you later pin a revision that holds principle 7, re-request review. |
kunchenguid
left a comment
There was a problem hiding this comment.
Speaking as Kun's firstmate: catalog-only diff, no security issue. Package is not admitted at the inspected pin (see comment).
# Conflicts: # README.md # catalog.yaml # docs/index.html
|
Re-requesting catalog review at exact Forgejo revision |
|
Speaking as Kun's firstmate: re-triage after your new pin. I ignored the earlier firstmate not-admit (that pin is stale) and independently inspected the package at the revision you named. Independent source review at pin
Catalog description (PR lifecycle, issues, raw VISION.md per-rule:
Diff is |
kunchenguid
left a comment
There was a problem hiding this comment.
Speaking as Kun's firstmate: catalog-only diff, no security issue. Independent source review at pin 307abb76 admits forgejo-axi (see comment).
|
Speaking as Kun's firstmate: this is merged. Thank you @escidmore — really appreciate you taking the time on this. |
What Changed
forgejo-axientry (escidmore, Forgejo domain) to thecommunitylist incatalog.yaml, describing pull request lifecycle, issues, and raw API access for self-hosted Forgejo with TOON output.README.mdanddocs/index.htmlso both generated regions include the new entry.Risk Assessment
✅ Low: The change is a 20-line docs-only catalog addition whose generated README/docs regions match the catalog.yaml source shape, with no executable code and a description fully corroborated by inspection of the referenced package's source.
Testing
Ran the repo's docs generator in check mode, which confirms the new
catalog.yamlentry is faithfully reflected in both generated regions (README table and docs/index.html table) with no drift, plus the generator's own unit tests covering catalog cell rendering and escaping. Since this is a user-visible docs surface, I also opened the built docs page in a real browser and captured a screenshot of the community catalog showing the forgejo-axi row rendering as the final entry with a working repo link, author, domain, and description — matching the other community entries. Everything passed and the worktree is left clean./Users/host/.no-mistakes/evidence/01M0F9NQ4B87PENS3XZQBBY5NF/forgejo-axi-catalog.png)Evidence: docs:check — generated regions match catalog.yaml
Evidence: Live DOM read of the rendered catalog row
Pipeline
Updates from git push no-mistakes
⏭️ **intent** - skipped
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
catalog.yaml:217- Independent source review (VISION.md catalog clause) of escidmore/forgejo-axi at pinned revision 307abb76cdd3d964efa5dffdfd8eaa735f2ee19d (v1.2.0 + merged upstream PRs Make SessionStart hook installation opt-in instead of auto-installing on every CLI invocation #40/Deal with asdf-managed environments better in session hooks #41): every claim in the description is source-backed.pr <find|list|view|history|reviews|diff|create|update|checks|mergeability|merge|merged>andissue <...>exist in src/help.ts:36-80; raw API access isapi METHOD PATH [--data JSON] [--paginate](src/help.ts:15); TOON is the default encoder with--jsonopt-in at the single output boundary (src/cli.ts:2, src/cli.ts:1660); mutations are reconciling (src/forgejo.ts:1755 reconcilePull,pr create/pr update/label createidempotent); non-interactive is verified by the absence of any readline/prompt/console.*/process.stderr use in src/ and bin/. License MIT, packageforgejo-axi@1.2.0builds onaxi-sdk-js. The two gaps recorded in PR docs: propose forgejo-axi for the community catalog #150 (principle 7 setup hooks, principle 10 --version fast path) are closed upstream, so noadmission:exception block is warranted here.catalog.yaml:217- Open PR docs: propose forgejo-axi for the community catalog #150 ("docs: propose forgejo-axi for the community catalog", author Freudator86) proposes this same entry, with a self-disclosure that its author is not the tool's author and that CONTRIBUTING.md asks for "one entry for your AXI". This branch is the author's own entry, which supersedes it and will conflict on catalog.yaml/README.md/docs/index.html. Decide whether docs: propose forgejo-axi for the community catalog #150 should be closed with a pointer to this change; that is a maintainer call on an external PR, not a defect in this diff.✅ **Test** - passed
✅ No issues found.
node scripts/generate-docs.mjs --check— confirms the README.md and docs/index.htmlgenerated:catalog-communityregions are in sync with the newcatalog.yamlentry (no drift; this is the same check thedocs-checkworkflow runs)node --test scripts/generate-docs.test.mjs— the generator's own unit tests (Markdown/HTML cell escaping, link destinations, table formatting) that govern how a catalog entry is renderedManual browser verification: openeddocs/index.htmlin Chrome viachrome-devtools-axi open, located theforgejo-axirow by its repo URL, scrolled it into view and highlighted it, then captured a viewport screenshot of the rendered community catalog tablechrome-devtools-axi evalon the rendered row — read back the live DOM cell text asforgejo-axi | escidmore | Forgejo | Pull request lifecycle, issues, and raw API access for self-hosted Forgejo - non-interactive, reconciling mutations, with token-efficient TOON output.git status --porcelain— confirmed testing left no stray files in the worktree✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.