@milehimikey/em 1.19.4 → 1.19.6

package/plugin/shared/reference/methodology.md

@@ -364,8 +364,10 @@ drift into **CRUD laid on a timeline**; these rules stop that. Quoted lines are
   ```
 - **One event, two commands.** When two commands record the same fact, repeat the event bare
   (`event X @Ctx`, same name and context) in the second slice: it inherits the first declaration, no
-  marker needed. Declaring different fields is `shared-event-field-mismatch`. (The arrow set for a
-  shared event read by a repeated view is under review: GH #328.)
+  marker needed. Declaring different fields is `shared-event-field-mismatch`. Each recording site
+  feeds the nearest instance of the reading view at or after it: a `view X again from "E"` draws
+  arrows only from the sites of E recorded since the previous instance of X that also reads E (the
+  first instance keeps every site at or before it).
   ```em
   model "Ordering"
 

package/plugin/skills/conform/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: conform
-em-version: 1.19.4
+em-version: 1.19.6
 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/conform/reference/conform.md

@@ -264,7 +264,8 @@ canonical model or a slice doc unprompted** — walk the report with the user, a
 proposals they approve, then re-render and `em validate`.
 
 **Also write the findings JSON (MIL-214).** Alongside the report, write
-`conformance/<YYYY-MM-DD>-findings.json` — one entry per `### n.` finding, ids matching the
+`conformance/<YYYY-MM-DD>-findings.json` (write the plain name; `em slice conform` also reads
+`<YYYY-MM-DD>-<name>-findings.json`) — one entry per `### n.` finding, ids matching the
 report's own numbering. Shape (`findingsSchemaVersion: "1.0"`, additive-only, 2-space indent,
 keys sorted, findings sorted by `id`, trailing newline):
 

package/plugin/skills/design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: design
-em-version: 1.19.4
+em-version: 1.19.6
 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.19.4
+em-version: 1.19.6
 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.19.4
+em-version: 1.19.6
 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.19.4
+em-version: 1.19.6
 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.19.4
+em-version: 1.19.6
 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/implement/reference/implement.md

@@ -43,15 +43,17 @@ every `## Open Questions` checkbox is checked, and no status/version/link incohe
 - `fields-completeness/event-field-no-source`: the `assigned` marker contract (MIL-148).
 - `invariants/public-command-without-invariants`: the API-first readiness requirement (`docs/process.md`).
 
-A warning whose code is in this list blocks; any other warning never does (it stays in `diagnostics`; don't treat it as a blocker). `--strict` promotes advisory rules only.
+A warning whose code is in this list blocks; any other warning never does — `command-repeated-across-slices`, `timeline-entity-clustered`, `fields-completeness/view-field-no-source`, `open-issue`, `doc-model-*`, `note-binding-*` and the shape lints stay in `diagnostics` and are not blockers. `--strict` promotes advisory rules only.
+
+Because of that list, `ready` can be `false` with every `gates` entry `true` (a `both-ends-of-a-flow/*` warning on one of the slice's own elements, say). Don't work it out from `gates`: read **`blockedBy`** (schema `1.5`, GH #377), the codes that flipped `ready`, `[]` exactly when it is `true`, and report those codes with the `false` gates when you hand the slice back.
 
 **`ready: false` means stop** — with one named exception: a slice already `status: implemented`
 with `driftSignal: in-sync` or `uncertified` (MIL-214) also reads `ready: false` (its
 `statusReady` gate fails because nothing is newly ratified), and that specific case is
 re-implementation/repair, not a blocker — see §3's third mode before treating it as one. For
 every other `false`, report which `gates`
-entries are `false` (and any `diagnostics` entries concerning this slice) and hand the slice
-back to the humans. Never make the gate pass yourself — checking an open-question box, flipping
+entries are `false` and what `blockedBy` names (and any `diagnostics` entries concerning this
+slice) and hand the slice back to the humans. Never make the gate pass yourself — checking an open-question box, flipping
 `status`, or editing frontmatter are ratification decisions, and ratification happens in a
 facilitated session, not in an implementation branch.
 

package/plugin/skills/review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review
-em-version: 1.19.4
+em-version: 1.19.6
 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