@sun-asterisk/sungen 3.2.12-beta.10 → 3.2.12-beta.11

package/dist/orchestrator/templates/ai-src/skills/sungen-data-factory/SKILL.md

@@ -177,12 +177,20 @@ create-test.
 ## Cross-artifact check — testcase ↔ data agree
 
 `data validate` checks the data alone; **`sungen data crosscheck`** checks the testcase and its data
-AGREE: no dangling `{{var}}` (every referenced var has a value), a cross-screen `shared` dataset is
-identical across the journey (confirmation shows what setup entered), and a declared state-precondition
-is surfaced in the feature. Run it after the `.feature` exists; fix any `error`. Together
-`data validate` + `data crosscheck` are the **Data Gate + Cross-artifact Gate** (the `data-only`
-harness profile). Every `data gen` also stamps a `_fingerprint` (catalog+generator+context hash) so a
-reader/cache can tell whether the inputs that produced the data changed.
+AGREE **and are COMPLETE**: no dangling `{{var}}`; a cross-screen `shared` dataset is identical across
+the journey; a declared state-precondition is surfaced; **and — even when you author `@cases` by hand
+instead of merging `data gen` — the authored values COVER the BVA the field-map's constraints require
+and the login experience checklist**:
+- **`BVA_UNCOVERED`** — a bounded dimension is missing a boundary value. Classic miss: `email
+  minLength: 5` → you must have an email of length **4 (invalid), 5, 6**; a URL/code of length 5 does
+  NOT count (matched by type). Add the missing values (the exact BVA is in `data gen`'s output) or waive.
+- **`EXPERIENCE_UNCOVERED`** — a login/auth unit is missing credential-state scenarios: **soft-deleted**,
+  locked, unverified, password-expired, **valid-with-surrounding-whitespace** (trim → accept). Add each
+  (a seeded account in that state) or waive per spec.
+
+Treat these as MUST-ADDRESS in the create-test loop — they are exactly the gaps a QA reviewer catches.
+Together `data validate` + `data crosscheck` are the **Data Gate + Cross-artifact + Coverage Gate** (the
+`data-only` profile). Every `data gen` also stamps a `_fingerprint` (catalog+generator+context hash).
 
 ## Boundary completeness + trim
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sun-asterisk/sungen",
-  "version": "3.2.12-beta.10",
+  "version": "3.2.12-beta.11",
   "description": "Deterministic E2E Test Compiler - Gherkin + Selectors → Playwright tests",
   "main": "src/index.ts",
   "types": "src/index.ts",
@@ -39,8 +39,8 @@
     "@babel/types": "^7.28.5",
     "@cucumber/gherkin": "^37.0.0",
     "@cucumber/messages": "^31.0.0",
-    "@sungen/driver-data-factory": "3.2.12-beta.10",
-    "@sungen/driver-ui": "3.2.12-beta.10",
+    "@sungen/driver-data-factory": "3.2.12-beta.11",
+    "@sungen/driver-ui": "3.2.12-beta.11",
     "chalk": "^5.6.2",
     "commander": "^14.0.2",
     "dotenv": "^17.2.3",

package/src/orchestrator/templates/ai-src/skills/sungen-data-factory/SKILL.md

@@ -177,12 +177,20 @@ create-test.
 ## Cross-artifact check — testcase ↔ data agree
 
 `data validate` checks the data alone; **`sungen data crosscheck`** checks the testcase and its data
-AGREE: no dangling `{{var}}` (every referenced var has a value), a cross-screen `shared` dataset is
-identical across the journey (confirmation shows what setup entered), and a declared state-precondition
-is surfaced in the feature. Run it after the `.feature` exists; fix any `error`. Together
-`data validate` + `data crosscheck` are the **Data Gate + Cross-artifact Gate** (the `data-only`
-harness profile). Every `data gen` also stamps a `_fingerprint` (catalog+generator+context hash) so a
-reader/cache can tell whether the inputs that produced the data changed.
+AGREE **and are COMPLETE**: no dangling `{{var}}`; a cross-screen `shared` dataset is identical across
+the journey; a declared state-precondition is surfaced; **and — even when you author `@cases` by hand
+instead of merging `data gen` — the authored values COVER the BVA the field-map's constraints require
+and the login experience checklist**:
+- **`BVA_UNCOVERED`** — a bounded dimension is missing a boundary value. Classic miss: `email
+  minLength: 5` → you must have an email of length **4 (invalid), 5, 6**; a URL/code of length 5 does
+  NOT count (matched by type). Add the missing values (the exact BVA is in `data gen`'s output) or waive.
+- **`EXPERIENCE_UNCOVERED`** — a login/auth unit is missing credential-state scenarios: **soft-deleted**,
+  locked, unverified, password-expired, **valid-with-surrounding-whitespace** (trim → accept). Add each
+  (a seeded account in that state) or waive per spec.
+
+Treat these as MUST-ADDRESS in the create-test loop — they are exactly the gaps a QA reviewer catches.
+Together `data validate` + `data crosscheck` are the **Data Gate + Cross-artifact + Coverage Gate** (the
+`data-only` profile). Every `data gen` also stamps a `_fingerprint` (catalog+generator+context hash).
 
 ## Boundary completeness + trim