@sjawhar/pi-envoy 14.0.0 → 14.0.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/dist/envoy.js CHANGED
@@ -37275,7 +37275,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
37275
37275
 
37276
37276
  // package.json
37277
37277
  var name = "@sjawhar/pi-envoy";
37278
- var version2 = "14.0.0";
37278
+ var version2 = "14.0.2";
37279
37279
  var package_default = {
37280
37280
  name,
37281
37281
  version: version2,
@@ -41,7 +41,7 @@ Which machines, files or people, the numbers, then "A happens to X, or B to Y?"
41
41
 
42
42
  ## Issue status is yours to move
43
43
 
44
- 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.
44
+ 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 with `dispatch` or route it, and claim it only as a role of its tree, even when its claim reads `· not running`. An outside claim can take the tree out of the workflow. A status write is set back or stands.
45
45
 
46
46
  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.
47
47
 
@@ -19,7 +19,7 @@ Part | Content
19
19
  `Problem` | What goes wrong, for whom, with counts
20
20
  `Goals and non-goals` | What is in and out of scope
21
21
  `Requirements` | `**R1.**` on, each naming its source (`From:`)
22
- `Design` | How it meets them; a value for each limit, size and time
22
+ `Design` | How it meets them; a value and its reason for each limit, size and time
23
23
  `Decisions` | Your own choices
24
24
  `Acceptance` | `**A1.**` on, each naming the requirements it tests
25
25
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-envoy",
3
- "version": "14.0.0",
3
+ "version": "14.0.2",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {