owui-mcp-spawner V. 0.1.0

• Renamed to owui-mcp-spawner (formerly "MCP Framework" / "MCP Manager") — the focus is spawning OpenWebUI tools as isolated MCP servers. Environment variable names (MCP_MANAGER_PASSWORD, …) are unchanged for compatibility.
• Per-instance virtual environments — every instance runs in its own venv under runtime/venvs//; dependencies are fully isolated and never pollute the spawner. Created on demand with base packages; validation, installs and runtime all use the instance venv. New app/venv_manager.py, MCPConfig.venv field, and a one-time migration of existing instances on first start.
• Dependencies actually install from requirements: — the docstring requirements: line is parsed and installed before validation, so tools importing numpy/pandas/yfinance/… upload in one go (previously rejected with ModuleNotFoundError).
• One-step create_tool — POST /api/tools/create and the editor's Install as MCP create an instance from raw Python in a single step (install → validate in venv → fill Valve values → save); no more placeholder + export + upload dance.
• Valve values sync on code save — saving edited code merges new Valve defaults into the editable config (keeps user-set values, drops removed valves), so valves stay editable in the UI after a code change.
• Safe delete — deleting an instance no longer removes a tool file still referenced by another instance (reference-counted); MCP-config uploads copy into an instance-owned file instead of sharing.
• Venv management UI — dashboard Venv column, venv dropdowns in the upload/editor/edit dialogs, and a Settings section to create/delete venvs (in-use protection, default protected).
• Port choice at install — optional fixed port on upload / create_tool; a clash returns 409 instead of being silently reassigned.
• Control tool v0.0.4+ — new tools: create_tool, update_instance_values, update_instance_dependencies, update_instance_venv (value changes report a hint to ask before restarting).