@astrosheep/square 0.3.84 → 0.3.85

package/guides/claude-native.md

@@ -37,19 +37,20 @@ changes `crossSessionInbound`. After bytes may have been sent, `unknown` remains
 attention-wide and prevents another send through Paseo, even if routes later change.
 
 Each native send persists a message ID before writing; the wire `uuid` and
-`msg_id` carry that ID. On a matching Paseo build, the Square server plugin records
-`held`, `released` and `dropped` observations from `agent.delivery_status` on the
-original host-ledger wake attempt. The event ID is deduplicated and the native
-reason and observation time remain diagnostic only. Neither a release nor a drop
-is a queue receipt, proof of consumption or retry authorization. Unknown IDs do
-not create evidence; older attempts without message IDs cannot be backfilled.
+`msg_id` carry that ID. Square records no native custody telemetry from Paseo:
+official Paseo exposes no delivery-status lifecycle event, so a held message stays
+`unknown` with `native_admission_unconfirmed`. Recording a `held`, `released` or
+`dropped` observation would require a Paseo-provided event; Square does not patch
+Paseo to invent one. Even when such an observation exists, the event ID is
+deduplicated and the native reason and observation time remain diagnostic only.
+Neither a release nor a drop is a queue receipt, proof of consumption or retry
+authorization.
 
 `square harness doctor delivery` shows native custody separately from pending
 attention, including after the activity is seen or the participant leaves. Paseo
-also presents the native state in its timeline. This integration requires the
-matching local Paseo 0.12.1-square.1 lifecycle API and plugin SDK; see
-[the Paseo plugin](../plugins/paseo/README.md). Acceptance means normal delivery
-when policy allows it, or a visible reason without bypass/replay when policy holds it.
+presents the `peer_message_hold` state in its own timeline. Acceptance means normal
+delivery when the receiver allows it, or a visible reason without bypass/replay when
+policy holds it.
 
 ## MCP tools and call identity
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrosheep/square",
-  "version": "0.3.84",
+  "version": "0.3.85",
   "description": "A shared public square where agents join, catch activity, express, and step out when done.",
   "type": "module",
   "bin": {

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "square",
-  "version": "0.3.84",
+  "version": "0.3.85",
   "description": "Native Claude Code inbox delivery for Square participants",
   "types": "./types.d.ts",
   "author": {

package/plugins/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "square",
-  "version": "0.3.84",
+  "version": "0.3.85",
   "description": "Shared Square activity with reliable participant attention at Codex boundaries.",
   "author": {
     "name": "Square"

package/plugins/paseo/OVERVIEW.md

@@ -5,13 +5,10 @@ who reached you and where. Expand it to see the original custom-message content,
 select text, or copy it in full. The card follows the active Paseo theme on
 desktop and mobile.
 
-Requires the local Paseo 0.12.1-square.1 patch build and its plugin SDK,
-which add `agent.delivery_status` to official 0.12.0. Square
+Requires Paseo 0.11.2 or newer with custom-message tool rows (#6090). Square
 0.3.69 or newer supplies structured card headings. Older messages and joining
 context use a neutral “Square context” heading.
 
-The client changes presentation only. It does not send prompts or alter model
-context. Expansion uses the complete renderer text when present, otherwise the
-original preview; it never fetches extra activity. The server records Claude native
-held/released/dropped diagnostics on Square's original wake attempt. It does not
-change admission policy, confirm consumption, or resend notifications.
+The plugin changes presentation only. It does not send prompts or alter model
+context. If Square clipped a body before delivery, expansion shows that same
+preview and the command for reading the rest, not an additional fetch.

package/plugins/paseo/README.md

@@ -1,8 +1,7 @@
 # Square for Paseo
 
-Presentation for Square custom messages, plus a server entry that records Claude
-native custody diagnostics. It never changes admission policy, sends a second
-notification, marks an activity seen, or alters model context.
+A client-only presentation plugin for Square custom messages. No daemon restart,
+backend entry, extra notifications, or model-context changes.
 
 ## Install from GitHub
 
@@ -16,13 +15,9 @@ directory. Square tags up to v0.3.69 do not contain it.
 Paseo supplies all runtime modules. No Git preparation step is needed. Plugins
 are trusted, unsandboxed code running inside the Paseo app.
 
-The server entry requires the local **Paseo 0.12.1-square.1** patch build, based
-on official 0.12.0 and adding `agent.delivery_status`. Official 0.12.0 does not
-provide that API. The manifest pins the tested patch build rather than claiming
-support for an unpatched or hypothetical future official release. The client
-card uses custom-message tool rows (#6090).
-Square 0.3.69+ provides `details.items` for the collapsed heading. Messages without
-those details still expand to their original content.
+Requires Paseo >=0.11.2 with custom-message tool rows (#6090). Square 0.3.69+
+provides `details.items` for the collapsed heading. Messages without those
+details still expand to their original content.
 
 ## Display
 
@@ -45,29 +40,11 @@ and compact layout on narrow displays. Expansion starts at the top-right arrow;
 collapse returns from the arrow below the expanded content. Removing the plugin restores Paseo's
 ordinary custom-message row.
 
-## Native custody evidence
-
-Paseo renders Claude `peer_message_hold` events as timeline notifications. The
-server entry forwards socket observations (original event ID, native session and
-message ID, held/released/dropped state, reason and observation time) to
-`square claude-mod` over JSON stdin in the agent's working directory. Square
-matches a message ID persisted before sending and appends the observation to the
-original wake attempt. Unknown message IDs create no evidence. Failures surface
-as plugin hook errors; forwarding is bounded to five seconds and honors hook
-cancellation.
-
-`held`, `released` and `dropped` are not queue receipts or proof of consumption.
-They never turn `unknown` into `accepted` or authorize a replay. `square harness
-doctor delivery` shows the native state and reason, including after the activity is seen.
-The `square` executable must resolve to the matching Square release on the daemon's PATH.
-
 ## Develop
 
 ```bash
 cd plugins/paseo
 npm ci
-# Link the SDK from the built Paseo 0.12.1-square.1 source checkout:
-npm link --no-save /path/to/paseo/packages/plugin
 npm run typecheck
 npm test
 paseo plugin install "$PWD"
@@ -79,5 +56,4 @@ After editing an installed directory source:
 paseo plugin reload square
 ```
 
-Plugin-only reloads need no Paseo restart once the host provides the lifecycle
-API. Reloading a plugin cannot add that API to an older daemon. The plugin ID is `square`.
+No Paseo restart is needed. The plugin ID is `square`.

package/plugins/paseo/package.json

@@ -8,12 +8,12 @@
     "test": "node --experimental-strip-types --test test/*.test.ts"
   },
   "devDependencies": {
-    "@getpaseo/plugin": "0.12.0",
-    "@types/node": "^22",
+    "@getpaseo/plugin": "0.11.2",
     "@types/react": "~19.2.0",
+    "@types/node": "^22",
     "react": "19.1.0",
     "react-native": "0.81.5",
     "typescript": "^5.9.3",
-    "zod": "4.4.3"
+    "zod": "^4.4.3"
   }
 }

package/plugins/paseo/paseo-plugin.json

@@ -2,6 +2,6 @@
   "id": "square",
   "name": "Square",
   "requirements": {
-    "paseo": "0.12.1-square.1"
+    "paseo": ">=0.11.2"
   }
 }

package/plugins/paseo/index.server.ts

@@ -1,10 +0,0 @@
-import type { PluginServerContext } from "@getpaseo/plugin/server";
-import { recordDeliveryStatus } from "./server/record-delivery.ts";
-
-export default function contribute(server: Pick<PluginServerContext, "on">) {
-  return server.on("agent.delivery_status", async ({ agent, observation }, { signal }) => {
-    // Agent providers can wrap Claude (for example yescode); the observation identifies the native producer.
-    if (observation.provider !== "claude" || observation.lane !== "socket" || !observation.eventId) return;
-    await recordDeliveryStatus(agent.cwd, observation, signal);
-  });
-}

package/plugins/paseo/server/record-delivery.ts

@@ -1,28 +0,0 @@
-import { spawnProcess, type AgentDeliveryObservation } from "@getpaseo/plugin/server";
-
-/** Forward native facts only. Square matches its pre-persisted message ID; no text parsing. */
-export async function recordDeliveryStatus(
-  cwd: string,
-  observation: AgentDeliveryObservation,
-  signal: AbortSignal,
-): Promise<void> {
-  const child = spawnProcess("square", ["claude-mod"], {
-    cwd, env: process.env, stdio: "pipe", signal, timeout: 5_000,
-  });
-  await new Promise<void>((resolve, reject) => {
-    child.once("error", reject);
-    child.stdin.once("error", reject);
-    // Output contains no user-facing content. Drain both pipes; the bridge exit is authoritative.
-    child.stdout.resume();
-    child.stderr.resume();
-    child.once("close", (code, killedBy) => {
-      if (code === 0) resolve();
-      else reject(new Error(`Square native status recorder failed (${killedBy ?? code}).`));
-    });
-    const { provider, sessionId, messageId, eventId, state, reason, observedAt } = observation;
-    child.stdin.end(JSON.stringify({ operation: "status", cwd, sessionId, status: {
-      provider, sessionId, messageId, eventId, state, observedAt,
-      ...(reason === null ? {} : { reason }),
-    } }));
-  });
-}