@siteoshq/cli 2.6.0 → 2.7.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Pixel Point
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

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.0; 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
@@ -10,6 +10,11 @@ Service-local `project` and `environment` commands have been removed; use `siteo
 
 Node.js 22 or newer is required.
 
+## License
+
+The `@siteoshq/cli` package is licensed under the [MIT License](./LICENSE).
+Copyright (c) 2026 Pixel Point.
+
 ## Install and authenticate
 
 ```sh
@@ -411,3 +416,29 @@ 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.
+
+
+## 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.