@siteoshq/cli 2.0.0 → 2.2.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.0.0; source changes require a separate release to reach npm.
+Search, Trace, SEO/GEO and Integrations. This source is version 2.2.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
@@ -193,11 +193,16 @@ siteos seo audit show '<audit-id>' --json
 siteos seo pages --audit '<audit-id>' --json
 siteos seo issues --audit '<audit-id>' --json
 siteos seo changes --audit '<audit-id>' --state resolved --json
-siteos seo recheck --audit '<audit-id>' --url https://example.com/pricing --json
+siteos seo repair --audit '<audit-id>' --url https://example.com/pricing --rule metadata.description_missing --json
+siteos seo recheck --audit '<audit-id>' --url https://example.com/pricing --url https://example.com/about --json
 ```
 
-Setup performs no crawl. `audit run` queues a full HTML audit; `recheck` queues one previously
-observed URL. Read the returned audit ID until a terminal state; a queued response is not a result.
+Setup performs no crawl. `audit run` queues a full HTML audit; `recheck` queues 1–20 explicitly selected, previously observed URLs.
+CLI 2.1.0 adds `repair` and repeated recheck `--url` values. The optional `--resource` guard
+rejects a different Project environment before sending the request. Repair briefs read saved
+evidence without an AI call; they do not authorize a deployment or another audit.
+Full HTML audits allow 1–500 pages (default 100); the selected server and saved settings enforce
+that limit independently of the installed CLI version. Read the returned audit ID until a terminal state; a queued response is not a result.
 `audit cancel '<audit-id>'` revokes further work. Pages and changes are paginated with `--page`.
 
 `issue ignore` and `issue restore` require `--audit`, `--url`, `--rule`, `--reason` and the current
@@ -384,3 +389,16 @@ definitions. Creation uses `--file <definition.json>`; reports and realtime read
 to Analytics and the operation, with editor roles required for writes. Analytics is Unlimited in
 Usage during early access. See the canonical plugin's website Analytics skill for event contracts
 and the browser-to-report verification workflow; Search reports use `search analytics` separately.
+
+### Trace actionable monitoring (2.2.0)
+
+`trace coverage`, `trace gtm summary`, `trace notifications show` and
+`trace notifications destinations` read the selected environment. `trace observations list`
+accepts `--kind tag_execution`, `--container-id`, `--tag-id` and `--result`;
+`trace issues list` accepts the same GTM identity filters.
+`trace notifications save|retry --input <file>` and
+`trace schema-baselines reset --input <file>` are explicit, version-guarded writes.
+See the [Trace workflow](../../plugins/siteos/skills/siteos-trace/references/actionable-monitoring.md)
+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.