feat: add Oh My Pi (omp) agent support

[FelipeMayerDev]

Summary

Adds Oh My Pi (omp) as the 11th supported agent in HarnessKit.

Backend

• New OmpAdapter for ~/.omp / ~/.omp/agent layout.
• Discovers user/project skills:
  • ~/.omp/agent/skills/<name>/SKILL.md
  • .omp/skills/<name>/SKILL.md
• Discovers MCP config:
  • ~/.omp/agent/mcp.json
  • .omp/mcp.json
  • JSON mcpServers format, including stdio command, remote url, args, env, and native enabled flag.
• Discovers TypeScript/JavaScript extension modules as plugins:
  • ~/.omp/agent/extensions/*.{ts,js,mjs,cjs}
  • .omp/extensions/
• Discovers native config/rules:
  • AGENTS.md, RULES.md, config.yml, settings.json.
• Declares HookFormat::None because omp hooks are JS/TS event modules, not shell-command hook configs (same model as OpenCode).

Frontend

• Adds omp to AGENT_ORDER and display names.
• Adds theme color variables and extension filter colors.
• Adds an Oh My Pi mascot using the official omp.sh/favicon.svg π logo (pink→purple→cyan gradient).
• Updates onboarding layout for the new agent.

Docs

• Updates English and Chinese README agent count and capability matrix.

Verification

• cargo check -p hk-core ✅
• cargo test -p hk-core ✅ — 557 tests passed
• npx tsc --noEmit ✅
• npx vitest run src/lib/__tests__/types.test.ts src/stores/__tests__/extension-helpers.test.ts ✅ — 76 tests passed
• Manual smoke test against a real ~/.omp install ✅
  • detected omp
  • read ~/.omp/agent/config.yml
  • discovered 3 real extension modules: orca-agent-status, orca-prefill, orca-titlebar-spinner

Screenshots

Overview — Oh My Pi detected

Agent details — Oh My Pi

Extensions filtered by Oh My Pi

Oh My Pi mascot card crop

[RealZST]

Thanks for adding OMP! I cross-checked every convention against the omp source and docs, then pushed five commits on top of yours:

• 01c87bf — Your is_extension_file matched .ts/.js/.mjs/.cjs. We checked omp's loader: it only globs *.{ts,js} (https://github.com/can1357/oh-my-pi/blob/main/docs/extension-loading.md), so a .mjs/.cjs file would show up in HarnessKit as a toggleable plugin while omp never actually loads it. This commit narrows the match to .ts/.js.
• 654f57b — Your MCP reader only looked at the per-entry enabled flag. omp actually applies two more user-level lists on top: the disabledServers denylist (always wins) and the enabledServers allowlist (overrides enabled: false). See https://github.com/can1357/oh-my-pi/blob/main/docs/mcp-config.md. This commit reads all three, so HarnessKit shows the state omp actually uses.
• ce0ed01 — Your adapter discovered top-level extension files and the AGENTS.md/RULES.md context files. omp also discovers directory-form extensions (/index.{ts,js}) and per-file rules (rules/*.{md,mdc}, both user and project scope), so this commit adds those two surfaces to the scan.
• 62f21ca — HarnessKit disables a plugin by renaming it to *.disabled and remembering the path in its DB. If the file was renamed outside HK (so there's no DB record), re-enable falls back to searching the plugin dir and re-deriving each plugin's ID — but that derivation only knew opencode's ID format, and your omp plugins use the same format. So re-enabling such an omp extension silently did nothing; fixed. Also small polish: mcp.json shown in the settings view, a redundant project marker removed, animation timing fixed.
• 9c8b231 — MCP toggle used HarnessKit's generic remove+snapshot+restore path, which redacts secrets and can drop keys like type/url. omp natively honors the per-entry enabled flag, so this commit just flips that flag in place — nothing gets deleted or redacted, and servers disabled by omp itself can now be re-enabled from HK.

Heads up: the project-level .omp/extensions/ path currently has no effect — HarnessKit doesn't scan project-level plugins for any agent yet, so only ~/.omp/agent/extensions/ is picked up. It will start working as soon as I add project-level plugin scanning.

Thanks again! Merged.