v2.0.5 — a go-ahead no longer closes edits

SETTLE gate: judged with the conversation, not the message alone.

Up to v2.0.4 the gate asked whether each message literally fixed the result. A short go-ahead ("진행해줘", "go ahead") after a working turn never does, so edits closed in the middle of agreed work.

The gate now gives Jev the user's message and the agent's last message and asks one question: to carry this out, must the agent choose something the user will see or rely on that nothing has settled yet? Continuing, approving or correcting the plan, fixing a reported problem, running, testing, deploying and standing procedures keep edits open; open-ended new work asks first.

Author's messages, fresh sample of 100 (threshold chosen on a separate 100)	Wrongly closed	Wrongly opened
v2.0.4 rule, after a working turn	42 of 42	0 of 5
v2.0.5 rule	1 of 42	0 of 5

• Optional: ~/.config/lean-forge/profile.txt, a short private note on how you instruct agents, is sent to Jev with each judgment. Keep it out of any repository.
• Without Jev, a message after an asking turn counts as its answer, and the one-line reason path stays for mechanical work.
• Threshold 0.8, set on one person's messages; tune it on your own traffic.

Same change as lean-forge-55 v0.2.0, without its shell layer.