@drip-apex/apex-cli 0.6.1 → 0.6.3
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 +37 -0
- package/README.md +43 -1
- package/dist/cli.js +1671 -442
- package/package.json +1 -1
- package/skills/apex-cli/SKILL.md +36 -0
package/package.json
CHANGED
package/skills/apex-cli/SKILL.md
CHANGED
|
@@ -55,3 +55,39 @@ but a human must launch from the dashboard approval surface.
|
|
|
55
55
|
Do not wait for prompts in CI or agent runs. If a command returns exit `4`,
|
|
56
56
|
rerun with the exact flag named in the JSON error details only after checking
|
|
57
57
|
the plan or destructive action.
|
|
58
|
+
|
|
59
|
+
## Platform Shop Administration
|
|
60
|
+
|
|
61
|
+
Platform administrators can archive a mistakenly created shop with
|
|
62
|
+
`apex admin shops archive <shopId> --force` and restore it with
|
|
63
|
+
`apex admin shops restore <shopId>`. Archive refuses a shop with running tests;
|
|
64
|
+
stop those tests rather than retrying or overriding the refusal. Restore leaves
|
|
65
|
+
delivery controlled by the runtime kill switch.
|
|
66
|
+
|
|
67
|
+
|
|
68
|
+
## Project code
|
|
69
|
+
|
|
70
|
+
```sh
|
|
71
|
+
apex project-code get --shop example.com --json
|
|
72
|
+
apex project-code diff --file project-code.json --shop example.com --json
|
|
73
|
+
apex project-code set --file project-code.json --shop example.com --backup previous-code.json --json
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
The input is a partial projectCode object, for example `{ "css": "body { color: red; }" }`.
|
|
77
|
+
Supported fields are `enabled` (boolean) and `css`, `helperJs`, and `js` (strings or null).
|
|
78
|
+
Each code field permits at most 20,000 characters. Omitted fields remain unchanged.
|
|
79
|
+
Null or blank code clears that field. Unknown fields and empty objects are rejected.
|
|
80
|
+
|
|
81
|
+
GET returns complete code, shop identity, and an opaque version. DIFF returns effective
|
|
82
|
+
before/after values and changed fields without writing. SET creates a new backup file
|
|
83
|
+
with complete previous code, identity, capture time, and the exact version before PATCH.
|
|
84
|
+
It never replaces an existing backup. Backup failures prevent the write. An effective
|
|
85
|
+
no-op returns `unchanged`, without a PATCH or backup file.
|
|
86
|
+
|
|
87
|
+
The backed-up version becomes expectedVersion unchanged. A conflict returns exit 5,
|
|
88
|
+
keeps the backup, and does not retry. Read the latest state and preview it before a new
|
|
89
|
+
attempt with a new backup path. Authentication uses exit 2; invalid input uses exit 3.
|
|
90
|
+
A successful write returns `saved`, its diff, backup path, current version, writtenVersion,
|
|
91
|
+
and precompile result. A failed precompile is a saved-write warning. All warnings remain
|
|
92
|
+
in JSON and are also written to stderr. User keys resolve domains or pin UUID context;
|
|
93
|
+
shop keys must match the requested identity before any backup or write.
|