@paigy/harness 0.3.2 → 0.3.3

package/README.md

@@ -101,6 +101,40 @@ empty box. Note also that presence is **not** in the E2EE lane (`e2ee/flow.md` c
 notifications and responses) — which is why the publisher clips each line and shortens
 absolute paths to their last two segments before it leaves the machine.
 
+## The broker has a space too
+
+> Owner, 2026-08-28: *"i feel like the desktop app also needs a space for the broker, and
+> the queue of things to deal with after that."*
+
+Every agent on this Mac had a face on the perch and a page behind it. **Paigy** — the one
+actually holding the work, since a note is a request addressed to the broker — had none,
+even though this is the machine its sweep runs on (`paigy-harness triage`, #1255). You
+could produce a proposal here and then had to pick up a phone to act on it.
+
+So the home screen gains a **broker card** (the mark, and one standing sentence: how many
+open notes, when it last swept, whether something is waiting on a click), and behind it a
+**page**:
+
+- **What Paigy suggests** — `GET /api/triage`'s open proposal, grouped exactly as the
+  phone groups it: close, stale, and one card per hatchling with the queue it would
+  receive underneath it. One button per group, `POST /api/triage/:id/accept` with no
+  `noteIds` — the same endpoint the phone's button and the CLI's `--apply` hit, so the
+  three doors cannot mean three different things by "accept". **Nothing on the page has
+  happened**; accepting is the user's, always.
+- **The queue** — every open note, longest-ignored first, with its assignee and the same
+  deterministic `why` a sweep would quote (`no movement in 40 days`). Opening a note and
+  answering it still belongs to the phone; this is the *shape of the pile*, which is what
+  the machine can say.
+- **Sweep the queue** — calls `runTriage` directly, not our own CLI: it is already a
+  function with injected network deps, and a shell-out would read the DEFAULT `~/.paigy`
+  slot while this window is deliberately the `Desktop` one. A refusal (no judge on this
+  machine) stays on screen with the exact install line; a clean run's transcript goes,
+  because the cards it just produced say it better.
+
+`src/broker.ts` is the whole read, and it computes nothing of its own: the queue is
+`noteSignals()` — literally the dossier the sweep judges — so the card and the proposal
+above it can never disagree about what "open" or "40 days idle" means.
+
 ## The catalog and the doctor
 
 The other thing Buzz got right: connecting a harness should be a status line and a
@@ -130,6 +164,9 @@ src/harness/   events.ts   the neutral HarnessEvent the driver produces
 src/paigy/     level.ts        event → NotifyLevel
                bridge.ts       mirror turns, ask permissions/questions, setup nudges
                conversation.ts the round trip — your words into a running agent's stdin
+src/triage/    evidence.ts the deterministic signals; judge.ts the one model boundary
+               verdict.ts  the prompt + its defensive parser; triage.ts the sweep itself
+src/broker.ts  what Paigy is HOLDING — the open queue + the one open proposal, one read
 src/run.ts     the whole bridge, Electron-free — what main.ts and cli.ts both drive
 src/main.ts    Electron main; renderer/ is a doctor, a form and a log
 src/cli.ts     `paigy-harness` — the same bridge from a terminal or a service unit
@@ -216,7 +253,8 @@ node apps/desktop/dist/cli.js host --grant ~/projects   # standby, launchable fr
 ```
 
 The window deliberately has NO run form — launching moved to the phone (companion.md).
-It shows pairing, the doctor, the workspace allow-list, a Stop button, and the log.
+It shows pairing, the party, the broker's card and queue, the doctor, the workspace
+allow-list, a Stop button, and the log.
 
 Headless flags: `--harness claude|codex`, `--mode bypass|ask`, `--cwd DIR`,
 `--identity NAME`, `--grace SECONDS`, `--doctor`; subcommands `host [--grant DIR]…`