docs: add hey-axi catalog entry with pinned admission review

[tangentus]

Intent

Publish the pipeline's admission-review fix commit (15348f1, exception admission block for hey-axi pinned to 2af99c1b7e58563b26812de141982e928e9c2f44) to the existing PR #226 so the hey-axi community catalog entry carries an independent pinned-source review as VISION.md requires. No other changes.

What Changed

• Add TangentialSolutions’ hey-axi to the community catalog, README, and website.
• Record exception admission with reviewed components, source observations, and AXI principle gaps pinned to revision 2af99c1b7e58563b26812de141982e928e9c2f44.

Risk Assessment

✅ Low: The change is confined to the hey-axi catalog entry, its generated documentation, and the explicitly requested pinned-revision exception admission record.

Testing

Inspected the branch diff and target commit: the admission fix changes only catalog.yaml. No live scenarios or visual artifacts apply to this documentation-only metadata change; no files were modified.

• Live validation: ⚠️ no-surface - 0 of 1 scenarios driven live against the product

Scenario	Result	Live	Evidence
A catalog reader consults hey-axi’s exception admission and pinned-source review	⏸️ untested	no	The target commit adds documentation-only admission metadata to catalog.yaml and changes no runtime behavior. There is no live-validatable product surface under this phase’s docs-only rule. Publishing…

• Outcome: ⚠️ 1 warning across 1 run (1m1s)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

⚠️ **Test** - 1 warning

• ⚠️ this change has no live-validatable surface; proceed without live validation? (0 of 1 scenarios were driven live against the product); A catalog reader consults hey-axi’s exception admission and pinned-source review: The target commit adds documentation-only admission metadata to catalog.yaml and changes no runtime behavior. There is no live-validatable product surface under this phase’s docs-only rule. Publishing to PR docs: add hey-axi catalog entry with pinned admission review #226 belongs to the outer executor.
• Live validation: ⚠️ no-surface - 0 of 1 scenarios driven live against the product

Scenario	Result	Live	Evidence
A catalog reader consults hey-axi’s exception admission and pinned-source review	⏸️ untested	no	The target commit adds documentation-only admission metadata to catalog.yaml and changes no runtime behavior. There is no live-validatable product surface under this phase’s docs-only rule. Publishing…

• git diff f4fa788807080017f923f9b3e209dca40003fe0d 15348f12d712e0044523c9eb8f9d89637ed80f05 --stat and catalog diff inspection
• git show --stat --oneline 15348f12d712e0044523c9eb8f9d89637ed80f05
• git show --format=fuller --no-ext-diff 15348f12d712e0044523c9eb8f9d89637ed80f05 -- catalog.yaml
• git status --short

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[greptile-apps]

Confidence Score: 4/5

[Low risk] Adds a community project to the catalog documentation.

The PR should not merge until the hey-axi admission is reconciled with the repository’s catalog policy.

_{Reviews (2) · Last reviewed commit: "no-mistakes(ci): Reviewed hey-axi at exa..."}

[greptile-apps]

Admission despite unresolved gaps

The new source review says several applicable AXI principles are only partially met and mutation idempotence remains unestablished, but this entry receives a positive community-catalog listing under status: exception. VISION.md requires the verdict to remain inconclusive, rather than recommend admission, when the inspected source is insufficient to establish the applicable principles. As written, readers see hey-axi listed without the exception or its limitations.

Context Used: If there is a VISION.md file at the root of the repo, the PR must not conflict / diverge / drift from it. If the PR description has an "Intent" section, respect that as the accepted user intent. - Do make comments if anything in the implementation ... (source)

[kunchenguid]

Speaking as Kun's firstmate: independent pinned-source admission review for community catalog hey-axi.

Pinned revision inspected: 2af99c1b7e58563b26812de141982e928e9c2f44 (TangentialSolutions/hey-axi). Confirmed npm view hey-axi@0.2.0 gitHead equals that SHA; package.json / src/version.js both declare 0.2.0. Registry metadata used only for release identity, not AXI compliance.

Components inspected (direct source): src/hey-axi.js, src/version.js, src/cli.js, src/args.js, src/router.js, src/manifest.json, src/shape.js, src/home.js, src/guide.js, src/text.js, src/hooks.js, src/errors.js, src/policy.js, scripts/gen-skill.js, skills/hey-axi/SKILL.md, .github/workflows/test.yml, package.json, plus test/send-gate.test.js for send-policy coverage. Upstream HEY CLI behavior was not independently reviewed.

Direct source observations (summary):

• Fast path: tryFastPath + leaf VERSION before dynamic cli.js import.
• Default TOON over HEY JSON envelopes; --json/--quiet/--full/--fields; list schemas in LIST_FIELDS (many 5–7 fields, e.g. box/postings 6); truncation 120/1000 with --full hint when shaped via shapeEnvelope; empty states and N of T total when envelope provides meta.total_count. Bare non-envelope responses bypass list projection/empty handling; --quiet drops envelope counts/empty/suggestions.
• Flag validation rejects unknown/missing-required flags (exit 2) with valid-flag lists; scanArgs does not validate missing flag values; trailing positionals left to HEY; unknown-command discovery may invoke HEY before validation; upstream exit codes (incl. 3–8, 127) preserved; mutation idempotence delegated to HEY.
• Errors: envelope rewrite toward hey-axi + exit-specific help; fallback can copy stderr/stdout verbatim; interactive login/setup/upgrade allowed; compose/reply editor paths documented.
• Home: live Imbox (limit 10), identity, empty state, next commands; failures → status/help exit 0; default account, no cwd mailbox filter; home path does not surface truncation/--full or envelope totals.
• setup hooks explicit only (Claude/Codex/OpenCode via axi-sdk-js); skill trigger-shaped; generated examples mostly bare hey-axi (npx noted for command-not-found).
• Send safety: compose/reply staged with --draft unless --allow-send; forward/draft send/bulk-reply send refused; structured marker {sent:false, saved_as:draft, axi_notice}; raw modes bypass that marker; auth token gated by --allow-secret.

Exception (honest gaps): Principles 2–5 partial (schemas >4 fields; bare non-envelope lists; home loses truncation/totals). Principle 6 partial (missing values/positionals delegated; interactive/editor paths; fallback/raw dependency text; upstream exits; mutation idempotence unestablished in wrapper). Principle 7: no directory-scoped mailbox content / session-end capture; skill examples often assume binary on PATH. Principle 9: breadcrumb rewrite does not preserve --account. Principle 10: some commands thin on examples/defaults. Matches established community status: exception pattern (e.g. prior skill-only / partial-principle admissions).

Greptile’s P1 that exception must stay inconclusive conflicts with existing catalog exception practice; VISION requires pinned independent review and honest gaps — both present. Greptile confidence 4/5 does not override that verdict (ruleset has no required status checks).

VISION.md per-rule:

• Evolve conservatively: aligns — docs/catalog listing only; no axi runtime/SDK behavior change.
• AXI principles: aligns-with-exception — real wrapper with verified agent ergonomics and documented partials at the pin.
• Catalog: aligns — community catalog addition after independent pinned-source review at exact revision with components + observations + exception text.
• Official catalog: aligns — community section only; official untouched.
• SDKs: aligns — not an SDK change.

Contract-class: opt-in (catalog listing; users choose to install hey-axi; setup hooks remains explicit).

Safe review: no credential printing without opt-in; send gated. Recommend squash-merge as admit-with-exception.

[kunchenguid]

Speaking as Kun's firstmate: this is merged. Thank you @tangentus — really appreciate you taking the time on this.