AppifactRepl scripts can issue Artifact tool actions like get, set, upload, and publish over a JSON protocol
A new internal protocol lets scripts running inside AppifactRepl (see the related entries on this tool) issue Artifact tool actions directly: reading or querying data (get/list/query), writing it (set/update/delete/batch), working with files (read_file/read_files/list_files), handling assets (upload_asset/read_asset), and publishing or opening the artifact. Messages are exchanged as one JSON object per line.
Each action is checked against the session's permissions individually, and can be refused, for example, if the Artifact tool's database actions or asset actions are turned off for that session.
This lets a single script drive the full range of Artifact operations while still respecting the same per-action permission boundaries that apply outside the REPL.