[axi#104] docs: add cyber-mux to the community catalog

[github-actions]

Decision needed - axi#104

PR review by unional · merge-ready

docs: add cyber-mux 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 a5ac6e32

G0 (repo)

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

G1 (card)

• ❌ UNMET G1 - trusted unique decision card - no trusted unique pr-review card snapshot
• ⚪ UNAVAILABLE G1 - card published after triage - card state is unavailable until a card exists
• ⚪ UNAVAILABLE G1 - exclusive card claim - no card exists to claim

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 - 68 changed lines <= 1000

G6 (triage + behavior)

• ✅ MET G6 - automatic triage available - CLAUDE_CODE_OAUTH_TOKEN is configured
• ❌ UNMET G6 - successful triage for current head - no successful auto-triage verdict on the card
• ❌ UNMET G6 - top-level recommendation is merge - top-level triage recommendation is not an explicit merge
• ❌ UNMET G6 - eligible behavior class - structured behavior verdict absent; dependent behavior checks were not evaluated
• ⚪ UNAVAILABLE G6 - existing/default behavior unchanged - not evaluated because no structured behavior verdict exists
• ⚪ UNAVAILABLE G6 - class C is opt-in and default-off - not evaluated because no structured behavior verdict exists
• VISION.md-dependent checks
  • ⚪ UNAVAILABLE G6 - behavior aligns with VISION.md - not evaluated because no structured behavior verdict exists
  • ⚪ UNAVAILABLE G6 - behavior verdict recommends merge - not evaluated because no structured behavior verdict exists
  • ⚪ UNAVAILABLE G6 - verdict uses current VISION.md revision - not evaluated because no vision-bound behavior verdict exists
  • ⚪ UNAVAILABLE G6 - verdict uses current base revision - not evaluated because no vision-bound behavior verdict exists

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 one cyber-mux entry to the community catalog in catalog.yaml and regenerates README.md and docs/index.html via pnpm run docs:gen — no source, SDK, benchmark, or workflow files touched.
• Product implications: Routine catalog maintenance — no code change, no SDK impact, no behavior change. The addition follows the established community-catalog format and the generated files are confirmed byte-identical to generator output. Does not warrant owner discussion beyond normal catalog review.
• Recommended next step: merge - Docs-only community catalog addition that matches existing entry format, touches only the three expected files (catalog.yaml, README.md, docs/index.html), stays in the community list (not the owner-maintained official list), and the linked npm package and GitHub repo are verifiably real — squarely within the vision policy for community catalog contributions.

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]

does this strictly follow axi principles?

[github-actions]

The assistant did not produce a trusted result. No target action was taken; the card remains open and deterministic checkbox or slash-command controls are still available. See the workflow run for the stable stage/error code.