@sjawhar/pi-envoy 17.6.0 → 17.7.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.
Files changed (4) hide show
  1. package/README.md +12 -10
  2. package/dist/dispatch.js +7720 -6986
  3. package/dist/envoy.js +5013 -822
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -316,10 +316,12 @@ session's subscriptions, as the Envoy listener records them, covers that owner.
316
316
  The shared specs in `@legion/contracts` supply each command's description and flags:
317
317
  `@legion/envoy-client`'s `dispatch-command.ts` derives one command per spec and one flag per field.
318
318
 
319
- `dispatch artifact` takes exactly one upload source: a local `--path`, or inline `--content`. For
320
- example, an architect can post a specification directly, its text on stdin. Every issue is created
321
- with a `spec.md`, and the command refuses an upload under the name of a document the issue already
322
- holds, so this one carries `--force`, which writes the next version of it:
319
+ `dispatch artifact` takes at most one upload source: a local `--path`, or inline `--content`.
320
+ With neither, it makes an empty document under `--name`, which a person or an agent writes in
321
+ afterwards with `dispatch doc-edit`. For example, an architect can post a specification directly,
322
+ its text on stdin. Every issue is created with a `spec.md`, and the command refuses an upload
323
+ under the name of a document the issue already holds, so this one carries `--force`, which writes
324
+ the next version of it:
323
325
 
324
326
  ```sh
325
327
  dispatch artifact --issue LEGION-1 --name spec.md --content-file - --force <<'EOF'
@@ -327,12 +329,12 @@ dispatch artifact --issue LEGION-1 --name spec.md --content-file - --force <<'EO
327
329
  EOF
328
330
  ```
329
331
 
330
- Inline content is stored as a Markdown document, so `--content` and `--content-file` take only a
331
- `--name` that ends in `.md` or `.markdown` or has no extension. The command refuses any other name
332
- (`rows.jsonl`, `sizes.tsv`, `rows.jsonl.1`, `plan v1.2`) before it sends anything and names
333
- `--path`, which stores a file whose path does not end in `.md` or `.markdown` as its bytes,
334
- unchanged, under that name. A document title with a dot near its end takes `--content` once it
335
- ends in `.md`.
332
+ Inline content is stored as a Markdown document, so `--content`, `--content-file` and a call with
333
+ neither flag take only a `--name` that ends in `.md` or `.markdown` or has no extension. The
334
+ command refuses any other name (`rows.jsonl`, `sizes.tsv`, `rows.jsonl.1`, `plan v1.2`) before it
335
+ sends anything and names `--path`, which stores a file whose path does not end in `.md` or
336
+ `.markdown` as its bytes, unchanged, under that name. A document title with a dot near its end
337
+ takes `--content` once it ends in `.md`.
336
338
 
337
339
  `dispatch handoff-write --issue <KEY> --phase <phase> --body-file <path>` records a Legion phase
338
340
  handoff on its issue as this session: the file's text, one JSON object, is stored exactly as