Looper v2.14.176

Looper v2.14.176

This is the patch release v2.14.176, a hotfix line in which each merged change ships at once. It documents one change: #1326 (two maintainer decisions recorded in the plan; docs only).

Release Decision

Who should upgrade: No one needs to upgrade for this release. It changes a plan document only; the installed software behaves as in v2.14.175.

What this release solves: #1326 records two maintainer decisions in the long-horizon plan. It does not change code.

Breaking changes: No. There is no API, schema or behavior change. The bridge boundary is unchanged: upgrade to v2.13.165 first if the installation is older.

How to verify: Check the installed version.

looper --version   # looper 2.14.176

Contributors: Maintainer @foolzzz authored #1326; no community contribution was included in this release.

Upgrading

The bridge boundary is unchanged: an installation older than v2.13.165 must upgrade to v2.13.165 first (upgrade to v2.13.165 first) and be started once; see the Upgrading section of the v2.14.0 release for the steps and rollback. An installation on v2.14.0 to v2.14.175 upgrades directly. There is no database change.

Behavior changes

Read in the diff of #1326, which touches one file, the Chinese long-horizon plan (docs/plans/2026-10-13-long-horizon-agent-context.zh-CN.md):

• No behavior change. Only plan text changed.
• Plan entry: request recording for more runtimes. A new non-core todo for the Codex, OMP, Pi and DSH runtimes (CLI and runner), which are not covered by model request recording and show not_covered today. Recording them needs a local gateway or request proxy per runtime. The maintainer decided on 2026-11-12 to list it as a non-core todo, moved from #1144.
• Plan entry: keeper default-on. The todo now also closes #1067 and names its checks before the default turns on: keeper runs surviving a restart under Linux systemd, and a real PostgreSQL cluster restart, run at least once on Linux systemd. The default stays off until then.
• Model-visible changes: None. Prompts, tool schemas and channel_context are unchanged.

Optional Capability Activation & Use

No new optional capability activation is introduced in this release.

Validation

Reported by the pull request: #1326 reports plan text only and that the two entries were read back. It does not report a local full suite or reviews.

CI: CI runs after the release is drafted; its result is not recorded here.

Not tested for this draft: a local full suite and the built wheel. The release documentation gate checks the body only.

中文摘要

本版本是 patch release v2.14.176（热修线，每个合并的改动立即发布），说明一项改动：#1326（在计划中记录两项维护者决定，仅文档）。

升级决策

**谁需要升级：**无需为本版本升级。它只改动一份计划文档，已安装的软件行为与 v2.14.175 相同。

解决了什么：#1326 在长程计划中记录两项维护者决定，不改动代码。

**是否有破坏性变更：**无。没有 API、schema 或行为变化。桥接边界不变：早于 v2.13.165 的安装须先升级到 v2.13.165。

**如何验证：**核对版本为 2.14.176。

**贡献者：**维护者 @foolzzz 提交 #1326；本版本无社区贡献。

looper --version   # looper 2.14.176

升级

桥接边界不变：早于 v2.13.165 的安装必须先升级到 v2.13.165 并启动一次（upgrade to v2.13.165 first 即先升级到 v2.13.165），步骤与回退见 v2.14.0 发布说明的升级一节。v2.14.0 至 v2.14.175 上的安装可直接升级。没有数据库变更。

行为变化与入口

以下在 #1326 的差异中可见，它只改动一个文件，即中文长程计划（docs/plans/2026-10-13-long-horizon-agent-context.zh-CN.md）：

• **无行为变化。**只有计划文本改变。
• **计划条目：更多运行时的请求录制。**为 Codex、OMP、Pi、DSH 运行时（CLI 和 runner）新增非核心待办；它们目前不在模型请求录制范围内，界面显示 not_covered。要录制需为各自接上本地网关或请求代理。维护者于 2026-11-12 决定将其列为非核心待办，原记在 #1144。
• **计划条目：保留运行默认开启。**该待办现在同时关闭 #1067，并列出默认开启前的检查：Linux systemd 下重启后保留运行存活，以及真实 PostgreSQL 集群重启，至少在 Linux systemd 上真跑一次。在此之前默认保持 off。
• **面向模型的变化：**无。提示词、工具 schema 和 channel_context 均未改变。

可选能力启用与使用

本版本未新增可选能力启用入口。

验证

PR 报告的：#1326 报告仅为计划文本，并读回了两个条目。未报告本地完整套件或评审。

**CI：**发布草稿后 CI 会运行，其结果未在此记录。

**本次草稿未测试：**本地完整套件和构建出的 wheel。发布文档 gate 只检查正文。