@intentius/behold 0.29.1 → 0.29.3

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 CHANGED
@@ -369,6 +369,15 @@ any theme name the picker lists:
369
369
  the URL's fields (`member: null` is the whole estate). Messages from any
370
370
  other origin are ignored
371
371
  - gates are the host's to approve: behold draws them and says so
372
+ - `bare=1` (with `embed=1`) leaves the graph alone in the frame: no panel, no
373
+ inspect pane, no buttons, no now line. The kiosk frames behold this way
374
+ - `focus=<box>,<box>` (in the URL or a `behold:view` message) brings those boxes
375
+ forward and dims the rest; `focus: null` brings nothing forward. On a
376
+ terragucci repo the boxes are its roots
377
+ - `run=<commit>` (or a `behold:view` message's `run`) keeps a terragucci repo's
378
+ view on that commit's run view instead of the newest; `run=none` draws the
379
+ pull request's plan, `run=base` nothing in flight; `run: null` the newest
380
+ again. `GET /api/terragucci/progress?commit=<sha>` reads that run view
372
381
 
373
382
  `gates=<env>` sets the env the gate strip reads, apart from the graph's, so a
374
383
  host can open behold on the source graph and still show the gates of the env
@@ -407,10 +416,14 @@ the repo's `origin`, which `chant/lifecycle` is fetched from.
407
416
 
408
417
  `/kiosk` follows terragucci's looping demo (#569): it reads the `demo.json`
409
418
  the demo's driver writes beside `index.json`, and narrates the scenario, the
410
- step and the driver's next action with a countdown, next to the newest run of
411
- that step (the pull request's plan, then the merge's waves) and back to the
412
- start when the loop resets. It needs `--terragucci`, asks only GETs, and has
413
- no control. The docs' terragucci page says what it shows.
419
+ step and the driver's next action with a countdown in a status bar, over
420
+ behold's own view of the change in a frame (`/?embed=1&bare=1`): each root's
421
+ wave and its state, the reads between roots, and the roots the step is about
422
+ brought forward. Beside it, the pipeline's runs the way a CI page shows them:
423
+ the recent runs, the selected run's jobs and steps, and the running step's
424
+ log, which the loop driver copies into the bucket under `runs/`. It needs
425
+ `--terragucci`, asks only GETs, and has no control.
426
+ The docs' terragucci page says what it shows.
414
427
 
415
428
  In a declared workspace, the gates waiting on a person come from
416
429
  `chant workspace status <env> --json`, keyed `member/op/gate` the way arugula's