Fix review findings: importer DoS, sync data loss, views/profile rendering, docs

Source importers: lstat before open so FIFOs no longer hang the directory
walk; replace the quadratic Rust macro regex with a linear scan.
Three-way sync: report page add/add and delete-vs-modify as conflicts
instead of silently overwriting or resurrecting; canonical comparison so
key order is not a change; the sync action withholds output and fails on
conflicts unless --force. Story publishing escapes <, >, & and U+2028/9
inside the embedded JSON.
Views: drop parentId of unselected containers, re-layout instead of
manual geometry, validate before serialising; flatten() merges identical
nodes repeated across pages so C4 output works with every analysis
action. Dark theme edge labels get a background; tube-map corridors sit
above the stations; C4 containers keep the swimlane style and orphan
relationships land on the matching page; router keeps container header
bands as obstacles; sequence self-messages loop on one side.
Docs: SKILL.md lists all 23 CLI actions and how each capability family
is invoked, task wrappers for query/test/what-if/doctor, capability
tables and --page scope corrected, maintenance snippet uses the real
synchronous action signature, duplicated rule bullets moved to the rule
references, coverage matrix wording made verifiable.

Co-Authored-By: Claude Code <noreply@anthropic.com>

references/rules-layout.md

@@ -27,7 +27,49 @@ These rules are **MANDATORY** — apply them when generating any diagram.
   - `startSize=40`, 1 row h=80: total = 40+40+80+40 = 200 (children at y=80)
   - `startSize=40`, 2 rows h=40 each: total = 40+40+40+40+40+40 = 240 (row1 at y=80, row2 at y=160)
 
-  After generating or editing a diagram, run `page-spacing-audit` and `page-swimlane-audit` to verify.
+  After generating or editing a diagram, run `page-shape-bbox-validation`, `page-connectors-validation`, and `page-hierarchy-full` (geometry per nesting level) to verify.
+
+### Page size
+
+- Use page dimensions that fully fit the diagram, **including margins, legends, and connector routing corridors** — never let content clip the page edge
+- `page-recommendations` reports the smallest standard page size that fits the content with an 80 px margin
+
+### Parent (container) sizing — MANDATORY
+
+**A parent shape must always be large enough to fully enclose all its children, including inner padding.** When children grow (added, resized, or repositioned), expand the parent using:
+
+```
+parent.width  = max_child_right  + right_padding   (right_padding  ≥ 40, divisible by 40)
+parent.height = max_child_bottom + bottom_padding  (bottom_padding ≥ 40, divisible by 40)
+```
+
+Where `max_child_right = max(child.x + child.width)` and `max_child_bottom = max(child.y + child.height)` over all children (relative to the parent). Left/top inner padding must also be ≥ 40 pt and divisible by 40 pt.
+
+- **Cascade rule:** parent expansion may force *its* parent to expand. Walk up the containment tree and resize each ancestor until the outermost container fits all descendants
+- **Re-check after expansion:** when a parent grows, re-verify sibling spacing at every affected level — all gaps must remain divisible by 40 pt
+
+### Grouping and complexity
+
+- Keep diagram complexity medium: group services into logical zones/layers (swimlanes or containers per major domain) instead of scattering many unrelated services
+- Never route dense connector bundles directly through container titles/headers (see label-crossing prohibition below)
+
+### Connector labels and legends
+
+- In dense diagrams keep connector labels **off the connector path**; if labels are needed, place them in a clearly empty corridor, a side note, or a dedicated legend
+- Prefer a separate legend for flow explanations whenever connector labels would clutter the diagram
+- Keep legends **outside the main routing area** so no connector crosses legend text
+- Connector labels must never overlap shapes, cards, icons, or other text
+
+### Final visual inspection
+
+Before completion, re-open or visually inspect the diagram and check specifically for:
+- shape overlap (including external actors, cards, icons, notes, legends, containers)
+- connector overlap with cards/icons
+- connector label overlap
+- text overflowing card boundaries
+- page clipping
+- inconsistent spacing between lanes/columns and between rows
+- missing canonical vendor shapes
 
 ---