Add Hermes Agent example (daily-triage) + primitives matrix column

[jiaobotao]

What

• examples/hermes/daily-triage.md — Hermes Agent (by Nous Research) implementation of the Daily Triage pattern:
  • Report-only L1 with hermes cron create + --skill loop-triage + --deliver local
  • Faster cadence + Feishu channel delivery variants
  • Week 3+ chained-fix pattern via hermes cron edit --context-from (upstream job's stdout injected into downstream job's prompt)
  • Maker/checker split via delegate_task(role='leaf', toolsets=[...])
  • Webhook-triggered variant via POST /hooks/agent
• docs/primitives-matrix.md — new Hermes column across the primitives table, scheduling quick reference, skill packaging, sub-agent patterns, and copy-paste starters. Title/intro updated to eight tools.
• docs/adopters.md — Hermes Agent row (L1, Daily Triage).

Why

Hermes ships all six loop primitives (cronjob / skill / STATE / delegate_task / MCP / memory) in a single binary — a natural fit for the reference matrix. No loop-init --tool hermes yet; this PR is the "manual copy" bridge, same phase OpenClaw was in before its own starter kits landed.

Two Hermes-specific angles worth calling out that surfaced during the write-up:

1. Per-job --workdir injects that directory's AGENTS.md / CLAUDE.md / .cursorrules into the job's system prompt and pins the terminal cwd — cross-project loop isolation without a git worktree per run.
2. hermes cron edit --context-from <upstream-job-id> turns a two-job pipeline into a maker/checker chain: the upstream job's most recent completed stdout is injected into the downstream job's prompt on every tick.

Test

• Followed the OpenClaw example structure 1:1 for consistency.
• All hermes cron / hermes skills / delegate_task commands verified against the current Hermes CLI (hermes cron create --help, hermes skills --help).
• All internal relative links in examples/hermes/daily-triage.md resolve to files that exist in this repo (../../docs/primitives-matrix.md, ../../docs/safety.md, ../../patterns/daily-triage.md, ../../resources/sources.md, ../../starters/minimal-loop/STATE.md.example, ../../templates/SKILL.md.loop-triage).
• No source-code changes — docs + examples only.

Checklist

• Links work from README/index
• No secrets or internal URLs
• STATE.md examples use .example suffix (references upstream starters/minimal-loop/STATE.md.example)
• Safety-sensitive sections reference docs/safety.md
• Tool-agnostic prose kept in shared docs; Hermes-specific content in labeled sections

[cobusgreyling]

Thanks @jiaobotao for contributing an adopter listing — visible, reviewable PRs like this grow the reference for everyone.

What happens next

• Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
• good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

• Contributor quickstart + open issues
• Good first issue backlog

— loop-engineering maintainers