fix(opencode-go): restore curated catalog additions (#959)

hermes_cli/models.py

@@ -250,12 +250,16 @@ _PROVIDER_MODELS: dict[str, list[str]] = {
         "big-pickle",
     ],
     "opencode-go": [
-        "glm-5",
+        "kimi-k2.6",
         "kimi-k2.5",
+        "glm-5.1",
+        "glm-5",
         "mimo-v2-pro",
         "mimo-v2-omni",
         "minimax-m2.7",
         "minimax-m2.5",
+        "qwen3.6-plus",
+        "qwen3.5-plus",
     ],
     "ai-gateway": [
         "anthropic/claude-opus-4.6",

hermes_cli/setup.py

@@ -105,7 +105,7 @@ _DEFAULT_PROVIDER_MODELS = {
     "ai-gateway": ["anthropic/claude-opus-4.6", "anthropic/claude-sonnet-4.6", "openai/gpt-5", "google/gemini-3-flash"],
     "kilocode": ["anthropic/claude-opus-4.6", "anthropic/claude-sonnet-4.6", "openai/gpt-5.4", "google/gemini-3-pro-preview", "google/gemini-3-flash-preview"],
     "opencode-zen": ["gpt-5.4", "gpt-5.3-codex", "claude-sonnet-4-6", "gemini-3-flash", "glm-5", "kimi-k2.5", "minimax-m2.7"],
-    "opencode-go": ["glm-5", "kimi-k2.5", "mimo-v2-pro", "mimo-v2-omni", "minimax-m2.5", "minimax-m2.7"],
+    "opencode-go": ["kimi-k2.6", "kimi-k2.5", "glm-5.1", "glm-5", "mimo-v2-pro", "mimo-v2-omni", "minimax-m2.5", "minimax-m2.7", "qwen3.6-plus", "qwen3.5-plus"],
     "huggingface": [
         "Qwen/Qwen3.5-397B-A17B", "Qwen/Qwen3-235B-A22B-Thinking-2507",
         "Qwen/Qwen3-Coder-480B-A35B-Instruct", "deepseek-ai/DeepSeek-R1-0528",

optional-skills/dogfood/adversarial-ux-test/SKILL.md

@@ -1,190 +0,0 @@
----
-name: adversarial-ux-test
-description: Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.
-version: 1.0.0
-author: Omni @ Comelse
-license: MIT
-metadata:
-  hermes:
-    tags: [qa, ux, testing, adversarial, dogfood, personas, user-testing]
-    related_skills: [dogfood]
----
-
-# Adversarial UX Test
-
-Roleplay the worst-case user for your product — the person who hates technology, doesn't want your software, and will find every reason to complain. Then filter their feedback through a pragmatism layer to separate real UX problems from "I hate computers" noise.
-
-Think of it as an automated "mom test" — but angry.
-
-## Why This Works
-
-Most QA finds bugs. This finds **friction**. A technically correct app can still be unusable for real humans. The adversarial persona catches:
-- Confusing terminology that makes sense to developers but not users
-- Too many steps to accomplish basic tasks
-- Missing onboarding or "aha moments"
-- Accessibility issues (font size, contrast, click targets)
-- Cold-start problems (empty states, no demo content)
-- Paywall/signup friction that kills conversion
-
-The **pragmatism filter** (Phase 3) is what makes this useful instead of just entertaining. Without it, you'd add a "print this page" button to every screen because Grandpa can't figure out PDFs.
-
-## How to Use
-
-Tell the agent:
-```
-"Run an adversarial UX test on [URL]"
-"Be a grumpy [persona type] and test [app name]"
-"Do an asshole user test on my staging site"
-```
-
-You can provide a persona or let the agent generate one based on your product's target audience.
-
-## Step 1: Define the Persona
-
-If no persona is provided, generate one by answering:
-
-1. **Who is the HARDEST user for this product?** (age 50+, non-technical role, decades of experience doing it "the old way")
-2. **What is their tech comfort level?** (the lower the better — WhatsApp-only, paper notebooks, wife set up their email)
-3. **What is the ONE thing they need to accomplish?** (their core job, not your feature list)
-4. **What would make them give up?** (too many clicks, jargon, slow, confusing)
-5. **How do they talk when frustrated?** (blunt, sweary, dismissive, sighing)
-
-### Good Persona Example
-> **"Big Mick" McAllister** — 58-year-old S&C coach. Uses WhatsApp and that's it. His "spreadsheet" is a paper notebook. "If I can't figure it out in 10 seconds I'm going back to my notebook." Needs to log session results for 25 players. Hates small text, jargon, and passwords.
-
-### Bad Persona Example
-> "A user who doesn't like the app" — too vague, no constraints, no voice.
-
-The persona must be **specific enough to stay in character** for 20 minutes of testing.
-
-## Step 2: Become the Asshole (Browse as the Persona)
-
-1. Read any available project docs for app context and URLs
-2. **Fully inhabit the persona** — their frustrations, limitations, goals
-3. Navigate to the app using browser tools
-4. **Attempt the persona's ACTUAL TASKS** (not a feature tour):
-   - Can they do what they came to do?
-   - How many clicks/screens to accomplish it?
-   - What confuses them?
-   - What makes them angry?
-   - Where do they get lost?
-   - What would make them give up and go back to their old way?
-
-5. Test these friction categories:
-   - **First impression** — would they even bother past the landing page?
-   - **Core workflow** — the ONE thing they need to do most often
-   - **Error recovery** — what happens when they do something wrong?
-   - **Readability** — text size, contrast, information density
-   - **Speed** — does it feel faster than their current method?
-   - **Terminology** — any jargon they wouldn't understand?
-   - **Navigation** — can they find their way back? do they know where they are?
-
-6. Take screenshots of every pain point
-7. Check browser console for JS errors on every page
-
-## Step 3: The Rant (Write Feedback in Character)
-
-Write the feedback AS THE PERSONA — in their voice, with their frustrations. This is not a bug report. This is a real human venting.
-
-```
-[PERSONA NAME]'s Review of [PRODUCT]
-
-Overall: [Would they keep using it? Yes/No/Maybe with conditions]
-
-THE GOOD (grudging admission):
-- [things even they have to admit work]
-
-THE BAD (legitimate UX issues):
-- [real problems that would stop them from using the product]
-
-THE UGLY (showstoppers):
-- [things that would make them uninstall/cancel immediately]
-
-SPECIFIC COMPLAINTS:
-1. [Page/feature]: "[quote in persona voice]" — [what happened, expected]
-2. ...
-
-VERDICT: "[one-line persona quote summarizing their experience]"
-```
-
-## Step 4: The Pragmatism Filter (Critical — Do Not Skip)
-
-Step OUT of the persona. Evaluate each complaint as a product person:
-
-- **RED: REAL UX BUG** — Any user would have this problem, not just grumpy ones. Fix it.
-- **YELLOW: VALID BUT LOW PRIORITY** — Real issue but only for extreme users. Note it.
-- **WHITE: PERSONA NOISE** — "I hate computers" talking, not a product problem. Skip it.
-- **GREEN: FEATURE REQUEST** — Good idea hidden in the complaint. Consider it.
-
-### Filter Criteria
-1. Would a 35-year-old competent-but-busy user have the same complaint? → RED
-2. Is this a genuine accessibility issue (font size, contrast, click targets)? → RED
-3. Is this "I want it to work like paper" resistance to digital? → WHITE
-4. Is this a real workflow inefficiency the persona stumbled on? → YELLOW or RED
-5. Would fixing this add complexity for the 80% who are fine? → WHITE
-6. Does the complaint reveal a missing onboarding moment? → GREEN
-
-**This filter is MANDATORY.** Never ship raw persona complaints as tickets.
-
-## Step 5: Create Tickets
-
-For **RED** and **GREEN** items only:
-- Clear, actionable title
-- Include the persona's verbatim quote (entertaining + memorable)
-- The real UX issue underneath (objective)
-- A suggested fix (actionable)
-- Tag/label: "ux-review"
-
-For **YELLOW** items: one catch-all ticket with all notes.
-
-**WHITE** items appear in the report only. No tickets.
-
-**Max 10 tickets per session** — focus on the worst issues.
-
-## Step 6: Report
-
-Deliver:
-1. The persona rant (Step 3) — entertaining and visceral
-2. The filtered assessment (Step 4) — pragmatic and actionable
-3. Tickets created (Step 5) — with links
-4. Screenshots of key issues
-
-## Tips
-
-- **One persona per session.** Don't mix perspectives.
-- **Stay in character during Steps 2-3.** Break character only at Step 4.
-- **Test the CORE WORKFLOW first.** Don't get distracted by settings pages.
-- **Empty states are gold.** New user experience reveals the most friction.
-- **The best findings are RED items the persona found accidentally** while trying to do something else.
-- **If the persona has zero complaints, your persona is too tech-savvy.** Make them older, less patient, more set in their ways.
-- **Run this before demos, launches, or after shipping a batch of features.**
-- **Register as a NEW user when possible.** Don't use pre-seeded admin accounts — the cold start experience is where most friction lives.
-- **Zero WHITE items is a signal, not a failure.** If the pragmatism filter finds no noise, your product has real UX problems, not just a grumpy persona.
-- **Check known issues in project docs AFTER the test.** If the persona found a bug that's already in the known issues list, that's actually the most damning finding — it means the team knew about it but never felt the user's pain.
-- **Subscription/paywall testing is critical.** Test with expired accounts, not just active ones. The "what happens when you can't pay" experience reveals whether the product respects users or holds their data hostage.
-- **Count the clicks to accomplish the persona's ONE task.** If it's more than 5, that's almost always a RED finding regardless of persona tech level.
-
-## Example Personas by Industry
-
-These are starting points — customize for your specific product:
-
-| Product Type | Persona | Age | Key Trait |
-|-------------|---------|-----|-----------|
-| CRM | Retirement home director | 68 | Filing cabinet is the current CRM |
-| Photography SaaS | Rural wedding photographer | 62 | Books clients by phone, invoices on paper |
-| AI/ML Tool | Department store buyer | 55 | Burned by 3 failed tech startups |
-| Fitness App | Old-school gym coach | 58 | Paper notebook, thick fingers, bad eyes |
-| Accounting | Family bakery owner | 64 | Shoebox of receipts, hates subscriptions |
-| E-commerce | Market stall vendor | 60 | Cash only, smartphone is for calls |
-| Healthcare | Senior GP | 63 | Dictates notes, nurse handles the computer |
-| Education | Veteran teacher | 57 | Chalk and talk, worksheets in ring binders |
-
-## Rules
-
-- Stay in character during Steps 2-3
-- Be genuinely mean but fair — find real problems, not manufactured ones
-- The pragmatism filter (Step 4) is **MANDATORY**
-- Screenshots required for every complaint
-- Max 10 tickets per session
-- Test on staging/deployed app, not local dev
-- One persona, one session, one report

tests/hermes_cli/test_opencode_go_in_model_list.py

@@ -4,32 +4,62 @@ import os
 from unittest.mock import patch
 
 from hermes_cli.model_switch import list_authenticated_providers
+from hermes_cli.models import curated_models_for_provider
 
 
 @patch.dict(os.environ, {"OPENCODE_GO_API_KEY": "test-key"}, clear=False)
 def test_opencode_go_appears_when_api_key_set():
     """opencode-go should appear in list_authenticated_providers when OPENCODE_GO_API_KEY is set."""
     providers = list_authenticated_providers(current_provider="openrouter")
-    
+
     # Find opencode-go in results
     opencode_go = next((p for p in providers if p["slug"] == "opencode-go"), None)
-    
+
     assert opencode_go is not None, "opencode-go should appear when OPENCODE_GO_API_KEY is set"
-    assert opencode_go["models"] == ["glm-5", "kimi-k2.5", "mimo-v2-pro", "mimo-v2-omni", "minimax-m2.7", "minimax-m2.5"]
+    assert opencode_go["models"] == [
+        "kimi-k2.6",
+        "kimi-k2.5",
+        "glm-5.1",
+        "glm-5",
+        "mimo-v2-pro",
+        "mimo-v2-omni",
+        "minimax-m2.7",
+        "minimax-m2.5",
+    ]
+    assert opencode_go["total_models"] == 10
     # opencode-go can appear as "built-in" (from PROVIDER_TO_MODELS_DEV when
     # models.dev is reachable) or "hermes" (from HERMES_OVERLAYS fallback when
     # the API is unavailable, e.g. in CI).
     assert opencode_go["source"] in ("built-in", "hermes")
 
 
+@patch("hermes_cli.models.provider_model_ids", return_value=[])
+def test_opencode_go_curated_fallback_includes_new_models(_mock_provider_model_ids):
+    """Fallback catalog should include Kimi K2.6 and both Qwen Plus models."""
+    model_ids = [model_id for model_id, _ in curated_models_for_provider("opencode-go")]
+
+    assert model_ids == [
+        "kimi-k2.6",
+        "kimi-k2.5",
+        "glm-5.1",
+        "glm-5",
+        "mimo-v2-pro",
+        "mimo-v2-omni",
+        "minimax-m2.7",
+        "minimax-m2.5",
+        "qwen3.6-plus",
+        "qwen3.5-plus",
+    ]
+
+
 def test_opencode_go_not_appears_when_no_creds():
     """opencode-go should NOT appear when no credentials are set."""
     # Ensure OPENCODE_GO_API_KEY is not set
     env_without_key = {k: v for k, v in os.environ.items() if k != "OPENCODE_GO_API_KEY"}
-    
+
     with patch.dict(os.environ, env_without_key, clear=True):
         providers = list_authenticated_providers(current_provider="openrouter")
-        
+
         # opencode-go should not be in results
         opencode_go = next((p for p in providers if p["slug"] == "opencode-go"), None)
         assert opencode_go is None, "opencode-go should not appear without credentials"

tests/test_optional_adversarial_ux_skill_catalog.py

@@ -1,25 +0,0 @@
-from pathlib import Path
-
-from tools.skills_hub import OptionalSkillSource
-
-
-REPO_ROOT = Path(__file__).resolve().parents[1]
-
-
-def test_optional_skill_source_scans_adversarial_ux_test():
-    source = OptionalSkillSource()
-    metas = {meta.identifier: meta for meta in source._scan_all()}
-
-    assert "official/dogfood/adversarial-ux-test" in metas
-    assert metas["official/dogfood/adversarial-ux-test"].name == "adversarial-ux-test"
-    assert "tech-resistant user" in metas["official/dogfood/adversarial-ux-test"].description
-
-
-def test_optional_skill_catalog_docs_list_adversarial_ux_test():
-    optional_catalog = (REPO_ROOT / "website" / "docs" / "reference" / "optional-skills-catalog.md").read_text(encoding="utf-8")
-    bundled_catalog = (REPO_ROOT / "website" / "docs" / "reference" / "skills-catalog.md").read_text(encoding="utf-8")
-
-    assert "**adversarial-ux-test**" in optional_catalog
-    assert "official/dogfood/adversarial-ux-test" in optional_catalog
-    assert "`adversarial-ux-test`" in bundled_catalog
-    assert "dogfood/adversarial-ux-test" in bundled_catalog

website/docs/reference/optional-skills-catalog.md

@@ -16,7 +16,6 @@ For example:
 
 ```bash
 hermes skills install official/blockchain/solana
-hermes skills install official/dogfood/adversarial-ux-test
 hermes skills install official/mlops/flash-attention
 ```
 
@@ -57,12 +56,6 @@ hermes skills uninstall <skill-name>
 | **blender-mcp** | Control Blender directly from Hermes via socket connection to the blender-mcp addon. Create 3D objects, materials, animations, and run arbitrary Blender Python (bpy) code. |
 | **meme-generation** | Generate real meme images by picking a template and overlaying text with Pillow. Produces actual `.png` meme files. |
 
-## Dogfood
-
-| Skill | Description |
-|-------|-------------|
-| **adversarial-ux-test** | Roleplay the most difficult, tech-resistant user for a product — browse in-persona, rant, then filter through a RED/YELLOW/WHITE/GREEN pragmatism layer so only real UX friction becomes tickets. |
-
 ## DevOps
 
 | Skill | Description |

website/docs/reference/skills-catalog.md

@@ -59,12 +59,9 @@ DevOps and infrastructure automation skills.
 
 ## dogfood
 
-Internal dogfooding and QA skills used to test Hermes Agent itself.
-
 | Skill | Description | Path |
 |-------|-------------|------|
 | `dogfood` | Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports. | `dogfood/dogfood` |
-| `adversarial-ux-test` | Roleplay the most difficult, tech-resistant user for a product — browse in-persona, rant, then filter through a RED/YELLOW/WHITE/GREEN pragmatism layer so only real UX friction becomes tickets. | `dogfood/adversarial-ux-test` |
 | `hermes-agent-setup` | Help users configure Hermes Agent — CLI usage, setup wizard, model/provider selection, tools, skills, voice/STT/TTS, gateway, and troubleshooting. | `dogfood/hermes-agent-setup` |
 
 ## email