Context Guard 0.17.2

English

Highlights

• Context Guard automatically maintains eligible session records. Without a retention policy, sessions ended more than 30 days can move to a recoverable quarantine. Later ordinary use can permanently delete them after at least seven days there.
• Your explicit retention settings continue to apply. A disabled policy, custom period, quarantine-only setting, or durable opt-out takes precedence. A damaged or unreadable policy does not authorize deletion. A missing policy uses the automatic default, which permits permanent deletion after quarantine.
• You can upgrade context-guard@codex-context-guard from 0.17.1 in place. Finish tasks that still need the old Hook first, or keep them in a separate Codex environment. A 0.17.1 scheduler disable alone did not record a durable opt-out. If you want cleanup to remain off, the upgrade guide explains how to disable it before and after upgrading. Upgrade guide

Full changelog

简体中文

亮点

• Context Guard 会自动维护符合条件的会话记录。没有保留策略时，结束超过 30 天的会话可以进入可恢复隔离区。隔离至少 7 天后，后续普通使用可以触发永久删除。
• 已有的明确设置继续生效，包括已禁用的策略、自定义保留时间、仅隔离设置和持久关闭记录。策略损坏或无法读取时不会授权删除。策略缺失时使用自动默认值，允许隔离期后永久删除。
• 已通过 context-guard@codex-context-guard 安装 0.17.1 的用户可以原地升级。请先完成仍依赖旧 Hook 的任务，或把它们留在单独的 Codex 环境。0.17.1 仅关闭定时任务不会留下持久关闭记录。需要在升级前后保持清理关闭时，请按升级指南操作。升级指南

完整更新日志