Project Lead v0.3.2

Adds a visible controller closure receipt in the original executor task after independent acceptance. The receipt identifies the accepted task and states that it is complete and waiting for the next instruction. It is not new work, requires no reply, is deduplicated by task plus accepted candidate, and is never sent for an unaccepted result.

Project Lead v0.3.1

Fixes the approval relay when a controller can see waitingOnApproval but cannot read the approval card itself. The controller now tells the user that the card details are unavailable, never guesses the command or risk from task context, and never sends a clarification message to an executor frozen by the card. This release also synchronizes completion-relay rules that were already present in the installed skill.

Project Lead v0.3.0

Adds immediate controller-to-user relay for executor approval requests, confirmations, and required input. Tracks blocked_on_user state, deduplicates repeated notices, re-surfaces unresolved requests after controller resume, and never approves on the user's behalf.

Project Lead v0.2.0

Project Lead v0.2.0 adds bounded recovery for tasks that stop producing substantive progress, without introducing background polling.

Highlights

• After 30 silent minutes, take one fresh read-only snapshot and use one status-only gpt-5.6-luna follow-up only when the state remains unclear.
• Never repeat the Luna fallback in the same silent period; rearm it only after substantive progress.
• Never create heartbeat, cron, recurring automation, timer loops, or periodic polling.
• Keep a single owner for overlapping scope or the same checkout, including silent or abnormal nonterminal tasks.
• Require a terminated original task and complete handoff evidence before transferring ownership.
• Add sanitized Yuji and Shengxue Youpin use cases.
• Add auditable RED to GREEN behavior evidence, contribution guidance, and GitHub Issue templates.

See CHANGELOG.md for the complete release notes.