paseo-room 0.7.0 → 0.8.0

package/README.md

@@ -483,7 +483,9 @@ vocabulary for Lead and Peer, and exactly one body per role. TypeScript selects
   that settles it rather than pre-solving the work; any plan or file list in it is provisional.
   One moving write scope has exactly one owner, and at most one Peer is writable at a time. It
   explicitly requests native Paseo completion/error/permission notification for Peer creation and
-  every background follow-up, then waits for events rather than polling. Room tools: on.
+  every background follow-up, then waits for events rather than polling. A question only Human can
+  answer goes on its own `NEEDS-HUMAN:` line, and an effect beyond the work's intended scope on an
+  `INCIDENT:` line, so neither is lost in a long message. Room tools: on.
 - **Peer** owns one bounded assignment — writable inside an assigned scope, or read-only
   against a named candidate, question or area — under exactly one disposition Lead names in the
   brief (Engineer, Architect, Reviewer or Scout), forms its own technical position from the code
@@ -621,10 +623,23 @@ npx paseo-room verify
   working.
 - **Lead** gains room tools such as `assignment_create`, `assignment_dispatch`, `assignment_answer`,
   `assignment_accept`, `gate_run`, and for isolated writers `workspace_close` and `lease_reclaim`.
+  `assignment_create` refuses a base that is not a commit of the repository (`base_unknown`).
   **Supervisor** gains `room_status`, `runtime_findings`, `message_lead` (with a `project` for a
-  Supervisor of several projects) and `attention_feedback`, and cannot change an assignment.
-- **A runtime-dispatched Peer** gets exactly two tools, `ask` and `handoff`, for its own assignment,
-  and still no Paseo room tools. A report exists only once one of those calls is accepted; its
+  Supervisor of several projects) and `attention_feedback`, and cannot change an assignment. Its
+  status and findings cover only its portfolio and the project it stands in; `room_status` lists
+  the assignments still open or still to close, and only counts settled ones.
+- **Peer thinking.** A runtime-dispatched Peer launches on its room profile's model and thinking
+  option. In **Settings › Room seats › Thinking Lead may choose** you can allow other thinking
+  options per Peer provider, from the ones Paseo lists for its model. Lead may then pass `thinking`
+  (with a `thinkingReason`) to `assignment_dispatch`, as the Lead contract directs. The runtime
+  refuses anything outside what you allowed or what the model offers, and always refuses `ultra` and
+  `ultracode`, which start agents on their own. It records the choice, shows it with the reason to
+  Supervisor and in the panel, and keeps it for a reclaimed Peer while you still allow it. The model
+  itself is never Lead's to change.
+- **A runtime-dispatched Peer** is titled `<Disposition> · <outcome gist> · <assignment id>` (for
+  example `Reviewer · Review the Docker Compose dev env… · asg_…`), and the runtime's notices to Lead
+  name the assignment the same way. It gets exactly two tools, `ask` and `handoff`, for its own
+  assignment, and still no Paseo room tools. A report exists only once one of those calls is accepted; its
   final message is never read as a report. Claude asks for permission before a Peer's first call
   to `mcp__paseo_room__ask` or `mcp__paseo_room__handoff`: approve it in Paseo, since the runtime
   never answers a permission for a seat. Codex and Pi Peers do not ask.
@@ -637,8 +652,9 @@ npx paseo-room verify
 - **The Room runtime panel** (sidebar item, and a workspace panel that opens on its own project)
   puts what needs you first. Below that come your projects, ordered by status, then your
   Supervisors.
-  - A project shows its Supervisor, its Lead and Peer seats (each opens its agent in Paseo) and its
-    runtime record: assignments, isolated writers, findings and recovery.
+  - A project shows its Supervisor, its Lead and Peer seats (each opens its agent in Paseo, and
+    shows the model and thinking option it runs with) and its runtime record: assignments, isolated
+    writers, findings and recovery.
   - Starting a Supervisor, starting a project and assigning a Supervisor are guided forms.
   - The design notes are in [docs/design/runtime-panel-ux.md](docs/design/runtime-panel-ux.md).
 - **Settings › Room seats** shows which account each seat is signed in to (email, plan and
@@ -659,15 +675,20 @@ learn only when you ask it to check.
   - They report a permission waiting on any seat for 5 minutes, and a Peer result its idle Lead has
     not read for 10 minutes.
   - They report the same failure twice in a row, and possible concurrent writers in one working
-    tree.
+    tree, naming each seat's files and when its turn ended. A write outside that tree does not
+    count.
   - They report a Lead archived while its seats still work, and a Lead's finished turn that the
     Supervisor did not prompt itself.
+  - The Lead contract has Lead put a question for you on a line beginning `NEEDS-HUMAN:` and an
+    incident on one beginning `INCIDENT:`. The first wakes the Supervisor and the second pages it,
+    even for a turn it prompted, once per line, and the letter quotes those lines rather than the
+    message's end.
   - Letters are held until the Supervisor is idle, batched into digests, and limited to a few wakes
     an hour. They are never sent while the Supervisor holds a permission, because a send would
     deny it.
-  - Each item has an id for `attention_feedback`. A letter is evidence, not an instruction: the
-    Supervisor contract has it ask or nudge the Lead, or relay a question to you, and never direct a
-    Peer.
+  - Each item has an id for `attention_feedback`, and a letter's own id rates every item in it. A
+    letter is evidence, not an instruction: the Supervisor contract has it ask or nudge the Lead, or
+    relay a question to you, and never direct a Peer.
 - **Starting seats.** From the **Room** view, **Start Supervisor** opens one in an existing directory
   outside every repository. **Start project** checks a repository, opens its Lead under the
   Supervisor you pick, and sends a fixed kickoff with your first directive verbatim. **Assign

package/dist/index.js

@@ -15,7 +15,7 @@ var init_package = __esm({
   "package.json"() {
     package_default = {
       name: "paseo-room",
-      version: "0.7.0",
+      version: "0.8.0",
       description: "One CLI that configures Codex, Claude Code, and Pi role homes in $HOME and registers them with your local Paseo daemon.",
       keywords: [
         "paseo",
@@ -691,10 +691,10 @@ async function loginRole(agentValue, roleValue, options, output) {
   const childEnv = { ...env, ...invocation.env };
   const launch = options.spawn ?? spawnLogin;
   return new Promise((resolve5) => {
-    let settled = false;
+    let settled2 = false;
     const finish = (code2) => {
-      if (settled) return;
-      settled = true;
+      if (settled2) return;
+      settled2 = true;
       resolve5(code2);
     };
     let child;
@@ -1688,20 +1688,20 @@ function runProbeProcess(executable, adapterEntry, env, options, cwd) {
     const child = spawn2(executable, args, { cwd, detached: true, env, stdio: ["pipe", "pipe", "pipe"] });
     const stdout = [];
     let bytes = 0;
-    let settled = false;
+    let settled2 = false;
     const finish = (result) => {
-      if (settled) return;
-      settled = true;
+      if (settled2) return;
+      settled2 = true;
       clearTimeout(timer);
       resolveResult(result);
     };
     const abort = (reason3) => {
-      if (settled) return;
+      if (settled2) return;
       terminateProbe(child);
       finish({ ok: false, stdout: Buffer.concat(stdout).toString("utf8"), reason: reason3 });
     };
     const capture = (chunk, keep) => {
-      if (settled) return;
+      if (settled2) return;
       bytes += chunk.length;
       if (bytes > outputLimit) {
         abort("overflow");
@@ -2841,6 +2841,7 @@ function reclaimed(view, event) {
   delete copy.peerAgentId;
   delete copy.observedProviderId;
   delete copy.observedModel;
+  delete copy.observedThinking;
   return { ...copy, state: "dispatching", reportingState: "consumed", eventIds: [...view.eventIds, event.id] };
 }
 function applyReport(state, view, event) {
@@ -2923,7 +2924,13 @@ function applyEvent(state, event) {
   const id2 = view.id;
   switch (event.type) {
     case "assignment.dispatch-requested":
-      update(state, id2, { state: "dispatching", peerProviderId: event.data.peerProviderId, workspaceId: event.data.workspaceId }, event);
+      update(state, id2, {
+        state: "dispatching",
+        peerProviderId: event.data.peerProviderId,
+        workspaceId: event.data.workspaceId,
+        ...event.data.thinking === void 0 ? {} : { chosenThinking: event.data.thinking },
+        ...event.data.thinkingReason === void 0 ? {} : { thinkingReason: event.data.thinkingReason }
+      }, event);
       return;
     case "ownership.reserved":
       state.ownership.set(id2, { assignmentId: id2, workspaceId: event.data.workspaceId, baseCommit: event.data.baseCommit, state: "reserved" });
@@ -2950,7 +2957,12 @@ function applyEvent(state, event) {
       update(state, id2, { state: "uncertain" }, event);
       return;
     case "binding.published":
-      update(state, id2, { observedProviderId: event.data.providerId, observedModel: event.data.model, workspaceId: event.data.workspaceId }, event);
+      update(state, id2, {
+        observedProviderId: event.data.providerId,
+        observedModel: event.data.model,
+        workspaceId: event.data.workspaceId,
+        ...event.data.thinking === void 0 ? {} : { observedThinking: event.data.thinking }
+      }, event);
       return;
     case "ownership.held":
       setOwner(state, id2, { state: "held", agentId: event.data.agentId });
@@ -3281,7 +3293,11 @@ var init_actions = __esm({
         ...assignment,
         peerProvider: z6.string().min(1).max(128),
         isolation: z6.enum(["lead-workspace", "worktree"]).optional(),
-        serialOnly: boundedArray(boundedString()).optional()
+        serialOnly: boundedArray(boundedString()).optional(),
+        // A thinking option the operator allows for that Peer provider, and why; omitted, the Peer
+        // launches on its profile's option (docs/design/runtime-coordination-peer-effort.md E-D2).
+        thinking: z6.string().min(1).max(64).optional(),
+        thinkingReason: boundedString(1024).optional()
       }),
       assignment_answer: z6.strictObject({ ...assignment, answer: boundedString() }),
       assignment_rework: z6.strictObject({ ...assignment, instructions: boundedString() }),
@@ -3402,7 +3418,7 @@ function readEvent(value) {
   const parsed2 = readerSchema.safeParse(value);
   return parsed2.success ? { ok: true, event: parsed2.data } : { ok: false, reason: "invalid", detail: z8.prettifyError(parsed2.error) };
 }
-var EVENT_SCHEMA, id, text2, reason2, generation2, digest2, timestamp, workspaceIdSchema, branch, epoch, scopes, gateResultSchema, NOTICE_DISPOSITIONS, NOTICE_CLASSES, EVENT_PAYLOADS, EVENT_TYPES, SUPPORTED_PAYLOAD_VERSIONS, actorSchema, envelope, firstWriter, restWriters, firstReader, restReaders, writerSchema, readerSchema;
+var EVENT_SCHEMA, id, text2, reason2, thinkingOption, generation2, digest2, timestamp, workspaceIdSchema, branch, epoch, scopes, gateResultSchema, NOTICE_DISPOSITIONS, NOTICE_CLASSES, EVENT_PAYLOADS, EVENT_TYPES, SUPPORTED_PAYLOAD_VERSIONS, actorSchema, envelope, firstWriter, restWriters, firstReader, restReaders, writerSchema, readerSchema;
 var init_schema = __esm({
   "src/runtime-plugin/server/events/schema.ts"() {
     "use strict";
@@ -3415,6 +3431,7 @@ var init_schema = __esm({
     id = z8.string().min(1).max(128);
     text2 = boundedString();
     reason2 = boundedString(1024);
+    thinkingOption = z8.string().min(1).max(64);
     generation2 = z8.number().int().min(1);
     digest2 = z8.string().regex(/^sha256:[0-9a-f]{64}$/);
     timestamp = z8.iso.datetime({ offset: true });
@@ -3449,7 +3466,8 @@ var init_schema = __esm({
       "project.ownership-resolved": { keptLeadAgentId: id, decidedBy: z8.enum(["evidence", "human"]) },
       // Assignment lifecycle decided by Lead or Human (§5.1).
       "assignment.created": { input: assignmentCreateSchema, leadAgentId: id, leadProviderId: id },
-      "assignment.dispatch-requested": { peerProviderId: id, workspaceId: id },
+      // Lead's thinking choice within the operator's envelope, and why (peer-effort delta E-D2, E-D4).
+      "assignment.dispatch-requested": { peerProviderId: id, workspaceId: id, thinking: thinkingOption.optional(), thinkingReason: reason2.optional() },
       "assignment.answered": { answer: text2 },
       "assignment.rework-requested": { instructions: text2 },
       "assignment.accepted": {
@@ -3492,7 +3510,8 @@ var init_schema = __esm({
         model: z8.string().min(1).max(256),
         parentAgentId: id,
         workspaceId: id,
-        roomGeneration: id
+        roomGeneration: id,
+        thinking: thinkingOption.optional()
       },
       "reporting.generation-opened": { generation: generation2, capabilityHash: digest2, turn: z8.enum(["initial", "answer", "rework", "follow-up"]) },
       "run.requested": { intentId: id, generation: generation2, promptDigest: digest2 },