@oisin-ee/pi-dogsled 0.23.2 → 0.24.0
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 +15 -6
- package/package.json +1 -1
- package/plugins/dogsled/skills/dogsled/SKILL.md +18 -2
package/README.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# dogsled
|
|
2
2
|
|
|
3
|
+

|
|
4
|
+
|
|
3
5
|
Host status and placement for coding agents across [Herdr](https://herdr.dev) hosts.
|
|
4
6
|
|
|
5
7
|
Dogsled measures hosts, starts Pi, Claude, and Codex children and jobs on the host with room, queues work when every host is full, and carries every message between agents through an inbox. Nothing types into an agent's terminal.
|
|
@@ -11,13 +13,13 @@ Install the binary on each Herdr host. Use the same release tag in each command.
|
|
|
11
13
|
Binary:
|
|
12
14
|
|
|
13
15
|
```sh
|
|
14
|
-
mise use github:oisin-ee/dogsled@v0.
|
|
16
|
+
mise use github:oisin-ee/dogsled@v0.24.0
|
|
15
17
|
```
|
|
16
18
|
|
|
17
19
|
Pi (extension, tools, and skill), from npm or as part of `@oisin-ee/oisinpi`:
|
|
18
20
|
|
|
19
21
|
```sh
|
|
20
|
-
pi install npm:@oisin-ee/pi-dogsled@0.
|
|
22
|
+
pi install npm:@oisin-ee/pi-dogsled@0.24.0
|
|
21
23
|
```
|
|
22
24
|
|
|
23
25
|
At session start the extension compares its version with `dogsled --version` and warns when they differ.
|
|
@@ -25,14 +27,14 @@ At session start the extension compares its version with `dogsled --version` and
|
|
|
25
27
|
Claude Code (hooks, tools, and skill):
|
|
26
28
|
|
|
27
29
|
```sh
|
|
28
|
-
claude plugin marketplace add oisin-ee/dogsled#v0.
|
|
30
|
+
claude plugin marketplace add oisin-ee/dogsled#v0.24.0
|
|
29
31
|
claude plugin install dogsled@dogsled
|
|
30
32
|
```
|
|
31
33
|
|
|
32
34
|
Codex (hooks, tools, and skill):
|
|
33
35
|
|
|
34
36
|
```sh
|
|
35
|
-
codex plugin marketplace add oisin-ee/dogsled --ref v0.
|
|
37
|
+
codex plugin marketplace add oisin-ee/dogsled --ref v0.24.0
|
|
36
38
|
codex plugin add dogsled@dogsled
|
|
37
39
|
```
|
|
38
40
|
|
|
@@ -42,7 +44,7 @@ The [Codex CLI reference](https://developers.openai.com/codex/cli/reference#code
|
|
|
42
44
|
Herdr (left-docked work board):
|
|
43
45
|
|
|
44
46
|
```sh
|
|
45
|
-
herdr plugin install oisin-ee/dogsled --ref v0.
|
|
47
|
+
herdr plugin install oisin-ee/dogsled --ref v0.24.0 --yes
|
|
46
48
|
```
|
|
47
49
|
|
|
48
50
|
The Claude and Codex plugins use the binary on `PATH`. The Herdr plugin's build step (`plugin/fetch.sh`) installs its own binary at `bin/dogsled`: the release archive for the manifest version, checked against its published SHA-256. When that release has no archive for the platform, it runs `cargo build --release --locked` instead, which needs Rust at the crate's `rust-version` or newer. A checksum mismatch stops the install. `DOGSLED_RELEASES` replaces the download base, such as a mirror. `herdr plugin link` skips build steps, so run `sh plugin/fetch.sh` in a linked checkout. No plugin starts host services.
|
|
@@ -635,6 +637,13 @@ cargo build --release
|
|
|
635
637
|
npm ci
|
|
636
638
|
```
|
|
637
639
|
|
|
640
|
+
Proto and moon own the development tooling. `proto install` installs the versions in `.prototools`, and `moon run` runs the checks:
|
|
641
|
+
|
|
642
|
+
```sh
|
|
643
|
+
proto install
|
|
644
|
+
moon run :fmt-check :lint :test :typecheck :test-shim
|
|
645
|
+
```
|
|
646
|
+
|
|
638
647
|
The executable is `target/release/dogsled`.
|
|
639
648
|
Release archives include the binary, `dogsled.service`, and `dev.dogsled.plist` from `plugin/services/`.
|
|
640
649
|
Harness installers read their manifests and skill from Git, not the binary archive. The skill move does not change the archive contents.
|
|
@@ -644,6 +653,6 @@ For launchd, dotfiles creates `~/.local/state/dogsled` before loading the agent.
|
|
|
644
653
|
If mise has a different installation path, dotfiles adjusts the executable path.
|
|
645
654
|
Install the same release on every host before enabling its service. This PR does not install or start host services.
|
|
646
655
|
|
|
647
|
-
The pre-commit hook runs `
|
|
656
|
+
The pre-commit hook runs `moon run :#precommit --affected --status staged`: Rust format, Clippy, Rust tests, TypeScript typecheck, and Pi extension tests.
|
|
648
657
|
CLI behavior tests use private state and fake Herdr/SSH executables. Time-sensitive unit tests inject timestamps.
|
|
649
658
|
See [the design](docs/design.md) for watchdog delivery guarantees and cleanup scope.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@oisin-ee/pi-dogsled",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.24.0",
|
|
4
4
|
"description": "Pi extension for dogsled: the board, the /dogsled panel, the inbox reader, and the dogsled tools. Needs the dogsled binary of the same version.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -1,18 +1,34 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: dogsled
|
|
3
|
-
description: Lead procedure for a change to code, config, or Git. It covers splitting the work, starting workers, and landing their results. Load it when a top-level session gets a change request. Do not load it when your system prompt names you a writer, reviewer, scout, or architect, because that prompt is your whole job.
|
|
3
|
+
description: Lead procedure for a change to code, config, or Git. It covers splitting the work, starting workers, and landing their results. Load it when a top-level session gets a change request. Do not load it in an exec session given prewalk. Do not load it when your system prompt names you a writer, reviewer, scout, or architect, because that prompt is your whole job.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
+
# Exec agents given prewalk
|
|
7
|
+
|
|
8
|
+
If you are an exec agent given prewalk, this procedure is not for you. Do not delegate. Do not spawn workers. Execute the task locally. Stay in the same session through the prewalk model handoff.
|
|
9
|
+
|
|
6
10
|
# Lead
|
|
7
11
|
|
|
8
|
-
You
|
|
12
|
+
You split the work, brief workers, check their results, and land them.
|
|
9
13
|
You may edit plans, briefs, and docs that you own.
|
|
10
14
|
|
|
15
|
+
## 0. Do it yourself when a worker costs more
|
|
16
|
+
|
|
17
|
+
Make the code or config edit in this session, with no worker, in these cases:
|
|
18
|
+
|
|
19
|
+
- The cause and every edit are known, and the whole change is under about 100 changed lines.
|
|
20
|
+
- No host can start a worker, and the change fits in one session. A failed spawn alone is not a blocker.
|
|
21
|
+
- The user tells you to make the change. Never cite this skill to refuse.
|
|
22
|
+
|
|
23
|
+
Keep the scope of the request. Run the repository's checks as a writer would. Then go to step 6.
|
|
24
|
+
Otherwise, do not edit code or config. Delegate it with steps 1 to 5.
|
|
25
|
+
|
|
11
26
|
## 1. Split
|
|
12
27
|
|
|
13
28
|
List the deliverables. Each one has one outcome, one acceptance command, and the paths it owns.
|
|
14
29
|
Add each deliverable as a todo unit with a `worker` assignment and the profile from step 2.
|
|
15
30
|
Put deliverables that touch the same files in one unit.
|
|
31
|
+
Put small specified edits of one request in one unit, even across files. Never start one worker per small edit.
|
|
16
32
|
|
|
17
33
|
## 2. Pick the profile
|
|
18
34
|
|