Skip to content

v0.12.0

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Oct 04:59
· 3 commits to main since this release
v0.12.0
a56dde6

SysTorch 0.12.0 — 预发布 / Pre-release

把眼前的问题，变成下一步。

Turn questions into next steps.

SysTorch 0.12.0 将规范的 SysTorch 请求入口与可追踪的路由尝试接到「开始」工作面。本版本以 GitHub prerelease 提供，尚未经维护者人工验收。

SysTorch 0.12.0 brings the canonical SysTorch request endpoint and traceable route attempts into the Start workspace. This is a GitHub prerelease and has not been accepted hands-on by the maintainer.

自动化发布门禁已通过。完整 CI 结果、附件哈希、签名核验和 Pages 状态见0.12.0 发布核验。

Automated release gates have passed. See the 0.12.0 release verification for CI results, asset hashes, signing checks, and Pages status.

下载 / Downloads

本次只发布两个附件：

Exactly two assets are published:

Windows EXE 暂无 Authenticode 签名，Windows 可能提示发布者未知。Android 显示名称为 SysTorch，applicationId 与稳定签名保持不变，供已安装版本覆盖升级；如果 Android 报签名不一致，请停止安装，不要先卸载旧版。

The Windows EXE is not Authenticode-signed, so Windows may show an unknown publisher warning. Android displays SysTorch and keeps the existing applicationId and signing key for in-place upgrades. If Android reports a signature mismatch, stop and do not uninstall the existing app first.

本版内容 / What's included

  • 新增 canonical POST /v1/systorch/systemone，接受 SysTorch 请求超集并验证问题顺序；TypeSafe-compatible 部分仍按原格式送往上游，旧 /v1/systemone 保持兼容。

  • 「开始」成功回复可展开查看路由轨迹及真实 provider attempts；失败回复按 request ID 延迟读取调用历史，展示失败状态与后续路由策略。

  • 中英文 README、图册、发布说明与 GitHub About 统一使用 SysTorch 品牌和口号。

  • 既有 DAG、边级辉光、provider lifecycle、普通加密会话、人工作答和 Android daemon 身份继续保留。

  • Adds canonical POST /v1/systorch/systemone, validates question order, and projects the TypeSafe-compatible core to upstreams. The legacy /v1/systemone endpoint remains compatible.

  • Successful Start replies can reveal their route trace and actual provider attempts. Failed replies load existing call history by request ID and show failure status and retry path.

  • The Chinese and English READMEs, gallery, release notes, and GitHub About use the SysTorch brand and slogan.

  • Existing DAG routing, edge glow, provider lifecycle, encrypted chats, human decisions, and Android daemon identity remain in place.

用户叙事与对照场景 / User story and comparison

一个调用方提交结构化决策问题后，第一家上游可能因额度、网络或服务状态失败；DAG 按既有策略尝试下一家。成功时，「开始」把成功决策显示为主回复，并在路由轨迹中按需呈现前面的失败与最后的成功；完全失败时，用户可展开失败回复，用同一 request ID 对应到调用历史。这样能从“只有一个 HTTP 错误”进一步看清“请求经过哪些真实尝试”，同时保留单个入口父请求与多个上游 attempt 的关系。

After a caller submits a structured decision, the first upstream may fail because of quota, network, or service availability. The DAG then follows its existing policy and tries the next provider. On success, Start presents the decision as the main reply and reveals earlier failures and the successful attempt on demand. If all attempts fail, the failure reply can load call history with the same request ID. This turns a single HTTP error into an inspectable sequence while preserving one parent request and its upstream attempts.

路由轨迹是可追踪的操作元数据，不包含问题正文、回答、密钥或上游原始响应。此 Release 的 CI 与合成测试不等于维护者在 Windows 与 Android 真机上完成验收；真实上游能力还取决于使用者当前的凭据、路由和服务状态。

Route traces are operational metadata; they do not include question text, answers, credentials, or raw upstream responses. CI and synthetic tests do not equal maintainer acceptance on Windows or a physical Android device. Real upstream capability still depends on the user’s credentials, route configuration, and service availability.

Assets 4
Loading