@rosthq/cli 0.7.22 → 0.7.23

package/dist/generated/command-manifest.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"command-manifest.d.ts","sourceRoot":"","sources":["../../src/generated/command-manifest.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,gCAAgC,CAAC;AAE3E,eAAO,MAAM,gBAAgB,EAAE,SAAS,oBAAoB,EAwN3D,CAAC"}
+{"version":3,"file":"command-manifest.d.ts","sourceRoot":"","sources":["../../src/generated/command-manifest.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,gCAAgC,CAAC;AAE3E,eAAO,MAAM,gBAAgB,EAAE,SAAS,oBAAoB,EA2N3D,CAAC"}

package/dist/index.js

@@ -37979,6 +37979,147 @@ var CATALOG_ENTRIES = [
     scope_tiers: ["read"],
     credential_required: false,
     default_access_policy: "always_allow"
+  },
+  // DER-1293 (tool-id canonicalization): the stock agent templates
+  // (`packages/agents/src/templates.ts`) grant these dotted business-tool ids, so a
+  // signed AP-Clerk / SDR / Support / QA / Signal manifest derived from a template
+  // already carries them. They were missing from the catalog, which (1) made a Skill
+  // that requires one resolve `unknown_tool` at `skill.check_dependencies`, and (2)
+  // left the runtime guard's scope-tier lookup (`resolveToolScopeTier`) unresolved →
+  // fail-closed `critical` for an autonomous read/draft grant. Adding them here — the
+  // single source of truth for scope tier and access policy — reconciles all three
+  // surfaces (catalog ↔ templates ↔ skills). Conservative-by-default (invariant #10):
+  // read/draft tiers only, drafts never send, and the ids never mint new authority —
+  // authorization stays with the signed manifest + guard (invariant #6).
+  {
+    id: "accounting.bills.read",
+    title: "Read payable bills",
+    provider: "accounting",
+    description: "Call this to read payable bills, vendor records, and matching evidence when preparing accounts-payable work. Read-only: no payment release, coding change, or vendor send.",
+    default_scope_tier: "read",
+    scope_tiers: ["read"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "accounting.invoices.read",
+    title: "Read receivable invoices",
+    provider: "accounting",
+    description: "Call this to read receivable invoice aging and payment status for collections and reconciliation. Read-only: it never changes terms, applies credits, or sends.",
+    default_scope_tier: "read",
+    scope_tiers: ["read"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "inbox.ap.read",
+    title: "Read AP inbox",
+    provider: "email",
+    description: "Call this to read messages in the assigned accounts-payable inbox for triage and invoice matching. Read-only and scoped to the AP inbox.",
+    default_scope_tier: "read",
+    scope_tiers: ["read"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "inbox.ap.draft",
+    title: "Draft AP reply",
+    provider: "email",
+    description: "Call this to draft an accounts-payable reply for a human to review. Draft-only: it never sends.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "email.collections.draft",
+    title: "Draft collections reminder",
+    provider: "email",
+    description: "Call this to draft a collections reminder for human approval. Draft-only: it never sends, changes terms, or applies credits.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "helpdesk.ticket.read",
+    title: "Read support tickets",
+    provider: "helpdesk",
+    description: "Call this to read assigned support tickets and their history for triage. Read-only and scoped to the assigned queues.",
+    default_scope_tier: "read",
+    scope_tiers: ["read"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "helpdesk.ticket.classify",
+    title: "Classify support ticket",
+    provider: "helpdesk",
+    description: "Call this to tag and route a support ticket to the correct queue. Classification and routing only \u2014 it never replies, changes account state, or closes a ticket.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "helpdesk.reply.draft",
+    title: "Draft support reply",
+    provider: "helpdesk",
+    description: "Call this to draft a first support response from approved knowledge-base content. Draft-only: it never sends or promises a fix.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "crm.contacts.read",
+    title: "Read CRM contacts",
+    provider: "crm",
+    description: "Call this to read assigned inbound leads and account records for enrichment and briefing. Read-only: it never changes lifecycle stage or sends outreach.",
+    default_scope_tier: "read",
+    scope_tiers: ["read"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "content.calendar.draft_update",
+    title: "Draft content calendar",
+    provider: "content",
+    description: "Call this to draft content-calendar entries for review. Drafts only \u2014 it never publishes, schedules, or sends.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "release.artifacts.read",
+    title: "Read release artifacts",
+    provider: "release",
+    description: "Call this to read assigned release artifacts, checklists, and test results for review. Read-only: it never approves a release or changes production state.",
+    default_scope_tier: "read",
+    scope_tiers: ["read"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "issues.draft",
+    title: "Draft tracker issue",
+    provider: "issues",
+    description: "Call this to draft a release-risk or tracker issue for human review. Draft-only: it never closes, assigns, or changes issue state autonomously.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: true,
+    default_access_policy: "always_allow"
+  },
+  {
+    id: "signal.report",
+    title: "Draft Signal reading",
+    provider: "rost",
+    description: "Call this to propose a draft Signal reading for one of the seat's agent-sourced measurables, with a cited source. Draft-only: a human confirms the reading; it never fabricates a value or changes a measurable definition.",
+    default_scope_tier: "draft",
+    scope_tiers: ["draft"],
+    credential_required: false,
+    default_access_policy: "always_allow"
   }
 ];
 var catalogById = new Map(CATALOG_ENTRIES.map((entry) => [entry.id, entry]));
@@ -42206,6 +42347,34 @@ var softwareGithubActionSchema = external_exports.enum([
 ]);
 var softwareGithubPolicyDecisionSchema = external_exports.enum(["allowed", "denied", "requires_human"]);
 var softwarePhaseRunStatusSchema = external_exports.enum(["pending", "running", "passed", "failed", "blocked", "skipped"]);
+var softwarePlanVersionStatusSchema = external_exports.enum([
+  "draft",
+  "needs_clarification",
+  "ready_for_plan_review",
+  "approved",
+  "rejected"
+]);
+var softwareChangesetSplitCriterionSchema = external_exports.enum([
+  "single",
+  "risk_isolation",
+  "reviewability_budget",
+  "deploy_ordering",
+  "independent_revert"
+]);
+var softwareChangesetStatusSchema = external_exports.enum(["planned", "in_progress", "in_review", "merged", "declined"]);
+var softwareTaskStatusSchema = external_exports.enum(["planned", "in_progress", "blocked", "done"]);
+var softwareConformanceSeveritySchema = external_exports.enum(["blocker", "major", "minor"]);
+var softwareConformanceCategorySchema = external_exports.enum([
+  "scope_gap",
+  "plan_deviation",
+  "missing_test",
+  "security_constraint",
+  "secret_handling",
+  "authority_limit",
+  "skipped_scope",
+  "other"
+]);
+var softwareConformanceStatusSchema = external_exports.enum(["open", "accepted", "resolved"]);
 var softwareGateTypeSchema = external_exports.enum([
   "plan_review",
   "security_signoff",
@@ -42308,6 +42477,54 @@ var softwareGateSummarySchema = external_exports.object({
   rationale: external_exports.string().nullable(),
   created_at: external_exports.string()
 });
+var softwareChangesetSummarySchema = external_exports.object({
+  id: uuid10,
+  build_request_id: uuid10,
+  ordinal: external_exports.number().int(),
+  title: external_exports.string(),
+  split_criterion: softwareChangesetSplitCriterionSchema,
+  status: softwareChangesetStatusSchema,
+  branch_name: external_exports.string().nullable(),
+  pr_number: external_exports.number().int().nullable(),
+  pr_url: external_exports.string().nullable(),
+  pr_draft: external_exports.boolean(),
+  inferred_risk: softwareRiskLevelSchema.nullable(),
+  merged_at: external_exports.string().nullable(),
+  created_at: external_exports.string()
+});
+var softwareTaskSummarySchema = external_exports.object({
+  id: uuid10,
+  build_request_id: uuid10,
+  changeset_id: uuid10,
+  plan_version_id: uuid10,
+  ordinal: external_exports.number().int(),
+  task_key: external_exports.string(),
+  title: external_exports.string(),
+  status: softwareTaskStatusSchema,
+  depends_on: external_exports.array(external_exports.string()),
+  parallelizable: external_exports.boolean(),
+  est_turns: external_exports.number().int().nullable(),
+  actual_turns: external_exports.number().int().nullable(),
+  actual_files: external_exports.number().int().nullable(),
+  started_at: external_exports.string().nullable(),
+  completed_at: external_exports.string().nullable(),
+  created_at: external_exports.string()
+});
+var softwarePlanConformanceFindingSummarySchema = external_exports.object({
+  id: uuid10,
+  build_request_id: uuid10,
+  changeset_id: uuid10.nullable(),
+  phase_run_id: uuid10.nullable(),
+  plan_version_id: uuid10.nullable(),
+  severity: softwareConformanceSeveritySchema,
+  category: softwareConformanceCategorySchema,
+  summary: external_exports.string(),
+  detail: external_exports.string().nullable(),
+  status: softwareConformanceStatusSchema,
+  accepted_by_decision_id: uuid10.nullable(),
+  resolved_at: external_exports.string().nullable(),
+  created_at: external_exports.string()
+});
 var softwareAuthorityProfileSummarySchema = external_exports.object({
   id: uuid10,
   software_project_id: uuid10.nullable(),
@@ -42415,6 +42632,39 @@ var softwareGateDecideOutputSchema = external_exports.object({
   resolved_by_user_id: uuid10,
   decision_id: uuid10.nullable()
 });
+var forgeClarificationAnswer = external_exports.object({
+  question: external_exports.string().trim().min(1).max(2e3),
+  answer: external_exports.string().trim().min(1).max(4e3)
+}).strict();
+var softwareRequestAnswerClarificationInputSchema = external_exports.object({
+  build_request_id: uuid10,
+  answers: external_exports.array(forgeClarificationAnswer).min(1).max(50),
+  // The planner marks the plan ready once its questions are resolved; the human/COS can
+  // signal that here. Default false keeps the plan in needs_clarification.
+  mark_ready_for_plan_review: external_exports.boolean().default(false)
+}).strict();
+var softwareRequestAnswerClarificationOutputSchema = external_exports.object({
+  build_request_id: uuid10,
+  plan_version_id: uuid10,
+  status: softwarePlanVersionStatusSchema,
+  answered_count: external_exports.number().int()
+});
+var softwarePlanApproveInputSchema = external_exports.object({
+  build_request_id: uuid10,
+  rationale: external_exports.string().trim().min(1).max(4e3).optional()
+}).strict();
+var softwarePlanRejectInputSchema = external_exports.object({
+  build_request_id: uuid10,
+  // A rejection must say why (it routes the request back to discovery/scoping).
+  rationale: external_exports.string().trim().min(1).max(4e3)
+}).strict();
+var softwarePlanDecisionOutputSchema = external_exports.object({
+  build_request_id: uuid10,
+  plan_version_id: uuid10,
+  status: external_exports.enum(["approved", "rejected"]),
+  decision_id: uuid10,
+  current_phase: softwarePhaseSchema
+});
 var softwareAuthorityProfileListInputSchema = external_exports.object({
   software_project_id: uuid10.nullable().optional()
 }).strict();
@@ -42650,14 +42900,63 @@ var softwareDeveloperTeamInstallOutputSchema = external_exports.object({
 });
 var forgeArtifactText = external_exports.string().trim().min(1).max(4e3);
 var forgeArtifactList = external_exports.array(forgeArtifactText).max(50).default([]);
+var forgeTaskKey = external_exports.string().trim().min(1).max(200);
+var forgeTaskTitle = external_exports.string().trim().min(1).max(300);
+var forgeTaskPathList = external_exports.array(external_exports.string().trim().min(1).max(300)).max(20).default([]);
+var forgeTaskVerificationList = external_exports.array(external_exports.string().trim().min(1).max(500)).max(25).default([]);
+var forgeTaskDefinitionSchema = external_exports.object({
+  task_key: forgeTaskKey,
+  title: forgeTaskTitle,
+  // task_keys this task depends on (dependency DAG); disjoint-file tasks may be parallel.
+  depends_on: external_exports.array(forgeTaskKey).max(50).default([]),
+  parallelizable: external_exports.boolean().default(false),
+  // ≤ ~40% of the phase session budget (headroom for fix loops); split above the ceiling.
+  est_turns: external_exports.number().int().positive().max(1e3).nullable().default(null),
+  files_likely: forgeTaskPathList,
+  // verification commands + expected proof, stated BEFORE implementation.
+  verification: forgeTaskVerificationList
+}).strict();
+var forgeChangesetPlanSchema = external_exports.object({
+  ordinal: external_exports.number().int().positive().max(100),
+  title: forgeTaskTitle,
+  split_criterion: softwareChangesetSplitCriterionSchema.default("single"),
+  // task_keys grouped into this PR-boundary unit.
+  task_keys: external_exports.array(forgeTaskKey).max(200).default([])
+}).strict();
 var forgePlanArtifact = external_exports.object({
   scope: forgeArtifactText,
   plan_steps: forgeArtifactList,
   files_or_systems: forgeArtifactList,
   verification: forgeArtifactList,
   risks: forgeArtifactList,
-  clarifying_questions: forgeArtifactList
-}).strict();
+  clarifying_questions: forgeArtifactList,
+  // DER-1197 changeset B: structured human answers to the clarifying questions, written
+  // by software_factory.request.answer_clarification. Default [] keeps older artifacts valid.
+  clarification_answers: external_exports.array(forgeClarificationAnswer).max(50).default([]),
+  // DER-1197 decomposition. Default [] keeps pre-decomposition artifacts valid.
+  tasks: external_exports.array(forgeTaskDefinitionSchema).max(200).default([]),
+  changesets: external_exports.array(forgeChangesetPlanSchema).max(100).default([])
+}).strict().superRefine((artifact, ctx) => {
+  const taskKeys = /* @__PURE__ */ new Set();
+  for (const [i, task] of artifact.tasks.entries()) {
+    if (taskKeys.has(task.task_key)) {
+      ctx.addIssue({ code: external_exports.ZodIssueCode.custom, path: ["tasks", i, "task_key"], message: `Duplicate task_key "${task.task_key}"` });
+    }
+    taskKeys.add(task.task_key);
+  }
+  const ordinals = /* @__PURE__ */ new Set();
+  for (const [i, cs] of artifact.changesets.entries()) {
+    if (ordinals.has(cs.ordinal)) {
+      ctx.addIssue({ code: external_exports.ZodIssueCode.custom, path: ["changesets", i, "ordinal"], message: `Duplicate changeset ordinal ${cs.ordinal}` });
+    }
+    ordinals.add(cs.ordinal);
+    for (const [j, key] of cs.task_keys.entries()) {
+      if (!taskKeys.has(key)) {
+        ctx.addIssue({ code: external_exports.ZodIssueCode.custom, path: ["changesets", i, "task_keys", j], message: `Changeset references unknown task_key "${key}"` });
+      }
+    }
+  }
+});
 var forgeImplementationArtifact = external_exports.object({
   changes: forgeArtifactList,
   verification: forgeArtifactList,
@@ -43757,7 +44056,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-06-30.1",
+    version: "2026-07-04.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["graph_design", "staffing"],
@@ -43819,6 +44118,17 @@ The graph also carries a mission-control panel. It pulls the same operational st
 
 Agent seat pages show the operator-facing output trail, not just low-level run telemetry. The completed work area combines explicit \`agent_deliverables\`, successful \`work.log\` evidence, and recent successful run summaries into one readable list. Each item shows what was delivered, when it happened, what kind of work it was, and safe evidence links labelled as internal, Linear, GitHub, or external. Secret-shaped values are redacted before display, and run or task context is shown only when it belongs to the same seat.
 
+## Read a human seat's page
+
+A human seat's page opens on one computed answer line \u2014 for example "On track \u2014 4 of 5 measurables on target \xB7 1 held draft awaiting review" \u2014 instead of a wall of always-shown sections. Below it:
+
+- **Exceptions are fully visible**: off-target measurables, escalations addressed to this seat as Steward (a held draft awaiting the Steward's decision), and open Friction filed by or owned by this seat all render as rows up top, each with a one-click way to act (log a reading, review, or resolve).
+- **Healthy content collapses to a count**: on-target measurables and measurables with no reading yet fold into one expandable "N measurables on target" row so the calm majority does not compete with the exceptions for attention.
+- **Three lens tabs** \u2014 Overview, Activity, Access \u2014 are views of the same seat, not separate sub-pages: Overview holds the answer line, exceptions, Purpose and accountabilities, and the Cascade goal summary; Activity is the event feed and the seat's task queue; Access is occupancy, Charter status, decision authority, and the permission manifest.
+- **One Manage drawer** replaces the inline staffing panel: it opens to Occupancy (staffing controls, when this seat is eligible to be staffed, and Let go), Charter (a link to the Charter Builder), and Measurables (a link to log a reading in Signal). Opening the drawer calls the exact same commands as before \u2014 nothing moved out of it changed behavior.
+
+Agent seat pages keep their own dedicated Overview/Charter/Access layout with an always-visible fact sheet; see "Review an agent seat's delivered work" above for the agent-specific completed-work view.
+
 ## First-pass structure
 
 Start with the operating root, then major functions, then the few seats that own the most important recurring work. Do not over-model. A graph with eight clear seats is better than a graph with thirty vague boxes.
@@ -44195,7 +44505,7 @@ The dry run is a real sandbox rehearsal, not a stamp. It executes a mock-provide
     order: 80,
     title: "Sync rhythm playbook",
     summary: "How Signal, Friction, Cascade, and Sync Briefs turn weekly meetings into decision time.",
-    version: "2026-06-30.1",
+    version: "2026-07-04.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["operating_rhythm"],
@@ -44241,7 +44551,7 @@ The Sync Brief should answer:
 - Which agent escalations are aging?
 - Which goals lack current evidence?
 
-On screen the brief reads in plain terms: Signal exceptions, goal progress, task review, ranked Friction, and agent activity. Where a section has no source data, it lists gaps to confirm \u2014 the missing inputs a human should know about before the meeting \u2014 rather than a blank section.
+On screen the brief reads exceptions-first. One computed answer line states what changed in plain terms, then every exception \u2014 Signal breaches, slipped or at-risk Cascade goals, escalation-grade Friction, agent Charter exceedances, and stalled or overdue tasks \u2014 is fully visible in a single agenda; the agenda is the exceptions, not a tour of every seat. Friction, task review, and agent activity collapse to an expandable count when they hold nothing above their escalation threshold, so the page stays calm when nothing there needs attention. Signal and Cascade have no such collapsed count by design: the brief only ever records exceptions for those two sections, not a reviewed total, so the screen never blends a live count with this frozen, already-compiled snapshot. Where a section has no source data at all, it lists gaps to confirm \u2014 the missing inputs a human should know about before the meeting \u2014 rather than a blank section; a brief with open gaps but no exception rows says so plainly instead of reporting an all-clear. Compile now and Run current Sync live behind one Manage control so the read view stays uncluttered.
 
 Before the first brief exists, the Sync pages are readiness views. They show the next scheduled compile and the source areas that will feed it: Signal, Cascade, Tasks, Friction, and Agents. Use those links to add missing source data, or use Compile now to run the same idempotent persisted compile operation immediately when the company uses company-wide Sync Briefs. If the company is configured for per-cluster briefs, compile the target cluster from CLI or MCP with a cluster id until the UI offers a cluster selector. Once a brief exists, the page shows whether it covers the current period, when it was compiled, and which sections were omitted or compiled with gaps.
 
@@ -44270,7 +44580,7 @@ Decisions should be recorded as human decisions. Handoffs should attach to seats
     order: 45,
     title: "How agents work",
     summary: "How {{brand}} agents operate inside seats, use Charters, report work, and escalate beyond authority.",
-    version: "2026-07-02.1",
+    version: "2026-07-04.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing", "operating_rhythm"],
@@ -44353,7 +44663,7 @@ The model is only ever offered the tools the seat's manifest grants \u2014 a den
 
 1. The manifest guard runs first and decides: allowed, denied, or must-escalate. A denied or must-escalate call never runs the action; an escalation is raised for a human.
 2. For an allowed call, the proposed input is validated against the tool's schema. Malformed input fails closed \u2014 the action does not run, and the model is told to correct it.
-3. The action runs bound to the seat's vaulted credential. The secret stays inside the call and never reaches the result, the audit row, the logs, or the model.
+3. The action runs bound to the seat's vaulted credential. The secret stays inside the call and never reaches the result, the audit row, the logs, or the model. Brokered secret access applies the same rule on every attempt, including a denied or missing grant: it records a redacted, constraint-safe access-log entry and never opens the vault when the grant does not match.
 4. Every call \u2014 allowed, denied, escalated, or invalid \u2014 writes a tool-call audit row you can review.
 
 When operational evidence appears in the app, it is formatted for review instead of shown as primary raw JSON. Tool arguments, escalation evidence, status evidence, Sync inputs, and task context are summarized as labeled fields; secret-looking values stay redacted. Raw identifiers remain available only as supporting detail when they help an operator trace the record.
@@ -44472,7 +44782,7 @@ There is exactly one way to give a connected tool its credential, and it is the
     order: 47,
     title: "Available tools guide",
     summary: "How to think about tool categories available to seats and what each category should be used for.",
-    version: "2026-06-30.1",
+    version: "2026-07-04.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing"],
@@ -44510,6 +44820,8 @@ Start from the seat's responsibility, not the tool list. If a tool does not dire
 
 Skills are reusable procedures a seat can learn from; they are not tools and they never grant authority. A skill package may declare required or optional tool dependencies so setup can identify blockers before assignment. Those dependencies are checked against the discoverable \`tool.catalog\` ids and scope tiers, then compared to the seat's Charter permission manifest. Missing required tools block approval; optional tools produce setup warnings. A published skill version is immutable, so later corrections create a new version instead of rewriting what a run may have used.
 
+The catalog covers both the platform verbs (status, escalation, Signal readings) and the business tools the stock-agent templates grant \u2014 accounts-payable and receivable reads, AP-inbox and collections drafts, helpdesk triage, CRM reads, and content-calendar, release-artifact, and issue drafts. Each is listed at a conservative scope tier (read for the reads, draft for the drafts, where a draft never sends), and the business tools are credential-gated. Because a skill's required tool id is matched against these ids, a skill that requires one of them resolves against the catalog rather than reporting an unknown tool. Catalog membership is configuration only: it still confers no authority, and a listed id runs only once a live handler exists behind the seat's signed permission manifest, the server guard, and any required credential \u2014 the manifest and guard remain the control plane.
+
 ## How agents should request tools
 
 Agents should explain the job, the required tool category, the minimum permission needed, and the escalation boundary. Humans approve or decline the request.
@@ -44525,7 +44837,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-04.14",
+    version: "2026-07-04.15",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing"],
@@ -45249,6 +45561,9 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_show_a_forge_build_request\` | \`software_factory.request.show\` | The Forge request detail: the request, current phase, phase-run history, and gates. Read-only; requires the Forge add-on. | Tenant | Call with \`{"build_request_id":"<request-id>"}\`. |
 | \`rost_advance_a_forge_build_request_phase\` | \`software_factory.phase.advance\` | Advance a build request to its next phase; the server enforces the closed phase state machine and rejects an illegal transition. | Tenant | Call with \`{"build_request_id":"<request-id>","to_phase":"discovery_scoping"}\`. |
 | \`rost_decide_a_forge_gate\` | \`software_factory.gate.decide\` | A human approves or rejects a Forge gate; an agent caller routes to \`/approvals\` and can never self-approve. Sensitive gates record a linked human decision. | Tenant | Call with \`{"gate_id":"<gate-id>","decision":"approve"}\`; non-interactive callers receive a confirmation handoff. |
+| \`rost_answer_forge_plan_clarifications\` | \`software_factory.request.answer_clarification\` | Write structured human answers to a draft plan's clarifying questions and optionally mark it ready for plan review; answers append to the versioned planning artifact and never widen authority or automation mode. | Tenant | Call with \`{"build_request_id":"<request-id>","answers":[{"question":"Which database?","answer":"Postgres"}],"mark_ready_for_plan_review":true}\`. |
+| \`rost_approve_a_forge_plan\` | \`software_factory.plan.approve\` | A human approves the current plan at the plan_review gate; records a human decision and advances the request to implementation. Owner-only and human-gated. | Tenant-admin | Call with \`{"build_request_id":"<request-id>"}\`; non-interactive callers receive a confirmation handoff. |
+| \`rost_reject_a_forge_plan\` | \`software_factory.plan.reject\` | A human rejects the current plan (with a required rationale) and routes the request back to discovery/scoping for re-planning. Owner-only and human-gated. | Tenant-admin | Call with \`{"build_request_id":"<request-id>","rationale":"Scope too broad"}\`; non-interactive callers receive a confirmation handoff. |
 | \`rost_list_forge_authority_profiles\` | \`software_factory.authority_profile.list\` | List the tenant's Forge authority profiles (seat capability presets, read-only by default). Read-only; requires the Forge add-on. | Tenant | Call with \`{}\`. |
 | \`rost_create_a_forge_authority_profile\` | \`software_factory.authority_profile.create\` | Define a Forge authority profile (a named seat capability preset). Owner-only; defaults to the read_only preset. | Tenant-admin | Call with \`{"name":"Builder","preset":"contributor"}\`. |
 | \`rost_grant_forge_seat_authority\` | \`software_factory.authority.grant\` | Grant a seat a Forge authority profile on a project (seat \u2192 project \u2192 profile). Owner-only and human-gated; emits a durable authority-change event. | Tenant-admin | Call with \`{"software_project_id":"<project-id>","seat_id":"<seat-id>","authority_profile_id":"<profile-id>"}\`; non-interactive callers receive a confirmation handoff. |
@@ -45750,7 +46065,7 @@ Retrieve the narrowest relevant guide before making a setup recommendation. Pref
     order: 60,
     title: "Cascade guide",
     summary: "How to connect company goals to seat-level work without turning {{brand}} into a project-management tool.",
-    version: "2026-07-01.1",
+    version: "2026-07-04.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["operating_rhythm"],
@@ -45822,7 +46137,7 @@ On \`/cascade\`, the screen renders the full goal depth, not just one or two lev
 
 ## Goal progress and at-risk goals
 
-A goal can carry a quantified progress (0-100) distinct from its on/off/done status. Report it with \`goal.set_progress\`; when an agent reports progress it lands as a proposal a human approves before the goal moves. A seat goal that has milestones takes its progress from milestone completion instead \u2014 the percentage is the share of its non-dropped milestones marked done, recomputed automatically as milestones complete, drop, or re-open. \`goal.list_at_risk\` projects which goals are off pace by comparing progress against the elapsed fraction of the cycle window (deterministic date math, no forecast model). Off-pace goals surface on \`/cascade\`, on the owner home, in the weekly Sync Brief, and as a weekly owner alert. Status-only goals (no progress recorded) are excluded from the projection and render as pending measurement, not as proven on track.
+A goal can carry a quantified progress (0-100) distinct from its on/off/done status. Report it with \`goal.set_progress\`; when an agent reports progress it lands as a proposal a human approves before the goal moves. A seat goal that has milestones takes its progress from milestone completion instead \u2014 the percentage is the share of its non-dropped milestones marked done, recomputed automatically as milestones complete, drop, or re-open. \`goal.list_at_risk\` projects which goals are off pace by comparing progress against the elapsed fraction of the cycle window (deterministic date math, no forecast model). Off-pace goals surface on \`/cascade\`, in the owner-only band on \`/home\`, in the weekly Sync Brief, and as a weekly owner alert. Status-only goals (no progress recorded) are excluded from the projection and render as pending measurement, not as proven on track.
 
 On human and function seat pages, goal visibility includes both direct goals and descendant seat goals from the Responsibility Graph subtree, so a manager can review team progress without double-owning the agent's work.
 
@@ -45856,7 +46171,7 @@ Agents can suggest commitments and report progress. They should not create a new
     order: 61,
     title: "Signal guide",
     summary: "How to define and read measurables so the company runs on evidence instead of status theater.",
-    version: "2026-07-04.1",
+    version: "2026-07-04.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["operating_rhythm"],
@@ -45917,11 +46232,11 @@ Avoid vanity numbers, manual-only status fields, and metrics nobody can act on.
 
 ## Run Signal without an agent
 
-A human can run the whole loop from the Signal page. Each measurable has a "Log this period's number" control that records a human reading (the same \`signal.correct_reading\` path), and an "Add a measurable" form creates one against a seat (the \`measurable.create\` path). You do not need an agent to keep Signal current.
+A human can run the whole loop from the Signal page. The page opens answer-first \u2014 one computed line ("2 of 14 measurables need attention," or "All 14 measurables on target" when nothing needs you) with only the exception rows fully visible; healthy measurables collapse to a single "N on target" count you can expand. Every create/edit action lives behind the one "+ Add" button, which opens a drawer with four segments: **Log reading** records a human reading (the same \`signal.correct_reading\` path, or a row's own "Log reading" button seeds the drawer to that measurable), **New measurable** creates one against a seat (the \`measurable.create\` path, plus adopting from the template catalog), **Sources**, and **CSV import**. You do not need an agent to keep Signal current.
 
 ## Import a scorecard from CSV
 
-To move off a spreadsheet or another operating tool, upload a scorecard export from the Signal page "Import from CSV" panel (the \`signal.import\` command, also available on CLI/MCP). Each row becomes a measurable owned by the seat whose name matches the row's owner, with its target, unit, direction, cadence, and trailing readings. Import is idempotent \u2014 re-importing upserts by period \u2014 and a row whose cadence conflicts with an existing measurable is reported and skipped, not overwritten.
+To move off a spreadsheet or another operating tool, open the Signal page's "+ Add" drawer and choose the "CSV import" segment (the \`signal.import\` command, also available on CLI/MCP). Each row becomes a measurable owned by the seat whose name matches the row's owner, with its target, unit, direction, cadence, and trailing readings. Import is idempotent \u2014 re-importing upserts by period \u2014 and a row whose cadence conflicts with an existing measurable is reported and skipped, not overwritten.
 
 ## Adopt a measurable template
 
@@ -45944,7 +46259,7 @@ Discovery always returns a \`recipe_presets\` array; it is empty when {{brand}}
 
 Recipes are validated data, never code: a read-only GET, a closed set of non-secret headers, and a restricted scalar path to the value. Every fetch passes one SSRF guard (HTTPS only, a steward-confirmed host allowlist set at bind, and a runtime check that the host does not resolve to a private address). The preset output never contains \`nango://\` handles, vault refs, tokens, or static credential headers. Deterministic pulls write \`integration\`-sourced readings on the measurable's cadence.
 
-In the web app, the same workflow lives on \`/signal\` in the "Connect a self-filling source" panel. It shows each measurable's setup state \u2014 manual, agent draft, source draft, or auto-filled \u2014 plus the latest safe pull outcome when one exists. Choose a connected source, discover its non-secret metadata, preview a GET URL and value path, bind the working preview as a draft, then confirm the draft before scheduled pulls can write readings. The UI never displays credential material, vault refs, raw response bodies, or recipe secrets; if no connected source exists, connect one from Settings first.
+In the web app, the same workflow lives on \`/signal\` in the "+ Add" drawer's "Sources" segment. It shows each measurable's setup state \u2014 manual, agent draft, source draft, or auto-filled \u2014 plus the latest safe pull outcome when one exists. Choose a connected source, discover its non-secret metadata, preview a GET URL and value path, bind the working preview as a draft, then confirm the draft before scheduled pulls can write readings. The UI never displays credential material, vault refs, raw response bodies, or recipe secrets; if no connected source exists, connect one from Settings first.
 
 A source binding can inform a measurable without automatically changing a Cascade goal. The proven Leiluna Baserow binding uses \`informs\`. Use \`drives_status\` only after a second business anchor confirms that this exact measurable should compute a childless goal's status; otherwise the Signal should stay visible as evidence and exception context, not an automatic goal-status driver.
 
@@ -46044,7 +46359,7 @@ Resolving Friction should produce one of four outcomes: a decision, a task, a Ch
     order: 70,
     title: "Steward queue guide",
     summary: "How Stewards review escalations, approve agent boundaries, and keep agents accountable.",
-    version: "2026-06-27.2",
+    version: "2026-07-04.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing", "operating_rhythm"],
@@ -46083,6 +46398,8 @@ In the app, the evidence is shown as a legible card, not raw data: a proposed to
 
 When nothing is waiting, the Steward page still proves the governance loop. It shows which agent or hybrid seats the human stewards, how many escalations were raised or decided recently, and whether any are open. That empty state is an operating summary, not a dead end.
 
+The Steward page itself only lists charter-clause escalations (Queue, Escalations). Agent-raised confirmations that need a sign-off \u2014 Charter approvals, tool/permission grants, and other gated commands \u2014 live in the consolidated \`/approvals\` queue, one click away from a header link on the Steward page. See the confirmations guide for how that queue works.
+
 ## How escalations reach you
 
 An escalation reaches you the same way no matter how the agent raised it \u2014 in a chat or CLI session, or on its own scheduled cloud run. When the agent stops at a boundary it opens the queue item and sends a notification to the accountable human along the steward chain, preferring a connected Slack channel and falling back to email. If no human occupies the agent's seat, the chain walks up to the next Steward. Delivery is idempotent: a retried run never notifies you twice for the same escalation, and the notification carries only summarized, redacted evidence \u2014 never secret material.
@@ -46456,7 +46773,7 @@ Every notification should include the seat, cause, evidence, and requested decis
     order: 75,
     title: "Local runner guide",
     summary: "How local agent sessions and runner surfaces should operate through {{brand}} without bypassing Charters or audit.",
-    version: "2026-07-04.1",
+    version: "2026-07-04.3",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing", "operating_rhythm"],
@@ -46510,6 +46827,10 @@ AICOS runner chat uses the same runner process but not the scheduled work-order
 
 When the Forge add-on is enabled, Forge phase work uses the same runner work-order lane. A Forge phase with an owning runner-agent Seat is linked to a normal \`work_orders\` row; the runner claims it, starts it, reports the result, and the server advances the linked phase. There is no separate local lease store.
 
+A build request decomposes into changesets and tasks tracked as queryable execution state. A changeset is the pull-request boundary and the revert unit (default one per request; additional changesets only on a named split criterion such as risk isolation or a reviewability-size budget). A task is one coding session inside a changeset, carrying its own verification and a per-task checkpoint that is the safe resume and pause boundary. Plan-conformance findings loop a changeset back to implementation; a finding can only be accepted, rather than resolved, through a recorded human decision.
+
+The plan-review step is human-driven through tri-surface commands. A person answers a draft plan's clarifying questions and can mark it ready for review; approving the plan records a human decision and moves the request into implementation, while rejecting it records the decision and routes the request back to discovery and scoping for re-planning. Approving or rejecting a plan is owner-only and human-gated \u2014 an agent can never decide a plan on its own.
+
 Runner heartbeats can include advisory capacity telemetry: OS, runner version, CPU and memory, active session count, detected local runtimes, and a model-account alias plus usage-limit state. Missing, empty, or whitespace model-account aliases are treated as the same \`default\` account so the scheduler can enforce a conservative one-session default-account cap. The scheduler also caps active runner work per tenant, project, runner, and model account.
 
 Forge context packets are deliberately bounded. The runner receives ids, phase state, authority-profile metadata, config metadata, and secret-grant metadata. It does not receive request free text, source refs, repo source dumps, raw secrets, vault refs, or a model-visible runner bearer secret. A short-lived seat-scoped MCP token is written only to the local MCP config file for the claimed turn.
@@ -48453,8 +48774,11 @@ var COMMAND_MANIFEST = [
   { "id": "software_factory.github.policy.upsert", "namespace": "software_factory", "action": "github.policy.upsert", "title": "Set a Forge GitHub automation policy", "description": "Set the server-side policy for GitHub actions and automation-mode ceilings. Owner-only and human-gated; production deploy remains human-gated.", "requiredScope": "tenant_admin", "confirmation": "human_required", "exposeOverMcp": true, "fields": [{ "name": "software_project_id", "flag": "software-project-id", "type": "string", "required": true }, { "name": "authority_profile_id", "flag": "authority-profile-id", "type": "string", "required": false }, { "name": "automation_mode_ceiling", "flag": "automation-mode-ceiling", "type": "enum", "required": false, "enumValues": ["plan_only", "pr_only", "merge_after_checks", "deploy_preview", "deploy_production"] }, { "name": "allowed_actions", "flag": "allowed-actions", "type": "array", "required": true, "itemType": "string" }, { "name": "requires_human_for", "flag": "requires-human-for", "type": "array", "required": true, "itemType": "string" }], "hasComplexInput": false, "help": "Set Forge's server-side GitHub automation policy for actions, mode ceilings, and human-gated operations." },
   { "id": "software_factory.github.repository.unbind", "namespace": "software_factory", "action": "github.repository.unbind", "title": "Unbind a Forge GitHub repository", "description": "Remove a GitHub repository's Forge project binding. By default the repository stays connected (unbound) and can be re-bound later; pass disconnect to remove it entirely. Owner-only and human-gated.", "requiredScope": "tenant_admin", "confirmation": "human_required", "exposeOverMcp": false, "fields": [{ "name": "app_slug", "flag": "app-slug", "type": "string", "required": false }, { "name": "installation_id", "flag": "installation-id", "type": "integer", "required": true }, { "name": "repository_id", "flag": "repository-id", "type": "integer", "required": true }, { "name": "disconnect", "flag": "disconnect", "type": "boolean", "required": false }], "hasComplexInput": false, "help": "Remove a GitHub repository's Forge project binding; the repository stays connected for re-binding unless disconnect is set. Owner-only and human-gated." },
   { "id": "software_factory.phase.advance", "namespace": "software_factory", "action": "phase.advance", "title": "Advance a Forge build request phase", "description": "Advance a build request to the next phase, enforcing the closed phase state machine server-side (an illegal transition is rejected). Writes a phase-run row and updates the current phase. Entitlement-gated.", "requiredScope": "tenant", "confirmation": "none", "exposeOverMcp": true, "fields": [{ "name": "build_request_id", "flag": "build-request-id", "type": "string", "required": true }, { "name": "to_phase", "flag": "to-phase", "type": "enum", "required": true, "enumValues": ["intake", "discovery_scoping", "plan_review", "implementation", "plan_conformance_review", "security_review", "qa_verification", "release_preview", "merge_or_deploy_gate", "closeout"] }, { "name": "owning_seat_id", "flag": "owning-seat-id", "type": "string", "required": false }, { "name": "note", "flag": "note", "type": "string", "required": false }], "hasComplexInput": false, "help": "Advance a build request to its next phase; the server enforces the closed phase state machine and rejects an illegal transition." },
+  { "id": "software_factory.plan.approve", "namespace": "software_factory", "action": "plan.approve", "title": "Approve a Forge plan", "description": "A human approves the current plan at the plan_review gate; records a human decision and advances the request to implementation. Owner-only and human-gated (invariant #7).", "requiredScope": "tenant_admin", "confirmation": "human_required", "exposeOverMcp": true, "fields": [{ "name": "build_request_id", "flag": "build-request-id", "type": "string", "required": true }, { "name": "rationale", "flag": "rationale", "type": "string", "required": false }], "hasComplexInput": false, "help": "A human approves the current plan at the plan_review gate; records a human decision and advances the request to implementation. Owner-only and human-gated." },
+  { "id": "software_factory.plan.reject", "namespace": "software_factory", "action": "plan.reject", "title": "Reject a Forge plan", "description": "A human rejects the current plan at the plan_review gate; records a human decision (with a required rationale) and routes the request back to discovery/scoping for re-planning. Owner-only and human-gated (invariant #7).", "requiredScope": "tenant_admin", "confirmation": "human_required", "exposeOverMcp": true, "fields": [{ "name": "build_request_id", "flag": "build-request-id", "type": "string", "required": true }, { "name": "rationale", "flag": "rationale", "type": "string", "required": true }], "hasComplexInput": false, "help": "A human rejects the current plan (with a required rationale) and routes the request back to discovery/scoping for re-planning. Owner-only and human-gated." },
   { "id": "software_factory.project.create", "namespace": "software_factory", "action": "project.create", "title": "Create a Forge project", "description": "Create an active Forge software project before binding repositories or opening build requests. Tenant-admin, human-gated, and entitlement-gated.", "requiredScope": "tenant_admin", "confirmation": "human_required", "exposeOverMcp": true, "fields": [{ "name": "name", "flag": "name", "type": "string", "required": true }, { "name": "slug", "flag": "slug", "type": "string", "required": false }, { "name": "base_branch", "flag": "base-branch", "type": "string", "required": false }, { "name": "repo_ref", "flag": "repo-ref", "type": "string", "required": false }], "hasComplexInput": false, "help": "Create an active Forge software project before binding repositories or opening build requests. Tenant-admin and human-gated; requires the Forge add-on." },
   { "id": "software_factory.project.list", "namespace": "software_factory", "action": "project.list", "title": "List Forge projects", "description": "List active Forge software projects so a tenant can choose a project for build requests, GitHub repository bindings, and config. Read-only and entitlement-gated.", "requiredScope": "tenant", "confirmation": "none", "exposeOverMcp": true, "fields": [], "hasComplexInput": false, "help": "List active Forge software projects so a tenant can choose a project for build requests, GitHub repository bindings, and config. Read-only; requires the Forge add-on." },
+  { "id": "software_factory.request.answer_clarification", "namespace": "software_factory", "action": "request.answer_clarification", "title": "Answer Forge plan clarifications", "description": "Write structured human answers to a draft plan's clarifying questions and optionally mark it ready for plan review. Answers append to the versioned planning artifact; this never widens authority or automation mode.", "requiredScope": "tenant", "confirmation": "none", "exposeOverMcp": true, "fields": [{ "name": "build_request_id", "flag": "build-request-id", "type": "string", "required": true }, { "name": "mark_ready_for_plan_review", "flag": "mark-ready-for-plan-review", "type": "boolean", "required": false }], "hasComplexInput": true, "help": "Write structured human answers to a draft plan's clarifying questions and optionally mark it ready for plan review. Never widens authority or automation mode." },
   { "id": "software_factory.request.create", "namespace": "software_factory", "action": "request.create", "title": "Create a Forge build request", "description": "Open a governed Forge build request against a connected software project. Records the request plus its initial intake phase run. Entitlement-gated (Forge add-on); the title is untrusted display text, never an instruction.", "requiredScope": "tenant", "confirmation": "none", "exposeOverMcp": true, "fields": [{ "name": "software_project_id", "flag": "software-project-id", "type": "string", "required": true }, { "name": "title", "flag": "title", "type": "string", "required": true }, { "name": "source_channel", "flag": "source-channel", "type": "enum", "required": false, "enumValues": ["ui", "cli", "github_issue", "linear", "api"] }, { "name": "source_ref", "flag": "source-ref", "type": "string", "required": false }], "hasComplexInput": true, "help": "Open a governed Forge build request against a connected software project; the title is untrusted display text. Requires the Forge add-on." },
   { "id": "software_factory.request.list", "namespace": "software_factory", "action": "request.list", "title": "List Forge build requests", "description": "The Forge control-room board: the tenant's build requests with status, current phase, and risk/automation mode. Read-only, entitlement-gated.", "requiredScope": "tenant", "confirmation": "none", "exposeOverMcp": true, "fields": [{ "name": "limit", "flag": "limit", "type": "integer", "required": false }], "hasComplexInput": false, "help": "List Forge build requests (the control-room board) with status, current phase, and risk. Read-only; requires the Forge add-on." },
   { "id": "software_factory.request.show", "namespace": "software_factory", "action": "request.show", "title": "Show a Forge build request", "description": "The Forge request detail: the build request, its current phase, phase-run history, and gates. Read-only, entitlement-gated, tenant-scoped.", "requiredScope": "tenant", "confirmation": "none", "exposeOverMcp": true, "fields": [{ "name": "build_request_id", "flag": "build-request-id", "type": "string", "required": true }], "hasComplexInput": false, "help": "Show a Forge build request's detail: current phase, phase-run history, and gates. Read-only; requires the Forge add-on." },