@rosthq/cli 0.7.148 → 0.7.149

package/dist/index.js

@@ -53967,7 +53967,7 @@ Use the lower-level commands after health names a finding: \`agent.get_run\` for
     order: 46,
     title: "Tool access and vault",
     summary: "How to give agents access to tools without exposing raw credentials or expanding authority by accident.",
-    version: "2026-07-21.1",
+    version: "2026-08-01.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing"],
@@ -54049,7 +54049,7 @@ There is exactly one way to give a connected tool its credential, and it is the
 
 ## Change tool access after go-live
 
-Tool access on a live seat is part of its signed Charter, so changing it is a governed amendment, not an in-place edit. You can make the change from the agent detail page without leaving it: the Tools tab's manage-tools drawer edits the permission manifest directly \u2014 grant or revoke a tool, adjust its scope tier, or add an available tool from the catalog. Your edits are staged as one confirmation that lands in Approvals with a plain summary of what changes ("grants work.record (draft) \xB7 revokes email.draft"). Approving that confirmation is the re-sign: it creates a new Charter version that supersedes the prior one, and the tool guard honors the new manifest on the next run. Nothing changes until a human approves \u2014 selecting a tool never grants access on its own.
+Tool access on a live seat is part of its signed Charter, so changing it is a governed amendment, not an in-place edit. You can make the change from the agent detail page without leaving it: the Tools tab's manage-tools drawer edits the permission manifest directly \u2014 grant or revoke a tool, adjust its scope tier, or add an available tool from the catalog. Your edits are staged as one confirmation that lands in Approvals with a plain summary of what changes ("grants work.record (draft) \xB7 revokes email.draft"). Approving that confirmation is the re-sign: it creates a new Charter version that supersedes the prior one, and prepares a successor agent pinned to that new version. The running agent does not switch to the new manifest at that moment. It stays on the manifest it rehearsed, and the tool guard keeps enforcing that one, until you rehearse the successor with a dry run and promote it with \`agent.go_live\` \u2014 the promotion is what moves the seat onto the new manifest, and it retires the agent generation it replaced. Nothing changes until a human approves \u2014 selecting a tool never grants access on its own.
 
 The charter builder's amendment mode edits the same manifest for a draft Charter (toggle a tool's grant or scope tier), staged into the draft; the draft stays inert until the existing sign or go-live step. If a seat already has an amendment draft open, finish it in the charter editor rather than staging a separate tool change from the drawer.
 
@@ -54125,7 +54125,7 @@ External connectors are being rolled out provider by provider, conservatively (r
     order: 48,
     title: "CLI and MCP installation guide",
     summary: "Install the public CLI, register remote token-backed MCP clients, and find the full command and tool catalog.",
-    version: "2026-07-31.6",
+    version: "2026-08-01.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing"],
@@ -54885,7 +54885,7 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_assign_dry_run_agent_to_seat\` | \`staffing.assign_agent_dry_run\` | Assign an agent occupancy in dry-run mode. | Seat or tenant-admin | Call only after Steward chain is clear. |
 | \`rost_staff_seat\` | \`staffing.assign\` | Compatibility helper for human, agent, or hybrid staffing. | Seat or tenant-admin | Call with \`seat_id\` and \`occupant\`. |
 | \`rost_import_agent_definition\` | \`agent.import_definition\` | Import a strict, versioned agent definition into a canonical draft Seat/setup without credentials, placement ids, or go-live side effects. | Tenant | Human-gated; call with \`definition_json\` and optional \`idempotency_key\`. Review the resulting draft setup before tools, dry run, or go-live. |
-| \`rost_go_live\` | \`agent.go_live\` | Promote a dry-run agent seat to live. | Seat or tenant-admin | Call after human approval. |
+| \`rost_go_live\` | \`agent.go_live\` | Promote a dry-run agent seat to live, retiring the agent generation the promoted agent replaces on that seat. | Seat or tenant-admin | Call after human approval. Paused agents, and an agent pinned to another still-draft Charter version, are left in place. |
 | \`rost_create_mcp_token\` | \`mcp_token.create\` | Mint a tenant-admin or seat-scoped MCP token. | Tenant | Prefer \`{{cli}} mcp install\` for users. |
 | \`rost_revoke_mcp_token\` | \`mcp_token.revoke\` | Revoke an MCP token immediately. | Tenant | Call with \`token_id\`. |
 | \`rost_get_responsibility_graph\` | \`graph.get\` | Read the Responsibility Graph: seats, edges, root, occupants, status rollups. | Tenant | Call with \`{}\` before mutating or routing work. |