@stalfh233/omc-cli 0.4.14 → 0.4.16

package/skills/omc-acceptance-criteria.md

@@ -1,47 +1,47 @@
----
-name: omc-acceptance-criteria
-description: Decide whether a CLI change is accepted. Use before claiming done: readback, delivery-state, zero-residue, and negative-test gates.
----
-
-# Acceptance Criteria (验收标准)
-
-A change is accepted only when every gate below holds.
-
-## Per-write
-
-1. **Environment permission** — `writable:true` admits the write; `writable:false` refuses before wire. A production write additionally carries `confirmProduction:true` and records `productionConfirmed:true`.
-2. **Authoritative readback** — the post-write read proves the intended state from the authoritative face (`field.list` published face, `form.get` published flags, `data.load` for M2 data, `onlinejs.compose` publishedHtmlJson + SHA-256 for Online JS). "Called without error" is not acceptance.
-3. **Delivery state recorded** — the `.omc/` artifact exists with `deliveryState: DELIVERED` and the environment fingerprint.
-4. **Zero residue** — fixtures removed and exact absence proven on every face (draft and published); final state CLEANED.
-
-## Per-session
-
-5. **`uncertain` resolved** — every uncertain outcome was re-discovered before any further write.
-6. **Secrets zero-echo** — no output, artifact, or error contains the credential or bearer token.
-7. **Boundaries respected** — every `capability-out-of-coverage` refusal was treated as a boundary, not retried through another tool.
-8. **Draft gate evidenced** — if the session performed any write, the report must attach each design draft it presented and the human's approval turn(s) (and every revision). A write with no preceding draft/approval record fails acceptance — read `omc-config-draft-review`.
-
-## Portal/DOM acceptance (opt-in, real platform)
-
-Storage readback is NOT platform consumption. When the change is a form/design
-artifact, the strongest acceptance is the opt-in live batteries — and they ARE
-the "open a browser" step; do not report "no portal acceptance entry point":
-
-- `npm run test:live` — designer canvas, condition panels **and the condition
-  dialog must render >=1 rule row** (a serialization can crash the formatter and
-  silently drop the row while the panel still says "Set"), portal fields (two
-  loads), list columns, list buttons, Online JS wrapper + `window.h3form` boot.
-- `npm run test:live-workflow` — two-stage workflow + rule write-back via
-  `data.save(workflowCode)` → `workitem.list` → `data.submit` → `data.load`.
-- `npm run test:live-permission` — node field permissions read from
-  `form/load.formPermission.dataPermissions` as a NON-admin participant (an
-  admin is force-granted `e:true`).
-
-## Negative baseline (must stay green)
-
-- Read-only environment → `environment-write-disabled`, zero wire calls.
-- Writable production without `confirmProduction:true` → `production-confirmation-required`, zero wire calls.
-- Concurrent writes → serialized by the write lease (max 1 in flight).
-- Blocked lane (e.g. `W2-permissions`) → refused with citation.
-- Transport outage during a write → `uncertain` + `frozen`, never `ok`.
-- Non-8.6 version (or missing version evidence) → writes fail closed.
+---
+name: omc-acceptance-criteria
+description: Decide whether a CLI change is accepted. Use before claiming done: readback, delivery-state, zero-residue, and negative-test gates.
+---
+
+# Acceptance Criteria (验收标准)
+
+A change is accepted only when every gate below holds.
+
+## Per-write
+
+1. **Environment permission** — `writable:true` admits the write; `writable:false` refuses before wire. A production write additionally carries `confirmProduction:true` and records `productionConfirmed:true`.
+2. **Authoritative readback** — the post-write read proves the intended state from the authoritative face (`field.list` published face, `form.get` published flags, `data.load` for M2 data, `onlinejs.compose` publishedHtmlJson + SHA-256 for Online JS). "Called without error" is not acceptance.
+3. **Delivery state recorded** — the `.omc/` artifact exists with `deliveryState: DELIVERED` and the environment fingerprint.
+4. **Zero residue** — fixtures removed and exact absence proven on every face (draft and published); final state CLEANED.
+
+## Per-session
+
+5. **`uncertain` resolved** — every uncertain outcome was re-discovered before any further write.
+6. **Secrets zero-echo** — no output, artifact, or error contains the credential or bearer token.
+7. **Boundaries respected** — every `capability-out-of-coverage` refusal was treated as a boundary, not retried through another tool.
+8. **Draft gate evidenced** — if the session performed any write, the report must attach each design draft it presented and the human's approval turn(s) (and every revision). A write with no preceding draft/approval record fails acceptance — read `omc-config-draft-review`.
+
+## Portal/DOM acceptance (opt-in, real platform)
+
+Storage readback is NOT platform consumption. When the change is a form/design
+artifact, the strongest acceptance is the opt-in live batteries — and they ARE
+the "open a browser" step; do not report "no portal acceptance entry point":
+
+- `npm run test:live` — designer canvas, condition panels **and the condition
+  dialog must render >=1 rule row** (a serialization can crash the formatter and
+  silently drop the row while the panel still says "Set"), portal fields (two
+  loads), list columns, list buttons, Online JS wrapper + `window.h3form` boot.
+- `npm run test:live-workflow` — two-stage workflow + rule write-back via
+  `data.save(workflowCode)` → `workitem.list` → `data.submit` → `data.load`.
+- `npm run test:live-permission` — node field permissions read from
+  `form/load.formPermission.dataPermissions` as a NON-admin participant (an
+  admin is force-granted `e:true`).
+
+## Negative baseline (must stay green)
+
+- Read-only environment → `environment-write-disabled`, zero wire calls.
+- Writable production without `confirmProduction:true` → `production-confirmation-required`, zero wire calls.
+- Concurrent writes → serialized by the write lease (max 1 in flight).
+- Blocked lane (e.g. `W2-permissions`) → refused with citation.
+- Transport outage during a write → `uncertain` + `frozen`, never `ok`.
+- Non-8.6 version (or missing version evidence) → writes fail closed.