Discovery

Spawned polynomial-explorer vertical worker tonight in duplex container (devagentic-duplex-claude). The hermes binary there shows:

```
Hermes Agent v0.14.0 (2026.5.16)
Profile: polynomial-explorer
16 tools · 0 skills
```

This is pre-G1/G2/G3/G4. Partner just shipped:

• G1 — devagentic-vertical-preamble plugin (PR feat(plugin): devagentic-vertical-preamble — auto-load vertical context on session boot (#55, G1 of devagentic#203) #59, merged)
• G2 foundation — silo_query + confer_run MCP tools (PR feat(mcp): silo_query + confer_run tools — devagentic-mutations plugin (#56, G2 of devagentic#203) #63, merged)
• G3 — file_issue MCP tool (PR feat(mcp): file_issue tool — hermes-github plugin (closes #57, G3 of devagentic#203) #64, merged)
• G4 — lane_h_list + lane_h_fetch MCP tools (PR feat(mcp): lane_h_list + lane_h_fetch — devagentic-lane-h plugin (closes #58, G4 of devagentic#203) #65, merged)

Expected tool count post-G4: 31. Actual in container: 16.

Root cause

The hermes container ships a baked binary that hasn't been rebuilt + redeployed since v0.14.0 (2026-05-16). Every G1-G4 PR is on main but not in any container.

What's needed

Whoever owns the container image build (probably devagentic infra side, possibly partner with operator help) needs to:

1. Cut a new hermes-agent release (v0.14.1 or v0.15.0)
2. Rebuild the duplex container image (or whichever image hosts hermes for verticals)
3. Redeploy

Side note: poly-explorer vertical is already materialized

Vertical doc set on canonical devbox:

• verticalSpec: doc-20260524-94b8
• workerGuardrails: doc-20260524-9676
• 70 grafted contexts

POST /graphql works end-to-end with proper auth. Worker session boots fine. Just can't actually USE the new plugins because they're not in the binary.

Parent

devagentic#203 (canonical fusion contract). This is "G6: deploy the G1-G4 plugins so they're reachable from real worker containers."