[Docs] align Sprint 1 UI workflow docs

[SilverSupplier]

Summary

• UI 문서를 현재 Sprint 1 application workflow와 맞춥니다.
• Layout Review, Scenario Authoring, Run, Result Summary의 실제 구현 범위와 Sprint 2 이후 범위를 분리해 적었습니다.
• 문서가 현재 코드의 staged baseline, readiness, configured events, authoring state persistence 표현과 어긋나지 않도록 정리합니다.

Related Issue

• Refs Task-도면 import와 구조 검토 application workflow 구현 #117
• Refs Task-baseline 시나리오 라이브러리와 readiness panel UI 구현 #118
• Refs Task-ControlPlan 운영 이벤트 editor UI 구현 #119
• Refs Task-run queue와 실행 제어 workspace UI 구현 #120
• Refs Task-run 결과 요약과 variation summary analysis UI 구현 #130
• Part of EPIC-2 Sprint 1 Demo Vertical Slice #2

Area

• Engine
• Domain
• Application
• Docs
• Build
• Analysis
• Chore

Architecture Check

• I kept the dependency direction application -> domain -> engine.
• I did not add Qt UI code to src/domain.
• I did not add domain or application dependencies to src/engine.
• I used src/ as the include root.

Verification

• cmake --preset windows-debug
• cmake --build --preset build-debug
• ctest --preset test-debug
• cmake --build --preset build-no-app-debug
• ctest --preset test-no-app-debug
• Not run (reason below)

Verification was run on the integrated Sprint 1 stack before opening this docs sync PR.

Risks / Follow-up

• This PR is stacked on [Application] connect Sprint 1 authoring run flow #152, so the docs should be reviewed against the application changes in that PR.
• The document intentionally calls out Sprint 2+ boundaries instead of promising full analysis/persistence features in Sprint 1.