openxiangda 1.0.133 → 1.0.135

package/README.md

@@ -33,6 +33,10 @@ openxiangda data-view list --profile dev
 openxiangda data-view status ticket_with_customer --profile dev
 openxiangda doctor --profile dev --json
 openxiangda design gates --topic public-access --json
+openxiangda sdd context --json
+openxiangda sdd propose add-customer-page --pages customer --runtime
+openxiangda sdd approve add-customer-page --summary "用户确认"
+openxiangda sdd verify add-customer-page --changed
 openxiangda resource validate --profile dev
 openxiangda resource plan --profile dev
 openxiangda resource publish --profile dev
@@ -78,6 +82,8 @@ Domestic npm mirrors may lag and return an older OpenXiangda version. `openxiang
 
 Architecture-class requests are plan-gated by default. For new apps, complex pages, login/register, public/no-login access, role/data-scope design, workflow/automation, App Function, connector, notification, and external integration work, AI agents must plan first and implement only after the user confirms the design.
 
+High-risk implementation is also SDD-gated. New workspaces include `openspec/` by default. Before changing forms, pages, resources, functions, automations, workflows, JS_CODE nodes, runtime code, or `app-workspace.config.ts`, run `openxiangda sdd context --json`, create or continue a change with `openxiangda sdd propose <change>`, and wait for `openxiangda sdd approve <change>`. Release checks fail when high-risk targets are not covered by an approved active change; emergency releases can use `--sdd-bypass --reason "..."`, which writes `openspec/changes/bypass-log.md`.
+
 Before confirmation, agents may read, inspect, snapshot, dry-run, ask questions, and output/write the architecture document. They must not edit source files, mutate platform resources, publish, deploy, send notifications, or call live write/delete endpoints.
 
 Use the discoverable gate commands: