[axi#105] docs: add gherkin-cli to the community catalog

[github-actions]

Decision needed - axi#105

PR review by unional · merge-ready

docs: add gherkin-cli to the community catalog

Situation

• Compliance: pass
• Tests: green
• Notes: compliance=pass tests=green

Auto-merge criteria

Note

Read-only preflight from the authoritative auto-merge evaluator. A displayed MET result never authorizes a merge: Wheelhouse re-evaluates every gate and performs G7 immediately before acting.

Scope

• ✅ MET Scope - merge-ready PR review - kind=pr-review bucket=merge-ready

Safety

• ✅ MET Safety - complete healthy scan - repo scan is ok, complete, and mergeability settled
• ✅ MET Safety - target PR is open - target PR is open and unmerged
• ✅ MET Safety - no per-PR auto-merge opt-out - wheelhouse:no-auto-merge is absent
• ✅ MET Safety - head SHA unchanged - scan and live head b8f3c638

G0 (repo)

• ✅ MET G0 - repository auto-merge enabled - enabled by effective repository policy
• ✅ MET G0 - default-branch VISION.md present - default-branch VISION.md 616ef37c

G1 (card)

• ✅ MET G1 - trusted unique decision card - trusted unique machine-created card [axi#105] docs: add gherkin-cli to the community catalog #1503
• ✅ MET G1 - card published after triage - decision controls are published
• ⚪ UNAVAILABLE G1 - exclusive card claim - claim is acquired and revalidated only at the act boundary

G2 (files)

• ✅ MET G2 - complete immutable file list - 3 immutable changed path entries read
• ✅ MET G2 - workflow and security exclusions clear - no unconditional workflow/security/governance exclusions

G3 (author)

• ✅ MET G3 - non-maintainer human contributor - unional is a non-maintainer human
• ❌ UNMET G3 - prior merged contribution in this repo - G3 author unional has no prior merged PR in axi

G4 (checks)

• ✅ MET G4 - configured checks green - comp=pass tests=green (merge-ready)
• ✅ MET G4 - PR mergeable - live mergeable is MERGEABLE
• ✅ MET G4 - merge state clean - live merge state is CLEAN

G5 (size)

• ✅ MET G5 - changed-file limit - 3 changed files <= 20
• ✅ MET G5 - changed-line limit - 20 changed lines <= 1000

G6 (triage + behavior)

• ✅ MET G6 - automatic triage available - CLAUDE_CODE_OAUTH_TOKEN is configured
• ✅ MET G6 - successful triage for current head - successful triage for head b8f3c638
• ❌ UNMET G6 - top-level recommendation is merge - top-level triage recommendation is not an explicit merge
• ✅ MET G6 - eligible behavior class - class A
• ✅ MET G6 - existing/default behavior unchanged - no existing/default behavior change
• ✅ MET G6 - class C is opt-in and default-off - not applicable to class A
• VISION.md-dependent checks
  • ❌ UNMET G6 - behavior aligns with VISION.md - alignment not confirmed
  • ❌ UNMET G6 - behavior verdict recommends merge - merge not recommended
  • ✅ MET G6 - verdict uses current VISION.md revision - verdict and default branch use 616ef37c
  • ✅ MET G6 - verdict uses current base revision - verdict and live base use fbfe6d23

G7 (final gate)

• ⚪ UNAVAILABLE G7 - immediate live recheck and manual merge gate - runs only immediately before merge: card claim, VISION, head/base, mergeability, checks, opt-out label, and unchanged manual workflow gate

Triage

• Summary: Adds a gherkin-cli entry (cyberuni/gherkin-cli, Gherkin/BDD domain) to the community list in catalog.yaml and regenerates README.md and docs/index.html via the docs generator.
• Product implications: Routine catalog addition with no code changes; the docs format, generator output, and CONTRIBUTING workflow are all correct. However, vision.md mandates independent package review before any positive admission verdict, and the PR body supplies only docs-format evidence, not that independent review — making this a maintainer judgment call rather than routine internal work.
• Recommended next step: hold - vision.md requires an independent reviewer to inspect the actual cyberuni/gherkin-cli source at a pinned revision/release and execute it through representative success, error, and discovery paths before a positive admission verdict; the PR provides docs-format verification (docs:check, generator tests) only, which vision.md explicitly states is insufficient on its own. Additionally, the pipeline review flagged a mismatch: the recorded session intent describes registering cyber-mux, but the commit adds gherkin-cli — the PR body acknowledges this inconsistency and asks the maintainer to confirm the intended tool. A third minor note: gherkin-cli is the only community entry without the *-axi...

Your decision

Tick one box for a quick call, or reply with a slash-command (/merge, /close, /decline <reason>, /hold, /comment <text>, /request-changes <text>):

• Accept recommendation
• Merge it
• Close / decline
• Investigate - deep code-grounded review (leaves this card open)
• Hold - I'll handle this manually

_{Only the repository owner can drive this decision - everyone else's edits and comments are ignored.}

[github-actions]

Agent triage event finished with consumer.committed.

[github-actions]

[kunchenguid]

review the package for AXI compliance

[github-actions]

AXI compliance review — cyberuni/gherkin-cli @ 2c467e6b

Source inspected at pinned commit 2c467e6b68044d9e0a3eda0d64d72c5d5ee6c3d5. Files reviewed: .agents/specs/gherkin-cli/axi/README.md, .agents/specs/gherkin-cli/design/decisions/0001-adopt-axi.md, packages/gherkin-cli/src/cli.ts.

The package formally adopts AXI principles kunchenguid/axi#1–kunchenguid/axi#6 and kunchenguid/axi#8–kunchenguid/axi#10. Principle kunchenguid/axi#7 (ambient context / Agent Skill) is explicitly out of scope for a leaf CLI — this is noted in both the ADR and the spec and is an acceptable scoping decision.

Principle-by-principle findings:

#	Principle	Status	Evidence
kunchenguid/axi#1	Token-efficient output (TOON by default)	✅	--format <fmt> defaults to 'toon'; --format json is the explicit escape.
kunchenguid/axi#2	Minimal default schema	✅	Spec states scenario row = name, keyword, tags (3 fields); --full adds step detail.
kunchenguid/axi#3	Truncation + --full	✅	truncate() call in emit(); --format json is never truncated.
kunchenguid/axi#4	Pre-computed aggregates	✅	Every command result carries summary (parse → files/scenarios; validate → files/errors; diff → added/modified/removed/unchanged).
kunchenguid/axi#5	Definitive empty states	✅	Confirmed in cli.ts: "scenarios: 0 scenarios found across N file(s)", "errors: 0 syntax errors...", "changes: 0 scenario changes..." — never blank output.
kunchenguid/axi#6	Structured errors / exit codes / no prompts / fail-loud	✅	Stable error codes (ENOENT, EGIT, EBADFLAG); exit(1) on failure; commander's own output suppressed and replaced with structured errors; unknown flags name valid flags and exit 1.
kunchenguid/axi#7	Ambient context	N/A	Leaf CLI — explicitly out of scope, as documented.
kunchenguid/axi#8	Content-first (bare invocation)	✅	Bare gherkin-cli runs home(): shows .feature inventory for the current directory, not a usage manual.
kunchenguid/axi#9	Next-step suggestions	✅	writeHelp([...]) after every command, naming natural follow-up commands.
kunchenguid/axi#10	Consistent help	✅	Each subcommand registers synopsis, flags, and an addHelpText('after', '\nExample:\n $ ...') block.

Stream discipline: stdout carries the machine result only (TOON or JSON payload); stderr carries next-step lines, warnings, and structured errors. Confirmed in spec and implemented consistently in cli.ts.

Source inspection verdict: ✅ Conforms to AXI principles kunchenguid/axi#1–kunchenguid/axi#6 and kunchenguid/axi#8–kunchenguid/axi#10.

---

Gap per VISION.md policy: The VISION.md requires that "when a runnable release exists, execute that released package through representative success, error, and discovery paths." This environment cannot install and run the npm package, so execution-based evidence (live success/error/discovery paths) is absent. Source inspection is strong and the code paths are straightforward, but the formal VISION.md admission standard is not fully met without a live execution run.

Two low-severity notes from the pipeline review (not AXI blockers):

1. The name gherkin-cli does not carry the *-axi suffix that every other community entry uses. CONTRIBUTING.md does not mandate the suffix — this is a maintainer convention call, not a policy violation.
2. The PR's recorded "Intent" section describes a different tool (cyber-mux/terminal-multiplexers). The actual diff is internally consistent and adds gherkin-cli correctly; the stale intent context is a pipeline artifact, not a problem with the change itself.

[github-actions]

Self-healed by the scheduled backstop: axi#105 no longer needs a maintainer decision in the current scan - consuming this card.