2026-04-14 Hermes migration batch O 실제 이전
결론
- 최종 이전 완료: 5개
- OpenClaw 최종 비활성:
upstream-tracker,tanker-tracker,refining-tracker,eia-energy-3indicators,cron-watchdog-6h - Hermes 최종 활성:
ocO-O001~ocO-O005중ocO-O001~ocO-O0055개 (ocO-O000제외) - 코드/LaunchAgents 변경 없음:
shared/llm.py,shared/cycle_base.py, LaunchAgents 미수정
백업
- Hermes jobs 백업:
/Users/ron/.hermes/cron/jobs.json.bak-batchO-20260414151732 - OpenClaw jobs 백업:
/Users/ron/.openclaw/cron/jobs.json.bak-batchO-20260414152125
최종 이전 목록
| OpenClaw ID | Hermes ID | 스케줄 | 검증 | 최종 상태 |
|---|---|---|---|---|
upstream-tracker |
ocO-O001 |
30 6 * * * |
strict dual-run 3/3 PASS | OpenClaw off / Hermes scheduled |
tanker-tracker |
ocO-O002 |
35 6 * * * |
strict dual-run 3/3 PASS | OpenClaw off / Hermes scheduled |
refining-tracker |
ocO-O003 |
40 6 * * * |
strict dual-run 3/3 PASS | OpenClaw off / Hermes scheduled |
eia-energy-3indicators |
ocO-O004 |
30 6 * * 1 |
strict dual-run 3/3 PASS | OpenClaw off / Hermes scheduled |
cron-watchdog-6h |
ocO-O005 |
0 0,6,12,18 * * * |
strict dual-run 3/3 PASS | OpenClaw off / Hermes scheduled |
검증 리포트
upstream-tracker ↔ ocO-O001
/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152048_upstream-tracker_ocO-O001.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152057_upstream-tracker_ocO-O001.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152105_upstream-tracker_ocO-O001.json
tanker-tracker ↔ ocO-O002
/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152050_tanker-tracker_ocO-O002.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152059_tanker-tracker_ocO-O002.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152107_tanker-tracker_ocO-O002.json
refining-tracker ↔ ocO-O003
/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152052_refining-tracker_ocO-O003.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152101_refining-tracker_ocO-O003.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152109_refining-tracker_ocO-O003.json
eia-energy-3indicators ↔ ocO-O004
/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152054_eia-energy-3indicators_ocO-O004.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152103_eia-energy-3indicators_ocO-O004.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152111_eia-energy-3indicators_ocO-O004.json
cron-watchdog-6h ↔ ocO-O005
/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152055_cron-watchdog-6h_ocO-O005.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152104_cron-watchdog-6h_ocO-O005.json/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_152113_cron-watchdog-6h_ocO-O005.json
제외/롤백
daily-kpi-eval→ocO-O000은 롤백 유지.- 이유: strict diff 1차 검증에서 OpenClaw 쪽 stdout에만
Telegram send failed after 3 retries: <urlopen error [Errno 8] ...>라인이 생겨strict_diff_mismatch발생. - 조치: Hermes
ocO-O000은enabled=false,state=paused; OpenClawdaily-kpi-eval은 그대로enabled=true유지. - 실패 리포트:
/Users/ron/.openclaw/workspace/verification/hermes-migration/20260414_151913_daily-kpi-eval_ocO-O000.json
최종 상태 확인
| ID | OpenClaw enabled | Hermes enabled | Hermes state | next_run |
|---|---|---|---|---|
upstream-tracker |
false | true | scheduled | 2026-04-15T06:30:00+09:00 |
tanker-tracker |
false | true | scheduled | 2026-04-15T06:35:00+09:00 |
refining-tracker |
false | true | scheduled | 2026-04-15T06:40:00+09:00 |
eia-energy-3indicators |
false | true | scheduled | 2026-04-20T06:30:00+09:00 |
cron-watchdog-6h |
false | true | scheduled | 2026-04-14T18:00:00+09:00 |
daily-kpi-eval |
true | false | paused | rollback |
중복 확인
- 최종 5개 모두 Hermes
migration.openclaw_id기준 중복 없음. - batch O 최종 Hermes IDs:
ocO-O001,ocO-O002,ocO-O003,ocO-O004,ocO-O005.
JSON 검증
/Users/ron/.hermes/cron/jobs.json→python3 -m json.tool통과/Users/ron/.openclaw/cron/jobs.json→python3 -m json.tool통과
Remaining Risks
daily-kpi-eval류의 Telegram 발송 포함 작업은 네트워크/DNS 상태에 따라 stdout이 달라져 strict diff가 흔들릴 수 있음. 다음 배치에서는 알림 포함 작업을 따로 묶어--no-notify동등성 또는 stdout 정규화 정책을 먼저 정해야 함.- 이전 완료된 5개 중
--notify가 붙은 트래커 3개는 검증 시에는 anomaly가 없어 발송 차이가 없었음. 향후 anomaly 발생일에는 Hermes/OpenClaw 출력이 달라질 수 있으나, OpenClaw는 비활성화되어 Hermes 단독 실행만 남음.
자체평가
- 정확성 5/5: 5개 최종 이전, 3회 strict dual-run, 중복 확인 완료.
- 완성도 5/5: 백업/롤백/최종 상태/리포트까지 기록.
- 검증 5/5: 각 3회 PASS + JSON 검증 완료.
- 최소 변경 5/5: cron JSON만 변경, 코드/LaunchAgents 미수정.
- 종합 5.0/5.