v5.0.22：Hermes v0.23.1 精确兼容

修复范围

• #520 stable 兼容：新增官方 Hermes v0.23.1 3b421578588243f920886e6fe79a6faa87ea026e 的独立来源集合。31 个 admission/topology 文件、107 个 writer 文件及 4 个 launch 文件按完整字节校验；运行态继续检查真实加载的函数、defaults、contextmanager、settlement 与 producer 绑定。保留 v0.23.0 当前和历史受管渲染集合，混合或未知来源仍拒绝。
• 安装与配置：pm-0231 使用上游真实 schema 53，早期 family 保持 schema 52；把新增 writer/launch 依赖纳入隔离子进程来源检查。不手改版本戳，也不自动替用户执行未知配置迁移。请先完成 Hermes 官方升级和配置迁移。
• slash-confirm 锚点：以精确 AST 定位旧四位置参数调用，或已审查的 requester-authority 调用，完整保留上游调用与权限表达式。错误参数、未知关键字、解包与歧义匹配仍拒绝。只修复这个锚点不构成未知 main cohort 的兼容证明。
• CI 与依赖：合入 #516 Ruff 0.17.4、#517 CodeQL v4.39.3 原始维护提交；固定上游矩阵显式执行 v0.23.1 三组测试，并加入官方镜像 preserved/cleared 验收。#510 的 latest_stable 明确为历史 v0.22.4 固定基线，既有覆盖保留。
• 超时诊断：pytest worker 原子替换一个 .progress 文件，记录当前 node、顺序与耗时；该文件不算完成证据。最终报告的精确 commit、完整并集与每例一次门禁保留。旧 #516 超时日志未能定位精确卡点，本版不宣称已修复其根因或达到耗时目标。

验收与限制

发布需分别通过独立普通 wheel/真实子进程安装、修复、重复安装与逐字恢复，完整 PR/main/tag 矩阵、官方镜像、发行包校验和实际解压，以及公开 tag 安装。精确 SHA、CI 链接和实测结果在正式 GitHub Release 中登记；候选阶段不提前记为通过。

本版不改卡片布局或默认设置，不加入 #521 本地 repin。#497 报告者 Windows 原机的 source_digest 拒绝仍未独立复现。真实 Hermes Gateway/model 回合、飞书客户端点击与桌面/Android/iOS 视觉未由本轮自动化替代。

安装包保持三平台独立顶层目录：解压后进入 hermes-feishu-card-v5.0.22-<platform>/ 再运行安装器。保留既有保护记录、备份及已发表 tag/资产；不要手改 Hermes 源码或删除保护文件绕过检查。

贡献记录

感谢 Lite-G 在 #520 提供 main 锚点证据，ywarmy 提供 v0.23.1 stable 字节、安装与运行分析。Dependabot 提供 #516 和 #517；原始提交、作者和历史署名保留，问题证据与代码作者分开记录。

v5.0.22: exact Hermes v0.23.1 compatibility

Changes

• #520 stable compatibility: add a separate source cohort for official Hermes v0.23.1 3b421578588243f920886e6fe79a6faa87ea026e. Verify whole-file bytes for 31 admission/topology, 107 writer and 4 launch sources. Retain loaded-function/default/contextmanager, settlement and producer identity checks, and both current and historical owned v0.23.0 render sets. Mixed and unknown sources remain refused.
• Installation/configuration: bind pm-0231 to upstream schema 53 while earlier families retain schema 52. Include the new writer/launch dependencies in isolated-child source checks. Complete the normal Hermes upgrade/configuration migration first; do not edit the version stamp or bypass protection records.
• Slash-confirm anchor: match only the exact historical four-positional-argument AST or reviewed requester-authority form. Preserve the original upstream call and authority expression. Reject changed arguments, unknown keywords, unpacking and ambiguous matches. Fixing this anchor alone does not establish compatibility with an unknown main cohort.
• CI/dependencies: retain the original #516 Ruff 0.17.4 and #517 CodeQL v4.39.3 maintenance commits. Explicitly run the three v0.23.1 source suites in the pinned matrix and add preserved/cleared official-image acceptance. Clarify that #510's latest_stable is the fixed historical v0.22.4 baseline; preserve earlier coverage.
• Timeout diagnostics: atomically replace one bounded .progress file with the running node, ordinal and elapsed time. It is not completion evidence. Exact-commit, complete-union and once-only final-report gates remain unchanged. The old #516 logs do not identify the precise stuck stage; no root-cause or timing-target claim is made.

Acceptance and limits

Publication requires independent ordinary-wheel/real-child install, repair, repeat and byte-exact restore, full PR/main/tag matrices, official images, archive/checksum/actual extraction checks and public-tag installation. Exact SHAs, CI links and measured outcomes are recorded in the published GitHub Release; pending candidate gates are not marked passed.

No card-layout/default change or #521 local repin. The original #497 Windows-host source_digest refusal remains independently unconfirmed. Actual Hermes Gateway/model turns, client clicks and desktop/Android/iOS visual acceptance are separate from this automated evidence.

Archives retain a single platform-specific top-level directory: enter hermes-feishu-card-v5.0.22-<platform>/ before running an installer. Keep existing protection records, backups and published tags/assets. Never edit Hermes source or delete protection files to bypass checks.

Credits

Thanks to Lite-G for main-anchor evidence in #520, and ywarmy for v0.23.1 stable source, installation and runtime analysis. Dependabot supplied #516 and #517. Original commits, authors and historical credits are retained; issue evidence is separate from code authorship.

本版实际验收记录 / Verified release evidence

• Commit: 0b5a53e0d1d873ee552ca030b05125b443fc0b38; annotated tag v5.0.22 (object 600cac70d869dd17693a80546681696c69d97f13).
• PR complete CI, exact-main complete CI, exact-main CodeQL, immutable-tag release gate: passed. Python 3.9–3.14, macOS/Windows, pinned upstream contracts and preserved/cleared official v0.23.1 images retain their coverage.
• Independent ordinary-wheel/real-child install → repair → repeat install → doctor → restore passed after the real upstream migration to config schema 53. Source/config bytes restored exactly. The 4 normal writer selections and 3 failure-injection cases passed. These use controlled PM test tooling; they are separate from actual Gateway/model execution.
• Public Git-tag non-editable installation: VCS commit equals the tested merge; all 162 package resources match the independently tested wheel. No checkout/editable import or test injection remains in that runtime.
• All four release assets passed checksums and complete manifests. Archives retain a single version/platform top-level directory, normalized ownership/modes and no links or path escapes. Actual macOS BSD tar extraction in private 0700/1777 destinations preserved the destination inode/owner/mode and sentinel, with exact bytes and executable modes. Linux GNU tar root/non-root extraction is covered by the linked release gate.
• 未在本轮验证：报告者原 Windows 主机的 source_digest 拒绝、真实 Hermes Gateway/model 回合，以及桌面/Android/iOS 的实际点击与视觉。未知 upstream main 的完整兼容不在本版承诺范围。 / Unverified this round: the original Windows-host refusal, actual Gateway/model turns and client clicks/visuals; unknown upstream main builds remain unsupported without exact source proof.