The V3.1 parser had the same issue — .*? without re.DOTALL fails to
match multi-line JSON arguments. Found during review of PR #444.

…k V3 tool call parser

Authored by PercyDikec. Fixes NousResearch#443. Without re.DOTALL, the regex .*
doesn't match newlines, so multi-line JSON arguments (the normal case)
silently fail to parse. Every other parser in the codebase that matches
across lines already uses re.DOTALL.

The V3.1 parser had the same issue — .*? without re.DOTALL fails to
match multi-line JSON arguments. Found during review of PR NousResearch#444.

…k V3 tool call parser

Authored by PercyDikec. Fixes NousResearch#443. Without re.DOTALL, the regex .*
doesn't match newlines, so multi-line JSON arguments (the normal case)
silently fail to parse. Every other parser in the codebase that matches
across lines already uses re.DOTALL.

The V3.1 parser had the same issue — .*? without re.DOTALL fails to
match multi-line JSON arguments. Found during review of PR NousResearch#444.

…k V3 tool call parser

Authored by PercyDikec. Fixes NousResearch#443. Without re.DOTALL, the regex .*
doesn't match newlines, so multi-line JSON arguments (the normal case)
silently fail to parse. Every other parser in the codebase that matches
across lines already uses re.DOTALL.

The V3.1 parser had the same issue — .*? without re.DOTALL fails to
match multi-line JSON arguments. Found during review of PR NousResearch#444.

…lti-tenant cockpit chrome + wizard resume (#207)

Deliverable A — tenant-picker cockpit chrome:
  * /api/tenants/list BE endpoint (wraps list_cost_holder_tenants;
    always default-first, synthesizes default when registry is
    named-only)
  * useActiveTenant() hook with URL ?tenant= → localStorage →
    "default" resolution; cross-tab + in-tab event-driven re-render
  * TenantPicker dropdown in sidebar header chrome; renders nothing
    when <2 tenants observed (A.6 single-tenant degradation)
  * /api/cost-state extended with optional ?tenant_id= → per-tenant
    holder lookup; CostStatePage + DashboardPage CostCardBody read
    snap.cost_ladder_by_tenant[activeTenant] when non-default
  * Audit + promotion pages forward ?tenant_id= (Probe + Alert
    Investigations, Email Intent + Outbound + Autofix logs, Kora
    Actions, PromotionReviewPage); BE-side filter lands with CC#1
    NousResearch#444 — FE wires the param + graceful fallback today
  * Drift-guard pins: TENANT_ID_QUERY_PARAM_NAME (BE) ↔
    TENANT_ID_QUERY_PARAM (FE) cross-stack test in
    tests/test_tenants_endpoint.py + storage-key + default-id pins

Deliverable B — wizard sessionStorage resume:
  * sessionStorage["kora_wizard_state"] persists step + non-cred
    config on every change
  * On mount past step 0, render Resume? prompt (yes restores +
    jumps to saved step; no clears + fresh start)
  * Credentials NEVER stored (anthropicApiKey,
    substrateServiceRoleKey, slackBotToken stripped before
    persist); validation results also reset on resume so the
    operator re-validates re-entered creds
  * Cleared on wizard complete + skip (terminal states)

Note: PM bucket attributed cost_ladder consumption to
CostTelemetryPage; in HEAD the cost_ladder block is consumed by
DashboardPage CostCardBody + CostStatePage (CostTelemetryPage
reads per-route /api/cost_telemetry, not per-tenant cost_ladder).
A.4 applied to the actual cost_ladder consumers.

Co-authored-by: CC#2 Kora Web <kora-pm@stormhavenenterprises.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…k V3 tool call parser

Authored by PercyDikec. Fixes NousResearch#443. Without re.DOTALL, the regex .*
doesn't match newlines, so multi-line JSON arguments (the normal case)
silently fail to parse. Every other parser in the codebase that matches
across lines already uses re.DOTALL.

The V3.1 parser had the same issue — .*? without re.DOTALL fails to
match multi-line JSON arguments. Found during review of PR NousResearch#444.