v3.9.0 — Operations and Reliability

V3.9.0 — Operations and Reliability

Released on 2026-07-11. The annotated v3.9.0 tag triggers the release-assets workflow; assets are published by that workflow.

V3.9.0 establishes an operations and reliability foundation for the sidecar-only plugin. It adds focused recovery controls and diagnostics without changing the normal streaming-card layout or footer.

Highlights

• Feishu/Lark operations cards can show diagnosis, recheck, two-step 安全修复 (safe repair), and Gateway restart confirmation. When operations cards are unavailable, use the existing CLI commands; normal card delivery remains fail-open.
• Ownership is explicit: private operations do not compare operators, while group repair/restart confirmation remains with the initiating operator. The stateful command transport uses a zero-configuration secret in the private sidecar state-directory transport root, rather than configuration or environment variables.
• Profile-aware setup resolves --profile-id / --event-url before process environment, then the selected env file, then defaults. Only doctor shows the complete redacted identity/profile/event-endpoint route chain; status summarizes runtime routing and profile events, while /health reports actual routing health fields.
• Known-safe install evidence may be automatically repaired during install/setup; --no-repair opts out. Unverifiable user edits remain refused. Lifecycle cleanup keeps runtime state and cleanup history bounded.
• Operations-card WebSocket clicks ACK Feishu immediately and enter a bounded background dispatcher with retry. The sidecar PATCHes every authenticated transition to the original card without making recheck/repair/restart wait for the Feishu update call.
• Hermes compatibility and existing-container Docker install paths remain supported by automated coverage. Existing-container Docker smoke is still pending acceptance.

Contribution

PR #84 by @Zanetach contributed card progress-status routing and .env allowlist expansion for profile environment support.

Validation

• Automated release gate: 1172 passed, 3 skipped on Python 3.9 and Python 3.12. Operations semaphore/publish-lock state is initialized only inside the active event loop, preserving the declared Python 3.9 support.
• Real Feishu private-chat acceptance passed on 2026-07-11: /hfc doctor without a gray native unknown-command reply; localized details and two consecutive rechecks, including the background successor, ACKed in 156–201 ms without a callback-timeout toast and PATCHed the same card; sandboxed two-step safe repair, card-triggered Gateway restart, and the normal streaming-card footer also passed.
• Real Feishu cron acceptance passed on 2026-07-11: a no-agent one-shot result produced the expected completed card with successful sidecar receive/apply/send metrics and no native fallback. Hermes upstream can still mislabel the same successful finite one-shot as Ran now: failed after auto-deleting its job record; this is an upstream CLI status bug, not a card-delivery failure.
• Profile mismatch acceptance passed on 2026-07-11: a temporary unknown profile produced only a redacted profile_unknown route chain, and normal routing recovered after the temporary environment was removed without changing persistent config.
• Pending real Feishu acceptance: group initiator repair/restart, changed-operator rejection, and topic. These are not claimed as verified here.
• Pending existing-container Docker smoke: fresh install, pinned upgrade, known-safe corrupt-marker auto-repair, refusal of user edits, main/child profile endpoint mapping, and final doctor.

Release Assets

The release-assets workflow publishes four assets for the v3.9.0 tag:

• hermes-feishu-card-v3.9.0-macos.tar.gz
• hermes-feishu-card-v3.9.0-linux.tar.gz
• hermes-feishu-card-v3.9.0-windows.zip
• hermes-feishu-card-v3.9.0-checksums.txt