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

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

@@ -85,12 +85,15 @@ This is the core discipline: *common is never enough; when blind, think and ask
 ## Customizing the catalog — `.overwrite` (survives `sungen update`)
 
 The shipped `common/` is a floor. Project rules go in `qa/data-factory/common.overwrite.yaml`,
-deep-merged over the common (**later-wins**, keyed by `type` + data-point `id`): same `id` replaces,
-new `id` appends, `constraints` merge key-by-key. `sungen update` refreshes `common/` but never
-touches your overlay. If an update makes an overlay entry stale (references a bank/constraint that no
-longer exists), the loader **warns you to prune it** — it never edits your file. Prefer a targeted
-`errorMap`/`constraints` in the field-map for per-screen tweaks; use `.overwrite` only for rules that
-apply project-wide.
+deep-merged over the common (**later-wins**, keyed by `type` + data-point `id`) via three explicit
+operations: **EXTEND** (a new `id` appends), **REPLACE** (same `id` wins; `constraints` merge
+key-by-key), **DISABLE** (list ids under `disable:` to drop shipped cases that don't apply — a stale
+target id warns). You can also override `security:` banks and `techniques:` the same way. `sungen
+update` refreshes `common/` but never touches your overlay; a stale entry **warns you to prune it** —
+it never edits your file. Nothing is silently overwritten: **`sungen data provenance`** (and a
+`⟲ .overwrite →` line at `data gen`) shows exactly what your overlay changed, and each overlaid value
+is tagged `via: .overwrite` in the test-data. Prefer a targeted `errorMap`/`constraints` in the
+field-map for per-screen tweaks; use `.overwrite` only for rules that apply project-wide.
 
 ## Bulk-import fixtures (CSV)
 

package/package.json

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

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

@@ -85,12 +85,15 @@ This is the core discipline: *common is never enough; when blind, think and ask
 ## Customizing the catalog — `.overwrite` (survives `sungen update`)
 
 The shipped `common/` is a floor. Project rules go in `qa/data-factory/common.overwrite.yaml`,
-deep-merged over the common (**later-wins**, keyed by `type` + data-point `id`): same `id` replaces,
-new `id` appends, `constraints` merge key-by-key. `sungen update` refreshes `common/` but never
-touches your overlay. If an update makes an overlay entry stale (references a bank/constraint that no
-longer exists), the loader **warns you to prune it** — it never edits your file. Prefer a targeted
-`errorMap`/`constraints` in the field-map for per-screen tweaks; use `.overwrite` only for rules that
-apply project-wide.
+deep-merged over the common (**later-wins**, keyed by `type` + data-point `id`) via three explicit
+operations: **EXTEND** (a new `id` appends), **REPLACE** (same `id` wins; `constraints` merge
+key-by-key), **DISABLE** (list ids under `disable:` to drop shipped cases that don't apply — a stale
+target id warns). You can also override `security:` banks and `techniques:` the same way. `sungen
+update` refreshes `common/` but never touches your overlay; a stale entry **warns you to prune it** —
+it never edits your file. Nothing is silently overwritten: **`sungen data provenance`** (and a
+`⟲ .overwrite →` line at `data gen`) shows exactly what your overlay changed, and each overlaid value
+is tagged `via: .overwrite` in the test-data. Prefer a targeted `errorMap`/`constraints` in the
+field-map for per-screen tweaks; use `.overwrite` only for rules that apply project-wide.
 
 ## Bulk-import fixtures (CSV)