Hermes Vault · Update Log
d71033a4 live locally
5.8 GB rollback backup
Gateway service repair pending

Last updated: 27 July 2026, 12:24 BST

Hermes Update Log, Boyd's System
v0.19.0 mainline update and reliability check

Hermes was updated from v0.18.2 at b9b463f3 to v0.19.0 at d71033a4, a 3,145-commit mainline jump. A full 5.8 GB backup completed before mutation. The repo is clean, Camofox remains localhost-only, all seven role-skill links survived, Context7 and Linear MCP connect, Computer Use passes doctor, and Telegram plus Photon are running. The remaining maintenance item is the stale launchd service definition. It needs one separately approved gateway restart to install the new crash-loop and shutdown timing settings.

Current Hermes
v0.19.0 · d71033a4 · repo clean
Main decision
Approve one more gateway restart when convenient so Hermes can rewrite the stale launchd definition with the new managed Node path, crash-loop throttle and graceful shutdown timeout.
d71033a4current upstream HEAD
3,145commits installed
5.8 GBpre-update backup
2gateway platforms live

Executive Summary

Hermes is current on main at d71033a4 and reports v0.19.0. The guarded update completed with a verified full backup and a clean source tree. Core local checks passed. Drift review found a broken reviewer ownership flow; orchestrator 2.1.1, reviewer 2.2.0, their linked guidance and the coder success exit now use an ownership-safe reviewer gate. Direct approve and revise mechanics passed against temporary real Kanban databases. A late audit also found two unresolved memory-gate defects: V4A multi-file patches can bypass protected-path inspection, and legitimate compressed or branched interactive sessions can be misclassified as subagents. The exact hook repair remains approval-gated and was not applied. The gateway needed two automatic recovery restarts during a cold-start skill scan, then stabilised at one PID with Telegram and Photon connected. Its launchd definition remains stale and needs a separately approved restart. The automatic cua-driver refresh failed due to an upstream archive packaging error, but installed 0.7.1 is healthy. Hindsight recall works even though the CLI status screen incorrectly reports its local setup unavailable.

Update complete

Hermes is v0.19.0 at d71033a4 with a clean tree and 0 ahead / 0 behind origin/main.

Core passed; security hook repair pending

Services passed and the review-flow P0 was repaired. Memory-gate still needs an approved V4A path and session-lineage fix.

Gateway service repair

The launchd plist is running but stale. One separately approved restart will install the new Node path, crash-loop throttle and graceful shutdown timeout.

No live paid provider, delegation or model-driven Kanban smoke tests were run. The review flow was tested directly through the real runtime against temporary databases. Claude and Anthropic were untouched by design. BB approved this report deploy during the update gate.

Decisions Needed

Top Maintenance Changes

2026-07-27 v0.19.0 mainline updateHermes moved 3,145 commits to d71033a4 with a full backup. Core checks passed; one gateway service repair remains.watch

What changed: Ran hermes update --backup --yes from b9b463f3 to d71033a4. Hermes now reports v0.19.0 and up to date.

Validation: Repo clean; Camofox localhost-only and healthy; all seven role-skill symlinks intact; Context7 and Linear MCP connected; Computer Use doctor passed; Telegram and Photon reached ready state.

Open maintenance: The launchd plist is stale relative to v0.19.0. Updating it requires a separately approved gateway restart.

Decision: Approve hermes gateway start during a quiet window to install the new launchd safety settings.
v0.19 reviewer ownership drift repairedA stale custom review flow contradicted Hermes' permanent worker ownership guard. The skills and audit template now match the runtime.better

Problem: The reviewer skill instructed a dispatcher-spawned reviewer to complete or block the producer's task. v0.19.0 rejects foreign lifecycle mutations and has no reviewer exception.

Fix: Orchestrator 2.1.1, reviewer 2.2.0, linked role guidance and coder success exits now use cross-task comments for evidence and the reviewer's own task as the gate. Revise creates a correction card and blocks the reviewer's own gate.

Proof: Temporary real Kanban databases confirmed foreign complete/block are rejected, foreign comment succeeds, approve completes the reviewer gate, and revise creates a ready correction card while leaving the producer done.

Remaining proof: Run one paid model-driven approve and revise smoke on the live board after separate approval.
Late memory-gate security findingsThe deployed hook misses V4A embedded paths and over-blocks interactive child sessions. The exact repair is approval-gated.watch

Bypass: Patch mode embeds Add, Update, Delete and Move targets inside patch text. The hook currently checks only tool_input.path, so a protected basename can bypass inspection.

False block: The hook treats any non-null parent_session_id as a subagent. v0.19 also uses parent lineage for legitimate compression continuations and branches.

Proposed repair: Extract every V4A endpoint, fail closed on multiple protected targets, and use explicit session source to distinguish subagents. No hook or config change was applied because approval timed out.

Decision: Approve the exact memory-gate patch and temporary-home verification plan.
2026-07-10 update and DB maintenanceHermes main updated to b9b463f3; DB optimize and integrity check completed.better

What changed: Ran hermes update --backup from 449706cb to b9b463f3 after precheck found 183 upstream commits.

Validation: Repo clean, gateway launchd-supervised, Context7 and Linear MCP connected, Camofox health OK on 127.0.0.1, worker skill symlinks OK.

DB maintenance: hermes sessions optimize completed and SQLite PRAGMA quick_check returned ok; database stayed around 3.28 GB.

Action: No rollback needed from current evidence.
Generated Desktop JS cleanupUpdate/build produced 697 untracked .js files beside tracked TS/TSX source; they were moved to Trash.better

Evidence: Files appeared under apps/desktop/src and apps/shared/src around update time and matched generated JavaScript output.

Cleanup: Moved to ~/.Trash/hermes-generated-js-post-update-20260710-191358; git status is clean afterward.

Rollback handle: Trash folder can be restored if needed.
Previous Telegram model and delivery risks changedThe old gpt-5.5 route is gone and v0.19.0 adds durable delivery protection. Monitor normal restarts only.better

Delivery protection: v0.19.0 adds a durable delivery-obligation ledger so finished replies can survive a gateway restart. This run did not perform a destructive crash test.

Current model: Default model is now openai-codex gpt-5.6-sol. The configured fallback entries are blank, so Hermes reports no active fallback providers.

Action: No Boyd action. Mikey should monitor ordinary restart evidence and only escalate if a finished reply is lost again.
Speed and prompt-build reliabilitySkill snapshot prompt builds are faster and CLI/runtime responsiveness improved.better

What changed: The update includes perf(skills): speed up snapshot prompt builds, dashboard/session query offloading, and state-query compact rows.

What this means: Less waiting around the parts of Hermes that build prompts, list sessions, and render dashboard/status surfaces.

Recommended use: No behaviour change. Treat it as background speed.

Action: None.
Gateway and session hardeningGateway restart and live-session routing got safer; local gateway is healthy after restart.better

What changed: Fallback providers reload for live sessions, fallback-chain refresh hardening, delegation completion/session-boundary fixes, webhook route scripts off the event loop, and webhook payload filters.

Local check: Gateway is supervised by launchd at PID 4420. Fresh logs show Telegram connected, Photon sidecar listening on 127.0.0.1:8789, and gateway running with 2 platforms.

Action: None unless gateway logs start repeating errors.
Compression and long-session hygieneThe update includes a fix for compaction thrash and session-message pagination.better

What changed: Compression now has a 75% trigger floor under 512K, no summary output cap, and reasoning-trace exclusion. Session message API pagination and offset handling were fixed.

What this means: Long chats should be less likely to churn or lose useful shape during compaction.

Action: No immediate action. Watch only if long Telegram sessions behave oddly.
Matrix lazy backend refresh warningOne optional backend failed to refresh; active Telegram/Photon routes are fine.watch

What happened: During lazy backend refresh, platform.matrix failed its pip install/build refresh. Hermes kept the previous installed version.

What this means: Not a blocker for Boyd’s active Telegram/Photon setup. It matters only if Matrix is used.

Next step: If Matrix becomes relevant, rerun hermes update or test the Matrix platform backend directly.

Useful Improvements, No Decision Needed

Grok 4.5 catalog supportModel catalog gained Grok 4.5 context/reasoning metadata. No route change recommended.better

What changed: The update adds grok-4.5 GA to the model catalog, with context lengths and reasoning-effort allowlist.

Action: No provider switch.
Webhook payload filtersUseful for integrations later; not needed today.better

What changed: Gateway gained webhook payload filters and docs coverage for filters plus route scripts.

Action: Park until a webhook integration needs it.

What Was Done

Update and report task logHermes was updated from v0.18.2 to v0.19.0 with a full backup, post-update gates, drift review and report refresh.passed
  • Pre-update: Hermes v0.18.2 at b9b463f3; repo clean; origin/main 3,145 commits ahead.
  • Full backup forced because the incoming diff touched three custom-risk files plus package.json, pyproject.toml and uv.lock.
  • Backup created: ~/.hermes/backups/pre-update-2026-07-27-120649.zip, 5.8 GB. Restore with hermes import and the absolute zip path.
  • Update completed at d71033a4. Hermes reports v0.19.0, up to date, and source remains clean.
  • Config stayed at version 33. Python dependencies and Web UI rebuilt; desktop app was already current.
  • Automatic cua-driver refresh failed because the upstream archive lacked cua-cursor-theme. Installed 0.7.1 passes doctor, so no manual installer ran.
  • Camofox listens on 127.0.0.1 and health reports browserConnected=true and browserRunning=true.
  • All seven role-skill links remain symlinks to the shared productivity skills.
  • Drift review found the custom reviewer cross-task lifecycle flow contradicted v0.19.0 worker ownership enforcement.
  • Patched orchestrator to 2.1.1, reviewer to 2.2.0, linked role guidance, examples, starter prompts, audit template and coder success exits; D-046 records the ownership-safe flow.
  • Direct runtime tests passed approve and revise mechanics against temporary Kanban databases without paid model calls or live-board mutation.
  • Late audit found memory-gate V4A path bypass and parent-lineage false blocking. Exact repair was proposed but not applied because the security-hook approval timed out.
  • Context7 and Linear MCP passed live connection tests. Dropbox remains disabled by config. Stitch is not configured.
  • Gateway cold startup hit two watchdog exits during skill scanning under concurrent audit load, then stabilised with Telegram and Photon connected.
  • Gateway service definition is stale and remains unchanged because the separate repair restart approval timed out.
  • Hindsight live recall passed even though hermes memory status reports the local setup unavailable.
  • Claude and Anthropic checks were skipped by SOP. No paid provider or delegation smoke tests ran.

Historical Update Reports

2026-07-27v0.18.2 to v0.19.0 mainline update b9b463f3 to d71033a4, 3145 commits Large mainline update completed with a full backup. Core services are healthy and the P0 reviewer-flow conflict was repaired. A late audit found two unresolved memory-gate defects. Security-hook repair approval and one gateway restart remain open. outstanding
What Changed

3,145 commits installed across the Quicksilver release and 1,712 later mainline commits. Major areas include startup speed, durable delivery, delegation lifecycle, multi-profile gateways, provider routing, secret sources, approvals, security and desktop/TUI performance.

Impact

Hermes is v0.19.0 at d71033a4 with a clean repo. Camofox, role-skill symlinks, Context7, Linear, Computer Use, Telegram and Photon passed. Orchestrator 2.1.1, reviewer 2.2.0 and linked guidance now match the v0.19 ownership guard; direct approve and revise runtime tests passed. Memory-gate still has an unpatched V4A bypass and session-lineage false block. The gateway service definition needs a quiet-window refresh.

Decisions and Actions
  • blocked Approve the exact memory-gate V4A path and session-lineage patch.
  • outstanding Approve hermes gateway start during a quiet window to install the new launchd safety settings.
  • monitor Watch cold-start skill scanning only if the gateway run count rises again. No Boyd action now.
  • outstanding Approve paid model calls later for one full-agent approve and revise Kanban smoke.
  • no action Do not run the suggested curl-to-shell cua-driver installer. Installed 0.7.1 is healthy.
Update Log
  • Pre-update: v0.18.2 at b9b463f3, clean tree, 3,145 commits behind d71033a4.
  • Backup completed before mutation at ~/.hermes/backups/pre-update-2026-07-27-120649.zip, 5.8 GB.
  • Update exited 0. Hermes reports v0.19.0 at d71033a4 and up to date.
  • Config version 33 passed. Repo remained clean.
  • Camofox localhost bind and health passed. Seven role-skill symlinks passed.
  • Custom drift found: reviewer instructions attempted foreign task complete/block, which v0.19 rejects.
  • Orchestrator 2.1.1, reviewer 2.2.0 and linked reviewer/orchestrator guidance patched; coder success exits no longer block planned review.
  • Direct approve and revise runtime tests passed against temporary real Kanban databases.
  • Late audit found memory-gate V4A path bypass and parent-lineage false blocking; hook change remains approval-gated and unapplied.
  • Context7 and Linear MCP connected. Computer Use doctor passed.
  • Automatic cua-driver refresh failed on an incomplete upstream archive; installed 0.7.1 remained healthy.
  • Gateway hit two watchdog exits during cold-start skill scanning, then stabilised at one PID with Telegram and Photon ready.
  • Launchd definition is stale. Repair was not run because the separate restart approval timed out.
  • Hindsight live recall passed; its CLI status still misreads the local mode.
  • Claude/Anthropic and paid provider smokes were skipped by design.
2026-07-08v0.18.0 to v0.18.2 30e947e0 to 449706cb, 716 commits Reliability/speed update. Hermes is now v0.18.2; local gates passed. Matrix lazy backend refresh warned but did not block active Telegram/Photon use. monitor
What Changed

716 commits pulled. Notable changes include faster skill snapshot prompt builds, fallback-provider reload hardening, dashboard/session DB responsiveness, compression-thrash protection, webhook payload filters, session-message pagination fixes, Grok 4.5 catalog support, and broad gateway/MCP/runtime hardening.

Impact

Local system is healthy after update: repo clean, gateway supervised and freshly restarted, Telegram and Photon connected, Camofox localhost-only and healthy, all worker profile symlinks intact, Context7 and Linear MCP enabled. Matrix backend refresh warning is the only watch item.

Decisions and Actions
  • no action No workflow redesign from this update. Use the reliability improvements in place.
  • monitor Matrix lazy backend refresh warning: monitor only if Matrix is used.
  • resolved Report closeout contract: resolved for this run; report source/HTML/deploy path updated.
Update Log
  • Pre-update state: Hermes v0.18.0 at upstream 30e947e0; repo clean; update available.
  • Manual backup forced because incoming diff touched custom-risk files agent/anthropic_adapter.py and agent/prompt_caching.py.
  • Backup created: ~/.hermes/backups/pre-update-2026-07-08-222918.zip (4.6 GB). Restore command: hermes import /Users/boydbowker/.hermes/backups/pre-update-2026-07-08-222918.zip.
  • Update pulled 716 commits and installed hermes-agent==0.18.2 at upstream 449706cb.
  • Config migrated v31 to v33 with no new settings to configure.
  • CuaDriver upgraded from 0.7.0 to 0.7.1.
  • Web UI rebuilt successfully; desktop app reported up to date.
  • Warning: platform.matrix lazy backend failed to refresh; Hermes kept previous installed backend version.
  • Gateway drain timed out after 60s, then launchd restart succeeded.
  • Post-update: Hermes reports v0.18.2 (2026.7.7.2), upstream 449706cb, up to date, repo clean.
  • Gateway validation: launchd supervised PID 4420, service definition matches current install, fresh logs show Telegram connected and Photon connected.
  • Camofox validation: server.js listens on 127.0.0.1; launchd state running; health returned ok with browserConnected=true and browserRunning=true.
  • Profile symlinks: researcher, ops, coder, reviewer, writer, specifier, and orchestrator all point to shared productivity skills.
  • MCP validation: context7 and linear enabled; Dropbox MCP disabled by config.
  • Modified bundled skills kept by update: google-workspace, hermes-agent, ocr-and-documents.
  • Claude/Anthropic checks skipped by SOP because BB did not explicitly request Claude validation.
  • Live paid provider smokes and delegation smoke not run in this closeout; separate approval remains required for paid/API smokes.
2026-07-02v0.17.0 to v0.18.0 2ecca1e7d to 30e947e0, 1029 commits Major version bump. Local install is already v0.18.0 and core checks passed. The report was stale and is now being refreshed to match reality. outstanding
What Changed

v0.18.0 is the Judgment Release: P0/P1 cleanup, first-class Mixture-of-Agents, completion contracts and verification evidence, /learn and /journey, background delegation fan-out, desktop coding Projects, gateway scale-to-zero and drain coordination, Vertex AI support, and a broad security hardening round.

Impact

The local system is on v0.18.0 at upstream 30e947e0. Repo is clean. Gateway is supervised by launchd and Telegram is live. Camofox remains bound to 127.0.0.1. All seven worker profile skill symlinks survived. OpenAI Codex and Kimi smokes returned OK. The practical work now is to decide which new v0.18 capabilities are worth piloting, without turning the tool into the mission.

Decisions and Actions
  • outstanding Pilot /goal completion contracts and verification evidence on one real project before changing default workflows.
  • monitor Review first-class MoA and background delegation later as leverage tools, not as an excuse for more orchestration.
  • no action Keep current provider route: openai-codex / gpt-5.5 with Kimi fallback. No provider switch needed from this update alone.
  • outstanding Report lag incident logged as H-I-021. The process fix is to include the live update-report URL and version in every update closeout.
Update Log
  • Current local Hermes: v0.18.0 (2026.7.1) at upstream 30e947e0.
  • Deployed report was stale: it still described v0.17.0 at 2ecca1e7d.
  • Delta from deployed report head to current local head: 1029 commits.
  • Pre-check: git repo clean; origin/main delta 0; release tag v2026.7.1 present.
  • Camofox: server.js listen line still binds 127.0.0.1 and health endpoint returned ok.
  • Gateway: launchd supervised, current service definition matches install, Telegram receiving this thread.
  • Profile skills: researcher, ops, coder, reviewer, writer, specifier, and orchestrator are symlinks to shared productivity skills.
  • Provider smokes: openai-codex / gpt-5.5 returned OK; kimi-coding / kimi-k2.6 returned OK.
  • Claude/Anthropic checks skipped by SOP because Claude is not active and BB did not explicitly request Claude validation.
  • CuaDriver reports 0.7.0.
2026-06-27v0.17.0 to v0.17.0 mainline update 3e99ec0ff to 2ecca1e7d, 261 commits 261 commits, same public version. Kanban patch kept and verified. Review is complete; upstream PR package is now in progress. in progress
What Changed

Upstream Kanban added typed block reasons and loop protection. Backups now include project databases, Kanban boards, sibling stores, response store, memory store, and verification evidence. Gateway model-switching no longer blocks the event loop. Security redaction expanded. CuaDriver upgraded from 0.6.5 to 0.6.8.

Impact

Kanban patch kept and verified. Rollback coverage is now more complete. No other process changes.

Decisions and Actions
  • in progress Kanban patch formal review: complete. Recommended path is upstream PR first; local extension is fallback.
  • resolved Report template: JSON source and renderer now exist. Future reports should be generated, not hand-authored.
Update Log
  • 261 commits from 3e99ec0ff to 2ecca1e7d. Public version remains v0.17.0.
  • Pre-update: two dirty Kanban files. Local patch backed up at ~/.hermes/backups/hermes-update-20260627-225918/local-kanban-diff.patch.
  • Backup: ~/.hermes/backups/pre-update-2026-06-27-225937.zip, 3.9 GB. Snapshot 20260627-220547-pre-update.
  • Update: Python dependencies refreshed, web UI built, desktop packaged app rebuilt, CuaDriver upgraded to 0.6.8, bundled skills synced, gateway restarted.
  • Post-update verified: Hermes v0.17.0 at upstream 2ecca1e7d, Camofox localhost bind intact, profile symlinks intact, gateway launchd supervision healthy, Telegram connected, Context7 MCP passed, Linear MCP passed, Kanban patch compiles and imports.
  • Clean-up: desktop build dirtied apps/desktop/electron/main.cjs with bundled output. That source file was reverted. The desktop packaged app remains built.
  • Skipped by design: Claude/Anthropic checks and live provider smokes. Separate approval required for paid/API smokes.
2026-06-23v0.17.0 to v0.17.0 mainline update 5a53e0f0f to 5ecf3bf0e, 361 commits 361 commits, same version. Cron timeout watch carried from before this update. No Boyd decisions needed. monitor
What Changed

361 commits pulled. Package-lock.json was dirty pre-update. Incoming changes touched the Anthropic adapter. CuaDriver upgraded to 0.6.5. Python dependencies refreshed, web UI and desktop app rebuilt.

Impact

No local patches affected. Cron runs from before this update showed network timeouts. Reassessment scheduled after next cron runs.

Decisions and Actions
  • monitor Cron and network timeout watch: Mikey monitors after next scheduled runs. Not a Boyd action.
Update Log
  • 361 commits from 5a53e0f0f to 5ecf3bf0e. Public version remains v0.17.0.
  • Pre-update: one dirty file, package-lock.json. Incoming touched agent/anthropic_adapter.py, so manual backup was forced.
  • Backup: ~/.hermes/backups/pre-update-2026-06-23-160840.zip, 2.7 GB. Snapshot 20260623-151120-pre-update.
  • Update: Python dependencies refreshed, web UI built, desktop packaged app rebuilt, CuaDriver upgraded to 0.6.5, bundled skills synced.
  • Post-update verified: Hermes v0.17.0 at upstream 5ecf3bf0, repo clean, Camofox localhost bind intact, Camofox health OK, profile symlinks intact, gateway restarted under launchd, Telegram connected, Context7 MCP lookup passed, local MCP list passed.
  • Skipped by design: Claude/Anthropic checks and live provider smokes.
  • Watch: cron jobs active, but multiple last runs show network/timeouts from before this update. Reassess after next scheduled runs.
2026-06-19v0.16.0 to v0.17.0 509 commits Version bump to v0.17.0 via 509 commits. All provider checks passed. Follow-up fixes done same session. No open items. resolved
What Changed

Released hermes-agent==0.17.0. 509 commits pulled. Web UI rebuilt. Desktop packaged app rebuilt. CuaDriver upgraded to 0.5.7. SOP hook-table drift found and fixed. SOP updated to exclude Claude/Anthropic unless BB explicitly requests.

Impact

Major version jump. No breaking changes to Boyd's setup. OpenAI Codex and Kimi provider checks passed. Follow-up fixes completed in the same session.

Decisions and Actions
  • resolved CuaDriver daemon started and permissions verified.
  • resolved Cron jobs checked active.
  • resolved SOP hook-table drift fixed. Hermes update SOP now excludes Claude/Anthropic unless BB explicitly asks.
Update Log
  • 509 commits pulled locally, release v2026.6.19.
  • Pre-update: clean repo. Active provider openai-codex / gpt-5.5. Manual snapshot 20260619-215158-pre-update.
  • Backup: ~/.hermes/backups/pre-update-2026-06-19-225453.zip.
  • Update: Python package installed as hermes-agent==0.17.0, web UI built, desktop packaged app rebuilt, CuaDriver upgraded to 0.5.7, gateway restarted.
  • Post-update verified: Hermes v0.17.0, repo clean, Camofox localhost bind intact, profile symlinks intact, gateway loaded and Telegram connected, delegation smoke passed, Context7 MCP lookup passed, Kanban schema scan clean.
  • Provider checks: OpenAI Codex gpt-5.5 returned OK. Kimi kimi-k2.6 returned OK. OpenRouter smoke skipped (per-token, not required by SOP).
  • Excluded: Claude/Anthropic live checks and auth work. BB does not want Claude touched during ordinary Hermes updates.
  • Follow-up fixes done: CuaDriver daemon started and permissions verified. Cron jobs checked active. SOP hook-table drift fixed. Audit logged.
2026-06-14v0.16.0 to v0.16.0, 416 commits 6110aed9b to 4e6d05c6a, 416 commits 416 commits, same version. All checks passed. Three follow-up items all resolved later in the same period. resolved
What Changed

416 commits, same version tag, fast-forward from 6110aed9b to 4e6d05c6a. Pre-update zip backup created.

Impact

Camofox localhost patch intact, 7 profile symlinks intact, gateway service loaded, Telegram connected. Stitch MCP was not configured at this point.

Decisions and Actions
  • resolved Gateway launchd plist: now current.
  • resolved Telegram retry patch: absorbed upstream, no longer a local concern.
  • resolved Orchestrator merge: not needed. Boyd's overlay loads the stock playbook correctly.
Update Log
  • 416 commits, same version tag, fast-forward from 6110aed9b to 4e6d05c6a.
  • Pre-update: clean repo. Pre-update zip backup created at ~/.hermes/backups/pre-update-2026-06-14-202134.zip.
  • Post-update verified: Camofox localhost patch intact, 7 profile symlinks intact, gateway service loaded, Telegram connected.
  • Provider checks: OpenAI Codex, Kimi, delegation, and Context7 passed. Stitch MCP was not configured.
  • Resolved later: gateway launchd plist is now current. Telegram retry patch was absorbed upstream. Orchestrator merge is no longer needed because Boyd's overlay loads the stock playbook.
2026-06-10v0.16.0 to v0.16.0, 530 commits 5af899c7c to 6110aed9b, 530 commits 530 commits, same version. Gateway fell back to background process due to launchd bootstrap exit 5. Telegram reconnected. Drift items found and all resolved by 2026-06-14. resolved
What Changed

530 commits between 5af899c7c and 6110aed9b. Gateway fell back to background process because launchd bootstrap hit exit 5. Telegram reconnected and cron ticker ran.

Impact

Drift discovered: launchd plist stale, Telegram pause patch clobbered, degraded-send-path patch absorbed upstream. All resolved by the 2026-06-14 update session. SOP changed to make Claude smokes opt-in.

Decisions and Actions
  • resolved launchd plist stale: resolved by 2026-06-14.
  • resolved Telegram pause patch clobbered: absorbed upstream, resolved.
  • resolved Degraded-send-path patch: absorbed upstream, resolved.
  • resolved Claude Code CLI smoke and Hermes Anthropic smoke: opted out by SOP change.
Update Log
  • 530 commits between 5af899c7c and 6110aed9b.
  • Pre-update: clean repo. Auth had healthy Keychain and file credentials. Snapshot 20260610-191100-pre-update2 saved.
  • Update: gateway fell back to background process because launchd bootstrap hit exit 5. Telegram reconnected and cron ticker ran.
  • Post-update verified: Camofox localhost patch intact, 7 profile symlinks intact, gateway and Telegram reconnected.
  • Skipped per BB: Claude Code CLI smoke and Hermes Anthropic smoke. SOP changed to make Claude smokes opt-in by default.
  • Drift found: launchd plist stale, Telegram pause patch clobbered, degraded-send-path patch absorbed upstream. All resolved by 2026-06-14.
2026-06-06v0.15.1 to v0.16.0 227 commits Version bump to v0.16.0. Claude OAuth was expired; fixed during the update. All items resolved. resolved
What Changed

227 commits, tag v2026.6.5. Claude OAuth expired, only env-var credential active. Dirty repo had prompt_caching.py and package-lock noise.

Impact

Interactive Claude login ran during update. SOP-001 rewritten to use interactive login path and drop setup-token. Kanban orchestrator drift found but resolved: stock playbook load was correct, no full merge needed.

Decisions and Actions
  • resolved Claude OAuth expired: fixed. Interactive login ran, SOP-001 rewritten to use that path.
  • resolved Kanban orchestrator drift: stock playbook load resolves it. No full merge needed.
  • resolved launchd plist refreshed.
Update Log
  • 227 commits, tag v2026.6.5.
  • Pre-update: Claude OAuth expired, only env-var credential active. Dirty repo had prompt_caching.py and package-lock noise.
  • Auth fix: ran interactive Claude login, mirror, reset. SOP-001 rewritten to use that path and drop setup-token.
  • Update: clean pull after auto-stash. Pre-update zip backup created.
  • Post-update verified: Camofox localhost bind, 7 profile symlinks, gateway plus Telegram, Claude Code CLI smoke, launchd plist refresh.
  • Drift found: kanban orchestrator stock version moved ahead of Boyd's overlay. Later review found the overlay correctly loads the stock playbook, so no full merge was needed.
SOP reference: This report is generated as part of 40-Projects/claude-oauth-safety-guardrails/sops/update-gate.md. The stable URL is https://hermes-vault.pages.dev/briefs/hermes-update/.