waygraph 0.15.10 → 0.15.11

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/cli.d.ts CHANGED
@@ -8,6 +8,7 @@
8
8
  * run Execute; `--blocks` `--data` `--non-headless` `--video`
9
9
  *
10
10
  * Also: list / nav / validate / check / graph / init / agent-dive / traverse / try
11
+ * Skills: --skill / --skill-pilot / --skill-pilot-blind / --skill-convention
11
12
  * Aliases (one release): `chain` -> run/demo --blocks; `--autoplay` -> `--auto-next`
12
13
  *
13
14
  * "project" defaults to cwd. Flags beat WAYGRAPH_* env.
package/dist/cli.js CHANGED
@@ -8,6 +8,7 @@
8
8
  * run Execute; `--blocks` `--data` `--non-headless` `--video`
9
9
  *
10
10
  * Also: list / nav / validate / check / graph / init / agent-dive / traverse / try
11
+ * Skills: --skill / --skill-pilot / --skill-pilot-blind / --skill-convention
11
12
  * Aliases (one release): `chain` -> run/demo --blocks; `--autoplay` -> `--auto-next`
12
13
  *
13
14
  * "project" defaults to cwd. Flags beat WAYGRAPH_* env.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "waygraph",
3
- "version": "0.15.10",
3
+ "version": "0.15.11",
4
4
  "type": "module",
5
5
  "description": "A typed graph of reusable Blocks for driving a browser through E2E flows.",
6
6
  "license": "MIT",
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: waygraph-pilot
3
- description: Drive an existing waygraph Block graph as a real agent - use when a task needs to operate a web app that already has waygraph Blocks written for it (login, checkout, matching, chat, admin flows, etc.), not when writing new Blocks from scratch.
3
+ description: Drive an existing waygraph Block graph as a real agent - use when a task needs to operate a web app that already has waygraph Blocks written for it (login, checkout, matching, chat, admin flows, etc.), not when writing new Blocks from scratch. Includes how to paint demo-parity fixture highlights in Pilot via `auto highlight` (pilot:watch / --non-headless).
4
4
  ---
5
5
 
6
6
  Waygraph Pilot is not a planner you call and get an answer from - `pilot start` only
@@ -23,15 +23,42 @@ waygraph auto highlight <sessionId> '<json>' # paint rings/todos on the live pa
23
23
  just what's reachable from here - use it to plan several steps ahead before you start
24
24
  sending picks.
25
25
 
26
- ## Highlight fixtures (agent-sent narration)
26
+ ## Highlight fixtures (Pilot supports them — use `auto highlight`)
27
27
 
28
- Block `stubBefore` / `withHighlightFixtures` only paint in `waygraph demo`. In Pilot they
29
- land in `auto trace` as metadata but do **not** draw on the page. When a human is watching
30
- a headful session (or you want to narrate intent before a send), paint yourself with the
31
- same fixture surface:
28
+ **Yes, Pilot paints rings/todos/zoom/device on the live page.** That is what
29
+ `waygraph auto highlight` is for. It works on headful `pilot start --non-headless`
30
+ (consumer `pilot:watch`) and on headless sessions alike. Same fixture surface as
31
+ `waygraph demo` (rings, todos, focus veil, zoom badge, device viewport) — proven in
32
+ `tests/cli/auto-session.spec.ts` ("auto highlight: paints agent fixture rings…").
33
+
34
+ **Do not claim Pilot "doesn't support fixture highlights."** That is wrong. The only
35
+ thing that differs from demo is *who* triggers the paint:
36
+
37
+ | Mode | Who paints | How |
38
+ |------|------------|-----|
39
+ | `waygraph demo` | Engine, automatically | Block `stubBefore` / `stubAfter` / `withHighlightFixtures` run each step |
40
+ | Pilot / `auto --detach` | **You (the agent)** | `waygraph auto highlight <sessionId> '<json>'` before (or between) sends |
41
+
42
+ Block-authored `stubBefore` / `withHighlightFixtures` still exist on Blocks in Pilot —
43
+ they show up in `auto trace` as metadata — but they do **not** auto-draw. You re-express
44
+ the same intent with `auto highlight` (copy selectors/labels from the Block stubs or from
45
+ `auto dom`). Paint, then `auto send` the real Block. Clear when done.
32
46
 
33
47
  ```
48
+ # Headful watch session (rings visible to a human audience):
49
+ waygraph pilot start --non-headless
50
+ # → note sessionId from the bootstrap JSON
51
+
34
52
  waygraph auto highlight <sessionId> '{"rings":[{"selector":"#user-name","label":"Username","tone":"planned","focus":true},{"selector":"#password","label":"Password","tone":"info","detail":"secret"}],"todos":["Fill username","Fill password","Submit"],"todoIndex":0,"zoom":1.5,"holdMs":0}'
53
+ waygraph auto send <sessionId> fill-username
54
+ waygraph auto highlight <sessionId> '{"rings":[{"selector":"#password","label":"Password","tone":"planned","focus":true}],"todoIndex":1,"holdMs":0}'
55
+ waygraph auto send <sessionId> fill-password
56
+ waygraph auto highlight <sessionId> '{"clear":true}'
57
+ ```
58
+
59
+ More shapes:
60
+
61
+ ```
35
62
  waygraph auto highlight <sessionId> '{"device":"mobile","rings":[{"selector":".inventory_item:last-child","label":"Last item","zoom":1.6,"focus":true}],"holdMs":30000}'
36
63
  waygraph auto highlight <sessionId> '{"clear":true}'
37
64
  ```