eve-hub 0.6.24 → 0.6.25

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 (3) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/package.json +1 -1
  3. package/templates/forms.md +3 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # eve-hub
2
2
 
3
+ ## 0.6.25
4
+
5
+ ### Patch Changes
6
+
7
+ - 6433096: The Forms guide names the shape by what the content is: a path through three or more parts, events across actors, numbers to compare, and time split into phases (a latency breakdown) as a schedule chart. Never prose steps, an arrow chain, a character drawing or one bar per total.
8
+
3
9
  ## 0.6.24
4
10
 
5
11
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eve-hub",
3
- "version": "0.6.24",
3
+ "version": "0.6.25",
4
4
  "license": "Apache-2.0",
5
5
  "description": "Bot-side code shared by every hub agent: registry tools, the roster hook, the eve channel, the host sandbox and browser, and model helpers.",
6
6
  "type": "module",
package/templates/forms.md CHANGED
@@ -1,8 +1,10 @@
1
1
 
2
2
  ## Forms
3
3
 
4
- A form is an interactive figure the app draws from a fenced block with a JSON body. When the reader is trying to understand or review something, draw it by default; they should never have to ask. Pick the shape: a path through parts (`flow`), an order of events (`sequence`), numbers to compare (`chart`), a choice you need from the human (`ask`). Anchor the picture in something they know, e.g. a before form then an after form, each labeled, in one message. Every part of one diagram is the same kind of thing (all hosts, all processes or all functions); say which in the sentence before it, and for a sequence in `unit`. A group is the level that contains them (processes grouped under their host). Plain prose is for what no shape helps. At most one or two forms per message.
4
+ A form is an interactive figure the app draws from a fenced block with a JSON body. Any path through three or more parts, order of events across two or more actors, or numbers to compare is a form, never prose steps, an arrow chain or a character drawing; draw it by default; the reader should never have to ask. Pick the shape: a path through parts (`flow`), an order of events (`sequence`), numbers to compare (`chart`), a choice you need from the human (`ask`). Anchor the picture in something they know, e.g. a before form then an after form, each labeled, in one message. Every part of one diagram is the same kind of thing (all hosts, all processes or all functions); say which in the sentence before it, and for a sequence in `unit`. A group is the level that contains them (processes grouped under their host). Plain prose is for what no shape helps. At most one or two forms per message.
5
5
 
6
+ - A code fence is for text the reader will paste, never for a picture: no boxes, arrows, timelines or tables drawn with characters.
7
+ - Pick the shape by what the numbers are. Time split into phases or hops (a latency breakdown, a turn's timeline) is a `schedule` chart: one row per turn or request, one start/end segment per phase, never one `bar` per total. A `bar` compares one number across items.
6
8
  - Claim first: a sentence that says what the form shows comes before it. A chart's `title` is its claim.
7
9
  - Link a word in your prose to a part with `[word](#id)`. Ids are lowercase slugs (`a-z`, `0-9`, `-`, up to 32 characters), unique in the whole message.
8
10
  - Put the explanation of a part in `note` (up to 240 characters), which the human sees when they point at or step to it. Keep labels short.