@lotics/cli 0.316.27 → 0.317.0
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/AGENTS.md +1 -1
- package/dist/src/cli.js +111 -54
- package/docs/agent_surface.md +5 -3
- package/docs/building_an_app.md +4 -3
- package/docs/design.md +13 -9
- package/docs/document_templates.md +6 -0
- package/docs/examples.md +659 -678
- package/docs/first_build.md +21 -24
- package/docs/getting_started.md +1 -0
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -106,7 +106,7 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
|
|
|
106
106
|
`name`, `description`, `icon` and `color` being props of the App node; `{ "app_id": …, "nodes": { "<address>": <patch> } }`
|
|
107
107
|
to change a node, refused with `base_version_id` when the app has moved past the version you read. `dry_run` checks
|
|
108
108
|
without writing, a refusal lists everything wrong in the call, and every answer states the permissions the write
|
|
109
|
-
granted and removed. The answer
|
|
109
|
+
granted and removed. The answer shows what the platform drew where the tree is silent (nothing is stored for it) and says what it placed or folded in what the tree states; a placement is stored. A new workspace: one `set_tables` call with
|
|
110
110
|
the tables, then every `set_app` call, then fixes.
|
|
111
111
|
- **Every change to an app mints a version of it, and applying the earlier tree again is the undo.** An apply, a
|
|
112
112
|
deploy, a single `set_app_*`: each is a new version. Applying the earlier tree again restores the app — never a table change or a row a workflow wrote,
|