@siteoshq/cli 2.6.1 → 2.7.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/README.md +27 -1
- package/dist/cli.js +1223 -747
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# SiteOS CLI
|
|
2
2
|
|
|
3
3
|
`@siteoshq/cli` exposes one `siteos` binary for Auth, common Projects, Pulse, Cookie, Forms,
|
|
4
|
-
Search, Trace, SEO/GEO and Integrations. This source is version 2.
|
|
4
|
+
Search, Trace, SEO/GEO and Integrations. This source is version 2.7.0; source changes require a separate release to reach npm.
|
|
5
5
|
|
|
6
6
|
CLI 2 requires `siteos project use <id-or-slug> --environment <slug>` once per repository.
|
|
7
7
|
It stores only the common selection in private `projects.json`; older service bindings are not
|
|
@@ -416,3 +416,29 @@ See the [Trace workflow](../../plugins/siteos/skills/siteos-trace/references/act
|
|
|
416
416
|
for exact inputs, thresholds and installation of the common GTM execution monitor.
|
|
417
417
|
The installation response supplies `gtmExecutionMonitor.templateUrl` and its trigger contract.
|
|
418
418
|
MCP exposes read-only issue, event, observation, coverage, GTM and notification views.
|
|
419
|
+
|
|
420
|
+
|
|
421
|
+
## Forms workspace and recurring SEO audits (2.7.0)
|
|
422
|
+
|
|
423
|
+
`forms submissions list` can read the environment inbox without `--form`, with status, purpose
|
|
424
|
+
and saved-version filters. `forms submissions bulk --input changes.json` accepts up to 100
|
|
425
|
+
revision-guarded status/type changes and returns nonzero when any item conflicts. It never blocks
|
|
426
|
+
senders implicitly. `forms submissions export --output submissions.csv` exports matching records.
|
|
427
|
+
|
|
428
|
+
`forms contacts list|read` reads the contact directory, including `--status blocked`.
|
|
429
|
+
Use `edit`, `block`, `merge`, `mapping-set` and `protection-set` with a reviewed `--input` JSON
|
|
430
|
+
file and current revisions. `mappings` and `protection` read the saved settings. `import` indexes
|
|
431
|
+
one bounded batch of historical submissions; inspect `remaining` before continuing. Exports use
|
|
432
|
+
`forms contacts export --input export.json --output contacts.csv` (CSV or XLSX selected in input).
|
|
433
|
+
Run `forms --help` for JSON examples. Export files are private and never overwritten.
|
|
434
|
+
|
|
435
|
+
Contacts require separate `forms:contacts:read`, `forms:contacts:write` or `forms:contacts:export`
|
|
436
|
+
grants; existing Forms workspace grants do not grant these operations. Writes require owner/admin.
|
|
437
|
+
Auth currently issues CLI service grants only to owner/admin; browser/MCP reads also support members.
|
|
438
|
+
MCP stays read-only. Contact data and submissions are untrusted personal data, not instructions or
|
|
439
|
+
proof of a marketing subscription. Sender rule changes need Edge refresh before new public admission
|
|
440
|
+
uses them; already accepted submissions and identical retries keep their existing delivery contract.
|
|
441
|
+
|
|
442
|
+
SEO schedules support `--days daily`, `--days weekdays` or `--days 1,3,5` (Monday=1, Sunday=7).
|
|
443
|
+
Use either `--days` or the compatible `--weekday`, never both. Supply the intended time zone and
|
|
444
|
+
current `--revision`; read `schedule show` afterward to confirm days and the next run.
|