sad-mcp 2.1.0 → 2.1.1

package/dist/usecase/validate.js

@@ -318,6 +318,15 @@ export function validateModel(model) {
             // Wireframe safety pre-check (regex-only; defense in depth — the HTML runtime
             // also re-checks via wireframeSafe()).
             const wf = uc.wireframe;
+            // §WF — a UC initiated by a human actor must have a wireframe.
+            if (primaryActor && actorIds.has(primaryActor)) {
+                const pa = actors.find((a) => String(a.id) === primaryActor);
+                const isHuman = !pa || pa.actorType !== "system";
+                const wfMissing = typeof wf !== "string" || wf.trim() === "";
+                if (isHuman && wfMissing) {
+                    err("wireframe-missing", `${path}.wireframe`, `UC "${id}" has a human primary actor ("${primaryActor}") but no wireframe. Every human-initiated UC requires a wireframe per §WF. Add one, or explicitly use a placeholder describing what info is missing.`);
+                }
+            }
             if (typeof wf === "string" && wf.length > 0) {
                 const forbidden = [
                     /<script\b/i,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sad-mcp",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "description": "MCP server for Software Analysis and Design course materials at BGU",
   "type": "module",
   "bin": {

package/skills/uml-use-case-diagram/SKILL.md

@@ -789,9 +789,15 @@ The `connections` entry for a timed link looks like:
 
 ---
 
-## §WF. Wireframe Authoring (Per-UC, Optional)
+## §WF. Wireframe Authoring (Mandatory for Human-Initiated UCs)
 
-Where a UC benefits from a visual mock of the UI the user sees, emit a wireframe as an inline HTML fragment and attach it to `useCaseDocs[ucId].wireframe`. The modal renderer (§8a) injects the fragment after passing a safety check (see `wireframeSafe()` in §8a).
+**A wireframe is required for every UC whose `primaryActor.actorType === 'human'`.** The user sees a screen; a use case without a visual mock of that screen is incomplete documentation. The validator (§12) errors on any human-initiated UC missing a wireframe.
+
+Wireframe is **optional** (and usually omitted) only for:
+- UCs whose primary actor is a system or cron (`actorType: 'system'`) — no human sees a screen.
+- Pure include-target UCs (sub-behaviors with no actor association).
+
+For every other UC, emit a wireframe as an inline HTML fragment and attach it to `useCaseDocs[ucId].wireframe`. The modal renderer (§8a) injects the fragment after passing a safety check (see `wireframeSafe()` in §8a).
 
 Claude authors the wireframe using its own UI-generation judgment — there is no DSL. But the skill enforces a consistent look and safe sandbox via a scoped CSS theme and a set of forbidden patterns.
 
@@ -860,9 +866,10 @@ The `wireframeSafe()` regex rejects any of the following. A failing wireframe re
 
 ### When NOT to include a wireframe
 
-- The UC has no user-facing screen (e.g., a back-end cron job, an automated reconciliation).
-- The UI is trivial (e.g., a single "Approve" confirmation prompt) — prose in the scenario flow is enough.
-- You cannot author the wireframe without making up details the spec does not support — put those in `diagramModel.openQuestions` instead.
+- Primary actor is a system / cron (`actorType: 'system'`) — e.g., a back-end reconciliation triggered by the clock.
+- The UC is purely an `«include»` target (a sub-behavior, not a user-visible goal).
+
+**"The UI is trivial" is not a valid reason to skip.** A single approval prompt still deserves a mock — it shows the reader what the button says, what data is visible on the screen, and what confirmation text appears. If you genuinely cannot author the wireframe because the spec is silent, record the gap in `diagramModel.openQuestions` AND still emit a placeholder wireframe with the questions visible inside it.
 
 ---
 
@@ -1188,7 +1195,8 @@ Briefly report: actor count, use case count, include/extend count, whether split
 - [ ] Every `primaryActor` id exists in `actors[]` AND has an association with `role: 'initiator'` on that UC (aligning §4.1 with §4.4).
 - [ ] Every flow step of `kind: 'actor'` references a real actor id; every `kind: 'include'` references a real UC id; every `extension.at` references a valid step number in its scenario's flow.
 - [ ] Clicking a UC on the diagram opens the full-screen modal (§8a); Esc / backdrop click closes it. Step actor/UC references are clickable. Actor popup + association popup (§8b) still work for non-UC clicks.
-- [ ] Any `wireframe` HTML passes `wireframeSafe()` (no `<script>`, no `on*=`, no `<iframe>`, no external URLs, no `@import`, no inline `<style>`); all classes are `wf-*` only.
+- [ ] Every UC whose primary actor is human has a wireframe (§WF). System/cron-initiated UCs and pure include-targets may omit.
+- [ ] Any `wireframe` HTML passes `wireframeSafe()` (no `<script>`, no `on*=`, no `<iframe>`, no external URLs, no `@import`, no inline `<style>`); all classes are `wf-*` only; visible text is in Hebrew.
 - [ ] Every actor-UC association has a written §4.1 justification block (role, initiates? one-line "why"); every UC has ≥1 association with `initiates = yes`.
 - [ ] Every association line carries a transparent click-hitbox (stroke-width ≥12, `data-conn-id`) wired to `showDesc(id,'assoc',event)`; `assocDescriptions` entry exists for each id.
 - [ ] `assumptions` and `openQuestions` arrays are present in `diagramModel`; the HTML renders the bottom panel whenever either is non-empty.