@milehimikey/em 1.22.1 → 1.22.2

package/.claude/skills/event-modeling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when the user runs `/event-modeling` (with or without a phase name), or wants to resume an
   event-modeling session without specifying which part of the process applies. Reads the model's

package/.claude/skills/event-modeling-conform/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-conform
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when checking a ratified event model (and its slice docs) for drift against the codebase
   that implements it — advisory only, never a gate, never an unprompted edit — or when walking

package/.claude/skills/event-modeling-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-design
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when structuring a draft event model into swimlanes and the four patterns (State Change,
   State View, Automation, Translation), evaluating a model's structural completeness, or writing

package/.claude/skills/event-modeling-discover/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-discover
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when starting a brand-new event model from scratch — greenfield discovery: brainstorming
   past-tense events, storyboarding the happy path, finding the commands and read models — or when

package/.claude/skills/event-modeling-engagement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-engagement
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when leading an engagement: building a named set of ratified event-modeling slices
   (`em engagement`) into one independent PR per slice, each against main, by dispatching the

package/.claude/skills/event-modeling-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-implement
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when building a single ratified event-modeling slice (status: ready-to-implement) into
   merged, tested code — the one phase where the agent builds rather than facilitates. Gates on

package/.claude/skills/event-modeling-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-review
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when starting em's live browser viewer (`em watch --serve`) so a team can watch a model
   update in real time, or facilitating a SCHEDULED stakeholder walkthrough that steps through

package/.claude/skills/event-modeling-shared/reference/em-dsl.md

@@ -369,6 +369,11 @@ enum Name { member, ... }           # closed named value set, reusable from any
 - **Tags:** `@Persona` only on `ui`; `@Context` only on `event`. Undeclared tags auto-create a
   row. Multi-word tags need no quoting — the tag captures everything after `@` to end of line
   (`ui Ticket Queue @Customer Service` matches `persona Customer Service`).
+- **Optional fields:** a trailing `?` on a field name marks it optional (it may be absent);
+  fields are required by default (MIL-237). `note?: text`, typeless `note?` and quoted
+  `"display name"?: text` all work, and the `?` is never part of the name. `em export` carries
+  `optional: true|false`, `em api generate` emits `name?: T`, the slice-doc table shows
+  Required `no`, and `em diff` / `em api check` report a required<->optional flip.
 - **`from "X"`** on views/automations declares the source(s); names are quoted, comma-separated.
   Matching is case-insensitive and whitespace-normalized. A `from` may never point at an event or
   view that first appears in a LATER slice (forward-only timeline — validation error).

package/.claude-plugin/marketplace.json

@@ -1,9 +1,9 @@
 {
-  "name": "em-1-22-1",
+  "name": "em-1-22-2",
   "owner": {
     "name": "Mike Key"
   },
-  "description": "em v1.22.1: the Event Modeling skill bundle and MCP server as a Claude Code plugin.",
+  "description": "em v1.22.2: the Event Modeling skill bundle and MCP server as a Claude Code plugin.",
   "plugins": [
     {
       "name": "em",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@milehimikey/em",
-  "version": "1.22.1",
+  "version": "1.22.2",
   "description": "AI-friendly Event Modeling — a slice-first text DSL rendered to a strict, self-contained Graphviz grid (SVG/PNG)",
   "type": "module",
   "bin": {

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "em",
-  "version": "1.22.1",
+  "version": "1.22.2",
   "description": "Event Modeling with em: discover, design, implement, conform, review and engagement skills over a slice-first text DSL, plus the em MCP server.",
   "author": {
     "name": "Mike Key"
@@ -10,7 +10,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "@milehimikey/em@1.22.1",
+        "@milehimikey/em@1.22.2",
         "mcp"
       ]
     }

package/plugin/shared/reference/em-dsl.md

@@ -370,6 +370,11 @@ enum Name { member, ... }           # closed named value set, reusable from any
 - **Tags:** `@Persona` only on `ui`; `@Context` only on `event`. Undeclared tags auto-create a
   row. Multi-word tags need no quoting — the tag captures everything after `@` to end of line
   (`ui Ticket Queue @Customer Service` matches `persona Customer Service`).
+- **Optional fields:** a trailing `?` on a field name marks it optional (it may be absent);
+  fields are required by default (MIL-237). `note?: text`, typeless `note?` and quoted
+  `"display name"?: text` all work, and the `?` is never part of the name. `em export` carries
+  `optional: true|false`, `em api generate` emits `name?: T`, the slice-doc table shows
+  Required `no`, and `em diff` / `em api check` report a required<->optional flip.
 - **`from "X"`** on views/automations declares the source(s); names are quoted, comma-separated.
   Matching is case-insensitive and whitespace-normalized. A `from` may never point at an event or
   view that first appears in a LATER slice (forward-only timeline — validation error).

package/plugin/skills/conform/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: conform
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when checking a ratified event model (and its slice docs) for drift against the codebase
   that implements it — advisory only, never a gate, never an unprompted edit — or when walking

package/plugin/skills/design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: design
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when structuring a draft event model into swimlanes and the four patterns (State Change,
   State View, Automation, Translation), evaluating a model's structural completeness, or writing

package/plugin/skills/discover/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: discover
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when starting a brand-new event model from scratch — greenfield discovery: brainstorming
   past-tense events, storyboarding the happy path, finding the commands and read models — or when

package/plugin/skills/engagement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: engagement
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when leading an engagement: building a named set of ratified event-modeling slices
   (`em engagement`) into one independent PR per slice, each against main, by dispatching the

package/plugin/skills/event-modeling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: event-modeling
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when the user runs `/em:event-modeling` (with or without a phase name), or wants to resume an
   event-modeling session without specifying which part of the process applies. Reads the model's

package/plugin/skills/implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: implement
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when building a single ratified event-modeling slice (status: ready-to-implement) into
   merged, tested code — the one phase where the agent builds rather than facilitates. Gates on

package/plugin/skills/review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review
-em-version: 1.22.1
+em-version: 1.22.2
 description: >-
   Use when starting em's live browser viewer (`em watch --serve`) so a team can watch a model
   update in real time, or facilitating a SCHEDULED stakeholder walkthrough that steps through