mirror of
https://github.com/NanmiCoder/claude-code-haha.git
synced 2026-10-10 03:43:11 +08:00
程序员阿江-Relakkes
8ddf67390d
An approved team handed every member its instructions at the same moment, so members whose tasks depended on unfinished work started anyway: the second and third layers of a plan ran before the first, a member could mark a blocked task in progress, and results only ever went to the lead. The official CLI states dependencies in tool prompts and nothing more, so the plan the user approved was not what ran. - A member whose tasks all wait on other tasks gets its instructions only once one of them is ready. What the lead or a teammate sends it before that waits in its inbox and arrives with the instructions; only the user writing to it, or a shutdown request, reaches it earlier. This survives a Stop and a server restart. - TaskUpdate refuses a teammate that starts or completes a task while a task it is blocked by is unfinished. The lead is not held to it. - Each member is told who waits on its tasks and to send them its result before completing, so a dependent member starts with that result in hand. A member that starts without one is told whose is missing. - A member that exits after approving a shutdown request is no longer recorded as failed, and the lead gets no failure notice for it. The shutdown-approval schema keeps leaving out the desktop backend on purpose, now documented and tested. - TeamPlan tells the lead that a dependent member's prompt is delivered when its dependencies are done.