Prism Vesicle v1.0.0-rc.1

Release candidate channel and known limits / RC 频道与已知限制

1.0.0-rc.1 is a release candidate published to npm's next dist-tag. The latest dist-tag intentionally keeps tracking the newest beta, so npm install -g prism-vesicle continues to install the beta line; install the candidate explicitly with npm install -g prism-vesicle@next or by pinning 1.0.0-rc.1. Release candidates are stabilization builds for early testing and may still change before the stable release.

1.0.0-rc.1 是发布候选 (RC),发布到 npm 的 next dist-tag。latest dist-tag 会有意继续跟随最新 Beta,因此 npm install -g prism-vesicle 仍会安装 Beta 线;请使用 npm install -g prism-vesicle@next 或固定 1.0.0-rc.1 来显式安装候选版本。发布候选是面向早期测试的稳定化构建,在稳定版发布前仍可能调整。

Provider-native search is explicit and provider-scoped: /websearch on sends queries to the selected provider without a per-call tool approval, and is admitted only for configured Gemini generateContent, OpenAI Responses openai-public, and deepseek-subset-2026-08-19 models with capabilities.builtinWebSearch. Citations are optional provider behavior. Existing deepseek-subset-2026-07-31 configurations are not migrated automatically and remain search-disabled until changed deliberately. The applicable OpenAI, DeepSeek, Gemini, and Tavily dogfood evidence is dated 2026-08-20; opt-in real-endpoint suites report missing prerequisites as unavailable, never passed.

供应商原生搜索必须显式开启且受供应商范围限制:/websearch on 会将查询发送到当前供应商,不会逐次弹出工具批准;仅在模型声明 capabilities.builtinWebSearch 且使用已支持的 Gemini generateContent、OpenAI Responses openai-public 或 deepseek-subset-2026-08-19 时可用。引用由供应商选择是否返回。现有 deepseek-subset-2026-07-31 配置不会自动迁移,必须主动修改后才能使用搜索。适用的 OpenAI、DeepSeek、Gemini 与 Tavily dogfood 证据日期为 2026-08-20;可选真实端点测试在前置条件缺失时记为不可用,不计为通过。

MCP resource, audio, URL/link, and unknown result kinds remain deferred: Vesicle omits them without auto-fetch or prompt injection. See STATUS.md and Issue #177 for the current boundary.

MCP resource、audio、URL/link 与未知结果类型仍处于延后状态:Vesicle 会忽略它们,不自动抓取,也不注入提示。当前边界见 STATUS.md 与 Issue #177。

Windows code-signing status / Windows 代码签名状态

The Windows executable and installer in 1.0.0-rc.1 are not Authenticode-signed. Windows signing is deferred until the project has a stronger basis for a signing provider, with no version deadline. Download only from this official GitHub Release and verify the file against SHA256SUMS.txt. Do not disable Windows security features globally.

1.0.0-rc.1 中的 Windows 可执行文件和安装器没有 Authenticode 签名。Windows 签名推迟到项目具备引入签名服务的条件后再考虑，不设版本截止期限。请只从本 GitHub Release 官方页面下载，并使用 SHA256SUMS.txt 核对文件；不要在系统范围内关闭 Windows 安全功能。

See the Code Signing Policy / 参见代码签名政策。

What's Changed

• chore(release): forward-sync v1.0.0-beta.2 to develop by @3aKHP in #247
• test(support): skip host-incapable fixtures by capability probe by @3aKHP in #248
• fix(skills): harden SQLite index lock contention by @3aKHP in #249
• fix(runtime): stabilize Windows contracts and tests by @3aKHP in #250
• fix(skills): unify SQLite mutex release semantics by @3aKHP in #253
• feat(windows): add branded distribution resources by @3aKHP in #255
• feat(tui): mirror session titles to terminal tabs by @3aKHP in #256
• fix(session): harden title generation lifecycle by @3aKHP in #257
• fix(tui): complete built-in command arguments by @3aKHP in #258
• fix(session): stabilize title generation ownership by @3aKHP in #259
• feat(harness): adopt public 10.3.3 pack by @3aKHP in #260
• feat(tui): implement Terminal Title B Lane by @3aKHP in #261
• fix(release): stabilize Windows dogfood runtime by @3aKHP in #262
• release: v1.0.0-rc.1 by @3aKHP in #264

Full Changelog: v1.0.0-beta.2...v1.0.0-rc.1