@paigy/harness 0.3.40 → 0.3.42

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +7 -37
  2. package/dist/cli.js +28903 -29641
  3. package/dist/main.js +329 -945
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -109,39 +109,11 @@ empty box. Note also that presence is **not** in the E2EE lane (`e2ee/flow.md` c
109
109
  notifications and responses) — which is why the publisher clips each line and shortens
110
110
  absolute paths to their last two segments before it leaves the machine.
111
111
 
112
- ## The broker has a space too
113
-
114
- > Owner, 2026-08-28: *"i feel like the desktop app also needs a space for the broker, and
115
- > the queue of things to deal with after that."*
116
-
117
- Every agent on this Mac had a face on the perch and a page behind it. **Paigy** — the one
118
- actually holding the work, since a note is a request addressed to the broker — had none,
119
- even though this is the machine its sweep runs on (`paigy-harness triage`, #1255). You
120
- could produce a proposal here and then had to pick up a phone to act on it.
121
-
122
- So the home screen gains a **broker card** (the mark, and one standing sentence: how many
123
- open notes, when it last swept, whether something is waiting on a click), and behind it a
124
- **page**:
125
-
126
- - **What Paigy suggests** — `GET /api/triage`'s open proposal, grouped exactly as the
127
- phone groups it: close, stale, and one card per hatchling with the queue it would
128
- receive underneath it. One button per group, `POST /api/triage/:id/accept` with no
129
- `noteIds` — the same endpoint the phone's button and the CLI's `--apply` hit, so the
130
- three doors cannot mean three different things by "accept". **Nothing on the page has
131
- happened**; accepting is the user's, always.
132
- - **The queue** — every open note, longest-ignored first, with its assignee and the same
133
- deterministic `why` a sweep would quote (`no movement in 40 days`). Opening a note and
134
- answering it still belongs to the phone; this is the *shape of the pile*, which is what
135
- the machine can say.
136
- - **Sweep the queue** — calls `runTriage` directly, not our own CLI: it is already a
137
- function with injected network deps, and a shell-out would read the DEFAULT `~/.paigy`
138
- slot while this window is deliberately the `Desktop` one. A refusal (no judge on this
139
- machine) stays on screen with the exact install line; a clean run's transcript goes,
140
- because the cards it just produced say it better.
141
-
142
- `src/broker.ts` is the whole read, and it computes nothing of its own: the queue is
143
- `noteSignals()` — literally the dossier the sweep judges — so the card and the proposal
144
- above it can never disagree about what "open" or "40 days idle" means.
112
+ ## Retired queue sweep
113
+
114
+ `paigy-harness triage` returns a named retirement error. The local model sweep and
115
+ the desktop broker card, proposal page and IPC have been removed; `/api/triage` remains
116
+ a retired route. No replacement grouped sweep is shipped.
145
117
 
146
118
  ## The catalog and the doctor
147
119
 
@@ -172,9 +144,7 @@ src/harness/ events.ts the neutral HarnessEvent the driver produces
172
144
  src/paigy/ level.ts event → NotifyLevel
173
145
  bridge.ts permission asks, cannot-work notices, the turn's end as Goal progress
174
146
  conversation.ts the round trip — your words into a running agent's stdin
175
- src/triage/ evidence.ts the deterministic signals; judge.ts the one model boundary
176
- verdict.ts the prompt + its defensive parser; triage.ts the sweep itself
177
- src/broker.ts what Paigy is HOLDING — the open queue + the one open proposal, one read
147
+ src/ago.ts elapsed time shown in host status
178
148
  src/run.ts the whole bridge, Electron-free — what main.ts and cli.ts both drive
179
149
  src/main.ts Electron main; renderer/ is a doctor, a form and a log
180
150
  src/cli.ts `paigy-harness` — the same bridge from a terminal or a service unit
@@ -271,7 +241,7 @@ node apps/desktop/dist/cli.js host --grant ~/projects # standby, launchable fr
271
241
  ```
272
242
 
273
243
  The window deliberately has NO run form — launching moved to the phone (docs/clients/desktop/companion.md).
274
- It shows pairing, the party, the broker's card and queue, the doctor, the workspace
244
+ It shows pairing, the party, the doctor, the workspace
275
245
  allow-list, a Stop button, and the log.
276
246
 
277
247
  Headless flags: `--harness claude|codex`, `--mode bypass|ask`, `--cwd DIR`,