feat(sysml): add SysIDE Modeler view automation spike

[de4sdv]

Summary

• Add a SysIDE Modeler view automation spike for the DE4SDV context model slice.
• Add textual SysML v2 view definitions for systemContext and lifecycleEngineeringSystem.
• Commit generated SVG output from syside viz view as initial evidence.
• Document the proposed VS Code human-in-the-loop lane and the CLI automation lane.

Why this matters

This tests the workflow Orkun wants: humans use SysIDE Modeler in VS Code for visual feedback, but the authoritative view intent stays in reviewable .sysml text and can be re-rendered automatically.

Validation

• syside check textual-notation-of-model/snapshots/de4sdv-context-spike.sysml textual-notation-of-model/views/syside-modeler/de4sdv-syside-views.sysml
• syside viz view textual-notation-of-model/snapshots/de4sdv-context-spike.sysml textual-notation-of-model/views/syside-modeler/de4sdv-syside-views.sysml --output-dir textual-notation-of-model/views/syside-modeler/generated
• npx --yes markdownlint-cli sysmlv2-api/syside-modeler-spike.md
• python scripts/check_repo.py
• python scripts/smoke_test.py
• git diff --check

Notes

• Rendering on the ARM64 host used the x86_64 SysIDE CLI through an amd64 Docker/QEMU wrapper with SYSIDE_LICENSE_KEY passed from a local ignored .syside.env file.
• .syside.env is intentionally ignored and not committed.
• The SysIDE Modeler VS Code extension is not available for Linux ARM64, so the human-in-the-loop lane should be tested on a supported desktop platform such as macOS ARM64 or Linux x64.

[de4sdv]

Stale review — status check

This draft PR is 3 weeks old (last updated June 23) and has merge conflicts (dirty state).

What's here: SysIDE Modeler view automation spike — generates SVG views from SysML v2 using the Modeler CLI, including system-context and lifecycle-engineering-system views.

Context: This was a spike. The generated SVGs have since been moved to textual-notation-of-model/views/ (tracked by docs/repository-tree.md). The syside-modeler-spike.md doc is now sysmlv2-api/syson-spike.md territory.

Path forward:

1. Close as completed spike — the view generation concept was explored; outcomes can be documented as an ADR or methodology note without merging the spike code.
2. Rebase and prepare for merge — if the automation script itself is worth keeping as a tool.

Tagging @OrkunYilmaz for a decision.