chore: bump hermes-agent to v2026.9.11

[tropibot]

Automated version bump triggered by release v2026.9.11.

Changes

• upstream version (NousResearch/hermes-agent) → v2026.9.11
• UPSTREAM_VERSION → v2026.9.11

Supersedes: #46

[tropibot]

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 991fae5

This is a development version and should only be installed for testing purposes.

1. Package hermes-agent.dnp.dappnode.eth

Install link

Hash: /ipfs/QmPAdbzoCm6Y47hWLeJNumUBzKtUd9aNpG6UG8aLfq2Ymq

(by dappnodebot/build-action)

[tropibot]

✅ Package harness passed

Baseline and candidate containers became stably running

Package	Verdict	Reason	Duration	Cleanup
hermes-agent.dnp.dappnode.eth	✅ Passed	Candidate containers stable (candidate_containers_stable)	44m 49s	✅ Passed

Run overview

Context	Value
Pull request	dappnode/DAppNodePackage-Hermes-agent#49
Tested commit	1d1cb49c1220
Candidate artifact	Install on DAppNode · /ipfs/QmZqzqZGa3h4oAuo8Wh8rJoercQ1tQjv9qdRoUGZq4iaTG
Baseline request	automatic
Worker	worker-01
Run ID	gh-pr-49-1d1cb49c1220-ba7bba1a1c8f5041
Execution	2026-09-11T20:21:53.992617913+00:00 → 2026-09-11T21:06:43.400682560+00:00 (✅ Completed)

Baseline vs candidate

Check	Baseline	Candidate
Version	0.1.8	0.1.7
Install	✅ Passed · 2m 19s	✅ Passed · 40m 49s
Hard check	✅ Passed · 5 stable samples	✅ Passed · 5 stable samples
Containers	1 observed	1 observed
Stabilization	23s	23s
Log collection	✅ Passed · 1 container	✅ Passed · 1 container

Container comparison

• Added: none
• Removed: none
• Baseline inventory: DAppNodePackage-hermes-agent.hermes-agent.dnp.dappnode.eth
• Candidate inventory: DAppNodePackage-hermes-agent.hermes-agent.dnp.dappnode.eth
• Baseline non-running states: none
• Candidate non-running states: none
• Deterministic regressions: ✅ none

Container inventory

Baseline

Container	Service	State	Image	Created
DAppNodePackage-hermes-agent.hermes-agent.dnp.dappnode.eth	hermes-agent	✅ Running	hermes-agent.hermes-agent.dnp.dappnode.eth:0.1.8	1789158255

Candidate

Container	Service	State	Image	Created
DAppNodePackage-hermes-agent.hermes-agent.dnp.dappnode.eth	hermes-agent	✅ Running	hermes-agent.hermes-agent.dnp.dappnode.eth:0.1.7	1789160729

Runtime analysis _advisory

⚠️ Suspicious — Heuristic and Nexus analysis: Candidate boots and starts all s6 services, but introduces new configuration warnings that two platforms have no valid toolsets after migrating to schema 42, and the DAppNode setup init logs no longer show context/skill seeding or .env repair. These are runtime-visible changes compared with the baseline.

Analyzer	Status	Summary
Composite	⚠️ Suspicious	Heuristic and Nexus analysis: Candidate boots and starts all s6 services, but introduces new configuration warnings that two platforms have no valid toolsets after migrating to schema 42, and the DAppNode setup init logs no longer show context/skill seeding or .env repair. These are runtime-visible changes compared with the baseline.
Heuristic	✅ Clean	No configured candidate-only suspicious signature was found
Nexus	⚠️ Suspicious	Candidate boots and starts all s6 services, but introduces new configuration warnings that two platforms have no valid toolsets after migrating to schema 42, and the DAppNode setup init logs no longer show context/skill seeding or .env repair. These are runtime-visible changes compared with the baseline.
Baseline evidence	✅ Clean	No configured suspicious signature was found
Candidate evidence	✅ Clean	No configured suspicious signature was found

Severity	Container	Finding	Evidence
⚠️ Warning	DAppNodePackage-hermes-agent.hermes-agent.dnp.dappnode.eth	Baseline only warned that these platforms referenced unknown toolsets; candidate now reports no valid toolsets at all, suggesting the schema-42 migration removed or failed to retain valid toolset bindings and may break agent tooling on those platforms.	⚠ platform 'teams' has no valid toolsets configured — the agent will have no tools on this platform. Run `hermes tools` to reconfigure.\n⚠ platform 'google_chat' has no valid toolsets configured — the agent will have no tools on this platform. Run `hermes tools` to reconfigure.
⚠️ Warning	DAppNodePackage-hermes-agent.hermes-agent.dnp.dappnode.eth	The candidate DAppNode setup step no longer records required seeding and .env repair. Persistent state may explain the silence, but the log difference is a new runtime uncertainty that could leave context, skills, or API key unset on fresh installs.	Baseline cont-init.d/10-dappnode-setup logs: Seeded .hermes.md, Seeded DAppNode skill, Seeded DAppNode Nexus skill, Repaired default .env: API_SERVER_KEY. Candidate only logs: Patched config.yaml for DAppNode (api_port=3000, dashboard_auth=basic, whatsapp_bridge_port=3010).

Cleanup and diagnostics

Check	Result
Cleanup	✅ Passed
Leftover packages	none
Cleanup error	none

✅ No run errors were recorded.

---

_{Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs.}