@selesai/code 0.9.11 → 0.9.12

package/dist/extensions/pi-intercom/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-intercom",
-  "version": "0.10.0",
+  "version": "0.12.0",
   "license": "MIT",
   "type": "module",
   "main": "index.ts",

package/dist/extensions/pi-intercom/project-agent.ts

@@ -242,7 +242,7 @@ export async function openProjectPane(input: {
   const paneId = extractPaneId(split.data);
   if (!paneId) throw new Error("Herdr project pane error (PANE_GONE): pane split returned no pane id.");
 
-  const command = shellQuote(process.env.PI_INTERCOM_PI_BIN?.trim() || process.env.PI_BIN?.trim() || "pi");
+  const command = shellQuote(process.env.SELESAI_INTERCOM_BINARY?.trim() || process.env.SELESAI_BIN?.trim() || "selesai");
   const started = await client.run(["pane", "run", paneId, command], { timeoutMs: 15_000, signal: input.signal });
   if (started.ok === false) {
     await client.run(["pane", "close", paneId], { timeoutMs: 5_000 });
@@ -292,7 +292,7 @@ export async function waitForProjectSession(client: ListSessionsClient, input: {
     await sleep(pollMs, input.signal);
   }
 
-  throw new Error(`Timed out waiting for a Pi intercom session to register in ${input.projectRoot}. The Herdr pane may still be starting, or pi-intercom may not be loaded there.`);
+  throw new Error(`Timed out waiting for a Selesai intercom session to register in ${input.projectRoot}. The Herdr pane may still be starting, or  pi-intercom may not be loaded there.`);
 }
 
 function formatSessionRefs(sessions: SessionInfo[]): string {

package/dist/extensions/pi-intercom/skills/pi-intercom/SKILL.md

@@ -10,7 +10,7 @@ description: |
 # Selesai Intercom Skill
 
 Use this skill when you need to coordinate work across multiple Selesai sessions
-running on the same machine. pi-intercom enables direct 1:1 messaging between
+running on the same machine. Selesai-intercom enables direct 1:1 messaging between
 sessions for delegation, context sharing, and collaborative workflows.
 
 When you are supervising `pi-subagents`, delegated child agents can escalate to
@@ -238,99 +238,14 @@ new visible project panes should go through the supervisor.
 | `list` | Returns all sessions with live status | You need to discover targets or choose an idle peer |
 | `status` | Returns your connection state | Troubleshooting |
 
-## Optional: Visible Peer Sessions via cmux or tmux
+## Visible Peer Sessions
 
-If no suitable intercom-connected peer session already exists and the task benefits from a long-lived visible conversation, you may spawn a new `pi` session.
+For bounded cross-codebase work, prefer `pi-subagents` with an explicit `cwd`.
+Use `intercom({ action: "send", cwd: "/path", openProjectPaneIfMissing: true, ... })`
+only when a long-lived visible peer session is useful.
 
-Prefer `cmux new-split right` over new surfaces or workspaces so both sessions are visible side by side.
-
-If `cmux` is unavailable, `tmux` is an optional fallback when it is installed and relevant. Use it with a private socket so the session is isolated and observable.
-
-Use spawned peer sessions only for:
-- same-codebase worker/planner splits
-- reference-codebase scouting
-- long-lived visible conversations where the user benefits from watching both sides
-
-Do not use this for unrelated repos, trivial questions, or work you can finish cleanly in the current session.
-
-### Preferred: cmux Worker or Scout Session
-
-Same codebase:
-
-```bash
-cmux new-split right
-sleep 0.5
-cmux send --surface right 'cd /path/to/current/repo && pi\n'
-```
-
-Reference codebase:
-
-```bash
-cmux new-split right
-sleep 0.5
-cmux send --surface right 'cd /path/to/reference/repo && pi\n'
-```
-
-### Optional Fallback: tmux Worker or Scout Session
-
-Same codebase:
-
-```bash
-SOCKET_DIR=${TMPDIR:-/tmp}/pi-tmux-sockets
-mkdir -p "$SOCKET_DIR"
-SOCKET="$SOCKET_DIR/pi.sock"
-SESSION=pi-worker
-tmux -S "$SOCKET" new -d -s "$SESSION" -c "/path/to/current/repo" 'pi'
-```
-
-Reference codebase:
-
-```bash
-SOCKET_DIR=${TMPDIR:-/tmp}/pi-tmux-sockets
-mkdir -p "$SOCKET_DIR"
-SOCKET="$SOCKET_DIR/pi.sock"
-SESSION=pi-reference-auth
-tmux -S "$SOCKET" new -d -s "$SESSION" -c "/path/to/reference/repo" 'pi'
-```
-
-When you use `tmux`, tell the user how to watch it:
-
-```bash
-tmux -S "$SOCKET" attach -t "$SESSION"
-```
-
-After launch, name the new session clearly so it is easy to target:
-
-```text
-/name worker
-/name reference-auth
-```
-
-Then coordinate from the current session:
-
-```typescript
-intercom({
-  action: "send",
-  to: "worker",
-  message: "Take task X. Ask if blocked."
-})
-
-intercom({
-  action: "ask",
-  to: "reference-auth",
-  message: "How does this repo structure token refresh retries?"
-})
-```
-
-### Spawn Decision Rule
-
-Spawn a visible peer session only when all of these are true:
-- no existing intercom-connected session already fits the need
-- the work benefits from a long-lived visible peer session
-- the peer session is either in the same codebase or in an intentional reference codebase
-- `cmux` is available, or `tmux` is available as an intentional fallback
-
-If neither `cmux` nor `tmux` is available, skip this path and use normal `intercom` workflows.
+If Herdr is unavailable, do not invent a terminal fallback inside this workflow.
+Ask the user before opening another visible surface manually.
 
 ## Important Constraints
 
@@ -387,23 +302,6 @@ intercom({
 // Continue immediately, don't wait
 ```
 
-### Include reply hints in messages
-
-Make it easy for recipients to respond. Busy recipients receive your message
-through Selesai's steering queue at the next safe model boundary without aborting
-their active turn, so a reply hint keeps the conversation actionable:
-
-```typescript
-// GOOD: Recipient sees exact command to reply
-intercom({
-  action: "send",
-  to: "worker",
-  message: `Found the issue in auth.ts:142. Use getUserById() instead of getUser().
-
-Reply with: intercom({ action: "reply", message: "..." })`
-});
-```
-
 ### Name sessions meaningfully
 
 Use `/name` so others can target you easily:
@@ -472,7 +370,7 @@ if (!result.delivered) {
 
 ### Connection lost
 
-Sessions automatically reconnect if the broker restarts. A liveness heartbeat round-trips a lightweight request and tears down half-open sockets (for example after the broker is killed without a clean shutdown), so the `disconnected` → reconnect path fires within a bounded window. If persistently disconnected:
+Sessions automatically reconnect if the broker restarts. If persistently disconnected:
 
 ```typescript
 intercom({ action: "status" })

package/dist/extensions/pi-intercom/types.ts

@@ -1,7 +1,19 @@
 export const EXTENSION_BUS_FEATURE = "extension-bus-v1";
+export const EXACT_SEND_FEATURE = "exact-send-v1";
+
+export type DeliveryState = "socket_delivered" | "queued" | "failed" | "unknown";
+
+export interface DeliveryDetails {
+  delivery: DeliveryState;
+  code?: string;
+  retryable: boolean;
+  outcomeKnown: boolean;
+}
 
 export interface SessionInfo {
   id: string;
+  /** Broker-owned lifetime of this live endpoint. */
+  endpointEpoch?: string;
   name?: string;
   /** True only when the extension synthesized name for an unnamed runtime. */
   runtimeFallbackAlias?: boolean;
@@ -21,6 +33,13 @@ export interface SessionInfo {
   contextPct?: number;
   contextTokens?: number;
   contextWindow?: number;
+  /** tmux pane id (e.g. "%212") of the session's terminal, read from
+   *  $TMUX_PANE at registration. Present only when the session runs inside a
+   *  tmux pane; absent for cloud, headless, IDE-embedded, or Herdr sessions.
+   *  The pane id is immutable for the process lifetime — unlike the window
+   *  name, which is mutable — so a peer can live-resolve the current window
+   *  from it via tmux when it needs to introspect or drive that pane. */
+  tmuxPane?: string;
 }
 
 export interface Message {
@@ -35,12 +54,20 @@ export interface Message {
   retryOf?: string;
   replyTo?: string;
   expectsReply?: boolean;
+  provenance?: MessageProvenance;
   content: {
     text: string;
     attachments?: Attachment[];
   };
 }
 
+export interface MessageProvenance {
+  type: "extension_outbox";
+  extensionId: string;
+  extensionName: string;
+  requestId: string;
+}
+
 export interface Attachment {
   type: "file" | "snippet" | "context";
   name: string;
@@ -72,16 +99,16 @@ export interface ExtensionCapability {
   ownerEligible: boolean;
 }
 
-export type SessionRegistration = Omit<SessionInfo, "id" | "peerUid" | "trustedLocal"> & {
+export type SessionRegistration = Omit<SessionInfo, "id" | "endpointEpoch" | "peerUid" | "trustedLocal"> & {
   extensions?: ExtensionCapability[];
 };
 
 export type ClientMessage =
-  | { type: "register"; session: SessionRegistration; sessionId?: string; stateId?: string }
+  | { type: "register"; session: SessionRegistration; sessionId?: string; stateId?: string; scopeId?: string }
   | { type: "unregister" }
   | { type: "extension_capabilities_update"; extensions: ExtensionCapability[] }
   | { type: "list"; requestId: string }
-  | { type: "send"; to: string; message: Message }
+  | { type: "send"; to: string; message: Message; targetId?: string; targetEpoch?: string }
   | { type: "message_receipt"; receipt: MessageReceipt }
   | { type: "cancel_message"; messageId: string }
   | { type: "cancel_ask"; messageId: string }
@@ -110,8 +137,8 @@ export type BrokerMessage =
   | { type: "session_joined"; session: SessionInfo }
   | { type: "session_left"; sessionId: string }
   | { type: "error"; error: string }
-  | { type: "delivered"; messageId: string }
-  | { type: "delivery_failed"; messageId: string; reason: string }
+  | ({ type: "delivered"; messageId: string } & DeliveryDetails)
+  | ({ type: "delivery_failed"; messageId: string; reason: string } & DeliveryDetails)
   | { type: "message_receipt"; from: SessionInfo; receipt: MessageReceipt }
   | { type: "message_control"; from: SessionInfo; control: MessageControl }
   | { type: "extension_owner"; namespace: string; ownerId?: string; ownerEpoch?: string }

package/dist/extensions/pi-intercom/ui/inline-message.ts

@@ -67,6 +67,7 @@ export class InlineMessageComponent implements Component {
         const count = this.message.content.attachments.length;
         meta.push(`${count} attachment${count === 1 ? "" : "s"}`);
       }
+      if (this.message.provenance?.type === "extension_outbox") meta.push(`Via ${this.message.provenance.extensionName}`);
       if (this.message.replyTo && !this.message.expectsReply) meta.push(`Reply to ${this.message.replyTo.slice(0, 8)}`);
       meta.push("Ctrl+O to expand");
 
@@ -105,6 +106,11 @@ export class InlineMessageComponent implements Component {
       lines.push(frameLine(this.theme.fg("dim", ` Reply to ${this.message.replyTo.slice(0, 8)}`)));
     }
 
+    if (this.message.provenance?.type === "extension_outbox") {
+      lines.push(frameLine(""));
+      lines.push(frameLine(this.theme.fg("dim", ` Via extension: ${this.message.provenance.extensionName}`)));
+    }
+
     lines.push(this.theme.fg("muted", `╰${borderChar.repeat(bodyWidth)}╯`));
 
     return lines;

package/dist/extensions/pi-subagents/.github/workflows/release.yml

@@ -0,0 +1,28 @@
+name: Release
+
+on:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  id-token: write
+
+concurrency:
+  group: release-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
+        with:
+          node-version: 24
+          registry-url: https://registry.npmjs.org
+      - name: Install devDependencies
+        run: npm ci --ignore-scripts
+      - name: Run tests
+        run: npm run test:all
+      - name: Publish to npm
+        run: npm publish --provenance

package/dist/extensions/pi-subagents/.github/workflows/test.yml

@@ -0,0 +1,51 @@
+name: Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+      fail-fast: false
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
+        with:
+          node-version: 24
+      - name: Install devDependencies
+        run: npm ci --ignore-scripts
+      - name: Typecheck
+        run: npm run typecheck
+      - name: Unit tests
+        run: npm test
+      - name: Integration tests
+        timeout-minutes: 10
+        run: npm run test:integration
+      - name: E2E tests
+        timeout-minutes: 5
+        run: npm run test:e2e
+
+  bun-workflow-script:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
+        with:
+          node-version: 24
+      - uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+      - name: Install devDependencies
+        run: npm ci --ignore-scripts
+      - name: WorkflowScript Bun parity tests
+        run: >-
+          bun test test/unit/scripted-workflow.test.ts
+          --test-name-pattern "portable workflow parity|regex literals|template expressions|portable plain helper|nested plain helper|unawaited child launch|unawaited runs.all|directly returned runs.run|docs-style awaited|awaited native Promise|Promise.resolve|Promise.all|then chain|new Promise wrapper"

package/dist/extensions/pi-subagents/.greptile/config.json

@@ -0,0 +1,33 @@
+{
+  "instructions": "Follow the tracked review policy in .greptile/rules.md. Prefer concrete release-risk findings over speculative improvements. Do not describe a PR as safe to merge or merge-ready unless required changelog credit, focused validation, and exact-head CI gates are satisfied.",
+  "rules": [
+    {
+      "id": "release-risk-findings-only",
+      "rule": "Report only concrete, reachable release risks, direct contract contradictions, or clear local simplifications. Avoid speculative hardening, broad rewrites, and future-proofing suggestions.",
+      "severity": "high"
+    },
+    {
+      "id": "merge-ready-gates",
+      "rule": "Do not state that a PR is safe to merge or merge-ready unless required contributor credit, focused validation, and required CI on the exact PR head are present. If one is missing, call it out as a merge gate rather than a code defect.",
+      "severity": "high"
+    },
+    {
+      "id": "external-contributor-credit",
+      "rule": "When a change includes a CHANGELOG.md entry for material external contributor work, the entry must visibly credit the contributor with their GitHub login/name and PR or issue number, for example: Thanks to @login for #123.",
+      "scope": ["CHANGELOG.md"],
+      "severity": "high"
+    },
+    {
+      "id": "portable-tests",
+      "rule": "Tests must be portable across macOS, Linux, and Windows. Avoid machine-specific absolute Pi/TUI install paths, isolate both HOME and USERPROFILE when testing home-directory behavior, and prefer deterministic filesystem failures over POSIX chmod permission assumptions.",
+      "scope": ["test/**"],
+      "severity": "medium"
+    },
+    {
+      "id": "preserve-error-signals",
+      "rule": "Do not hide useful error signals by wrapping throwing/rejecting code into null, defaults, or less-informative results unless the surrounding code already uses a Result-style contract.",
+      "scope": ["src/**"],
+      "severity": "medium"
+    }
+  ]
+}

package/dist/extensions/pi-subagents/.greptile/files.json

@@ -0,0 +1,8 @@
+{
+  "files": [
+    {
+      "path": "CHANGELOG.md",
+      "description": "Unreleased changelog entries used to verify visible contributor credit for material changes."
+    }
+  ]
+}

package/dist/extensions/pi-subagents/.greptile/rules.md

@@ -0,0 +1,16 @@
+# pi-subagents review rules
+
+Only report findings that identify a concrete, reachable release risk, direct contract contradiction, or clear local simplification. Avoid speculative hardening, broad rewrites, optional future-proofing, and unsupported edge-case warnings.
+
+Before describing a PR as safe to merge or merge-ready, verify the process gates that matter for this repository:
+
+- material external contributors are credited in `CHANGELOG.md` or release notes with login/name and PR or issue number;
+- focused validation is present for changed behavior;
+- required CI has run on the exact PR head;
+- docs and tests match the actual runtime behavior.
+
+If a process gate is missing, report it as a merge gate rather than a code defect.
+
+For tests, prefer narrow changed-file or focused regressions. Do not request broad integration or E2E coverage unless the change actually crosses that behavior boundary.
+
+For TypeScript changes, preserve existing error signals and local project patterns. Avoid wrappers that turn useful errors into `null`, defaults, or less-informative results.