@sjawhar/pi-envoy 13.5.1 → 13.6.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 +22 -0
- package/dist/dispatch.js +201 -79
- package/dist/envoy.js +488 -78
- package/dist/skills/dispatch/SKILL.md +3 -3
- package/dist/skills/dispatch-writing-specs/SKILL.md +1 -1
- package/package.json +1 -1
|
@@ -45,12 +45,12 @@ Which machines, files or people, the numbers, then "A happens to X, or B to Y?"
|
|
|
45
45
|
|
|
46
46
|
Outside Legion, claim your issue (`dispatch claim`) and move it and your children: `in_progress` at implementation, `testing` on a production-like surface, `needs_review` while its PR waits, `done` with `--reason` once driven in production. An issue with the `legion` label, or under one: never write its status or route it, and claim it only as a Legion role of its tree, even when its claim reads `· not running`, as a suspended architect's does: taking it removes the tree from the workflow.
|
|
47
47
|
|
|
48
|
-
A claim, or `dispatch issue-update --route session:<your id>` (`--route ''` on release), brings a person's answers, comments and messages; for agents' activity, `envoy_subscribe notifications.dispatch.issue.<KEY
|
|
48
|
+
A claim, or `dispatch issue-update --route session:<your id>` (`--route ''` on release), brings a person's answers, comments and messages; for agents' activity, `envoy_subscribe notifications.dispatch.issue.<KEY>.>`, which shows no event Dispatch marks quiet, like an unnamed autosave.
|
|
49
49
|
|
|
50
50
|
## Close what you opened
|
|
51
51
|
|
|
52
|
-
- An ask you opened is yours until answered or resolved.
|
|
53
|
-
-
|
|
52
|
+
- An ask you opened is yours until answered or resolved. `dispatch resolve-ask` it that turn once anything makes it needless: another answer, a later write, work dropped.
|
|
53
|
+
- Retract an ask a new one replaces.
|
|
54
54
|
|
|
55
55
|
## Structure over stream
|
|
56
56
|
|
|
@@ -33,7 +33,7 @@ For each spec, ask, comment and message:
|
|
|
33
33
|
- Write about the current design, never the person or how people reached it. Never quote people or upload their words.
|
|
34
34
|
- Link each source where the person wrote it. With no link, state the design.
|
|
35
35
|
- In a spec, cite code by file and symbol, never a line number: it goes stale at the next edit.
|
|
36
|
-
- A sentence that cites a gate passing (a test, review, check or proof) also says
|
|
36
|
+
- A sentence that cites a gate passing (a test, review, check or proof) also says what the pass does not show: "The tests pass; they catch a wrong verdict, not a proof of a contradiction."
|
|
37
37
|
- Name your session only if a reader must reach it.
|
|
38
38
|
- Keep only text that helps a reader understand, decide, build, check.
|
|
39
39
|
- Explain each name or term a new reader may not know. Say in a clause what each issue you name does for this reader.
|