@intentius/behold 0.29.6 → 0.29.8

package/AGENTS.md

@@ -71,7 +71,12 @@ and none is the checkout's git remote) adds two reads, in
   Terraform root of the checkout with the newest `plan`, `drift` and `apply`
   run that held it; a missing stage means no report holds that root, which is
   not "no changes". `cards` maps a card id to its marks (`verdict: drift |
-  plan | wave`, terragucci's words, the instance addresses, the run). Nothing
+  plan | wave`, terragucci's words, the instance addresses, the run). Each
+  mark's `values` gives each changed attribute's `before` and `after`, or
+  `unknown: true` for a value known only after apply. A sensitive attribute
+  is never there, and a value longer than 300 characters of JSON is left out
+  with `long: true`. `applied` maps a card id to what its root's newest
+  applied wave wrote. The kiosk's popover reads both (behold#571). Nothing
   sets `_status`: a report is never painted as live. `waiting[]` carries each
   wave's roots, destroys, and the `command` a person runs. `estate` is
   terragucci's own counts when the source has `estate.json`. A key such as a

package/README.md

@@ -425,6 +425,13 @@ log, which the loop driver copies into the bucket under `runs/`. It needs
 `--terragucci`, asks only GETs, and has no control.
 The docs' terragucci page says what it shows.
 
+Each tool in the loop has a page of its own at `/<tool>`: `/terraform`,
+`/terragrunt`, `/cdk-terrain` and `/choudoufu` (behold#571). It shows that
+tool's scenario and runs alone, with a footer saying who makes the tool.
+While another tool's scenario runs, the page replays the tool's latest cycle at
+the pace it ran (`cycles/<tool>/latest.json` beside `demo.json`), and says so in
+a banner. Any other short path answers 404 with a link to `/kiosk`.
+
 In a declared workspace, the gates waiting on a person come from
 `chant workspace status <env> --json`, keyed `member/op/gate` the way arugula's
 workspace block keys them, so the two show the same set. Standalone, a gate's