@milehimikey/em 1.14.0 → 1.14.2

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

@@ -1,6 +1,6 @@
 ---
 name: event-modeling
-em-version: 1.14.0
+em-version: 1.14.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.14.0
+em-version: 1.14.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.14.0
+em-version: 1.14.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
@@ -211,6 +211,7 @@ For each slice:
    (`em validate` flags a block missing one as `slice-doc/structured-section-malformed`, and
    `--slice-ready` refuses it). A doc written before em 1.14 has no markers; leave it as it is
    unless you are re-creating it (`em slice new … --wire --force`, carrying the prose across).
+   A question this version will not answer is deferred with `em slice defer <model> <key> "<question>" --until v<n> --decision "<what this version does>"` — never left `- [ ]`, never deleted, never answered by guessing.
 2. **First-time authoring:** scaffold the doc mechanically rather than hand-writing the
    frontmatter — `em slice new "<slice name>" --pattern <state-change|state-view|automation|
    translation> --swimlane "<Persona> → <Context>" --wire <model>.em` writes `slices/<slice-name>.md`

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

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-discover
-em-version: 1.14.0
+em-version: 1.14.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.14.0
+em-version: 1.14.2
 description: >-
   Use when leading an engagement: building a named set of ratified event-modeling slices
   (`em engagement`) into a stack of PRs by dispatching the em-implementer, em-validator,

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

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-implement
-em-version: 1.14.0
+em-version: 1.14.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-implement/reference/implement.md

@@ -228,7 +228,10 @@ a bump here is a ledger defect.
 `em slice mark-implemented <model>.em <slice-key> <pr-url>` does the flip for you (MIL-103) —
 resolves the doc via the same note-binding join `--slice-ready` uses, is idempotent on a re-run
 with the same URL, and refuses (never silently overwrites) if the doc is already `implemented`
-with a different URL. Prefer it over hand-editing the doc's frontmatter.
+with a different URL. It also refuses a doc that isn't `ready-to-implement` (MIL-277): if it
+reports `doc is \`status: draft\``/`reviewed`, the slice was never ratified — stop and surface
+that to the human rather than editing the frontmatter by hand; the §1 gate should have caught it.
+Prefer it over hand-editing the doc's frontmatter.
 
 Then, if the project keeps a model README (from `../../event-modeling-shared/templates/model-readme.md`), run
 `em slice index <model-name>.em` so its generated Slices table reflects the new status and

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

@@ -1,6 +1,6 @@
 ---
 name: event-modeling-review
-em-version: 1.14.0
+em-version: 1.14.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
@@ -56,7 +56,7 @@ review:` marker (mirrors `Last conformance:`).
 **Per-slice outcome.** A slice whose open questions are all resolved in the room →
 `em slice review <model>.em <key> --by <name>` (flips its doc to `status: reviewed` and records
 `reviewedBy:`/`reviewedOn:`). Anything still open stays `draft` — the walkthrough doesn't decide
-it, the next session or the open-questions list does.
+it, the next session or the open-questions list does. A question this version will not answer is deferred with `em slice defer <model> <key> "<question>" --until v<n> --decision "<what this version does>"` — never left `- [ ]`, never deleted, never answered by guessing.
 
 **The facilitator never ratifies, never offers to ratify, and never suggests ratification in a
 review session. Ratification is a separate human gate after review**