@mjasnikovs/pi-task 0.16.0 → 0.16.2
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.
- package/README.md +6 -5
- package/dist/remote/server.js +24 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
[](https://www.npmjs.com/package/@mjasnikovs/pi-task)
|
|
10
10
|
[](./LICENSE)
|
|
11
11
|
[](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)
|
|
12
|
-
[](#development)
|
|
13
13
|
[](./tsconfig.json)
|
|
14
14
|
|
|
15
15
|
</div>
|
|
@@ -36,7 +36,7 @@ Every phase boundary is written to `.pi-tasks/TASK_NNNN.md`, so a task survives
|
|
|
36
36
|
pi install npm:@mjasnikovs/pi-task
|
|
37
37
|
```
|
|
38
38
|
|
|
39
|
-
> Requires [`pi`](https://www.npmjs.com/package/@earendil-works/pi-coding-agent) (the Earendil coding agent) ≥ 0.
|
|
39
|
+
> Requires [`pi`](https://www.npmjs.com/package/@earendil-works/pi-coding-agent) (the Earendil coding agent) ≥ 0.80.
|
|
40
40
|
|
|
41
41
|
## Slash commands
|
|
42
42
|
|
|
@@ -49,7 +49,7 @@ pi install npm:@mjasnikovs/pi-task
|
|
|
49
49
|
| `/task-auto <feature>` | Plan a feature into a task list and run each title through `/task` in order (resumable). |
|
|
50
50
|
| `/task-auto-resume` | Resume the active `/task-auto` run at the next unfinished task. |
|
|
51
51
|
| `/task-auto-cancel` | Stop the `/task-auto` loop after the current task (still resumable). |
|
|
52
|
-
| `/task-config` | Toggle pi-task settings in an editor dialog: remote server, compress reasoning, auto-commit, orientation, and enforce guidelines. |
|
|
52
|
+
| `/task-config` | Toggle pi-task settings in an editor dialog: remote server, compress reasoning, auto-commit, orientation, verify work, and enforce guidelines. |
|
|
53
53
|
| `/remote` | Show the QR code & URLs for the web view (`/remote stop` to stop). Answer grill questions, start tasks, and watch progress from your phone. |
|
|
54
54
|
|
|
55
55
|
## The pipeline
|
|
@@ -148,7 +148,8 @@ Run `/task-config` to toggle pi-task's behavior in an editor dialog. Settings pe
|
|
|
148
148
|
| **compress reasoning** | After each message, compresses the model's `<think>` blocks down to the decisions/constraints/facts that matter later — keeping long local-model runs from drowning their own context in self-talk. |
|
|
149
149
|
| **auto-commit** | Snapshots the working tree into one git commit per `/task-auto` sub-task (see above). |
|
|
150
150
|
| **orientation** | Pre-reads the project's core files (manifest, config, domain types, schema, entrypoints, API surface) once and hands the contents to the read-heavy research workers, so they skip re-discovering the same files cold. Bounded by a hard byte budget; applied only where it helps (FILES/APIS workers). |
|
|
151
|
-
| **
|
|
151
|
+
| **verify work** _(off by default)_ | After a `/task-auto` task implements — but **before** it's checked off or committed — actually **runs** the spec's own `VERIFY` block in the real workspace. pi-task otherwise only _authors_ a VERIFY block and never executes it, so a task that doesn't build is indistinguishable from one that works. A fresh `read` + `bash` child of the same local model runs the declared check, observes the real output, and reports **PASS/FAIL** (a legitimately no-op VERIFY is a PASS). On FAIL the run doesn't dead-stop: you get a boxed picker — **Autofix** (re-run the implementation turn against the failure, then re-verify; no attempt cap) or **Accept** (override a misjudged artifact) — and dismissing it pauses the run, resumable. A genuine clean pass is also the behavioral signal that lets **enforce guidelines** fix in place (see below). Adds one extra local-model pass per task, so it's opt-in. |
|
|
152
|
+
| **enforce guidelines** _(off by default)_ | After each `/task-auto` task is committed, re-checks that commit's work against the project's `AGENTS.md` / `CLAUDE.md` (in the working directory). A bare fix-in-place pass trashes working code (A/B-proven), so enforcement is gated on the **verify work** signal. **With** a genuine verify pass: a fresh `read` + `edit` child of the same local model reads the **last commit's** diff and fixes violations in place; its fixes are committed **separately** as an `ENFORCE GUIDELINES` commit, then the verify signal is re-run against the enforced tree — a regression **reverts** the enforce commit and keeps the verified work. **Without** that signal (verify off, no spec, or an accept-override): the pass runs read-only and only **reports** violations, never rewrites logic. Either way a violation it can't clear (or a pass that can't run) only **warns** — the task commit already landed, so the run continues. Skipped when nothing was committed for the task. |
|
|
152
153
|
|
|
153
154
|
## Configuration
|
|
154
155
|
|
|
@@ -167,7 +168,7 @@ Tasks are persisted to `<cwd>/.pi-tasks/TASK_NNNN.md`. Add `.pi-tasks/` to your
|
|
|
167
168
|
|
|
168
169
|
```sh
|
|
169
170
|
bun install
|
|
170
|
-
bun test src/ #
|
|
171
|
+
bun test src/ # 916 tests across 65 files
|
|
171
172
|
bun run lint # prettier + eslint + tsc --noEmit
|
|
172
173
|
bun run build # tsc → dist/
|
|
173
174
|
```
|
package/dist/remote/server.js
CHANGED
|
@@ -109,14 +109,38 @@ export async function startServer(onMessage, getHtml) {
|
|
|
109
109
|
}
|
|
110
110
|
});
|
|
111
111
|
const wss = new WebSocketServer({ server: httpServer, path: '/ws' });
|
|
112
|
+
// Track every accepted TCP socket so stop() can forcibly destroy lingering
|
|
113
|
+
// keep-alive / WebSocket connections. Without this, httpServer.close() only
|
|
114
|
+
// stops accepting new connections and waits for existing ones to drain — an
|
|
115
|
+
// open browser tab never drains, so the listening server and its sockets
|
|
116
|
+
// stay as active event-loop handles forever. In headless print mode the host
|
|
117
|
+
// exits by natural event-loop drain (it sets process.exitCode and returns,
|
|
118
|
+
// with no process.exit()), so these lingering handles keep the pi process
|
|
119
|
+
// alive indefinitely — which blocks `docker stop` / OS shutdown until the
|
|
120
|
+
// SIGKILL grace timeout fires. A/B-proven: terminating clients + destroying
|
|
121
|
+
// sockets here makes the loop drain in ~2ms instead of never.
|
|
122
|
+
const sockets = new Set();
|
|
123
|
+
httpServer.on('connection', s => {
|
|
124
|
+
sockets.add(s);
|
|
125
|
+
s.on('close', () => sockets.delete(s));
|
|
126
|
+
});
|
|
112
127
|
const handle = {
|
|
113
128
|
port,
|
|
114
129
|
ip,
|
|
115
130
|
ips,
|
|
116
131
|
onFirstConnect: null,
|
|
117
132
|
stop() {
|
|
133
|
+
// Terminate WebSocket clients (immediate close, no drain), then
|
|
134
|
+
// destroy any remaining raw sockets, then close the servers so the
|
|
135
|
+
// event loop has no lingering handles holding the process open.
|
|
136
|
+
for (const ws of wss.clients)
|
|
137
|
+
ws.terminate();
|
|
118
138
|
wss.close();
|
|
139
|
+
for (const s of sockets)
|
|
140
|
+
s.destroy();
|
|
141
|
+
sockets.clear();
|
|
119
142
|
httpServer.close();
|
|
143
|
+
httpServer.closeAllConnections?.();
|
|
120
144
|
}
|
|
121
145
|
};
|
|
122
146
|
wss.on('connection', ws => {
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mjasnikovs/pi-task",
|
|
3
|
-
"version": "0.16.
|
|
3
|
+
"version": "0.16.2",
|
|
4
4
|
"description": "Deterministic spec-orchestration for local models, with a bundled real-time remote web view and web/docs/fetch/worker subagent tools.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|