v0.3.2

Fixed

• Re-enabling the plugin failed with command "if" is already registered. The /if command was registered directly on the context instead of through ctx.effect, so unloading the plugin left the registration behind in the host's command service and the next activation collided with it. The registration now lives in the plugin fiber and is released on unload.

From 0.3.1

• A failed judgement no longer reaches the main model: the /if entry is dropped, the batch is rejected when nothing else remains, and the failure is logged as an 【/if 未执行】 command card (written after turn/end, so it stays visible) with a 取回 /if button on the right that puts the original input back into the composer.
• The judge can no longer hang forever (real deadline around fork start, result, and transcript streaming; a failed fork falls back to the transcript judge).
• A forked judge no longer inherits the parent's queued next-step work.
• A refused settings write is reported as 未保存 instead of a false 已保存; the client releases its mirror subscription and actually retries loading.