@synap-core/workspace-templates 0.27.0 → 0.29.0

package/README.md

@@ -25,7 +25,7 @@ How installs, reconciles and tiers work is in the `synap-market` skill
 | `skills/<slug>/` | `skill` | Either a manifest `<slug>.skill.json` (`creative-director`), or an Agent-Skills folder (`SKILL.md` plus references) with a header `skills/<slug>.catalog.json` beside it | The manifest: yes. A folder: only with its header, and only when it holds no reference files (a skill package carries no documents). Headers decided by the founder on 2026-11-05: `bookmark-enrichment` and `routing-to-channels` public, `mapping-the-server` unlisted (private to the official owner); `reading-client-progress` and the parked `stellar-scf-grants-advisor` stay **staged** |
 | `views/<slug>.view.json` | `view` | Manifest; `spec.views` in the canonical shape the CP stores (`{slug, displayName, type, config, scopeProfileSlugs}`) | Category `view`. Three today (`bookmark-views-pack`, `event-views-pack`, `task-views-pack`), moved from the old CP pack fragments on 2026-11-05. CI on every push to main |
 | `automations/<slug>.automation.json` | `automation` | bridge-setup `flowDefinition` form, plus a header `automations/<slug>.catalog.json` beside it | Only with its header, and only without apply-time placeholders. Headers decided by the founder on 2026-11-05: `bookmark-enrichment` public; `url-bookmark-capture`, `github-pr-events` and the five `ship-a-change-*` unlisted. `mail-feed` stays **staged**: it carries two placeholders bridge-setup fills |
-| `agents/<slug>.agent.yaml` | `agent` | Manifest. `spec` (`schema/agent.ts`) is what the pod reads as `definition.agent`: `harness` (the `agent_type` join key), `aliases`, `worker`, `tried`, `detect`, `wake` (data: `program` + `args` + `params`, never a shell line; required for a worker only), `practices.skills`. One per program of the backend harness registry, plus `hermes`. CP category `agent`, official vendor only, left out of browse lists (the catalog installs every official agent on every pod, founder decision D8) | **Not automatically.** `publish-official.mjs` leaves `agent` out when no `--kind` is given (`FIRST_PUBLISH_BY_HAND`), so main's publish skips it; the founder approves the first publish (`--kind agent`), after the CP that knows the category is deployed |
+| `agents/<slug>.agent.yaml` | `agent` | Manifest. `spec` (`schema/agent.ts`) is what the pod reads as `definition.agent`: `harness` (the `agent_type` join key), `aliases`, `worker`, `tried`, `detect`, `wake` (data: `program` + `args` + `params`, never a shell line; required for a worker only), `practices.skills`, `mcp` (where its program reads MCP servers: `config` under ~/, `format` yaml/json, `key` dot path, `entry`; the CLI writes the pod's server there on `synap agents add`, the pod ignores it). One per program of the backend harness registry, plus `hermes`. CP category `agent`, official vendor only, left out of browse lists (the catalog installs every official agent on every pod, founder decision D8) | Yes, on every push to main, like every other kind (the first publish was the founder's, by hand, on 2026-11-07; `FIRST_PUBLISH_BY_HAND` is empty since) |
 | `schema/` | | Zod manifest schema: `header.ts`, plus one body per kind (`workspace`, `capability`, `skill`, `automation`, `view`, `agent`, `playbook`) | |
 | `standards/*.standard.yaml` | | Quality standard per workspace (`pnpm eval`) | |
 | `scripts/catalog-lib.mjs` | | **The ONE lib**: `loadCatalog` → `validateCatalog` → `diffCatalog` → `publishCatalog` | |

package/agents/hermes.agent.yaml

@@ -3,16 +3,26 @@ kind: agent
 meta:
   slug: hermes
   name: "Hermes Agent"
-  description: "Nous Research's Hermes Agent CLI. A stub: its wake (hermes chat -q) has never been run on a real computer, so treat it as untested."
+  description: "Nous Research's Hermes Agent CLI. Tried on a real computer: its wake (hermes chat -q) answers and it reaches the pod's MCP tools. Not yet started through the Synap worker."
   tags: [assistant, worker]
 spec:
   harness: hermes
   worker: true
-  tried: false
+  # Tried 2026-11-07 on the founder's CT112 (Hermes Agent v0.23.0): `hermes chat -q`
+  # answered, and `hermes mcp test synap` found the pod's 14 tools. The worker path
+  # (`synap worker --once`, synap-cli#100) has not run it yet.
+  tried: true
   wake:
     program: hermes
     args: ["chat", "-q", "{prompt}"]
     params:
       prompt: { type: text, required: true }
+  # Hermes reads its MCP servers from ~/.hermes/config.yaml, under mcp_servers,
+  # a remote one as { url, headers } (hermes-agent.nousresearch.com/docs/user-guide/features/mcp).
+  mcp:
+    config: "~/.hermes/config.yaml"
+    format: yaml
+    key: mcp_servers
+    entry: url-headers
   practices:
     skills: [synap]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synap-core/workspace-templates",
-  "version": "0.27.0",
+  "version": "0.29.0",
   "type": "module",
   "description": "Canonical workspace definitions — YAML source + typed exports for browser, backend, CLI, and marketplace",
   "repository": {