@datarails-ai/dr-appspace-cli 0.10.8 → 0.10.9

package/README.md

@@ -100,6 +100,27 @@ place is `assemble-*`, exit 1. `--app-id <id>` names the app a first pass is
 for, and `--expect <card>=<figure>` holds a card to the figure the user
 confirmed once the package runs (exit 6 when it does not).
 
+A dataset `series` row may be drawn through its own transform — `"transform":
+"transforms/<name>.py"`, the App Builder's `transform(rows, ctx, params)`,
+handed the dataset's whole monthly history. A draft carries the file as
+`"transforms": {"transforms/<name>.py": "<text>"}`; it is written beside
+`contract.json` (not under `--check`) and compiled into the handler, and a
+later draft's text replaces it and says so — unless a card that is not the
+draft's is drawn through that file, which is refused. A skeleton page may
+carry `controls` (`{id, label, param, kind: "slider"|"number", min, max, step,
+default}`) and a card `params`: the control is written once a row on the page
+declares its param, the card redraws with it, and a row whose own rule is not
+the control's is refused. `preview` draws such a card in two round trips: the
+server hands over the rows the transform would get, the transform runs here
+with `python3 -I` — 20 s at most, what it prints shown under the card rather
+than read as its answer — and the server draws what it returned, so the
+figure printed is the card's. Only a transform the previewed file's drafts
+carry runs here, never a file in the folder: `get` restores there what the
+live app carries, whoever pushed it. `compile`'s lint and the server's own
+`ast` check run first, so preview refuses what the page would; neither is a
+sandbox, and the run starts with no environment beyond PATH, HOME, the locale
+and a Python version manager's own variables.
+
 ```
 app-space ship [dir] --draft spec-draft-cfo.json --app-id app-7k2m3f --expect revenue=870,000
 ```