feat(skills): per-profile skills toggle in Skills screen

[cypres0099]

Summary

Adds a Profile dropdown to the Skills screen so one workspace process can manage skills.disabled across every installed Hermes profile. Today the screen only edits the profile the dashboard daemon is bound to; toggling a sub-profile (scratch-worker, writer, emailtriage, …) requires running a second daemon.

Pairs with NousResearch/hermes-agent#25116, which adds the matching server-side endpoints on the dashboard:

• GET /api/profiles/{name}/skills
• PUT /api/profiles/{name}/skills/toggle
• is_active flag on /api/profiles

What changes

Backend

Two thin proxy routes that forward to the new dashboard endpoints:

Workspace route	Dashboard route
GET /api/profiles/skills?name=<profile>	GET /api/profiles/<profile>/skills
PUT /api/profiles/toggle-skill body {profile,name,enabled}	PUT /api/profiles/<profile>/skills/toggle

Both go through the existing dashboardFetch helper, so auth is transparent. They early-return when capabilities.dashboard.available is false, so older zero-fork/managed-gateway setups don't get spurious 5xxs.

I did not add a new /api/profiles proxy — the existing /api/profiles/list already surfaces which profile the workspace is bound to (active/activeProfile), which is the same source-of-truth the dashboard uses to compute is_active. Reusing it avoids a redundant network hop on every Skills mount.

Frontend (src/screens/skills/skills-screen.tsx)

• New Profile <select> in the Skills toolbar. Hidden when only one profile is installed (single-profile parity with the dashboard's sidebar). Defaults to the active profile, falls back to is_default, then any.
• The active profile is suffixed (active) so the user always knows which profile the daemon is currently bound to — mirrors the dashboard PR's affordance.
• When the user picks a non-active profile:
  • The screen fetches /api/profiles/skills?name=<profile> instead of /api/skills.
  • The lighter per-profile payload is normalized into SkillSummary so existing rows/dialogs render unchanged.
  • The Marketplace tab and Origin filter are hidden — both depend on workspace-side enrichment (Skills Hub, bundled manifest, agent-created flags) that the dashboard's per-profile endpoint deliberately omits.
  • Toggle writes go through PUT /api/profiles/toggle-skill so skills.disabled is mutated in the target profile's config.yaml, not the active one.
  • Install/uninstall on a non-active profile is intentionally blocked with a friendly error pointing the user back to the active profile — the dashboard's per-profile endpoint only supports toggle today.

How to test

1. Run a dashboard daemon with at least one sub-profile in ~/.hermes/profiles/ (e.g. scratch-worker, writer).
2. Start the workspace and open the Skills screen. The Profile dropdown appears in the toolbar, defaulted to the active profile with (active) suffix.
3. Switch to a non-active profile. The list refreshes from that profile's skills/ directory; Marketplace tab and Origin filter disappear.
4. Toggle any skill. Reload the page and verify skills.disabled in ~/.hermes/profiles/<name>/config.yaml reflects the change, and the active profile's config.yaml is untouched.

I smoke-tested this against two co-located Hermes installs:

• Iris (default + emailtriage + hivemind-community-manager) — toggling ascii-art off on emailtriage from the workspace UI added ascii-art to ~/.hermes/profiles/emailtriage/config.yaml only; ~/.hermes/config.yaml was unchanged.
• Artemis (default + scratch-worker + writer + analyst + creative + researcher + shopify-admin) — toggling airtable on scratch-worker removed airtable from scratch-worker/config.yaml only; default's disabled list was unchanged.

Known limitations

• The per-profile list excludes skills loaded via skills.external_dirs — same scope as the dashboard's endpoint.
• Install/uninstall on a non-active profile requires either a follow-up to dashboard PR #25116 or running a daemon bound to that profile.

🤖 Generated with Claude Code

[Cossackx]

Hermes verification: mergeable; local build previously passed for this 4-file change. GitHub reports no checks on the branch. Direct squash merge was attempted but blocked by GitHub permissions for Cossackx (MergePullRequest). Maintainer action needed: squash-merge if the paired Hermes Agent dashboard endpoint is available.

[cypres0099]

Closing as superseded by the current Hermes Agent main implementation of profile-scoped skills/toolsets management. This workspace-side branch targeted the older companion endpoint shape, so reviving it would need a fresh branch against the current upstream API instead of merging this PR.