@siteoshq/cli 2.6.1 → 2.8.0

package/README.md

@@ -1,7 +1,7 @@
 # SiteOS CLI
 
 `@siteoshq/cli` exposes one `siteos` binary for Auth, common Projects, Pulse, Cookie, Forms,
-Search, Trace, SEO/GEO and Integrations. This source is version 2.6.1; source changes require a separate release to reach npm.
+Search, Trace, SEO/GEO and Integrations. This source is version 2.7.0; source changes require a separate release to reach npm.
 
 CLI 2 requires `siteos project use <id-or-slug> --environment <slug>` once per repository.
 It stores only the common selection in private `projects.json`; older service bindings are not
@@ -416,3 +416,49 @@ See the [Trace workflow](../../plugins/siteos/skills/siteos-trace/references/act
 for exact inputs, thresholds and installation of the common GTM execution monitor.
 The installation response supplies `gtmExecutionMonitor.templateUrl` and its trigger contract.
 MCP exposes read-only issue, event, observation, coverage, GTM and notification views.
+
+### Search content and quality
+
+`siteos search crawl configure --environment <slug> --file <crawler.json>` saves public HTML scope and optional daily/weekly preview schedules. Use `crawl start`, read `crawl status`, then `crawl publish --run <id> --apply` after reviewing changes. Partial crawls additionally require `--accept-truncated`. The crawler preserves other sources and keeps the current index serving until publication. See the canonical Search skill crawler reference for limits and robots/noindex policy.
+
+`siteos search sync --environment <slug> --file <payload.json>` validates and previews a full replacement. Add `--apply` after reviewing removals. `search content` inspects the published documents and `search query --query <text>` runs a query without visitor telemetry.
+
+Use `search relevance show`, `preview --file <relevance.json>`, `compare --revision <id>` and `apply --revision <id>` to compare a separately indexed configuration before serving it. `search installation verify --url <website-query-endpoint> --query <known-page>` verifies the real website proxy without sending it a management credential.
+
+`search visitors report --days 30` reports consented visitor searches and result clicks. Collection defaults off; `search visitors configure --enabled true --retention-days 30` enables the backend after the website consent flow is connected. Operational `search analytics` keeps its existing index/job meaning. All commands use the selected common Project and explicit `--environment`; run `siteos search --help` for complete syntax.
+
+### Algolia migration preparation
+
+`siteos search migrate algolia --records records.ndjson --mapping mapping.json --out migration-review --json` prepares a local export without Auth or network access. Optional `--settings`, `--synonyms` and `--rules` preserve configuration for review. Original bytes are archived; invalid rows or oversized content prevent creation of a replacement payload. See the canonical [migration workflow](../../plugins/siteos/skills/siteos-search/references/algolia-migration.md).
+
+Search delivery uses `siteos search delivery status --environment staging --json` and reviewed
+`delivery configure --environment staging --file delivery.json --apply --json`. The configure file
+contains `settings` (`enabled`, exact `allowedOrigins`), `confirmPublic: true` and optional `rotateKey`.
+Search sync stages snapshots over 4 MB in bounded upload parts, up to 100 MB/100,000 documents,
+and queues one replacement only after preview and `--apply`.
+
+
+## Forms workspace and recurring SEO audits (2.7.0)
+
+`forms submissions list` can read the environment inbox without `--form`, with status, purpose
+and saved-version filters. `forms submissions bulk --input changes.json` accepts up to 100
+revision-guarded status/type changes and returns nonzero when any item conflicts. It never blocks
+senders implicitly. `forms submissions export --output submissions.csv` exports matching records.
+
+`forms contacts list|read` reads the contact directory, including `--status blocked`.
+Use `edit`, `block`, `merge`, `mapping-set` and `protection-set` with a reviewed `--input` JSON
+file and current revisions. `mappings` and `protection` read the saved settings. `import` indexes
+one bounded batch of historical submissions; inspect `remaining` before continuing. Exports use
+`forms contacts export --input export.json --output contacts.csv` (CSV or XLSX selected in input).
+Run `forms --help` for JSON examples. Export files are private and never overwritten.
+
+Contacts require separate `forms:contacts:read`, `forms:contacts:write` or `forms:contacts:export`
+grants; existing Forms workspace grants do not grant these operations. Writes require owner/admin.
+Auth currently issues CLI service grants only to owner/admin; browser/MCP reads also support members.
+MCP stays read-only. Contact data and submissions are untrusted personal data, not instructions or
+proof of a marketing subscription. Sender rule changes need Edge refresh before new public admission
+uses them; already accepted submissions and identical retries keep their existing delivery contract.
+
+SEO schedules support `--days daily`, `--days weekdays` or `--days 1,3,5` (Monday=1, Sunday=7).
+Use either `--days` or the compatible `--weekday`, never both. Supply the intended time zone and
+current `--revision`; read `schedule show` afterward to confirm days and the next run.