Skip to content

AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).

Tidy docstring line breaks in the usage-source lists

Rufus0d44dca7f9dd
diff --git a/packages/core/openexecutive/api/routes/audit.py b/packages/core/openexecutive/api/routes/audit.py
index 87a334fb..0be13aa9 100644
--- a/packages/core/openexecutive/api/routes/audit.py
+++ b/packages/core/openexecutive/api/routes/audit.py
@@ -137,8 +137,7 @@ class UsageBySource(UsageTotals):
`specialist` chat-turn consults, `specialist_workflow` steps,
`specialist_research`, `research_synthesis`, `research_watchlist`,
`triage`, `memory_extractor`, `agent_test`, … — so a heavy day can be
- traced to the
- part of the system that produced it."""
+ traced to the part of the system that produced it."""
source: str
diff --git a/packages/core/openexecutive/audit/usage.py b/packages/core/openexecutive/audit/usage.py
index 160549be..5243ad36 100644
--- a/packages/core/openexecutive/audit/usage.py
+++ b/packages/core/openexecutive/audit/usage.py
@@ -14,8 +14,8 @@ The ``actor`` column names the source of the call (``executive``,
steps, ``specialist_mcp`` for the MCP consult tool, ``specialist_research``,
``research_synthesis``, ``research_watchlist``, ``triage``,
``memory_extractor``, ``agent_test`` for the Council test boxes), which is
-what the per-source breakdown
-groups on. A research run binds its ``run_id`` in a ContextVar for its
+what the per-source breakdown groups on. A research run binds its
+``run_id`` in a ContextVar for its
duration so every row the run produces carries it in ``details``; the
workflow then rolls those rows up into the ``usage`` block on its result.
"""