playcanvas-agent-bridge-cli 0.4.2 → 0.5.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "playcanvas-agent-bridge-cli",
3
- "version": "0.4.2",
3
+ "version": "0.5.0",
4
4
  "description": "CLI-first local bridge for automating open PlayCanvas Editor tabs from AI coding agents.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -46,6 +46,8 @@
46
46
  "registry": "https://registry.npmjs.org/"
47
47
  },
48
48
  "dependencies": {
49
+ "@aws-sdk/client-s3": "^3.1102.0",
50
+ "dotenv": "^17.4.2",
49
51
  "tar": "^7.5.22",
50
52
  "ws": "^8.18.3"
51
53
  },
@@ -53,17 +53,27 @@ Workspace layout:
53
53
 
54
54
  ```text
55
55
  <workspace root>/<projectId>-<projectName>/
56
- pcbridge.project.json
57
- assets/ # remote folder tree and synchronized scripts
58
- tmp/ # task scripts, manifests, captures, and conflict copies
56
+ pcbridge.project.json # project metadata and agent-readable asset catalog
57
+ assets/ # remote folder tree and synchronized asset file contents
58
+ tmp/ # task files, builds, cache, conflicts, captures, and deletion quarantine
59
59
  .pcbridge/ # internal state; do not edit
60
60
  ```
61
61
 
62
- Existing script contents synchronize in both directions. Use structured commands for asset create,
63
- move, rename, and delete operations. Other asset files remain lazy until
64
- `pcbridge workspace pull --target editor:<sceneId> --asset <assetId>` is requested. Local file
62
+ Existing script and binary asset contents synchronize in both directions. Use structured commands
63
+ for asset create, move, rename, and delete operations. `pcbridge workspace pull --target
64
+ editor:<sceneId> --asset <assetId>` explicitly refreshes one file. Local file
65
65
  arguments must stay inside the selected project workspace. Do not use `--allow-external-path`
66
66
  unless the user explicitly asks to use a known external file.
67
+ Read `pcbridge.project.json.assets` to resolve asset ids to project-relative `assets/...` paths and
68
+ compare remote, local, and base MD5 values. Do not edit the managed asset catalog to request remote
69
+ operations. Remote deletions are quarantined under `tmp/trash/remote/`, while true content
70
+ divergence remains under `tmp/conflicts/`.
71
+
72
+ Selecting a Template Asset exposes **pcbridge Tiny Builder** in the Attributes panel. It collects
73
+ dependencies, fills the workspace cache, and uploads individual S3 objects without a ZIP. Project
74
+ `.env` overrides workspace-root `.env`; never expose credential values. CLI equivalents are
75
+ `pcbridge builder start --target editor:<sceneId> --asset <id>` and
76
+ `pcbridge builder status --job <jobId>`.
67
77
 
68
78
  Use structured commands for small, known Editor operations:
69
79
 
@@ -53,10 +53,10 @@ project-picker and scene Editor navigations; change the remembered mode only thr
53
53
 
54
54
  ```text
55
55
  <workspace root>/<projectId>-<projectName>/
56
- pcbridge.project.json
57
- assets/ # PlayCanvas folder tree; scripts synchronize automatically
58
- tmp/ # task scripts, manifests, captures, and conflict copies
59
- .pcbridge/ # internal index and sync state; do not edit
56
+ pcbridge.project.json # project metadata and agent-readable asset catalog
57
+ assets/ # PlayCanvas folder tree; all asset file contents synchronize automatically
58
+ tmp/ # task files, builds, cache, conflicts, captures, and deletion quarantine
59
+ .pcbridge/ # internal sync state; do not edit
60
60
  ```
61
61
 
62
62
  Use:
@@ -68,9 +68,20 @@ pcbridge workspace sync --target editor:<sceneId>
68
68
  pcbridge workspace pull --target editor:<sceneId> --asset <assetId>
69
69
  ```
70
70
 
71
- Existing script contents synchronize in both directions. Create, move, rename, and delete assets
72
- through structured pcbridge commands; do not perform structural changes by moving or deleting
73
- mirrored local files. Non-script files are indexed but downloaded only with `workspace pull`.
71
+ Existing script and binary asset contents synchronize in both directions. Create, move, rename,
72
+ and delete assets through structured pcbridge commands; do not perform structural changes by moving
73
+ or deleting mirrored local files. `workspace pull` explicitly refreshes one file but is not needed
74
+ for normal synchronization.
75
+ Read `pcbridge.project.json.assets` to resolve asset ids to project-relative `assets/...` paths and
76
+ compare remote, local, and base MD5 values. The catalog is managed by pcbridge; do not edit it to
77
+ request remote asset operations. Confirmed remote deletions are quarantined under
78
+ `tmp/trash/remote/`; `tmp/conflicts/` is reserved for divergent local and remote contents.
79
+
80
+ Selecting a Template Asset exposes **pcbridge Tiny Builder** in the Attributes panel. It collects
81
+ dependencies, fills the workspace cache, and uploads individual S3 objects without a ZIP. Project
82
+ `.env` overrides workspace-root `.env`; never read or return credential values. CLI equivalents are
83
+ `pcbridge builder start --target editor:<sceneId> --asset <id>` and
84
+ `pcbridge builder status --job <jobId>`.
74
85
 
75
86
  Local file arguments are restricted to the selected project workspace. Never use
76
87
  `--allow-external-path` unless the user explicitly asks to use a known external file.
@@ -19,9 +19,14 @@ with local-loopback permission. If no target appears, ask the user to install/re
19
19
 
20
20
  The daemon start directory is the workspace root. After selecting an explicit target, run
21
21
  `pcbridge workspace status --target editor:<sceneId>` and do not write while it reports a conflict
22
- or sync error. Project files live under `<projectId>-<projectName>/{assets,tmp}`. Existing scripts
23
- sync automatically; other files are lazy until
24
- `pcbridge workspace pull --target editor:<sceneId> --asset <id>`.
22
+ or sync error. Project files live under `<projectId>-<projectName>/{assets,tmp}`. Script and binary
23
+ asset contents synchronize automatically; `pcbridge workspace pull --target editor:<sceneId>
24
+ --asset <id>` explicitly refreshes one file.
25
+ Read `pcbridge.project.json.assets` for asset ids, types, project-relative file paths, presence, and
26
+ remote/local/base MD5 values. Treat that asset catalog as pcbridge-managed. Confirmed remote
27
+ deletions are quarantined under `tmp/trash/remote/`; `tmp/conflicts/` contains content divergence.
28
+ Template selection exposes pcbridge Tiny Builder for direct S3 object uploads; project `.env`
29
+ overrides workspace-root `.env`.
25
30
 
26
31
  For the optional published Editor build, use `pcbridge frontend install latest`, verify it with
27
32
  `pcbridge frontend status`, and switch custom/official mode from the extension popup.
@@ -15,8 +15,13 @@ with local-loopback permission. If no target is connected, install/reload the un
15
15
 
16
16
  The daemon start directory is the workspace root. After selecting an explicit target, run
17
17
  `pcbridge workspace status --target editor:<sceneId>` and stop if it reports a conflict or sync
18
- error. Each project is mirrored under `<projectId>-<projectName>/{assets,tmp}`. Script content syncs
19
- both ways; other asset files are lazy until explicitly pulled.
18
+ error. Each project is mirrored under `<projectId>-<projectName>/{assets,tmp}`. Script and binary
19
+ asset contents synchronize both ways; `workspace pull` explicitly refreshes one file.
20
+ Read `pcbridge.project.json.assets` for asset ids, types, project-relative file paths, presence, and
21
+ remote/local/base MD5 values. Treat that asset catalog as pcbridge-managed. Confirmed remote
22
+ deletions are quarantined under `tmp/trash/remote/`; `tmp/conflicts/` contains content divergence.
23
+ Template selection exposes pcbridge Tiny Builder for direct S3 object uploads; project `.env`
24
+ overrides workspace-root `.env`.
20
25
 
21
26
  For the optional published Editor build, use `pcbridge frontend install latest`, verify it with
22
27
  `pcbridge frontend status`, and switch custom/official mode from the extension popup.