low-frequency-thread-monitorlisted

# 低频巡检 Skill ## Purpose Monitor a background Codex thread with minimal reads, no interruption, and low wasted waiting time. This skill is monitoring only. It does not authorize writes, approvals, closure, gate unblocks, active promotion, or PROJECT_B consume/display changes. Use it for ordinary non-Goal controller windows that still need to keep background work moving. It complements Goal mode; it does not replace durable Goal workflows. ## Auto Trigger When a controller reads, checks, or inspects another Codex conversation thread/window, treat that action as a monitoring cycle and apply this skill even if the Owner did not repeat the skill name. Trigger hints include: "已读取对话线程", "读取对话线程", `read_thread`, `list_threads`, "read/check worker thread", or "check background window". ## State Model Keep these states separate: - Foreground monitor state: the controller is active, waiting, checking, absorbing, blocked, or done. - Background worker state: the worker is running, finalizing, completed, failed, blocked, or asking Owner. - Governance state: self-report, review, absorption, approval, and routing are separate steps. Pending next check means the monitor is still active, even if no foreground text is being generated. ## Hard Rules 1. If the target thread is still running and a next check is scheduled, the monitor is still active. Do not send a final answer that closes, archives, marks complete, abandons, or replaces the monitoring window. 2. Use a wakeup, automati