fix(runtime_provision): use team-template risk_profile, not hardcoded toolfree

The provisioner was hardcoding risk_profile=toolfree for every claw,
which the ZeroClaw config explicitly configures to EXCLUDE every
usable tool (shell, file_read, file_write, http_request, browser).
Result: coder/tester/committer claws had zero tools and produced text
in the context window with no ability to actually write files or run
tests — exactly what the last mission summary showed.

Fixes:
- provision_claw now takes risk_profile: &str, passed through from
  the team template (development teams already had coding_readwrite,
  which now actually gets applied).
- Research team templates updated from toolfree → research_readonly
  (file_read) and papers_research → research_web_readonly
  (file_read + web_search + web_fetch). Applied to both the on-disk
  TOML files and the live DB rows.
- Added RuntimeProvisioner::default_risk_profile_for_role for
  auto-provision code paths that lack a template context — picks
  coding_readwrite for coder-like roles, research_readonly otherwise.
- Split rebind_model out of provision_claw so the model-change UI
  path doesnt inadvertently clobber the existing risk_profile.

Templates DB fixup for missions launched pre-deploy is already
applied via manual UPDATE.

templates/teams/insight_research.toml

@@ -4,7 +4,7 @@ description      = "Bidirectional research↔project loop: do any of the papers
 stack            = ["research", "novelty", "publication", "obsidian", "citation-analysis"]
 category         = "research"
 default_topology = "pipeline"
-risk_profile     = "toolfree"
+risk_profile     = "research_readonly"
 mcp_bundles      = ["clawmates_door", "clawmates_skills", "web_fetch"]
 version          = 1