sad-mcp 1.0.1 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sad-mcp",
3
- "version": "1.0.1",
3
+ "version": "1.0.2",
4
4
  "description": "MCP server for Software Analysis and Design course materials at BGU",
5
5
  "type": "module",
6
6
  "bin": {
@@ -184,9 +184,9 @@ Plain double circle, NO icon inside:
184
184
  - When arrows must cross, make the crossing perpendicular (one horizontal, one vertical) so it's visually clear.
185
185
 
186
186
  ### Separate connection points
187
- - **NEVER attach two arrows to the same point on a task/gateway.** If a task has 2 incoming arrows, connect them to different spots on the border (e.g., one to the top edge, one to the left edge). Same for outgoing arrows.
188
- - For gateways with multiple outgoing branches: use different edges of the diamond (top, bottom, left, right) for different branches.
189
- - For tasks: use the 4 edges (top, bottom, left, right) to spread out connections. Never stack two arrows on the same edge point.
187
+ - **NEVER attach two arrows to the exact same point.** Multiple arrows CAN connect to the same side/edge of a shape, but they must be spaced apart along that edge (e.g., 2-3 arrows on the top edge of a task, each at a different x-coordinate with at least 15px between them).
188
+ - For gateways with multiple outgoing branches: use different edges of the diamond (top, bottom, left, right) OR spread multiple connections along one edge.
189
+ - For tasks: use all 4 edges (top, bottom, left, right) and spread connections along each edge as needed. A single edge can have 2-3 connection points.
190
190
 
191
191
  ### Labels
192
192
  - Labels (כן/לא) near the gateway, not at path end.