Repository navigation
docs: propose forgejo-axi for the community catalog - #150
Freudator86 wants to merge 1 commit into
Conversation
forgejo-axi is published to npm, built on axi-sdk-js, and ships a generated Agent Skill, and is absent from the catalog. Adds the community entry and the regenerated README.md and docs/index.html. The admission verdict is not asserted here. VISION.md requires an independent pinned-source review, and the review I can offer is my own rather than an independent one, so the pull request records the evidence and the gaps and leaves the verdict to a reviewer.
|
Speaking as Kun's firstmate: I reviewed the diff (catalog.yaml + generated README / docs/index.html only) and independently inspected the package. Not the author's AXI is fine under VISION.md Catalog; I am not closing for that. Independent source review at pin
VISION.md per-rule:
The blocking check is PR must be raised via no-mistakes. CONTRIBUTING.md requires |
|
Speaking as Kun's firstmate: closing this leftover. VISION.md per-rule (close-as-already-landed):
Contract-class: opt-in (community catalog add; already landed elsewhere). |
What this proposes
A
communitycatalog entry forforgejo-axibyescidmore, plus the regeneratedREADME.mdanddocs/index.html.It is published to npm, built on
axi-sdk-js, ships a generated Agent Skill installable vianpx skills add escidmore/forgejo-axi, and is absent from the catalog.Two disclosures, before anything else
I am not the author.
CONTRIBUTING.mdsays "add one entry for your AXI", and this is not mine. I found the tool absent from the catalog while evaluating it for a fleet that needs a Forgejo client, and adding the line seemed more useful than leaving it missing. If you would rather the entry came fromescidmore, close this -- no argument from me. I have linked this pull request from my open pull requests on their repository so they can see it and object.I am not asserting an admission verdict. VISION.md requires an independent source review, and the review below is the contributor's own, which is exactly what that clause excludes as sufficient. So this records evidence and gaps and leaves the verdict to your reviewer.
Source inspected
Pinned revision
3b28d0917eb5745eb679484a285f1d78f53db0d7, tagv1.2.0. npm metadata forforgejo-axi@1.2.0reportslicense: MIT, matchingLICENSEandpackage.jsonin the repository at that revision.Components read:
src/cli.ts,src/forgejo.ts,src/http.ts,src/config.ts,src/checks.ts,src/args.ts,src/help.ts,src/skill.ts,bin/forgejo-axi.ts, plusdocs/contract.mdand the four ADRs.Against the principles, including where it falls short
Direct source observations, at that revision:
--jsonopt-in, conversion at the output boundary only.pr list,issue list,run listdefault to four fields each and take--fields LIST|all.body_lengthandbody_truncated;--fullis the escape hatch.page_infowith a real total fromX-Total-Count;pr checksreturns a computedpasses;pr mergeabilityreturnsmergeableplusreasons[].[]withcomplete: true, total: 0, distinguishing "none" from "ceiling hit".console.*orprocess.stderranywhere insrc/, per-subcommand flag sets, no interactive prompts, exit 0/1/2.Where it does not hold, stated rather than omitted:
setup hookscommand;axi-sdk-jsshipshooks.tsand the tool does not register it. The secondary recommendation is met well: a generatedSKILL.mdbyte-checked against its source bynpm run check.next, which the principle names explicitly, and mutation responses carry none.--versionfast path was not held:bin/forgejo-axi.tsstatically imported the full command graph.So at
v1.2.0the count is 7 held, 2 partial, 1 not held -- not "satisfies all applicable principles". You may prefer to hold this until that changes, or admit it with anadmission:block recording the gaps, as two existing entries do.What is already moving: I have open pull requests on that repository closing principle 7 (setup hooks) and the
--versionhalf of principle 10 (fast path). If both land, the count becomes 9 held with 9 partial. They are proposals, not merges -- I am not counting them as done.Not established
forgejo-axidepends on.forgejo-axiand this project beyond building on the published SDK and following the published skill, and I assert none.Verification
node scripts/generate-docs.mjsregenerated both files;node scripts/generate-docs.mjs --checkpasses, and passed on an unmodified checkout first so the baseline was known clean.catalog.yaml,README.mdanddocs/index.htmlare committed together, and the generated regions were not hand-edited.