@rosthq/cli 0.7.1 → 0.7.2

package/dist/index.js

@@ -41877,7 +41877,7 @@ The Compass is drafted, then activated by a human through supersession.
     order: 15,
     title: "AICOS chat guide",
     summary: "How the AI Chief of Staff chat works in the authenticated app shell and what it can safely do today.",
-    version: "2026-07-02.5",
+    version: "2026-07-02.6",
     public: true,
     audiences: ["human", "in_app_agent"],
     stages: ["company_setup", "operating_rhythm"],
@@ -41921,7 +41921,11 @@ You can reopen prior threads or start a new one. Session history is stored in te
 
 Each turn carries server-normalized page context: route template, current path, safe search state, selected seat or object ids when authorized, and onboarding state when relevant. The server derives tenant and user authority from the authenticated session. Client-supplied tenant context is never accepted as authority.
 
-The current chat harness shows the effective lane and model. The initial lane is cloud, with a deterministic harness response while live model execution, action execution, and runner execution waves land. The contract is intentionally backend-neutral: future cloud and runner turns use the same sessions, messages, lane labels, sources, and linked artifacts.
+The current chat harness shows the effective lane and model. Cloud is the default and remains the enforced lane during onboarding, even if a post-onboarding lane has been selected. After onboarding, an owner or admin can select cloud, runner, or MCP only when the server says that lane is ready. Lane changes update the governed AICOS agent seat and write an append-only audit event; the browser never decides tenant authority or runner/MCP readiness.
+
+Runner mode uses the same AICOS sessions and transcript. A web turn in runner mode records the user's message, queues a governed AICOS work order for the live AICOS agent, links that work order to the assistant message, and leaves the transcript visible while the paired runner claims and reports through the normal runner lane. A runner must be paired, execute-ready, and backed by the live AICOS agent before it can be selected.
+
+MCP mode uses the existing tenant-authorized MCP surfaces. It requires an active seat-scoped MCP token for the AICOS seat and does not grant hidden tenant-admin access or run browser-side MCP tool calls. Users operate MCP AICOS from their authorized agent interface; the web chat remains the same readable thread surface.
 
 Model behavior is now explicit in the AICOS session contract. A thread can run in **Auto** or use a pinned compatible model from the guided catalog. Auto chooses a fast tier for short low-risk turns, the balanced default for normal operating help, and a higher-reasoning tier for onboarding synthesis or large context. The panel shows the effective model, disables lower-context choices once the active thread outgrows them, and tells the user to start a new session for those models. Session context is estimated and compacted into a durable summary when it crosses the configured threshold; raw messages remain in history, but future model calls can use the summary rather than resending the whole thread. Platform allowance and BYOK state are checked before routing; an exhausted included allowance keeps AICOS in guided mode and points the user toward BYOK/manual continuation. Because the DER-1068 implementation still uses the deterministic harness, it does not create fake llm_calls rows or settle fake allowance usage; reservation/settlement belongs to the real provider call path.
 
@@ -49274,10 +49278,12 @@ async function spawnRunnerTurn(appUrl2, workOrder, runtime) {
     task_id: workOrder.task_id ?? null,
     seat: workOrder.seat ?? null,
     charter: workOrder.charter ?? null,
-    permission_manifest: workOrder.permission_manifest ?? null
+    permission_manifest: workOrder.permission_manifest ?? null,
+    aicos: workOrder.aicos ?? null
   };
+  const hasAicosContext = typeof workOrder.aicos === "object" && workOrder.aicos !== null;
   const prompt = [
-    `Load your ${cliBrand.name} context, report one read-only status, and stop.`,
+    hasAicosContext ? `Load your ${cliBrand.name} context, answer the AICOS user turn using only seat-authorized context and tools, and stop.` : `Load your ${cliBrand.name} context, report one read-only status, and stop.`,
     "Do not call external systems or mutating tools.",
     `Claimed work order context: ${JSON.stringify(context).slice(0, 8e3)}`
   ].join("\n");