WobbleBot 2.0.11

WobbleBot 2.0.11 packages the final stabilization fixes for the 2.0.x closeout.

• Read-only health queries now drain failed SQLite connections before the event loop can close. Three deterministic regression cases cover the paths missed by the earlier storage-adapter repair.
• Counter-order exposure checks use the proposed order's actual notional, including partial fills and restart recovery.
• Advisor roles can use two explicit fallback targets, with persisted attempt history, shared spend caps and a final heuristic when all configured cloud routes fail.
• Native Ollama Cloud is available as a distinct provider using OLLAMA_API_KEY. Provider support is separate from model qualification; no Ollama candidate is selected in the current NAS configuration.
• Settings are grouped by purpose and ownership. Maintenance archives use unique export names so retries preserve existing exports.

Keep the operator's current settings and prompts. The generic example is a template, not a replacement for the configured NAS routes. This release widens the LLM ledger's provider constraint; tagged 2.0.9 cannot read new Ollama Cloud rows. Retain compatible source-pinned rollback images and verified backups. See the upgrade and acceptance runbook.

Validation: Windows Python 3.13.14 passed 4,229 tests. The packaged Linux Python 3.14.7 candidate passed 4,223 tests with six absent-private-file skips, plus 10 offline integration tests. Formatting, lint, type checks and mandatory upgrade gates passed. Publication CI is separately linked to this tag.

This release supersedes the unpublished v2.0.10 candidate. Its tag test failure exposed the reader race and blocked publication; that tag remains intact. No 2.0.10 NAS deployment occurred.

Release publication does not close the phase. NAS deployment and the authorized eight-hour observation campaign have separate receipts in the roadmap; formal acceptance and 2.1 development remain gated.