@sun-asterisk/sungen 3.2.12-beta.4 → 3.2.12-beta.6

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

@@ -100,8 +100,11 @@ field-map for per-screen tweaks; use `.overwrite` only for rules that apply proj
 For CSV/Excel import or bulk-upload testing, `sungen data fixture --screen <name> [--rows N] [--invalid]`
 turns the field-map into a fixture FILE under `qa/fixtures/`: `<name>.csv` (N valid rows; nested groups
 → dotted headers; `unique` fields row-indexed) that should import cleanly, and — with `--invalid` —
-`<name>.invalid.csv` (one seeded-bad row per field + a `_violation` column) for row-level rejection
-tests. Reference it from an `@api` upload (`files:`) or a UI file input.
+`<name>.invalid.csv` (one seeded-bad row per field, **same columns as the valid file so a strict
+importer fails on the data, not an extra column**) plus a **sidecar** `<name>.invalid.expected.yaml`
+that says which 0-based row must be rejected and why (`field`, `chk`, `reason`, `expected_error`).
+Reference the CSV from an `@api` upload (`files:`) or a UI file input, and assert row rejection against
+the sidecar.
 
 ## Verify before done — the phuong-phap §6 checklist
 
@@ -120,6 +123,14 @@ constraints and every synthesized `invalid` value actually violates them. A boun
 a constraint — fix the field-map/constraints and re-run. This is what stops the "structurally right but
 semantically wrong" data (e.g. a "below minimum length" case that is actually long enough to pass).
 
+**Applicability & profiles.** The generator only emits cases that apply, and reports the rest (never
+silent). Set **`required: true|false`** correctly — an optional field drops the "empty (required)" case;
+a numeric field with `min ≥ 0` drops the negative example. Security/injection payloads land in their own
+**`adversarial:`** bucket, separate from `invalid:`. Dropped cases show up as `_not_applicable` in the
+output + a `NOT_APPLICABLE` lint info. A `--profile` (`regression` default · `functional` · `smoke` ·
+`security-min`) and `--locale`/`--channel`/`--sink` on `data gen|validate|lint` select a reduced set;
+selection is deterministic. Prefer setting `required` in the field-map over disabling the empty case.
+
 ## Weaving into scenarios
 
 When a `.feature` exists, express invalid/boundary sets as data-driven `Scenario Outline` + `Examples`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sun-asterisk/sungen",
-  "version": "3.2.12-beta.4",
+  "version": "3.2.12-beta.6",
   "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.4",
-    "@sungen/driver-ui": "3.2.12-beta.4",
+    "@sungen/driver-data-factory": "3.2.12-beta.6",
+    "@sungen/driver-ui": "3.2.12-beta.6",
     "chalk": "^5.6.2",
     "commander": "^14.0.2",
     "dotenv": "^17.2.3",

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

@@ -100,8 +100,11 @@ field-map for per-screen tweaks; use `.overwrite` only for rules that apply proj
 For CSV/Excel import or bulk-upload testing, `sungen data fixture --screen <name> [--rows N] [--invalid]`
 turns the field-map into a fixture FILE under `qa/fixtures/`: `<name>.csv` (N valid rows; nested groups
 → dotted headers; `unique` fields row-indexed) that should import cleanly, and — with `--invalid` —
-`<name>.invalid.csv` (one seeded-bad row per field + a `_violation` column) for row-level rejection
-tests. Reference it from an `@api` upload (`files:`) or a UI file input.
+`<name>.invalid.csv` (one seeded-bad row per field, **same columns as the valid file so a strict
+importer fails on the data, not an extra column**) plus a **sidecar** `<name>.invalid.expected.yaml`
+that says which 0-based row must be rejected and why (`field`, `chk`, `reason`, `expected_error`).
+Reference the CSV from an `@api` upload (`files:`) or a UI file input, and assert row rejection against
+the sidecar.
 
 ## Verify before done — the phuong-phap §6 checklist
 
@@ -120,6 +123,14 @@ constraints and every synthesized `invalid` value actually violates them. A boun
 a constraint — fix the field-map/constraints and re-run. This is what stops the "structurally right but
 semantically wrong" data (e.g. a "below minimum length" case that is actually long enough to pass).
 
+**Applicability & profiles.** The generator only emits cases that apply, and reports the rest (never
+silent). Set **`required: true|false`** correctly — an optional field drops the "empty (required)" case;
+a numeric field with `min ≥ 0` drops the negative example. Security/injection payloads land in their own
+**`adversarial:`** bucket, separate from `invalid:`. Dropped cases show up as `_not_applicable` in the
+output + a `NOT_APPLICABLE` lint info. A `--profile` (`regression` default · `functional` · `smoke` ·
+`security-min`) and `--locale`/`--channel`/`--sink` on `data gen|validate|lint` select a reduced set;
+selection is deterministic. Prefer setting `required` in the field-map over disabling the empty case.
+
 ## Weaving into scenarios
 
 When a `.feature` exists, express invalid/boundary sets as data-driven `Scenario Outline` + `Examples`