@siteoshq/cli 1.1.1 → 1.3.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 and Integrations. This source prepares version 1.1.1; publishing is a separate release.
+Search, Trace, SEO and Integrations. This source prepares version 1.3.0; publishing is a separate release.
 Node.js 22 or newer is required.
 
 ## Install and authenticate
@@ -22,7 +22,7 @@ grants; the durable session never reaches a product endpoint.
 
 ## Hosted origins
 
-CLI 1.1.1 defaults to `https://app.siteos.sh` for Auth and every service. Existing credentials
+CLI 1.2.0 defaults to `https://app.siteos.sh` for Auth and every service. Existing credentials
 and repository bindings retain their selected origin; sign in again when moving installations.
 Never copy private state between production and staging.
 
@@ -69,7 +69,7 @@ siteos project environment connect forms --environment production --resource '<f
 Omit `--resource` to create a new local environment. `siteos project environment list` reports the
 common catalog and connections. Forms/Search/Trace operational `--environment` flags accept common
 slugs and resolve explicit native bindings; without the flag, commands use the selected environment.
-Pulse/Cookie use separate bound resources per environment. Missing bindings fail without a fallback.
+Pulse/Cookie/SEO use separate bound resources per environment. Missing bindings fail without a fallback.
 Manage names and website URLs with `project update` and `project environment update <slug>`.
 Cookie/Trace published addresses remain unchanged until explicit republication.
 
@@ -136,6 +136,35 @@ snippet is unavailable until runtime publication succeeds. Integrations connecti
 Organization; provider authorization opens the shared browser flow, and notification destinations
 are connected explicitly by each service.
 
+### SEO (prepared for release)
+
+Check `siteos seo --help` before use; install a matching release only after it is published. An
+SEO-capable server returns SEO in its Project service catalog, which older strict CLI parsers may
+reject. Coordinate the CLI update before that server rollout, then publish the matching plugin.
+
+```sh
+siteos project connect seo --json
+siteos seo status --environment production --json
+siteos seo audit run --environment production --json
+siteos seo audit list --json
+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
+```
+
+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.
+`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
+`--revision` (0 before the first decision). They use a distinct issue-write scope. Read back the
+decision after success; a revision conflict requires refreshing it. Ignore never means resolved.
+All SEO commands resolve the selected common Project and explicit environment binding. Current
+Auth policy permits CLI service-grant issuance to Organization owners/admins. JSON uses contract
+version 1 and does not include credentials. The focused plugin skill is `siteos-seo`.
+
 ## Local state and diagnostics
 
 ```sh
@@ -183,3 +212,22 @@ pnpm --dir packages/cli pack:check
 ```
 
 `pack:check` creates the publishable tarball locally. It does not publish the package.
+
+## Cookie verification
+
+CLI 1.2.0 adds `cookie schema`, `cookie validate --input draft.json`,
+`cookie regions resolve --country GB --source published` and `cookie restore --input restore.json`.
+Restore changes the draft only. Validation makes no write and reports a stale draft version.
+
+From the selected website repository, run `siteos cookie verify --json` or
+`siteos cookie verify --url /pricing --browser webkit --json`. Install the matching local browser
+when requested with `npx playwright@1.61.1 install chromium` or `npx playwright@1.61.1 install webkit`.
+The check opens fresh contexts, exercises the public consent API and reports request origins and
+storage names without values, query strings, request bodies or authenticated sessions. These are
+real visits; normal installation/aggregate signals may be recorded. Reports remain local.
+
+A report records the revision, runtime, observed Edge location, scenario scope and 24-hour expiry.
+`passed` exits 0; `needs-review` and `failed` exit 1. Unknown origins/storage require classification.
+The check covers one route and a bounded observation window, not hidden first-party/server-side
+tracking, every delayed interaction, visual accessibility or legal compliance. Repeat after
+website/publication changes and preserve a separate GTM Tag Assistant check where applicable.