paseo-room 0.8.0 → 0.9.0

package/README.md

@@ -278,9 +278,9 @@ recreate an existing Claude session after setup or an update.
 have none. Only the contract is dropped, never your own memory, and an earlier generation of it
 is removed rather than left behind. The choice is recorded in `room.json`, so `verify` compares
 against it and rejects the flag itself; `setup` without the flag restores the fallback. Keep the
-fallback unless you have a reason not to: the plugin hook is verified, and on Paseo 0.9.1 a
-*resumed* session was observed to keep the room prompt, but that is not proven for every
-supported version or for what the model actually reads, and `CLAUDE.md` is what covers that case.
+fallback unless you have a reason not to: the plugin hook is verified, and a *resumed* session
+keeps the room prompt it was created with (on Paseo 0.9.2 a daemon restart does not refresh it),
+but what the model actually reads is not proven, and `CLAUDE.md` is what covers that case.
 
 Pi providers use a strict command tail:
 
@@ -406,8 +406,10 @@ npx paseo-room@<new-version> verify
 First inspect the dry run, then apply it. The apply regenerates managed prompt carriers,
 the Codex model catalogs and `AUTHENTICATION.md` from the newly resolved binaries, but
 preserves role credential paths and the operator agent homes. Stop and restart every affected
-seat after the apply; sending another turn to an already-running seat is not a restart.
-`setup` and `verify` prove the files and live Paseo configuration, not that an existing model
+seat after the apply; sending another turn to an already-running seat is not a restart. A
+Claude seat keeps the contract Paseo stored when it was created, and a daemon restart resumes it
+with that same prompt, so for Claude open a new seat instead. `setup` and `verify` prove the
+files and live Paseo configuration, not that an existing model
 context reloaded them. Only a newly launched seat context is expected to ingest the
 regenerated instructions.
 
@@ -624,6 +626,11 @@ npx paseo-room verify
 - **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`).
+  `gate_run` runs in the background, and a notice tells Lead when the gate ends, green, red or
+  without a trustworthy result.
+  `assignment_status` leaves out the brief Lead wrote (its outcome stays), keeps the last 10 history
+  entries, and gives a decided assignment with nothing left to close one line, unless Lead passes
+  `full: true`.
   **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. Its
   status and findings cover only its portfolio and the project it stands in; `room_status` lists
@@ -636,6 +643,16 @@ npx paseo-room verify
   `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.
+- **Seat context.** The panel and each seat's role pill show how full the seat's context is, as
+  Paseo reports it for the latest model call, and when the runtime last saw it compact. **Settings ›
+  Room seats › Seat context** sets marks per role, as a share of each seat's own model window:
+  - *Lead · report at* (30%): past it, the Lead's Supervisor gets one fact line and the panel shows
+    it with **Replace Lead…**, so you can hand over to a fresh Lead rather than let this one compact.
+  - *compact at* (Lead 50%, Supervisor and Peer off): a room Claude seat gets
+    `CLAUDE_CODE_AUTO_COMPACT_WINDOW` when its session opens, at creation or on a resume after a
+    daemon restart, so Claude compacts at that share instead of near the end of a 1M window. An open
+    session keeps what it opened with. Codex and Pi seats show their context and keep their own
+    compaction.
 - **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
@@ -655,7 +672,8 @@ npx paseo-room verify
   - 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.
+  - Starting a Supervisor, adding a repository, starting a Lead for a project that has none, 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
   organization for Claude; login method for Codex; for Pi, only whether a credential file exists).
@@ -679,6 +697,7 @@ learn only when you ask it to check.
     count.
   - They report a Lead archived while its seats still work, and a Lead's finished turn that the
     Supervisor did not prompt itself.
+  - They report, in a digest, a Lead whose context passes the rotation mark, once per crossing.
   - 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
@@ -689,10 +708,32 @@ learn only when you ask it to check.
   - 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
-  Supervisor** moves an existing project under a Supervisor.
+- **Starting seats.** From the **Room** view, **New Supervisor** opens one in an existing directory
+  outside every repository. **Add repository** checks a repository, opens its Lead under the
+  Supervisor you pick, and sends a fixed kickoff with your first directive verbatim; it also offers
+  the projects the room observes without a Lead. A project with no live Lead offers **Start Lead**
+  on its own screen, with its Supervisor preselected. **Assign Supervisor** moves an existing
+  project under a Supervisor.
+- **Replacing a Lead.** **Replace Lead…** above a project's seats, or on a *context past rotation
+  mark* item, hands the project to a fresh Lead:
+  - It checks for a quiet point first: the Lead idle, every runtime assignment it leads settled, no
+    runtime notice waiting for it, no seat it opened still working. It also shows what Paseo's
+    archive does to each seat the Lead opened: those in its workspace are archived with it, and one
+    in another workspace or open in a tab is detached and kept.
+  - It asks the Lead for a handoff in fixed sections, and you review and edit it. Nothing is
+    archived until you confirm, and you may cancel until then.
+  - On **Replace Lead**, the runtime archives the Lead and starts `<repository> — Lead` with the same
+    agent under the same Supervisor. The new Lead's first message is the kickoff and your reviewed
+    handoff, verbatim, and it verifies the handoff and reports to you before it acts outside the
+    repository. The Supervisor gets one line naming the new Lead.
+  - The handoff stays on this machine, under `~/.paseo-room/runtime/v1/attention/successions/`,
+    owner-only and never sent to the sensor or in a letter. Finished replacements are pruned after 30
+    days.
+  - If the replacement stops after the archive, the project offers **Finish replacing Lead**, which
+    creates no second Lead, or cancel, which leaves the project as it is. A replacement that fails
+    before the archive stays on the project's screen for a day, with the reason.
+  - Paseo archives the seats in the Lead's workspace with it; the runtime archives them too when the
+    Lead is not running, when Paseo would take none.
 - **Settings › Room attention.** Here you turn letters on or off, change their thresholds, and
   configure the optional **attention sensor**.
   - The sensor speaks the System One HTTP shape, with [TypeSafe Jev](https://docs.typesafe.ai/)

package/dist/index.js

@@ -15,7 +15,7 @@ var init_package = __esm({
   "package.json"() {
     package_default = {
       name: "paseo-room",
-      version: "0.8.0",
+      version: "0.9.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",
@@ -870,6 +870,11 @@ var init_prompts = __esm({
       pi: {
         communicationStyle: { path: "pi/communication-style.md", kind: "capsule" },
         runtime: { path: "pi/runtime.md", kind: "capsule" }
+      },
+      /** Messages the runtime plugin sends a Lead on Human's instruction; setup renders them into the plugin. */
+      runtime: {
+        handoffRequest: { path: "runtime/handoff-request.md", kind: "section" },
+        successorKickoff: { path: "runtime/successor-kickoff.md", kind: "section" }
       }
     };
     PromptAssetError = class extends Error {
@@ -2417,6 +2422,21 @@ function renderRuntimeManifestFile(agents, roles) {
   return `${JSON.stringify(renderRuntimeManifest(agents, roles), null, 2)}
 `;
 }
+function renderSuccessionText() {
+  return [
+    "/** Generated by paseo-room setup. The Markdown prompt assets remain authoritative. */",
+    "export interface SuccessionText {",
+    "  readonly request: string;",
+    "  readonly kickoff: string;",
+    "}",
+    "",
+    "export const SUCCESSION_TEXT: SuccessionText | undefined = {",
+    `  request: ${typescriptTemplateLiteral(loadPromptAsset("runtime", "handoffRequest"))},`,
+    `  kickoff: ${typescriptTemplateLiteral(loadPromptAsset("runtime", "successorKickoff"))},`,
+    "};",
+    ""
+  ].join("\n");
+}
 function renderRuntimeLocation(layout) {
   const location = { pluginDirectory: runtimePluginDir(layout), runtimeRoot: join12(layout.roomHome, "runtime", "v1") };
   return [
@@ -2448,22 +2468,25 @@ function runtimePluginEntries(layout, agents, roles) {
     ...files.map((path) => ({
       kind: "file",
       path: join12(root, path),
-      content: path === LOCATION_MODULE ? renderRuntimeLocation(layout) : readFileSync4(join12(BUNDLE, path), "utf8")
+      content: path === LOCATION_MODULE ? renderRuntimeLocation(layout) : path === SUCCESSION_MODULE ? renderSuccessionText() : readFileSync4(join12(BUNDLE, path), "utf8")
     })),
     { kind: "file", path: join12(root, MANIFEST_FILE), content: renderRuntimeManifestFile(agents, roles) }
   ];
 }
-var BUNDLE, LOCATION_MODULE;
+var BUNDLE, LOCATION_MODULE, SUCCESSION_MODULE;
 var init_runtime = __esm({
   "src/runtime.ts"() {
     "use strict";
+    init_plugin();
     init_roles();
     init_instructions();
+    init_prompts();
     init_manifest();
     init_identity();
     init_policy();
     BUNDLE = fileURLToPath(new URL("./runtime-plugin/", import.meta.url));
     LOCATION_MODULE = "server/generated/location.ts";
+    SUCCESSION_MODULE = "server/generated/succession.ts";
   }
 });
 
@@ -2481,7 +2504,7 @@ function boundedString(max = MAX_STRING_BYTES) {
 function boundedArray(item) {
   return z4.array(item).max(MAX_ARRAY_ITEMS);
 }
-var MAX_AGGREGATE_BYTES, MAX_ARRAY_ITEMS, MAX_STRING_BYTES, MAX_COMMAND_BYTES, MAX_GATE_TIMEOUT_SECONDS, encoder, MAX_WORKTREE_LEASES;
+var MAX_AGGREGATE_BYTES, MAX_ARRAY_ITEMS, MAX_STRING_BYTES, MAX_COMMAND_BYTES, MAX_GATE_TIMEOUT_SECONDS, MAX_HANDOFF_BYTES, encoder, MAX_WORKTREE_LEASES;
 var init_limits = __esm({
   "src/runtime-plugin/shared/limits.ts"() {
     "use strict";
@@ -2490,6 +2513,7 @@ var init_limits = __esm({
     MAX_STRING_BYTES = 8 * 1024;
     MAX_COMMAND_BYTES = 16 * 1024;
     MAX_GATE_TIMEOUT_SECONDS = 3600;
+    MAX_HANDOFF_BYTES = 64 * 1024;
     encoder = new TextEncoder();
     MAX_WORKTREE_LEASES = 3;
   }
@@ -3311,7 +3335,7 @@ var init_actions = __esm({
       assignment_reject: z6.strictObject({ ...assignment, reason }),
       assignment_abandon: z6.strictObject({ ...assignment, reason }),
       assignment_close: z6.strictObject(assignment),
-      assignment_status: z6.strictObject({ assignmentId: assignmentIdSchema.optional() }),
+      assignment_status: z6.strictObject({ assignmentId: assignmentIdSchema.optional(), full: z6.boolean().optional() }),
       gate_run: z6.strictObject(assignment),
       // Discarding a retained worktree's uncommitted work is Lead's explicit decision, with a reason.
       workspace_close: z6.strictObject({ ...assignment, discardUncommitted: z6.literal(true).optional(), reason: reason.optional() }).refine((input) => input.discardUncommitted !== true || input.reason !== void 0, { message: "discardUncommitted needs a reason", path: ["reason"] }),