v0.2.135

Improvements

• Finished, unresolved result-required jobs can now be explicitly abandoned from their task details, with confirmation. Their exit status, review and logs are preserved, and abandonment is recorded separately from successful verification.
• Abandoning a job removes it from outstanding work and skips an end callback that has not yet been taken up. It does not interrupt an agent turn already in progress.
• Newly reviewed incomplete job results receive one follow-up step: continue safe in-scope diagnosis or repair, or clearly explain the blocker and the decision needed. Historical failures do not repeatedly restart on unrelated messages, and person-stopped work is not restarted automatically.

Fixes

• Opening a sub-agent or switching away from its parent conversation closes the agent menu, preventing a floating menu from remaining after its anchor is hidden.
• Very short jobs that finish before their startup status is read return their saved exact-run result instead of failing the start call.
• Exact-run checks prevent stale task controls from affecting a replacement job. Concurrent reconciliation cannot overwrite a person's abandonment decision.

Includes desktop/mobile UI, API, callback, stopped-work, replacement and concurrency regressions. Abandonment is not a claim that failed verification succeeded.