@rosthq/cli 0.7.51 → 0.7.52

package/dist/generator/groups.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"groups.d.ts","sourceRoot":"","sources":["../../src/generator/groups.ts"],"names":[],"mappings":"AAuCA,OAAO,EAAgB,KAAK,SAAS,EAAE,MAAM,YAAY,CAAC;AAM1D,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,MAAM,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAKhF,CAAC;AAmmCF,eAAO,MAAM,WAAW,EAAE,MAAM,CAAC,MAAM,EAAE,SAAS,CA2OjD,CAAC"}
+{"version":3,"file":"groups.d.ts","sourceRoot":"","sources":["../../src/generator/groups.ts"],"names":[],"mappings":"AAuCA,OAAO,EAAgB,KAAK,SAAS,EAAE,MAAM,YAAY,CAAC;AAM1D,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,MAAM,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAKhF,CAAC;AAonCF,eAAO,MAAM,WAAW,EAAE,MAAM,CAAC,MAAM,EAAE,SAAS,CA2OjD,CAAC"}

package/dist/index.js

@@ -41339,7 +41339,9 @@ var graphNodeSchema = external_exports.object({
   }).strict().nullable(),
   signal_state: rollupStateSchema,
   cascade_state: rollupStateSchema,
-  open_task_count: external_exports.number().int().nonnegative()
+  open_task_count: external_exports.number().int().nonnegative(),
+  unassigned: external_exports.boolean(),
+  is_peer: external_exports.boolean()
 }).strict();
 var graphEdgeSchema = external_exports.object({
   parent_seat_id: uuidSchema11,
@@ -44516,7 +44518,7 @@ Treat AICOS as a coordinator over the operating system. It can become more usefu
     order: 20,
     title: "Responsibility Graph playbook",
     summary: "How to build a functions-first graph with seats, owners, Stewards, vacancies, and clean authority.",
-    version: "2026-07-04.3",
+    version: "2026-07-06.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["graph_design", "staffing"],
@@ -44549,6 +44551,23 @@ The Responsibility Graph is the company's operating structure. It answers who ow
 - Give every agent seat a human Steward chain.
 - Attach goals, measurables, and tasks to seats, not directly to people.
 
+## Single-root chart and parent resolution
+
+The graph always resolves to a single canonical root seat (Founder & CEO in the standard shape) so the web canvas, CLI \`rost graph show\`, and MCP \`graph.get\` all agree on the same structure. The parent of each seat is derived deterministically:
+
+1. An explicit parent seat id, when it names a live seat in the same chart.
+2. The seat at the ltree parent path, when one exists.
+3. The steward seat, when the seat is not AICOS and the steward is a live non-self seat.
+4. Otherwise the seat has no parent.
+
+AICOS always stays a peer of the root (never a child of its steward) and never appears as an orphan in the unassigned set \u2014 this is intentional and not a data-quality issue.
+
+Seats that do not reach the single root through the resolved parent chain are listed as **unassigned** (with \`unassigned: true\` and no incoming edge). Each \`graph.get\` node carries an \`unassigned\` boolean, and the CLI \`rost graph show\` output prints unassigned seats under a separate \`Unassigned\` section so operators can see which parts of the chart need attention. The web canvas parks unassigned seats at the bottom of the chart instead of inventing fake root edges.
+
+## Forge Developer Team seats are pinned
+
+Seats under \`forge.developer_team\` are resolved by Forge build dispatch using their exact path, so they cannot be reparented or merged from the graph, CLI, or MCP \u2014 moving a seat (or an ancestor whose subtree holds them) would eject them from dispatch, and no command can restore the path. To change who is accountable for one of these seats, update its steward with \`agent_setup.update\`; the reporting path stays fixed. To stand the team down, use the governed Forge team teardown flow, not a merge or decommission.
+
 ## Add an agent from the graph
 
 Agent creation is a first-class graph action. From a seat in the Responsibility Graph you can open the agent setup wizard with the seat already chosen as the parent:
@@ -44619,7 +44638,7 @@ Each seat needs:
 
 Read before you write. Load the whole graph first so seat ids, parents, and occupancy are known.
 
-- CLI: \`{{cli}} command graph.get --json '{}'\` (scope: tenant). Returns seats, edges, root, occupants, and status rollups.
+- CLI: \`{{cli}} command graph.get --json '{}'\` (scope: tenant). Returns seats, edges, root, occupants, status rollups, and unassigned-seat flags. The output includes a single \`root_seat_id\`, exactly one \`is_root: true\` node, and unassigned seats listed under their own section with a data-quality note.
 - MCP tool: \`rost_get_responsibility_graph\` with \`{}\`; or read the resource \`rost://graph\` (tenant-admin token).
 - One seat: \`{{cli}} command seat.get --json '{"seat_id":"<seat-id>"}'\` or \`rost_get_seat_detail\`.
 
@@ -49864,10 +49883,27 @@ function renderGraph(output) {
     `root_seat_id=${field(record2, "root_seat_id")}`,
     "seat_id  parent_seat_id  type  status  name"
   ];
+  const assigned = [];
+  const unassigned = [];
   for (const node of nodes) {
     const row = asRecord(node);
+    if (row.unassigned) {
+      unassigned.push(row);
+    } else {
+      assigned.push(row);
+    }
+  }
+  for (const row of assigned) {
     lines.push(`${field(row, "seat_id")}  ${field(row, "parent_seat_id")}  ${field(row, "seat_type")}  ${field(row, "status")}  ${field(row, "name")}`);
   }
+  if (unassigned.length > 0) {
+    lines.push("");
+    lines.push("Unassigned (no path to root \u2014 data-quality signal)");
+    lines.push("seat_id  parent_seat_id  type  status  name");
+    for (const row of unassigned) {
+      lines.push(`${field(row, "seat_id")}  ${field(row, "parent_seat_id")}  ${field(row, "seat_type")}  ${field(row, "status")}  ${field(row, "name")}`);
+    }
+  }
   return lines.join("\n");
 }
 function renderSeatList(output) {