feat(execution): add deterministic step display ordering

[pocky]

Summary

• Fix non-deterministic step display in CLI execution summaries — steps were previously iterated from a Go map, producing inconsistent ordering across runs; display now follows the workflow-defined default path (Initial → transitions → OnSuccess)
• Introduce ExecutionOrder(*Workflow) and NextDefaultStep(*Step) domain functions in graph.go as a single authoritative source for default-path graph traversal, replacing duplicated ordering logic in both CLI and TUI layers
• Update all CLI display functions (showExecutionDetails, showStepOutputs, showEmptyStepFeedback, buildStepInfos) and the resume command to accept *workflow.Workflow and iterate via ExecutionOrder() instead of direct map access
• Remove TUI-private orderedSteps/nextStepName helpers and delegate to the new domain functions, eliminating inconsistent parallel implementations

Changes

Domain — Graph traversal

• internal/domain/workflow/graph.go: Add NextDefaultStep(*Step) (returns next step via unconditional transition, falling back to OnSuccess) and ExecutionOrder(*Workflow) (walk default path from Initial, stop at terminals, cycle-safe)

CLI — Deterministic display

• internal/interfaces/cli/run.go: Thread *workflow.Workflow into showExecutionDetails, showStepOutputs, showEmptyStepFeedback, buildStepInfos; replace map iteration with ExecutionOrder() loop using thread-safe GetStepState per step
• internal/interfaces/cli/resume.go: Load workflow from repository after execution; pass to all display helpers replacing previous map-based iteration

TUI — Remove duplicate ordering logic

• internal/interfaces/tui/tab_monitoring.go: Delete private orderedSteps/nextStepName; delegate to workflow.ExecutionOrder() and workflow.NextDefaultStep()
• internal/interfaces/tui/tab_monitoring_test.go: Remove tests that validated the now-deleted private TUI ordering helpers

Tests

• internal/domain/workflow/graph_test.go: Add full unit test suite for NextDefaultStep (nil, default transition precedence, OnSuccess fallback, conditional-only) and ExecutionOrder (linear chains, cycle prevention, terminal stops, parallel steps, value copy safety)
• internal/interfaces/cli/run_internal_test.go: Update showExecutionDetails, showStepOutputs, showEmptyStepFeedback, buildStepInfos tests to supply *workflow.Workflow; add ordering assertion coverage
• tests/integration/features/execution_order_determinism_test.go: New integration test suite verifying deterministic step ordering across repeated runs, branching workflows, and parallel step scenarios

Documentation

• docs/user-guide/commands.md: Document that execution summary steps always appear in workflow-defined order; add annotated example output
• CHANGELOG.md: Add F095 entry under Unreleased

Project config

• CLAUDE.md: Refine development pitfall and test convention rules based on lessons from this feature

Test plan

• Run make test — all unit and integration tests pass, including new execution_order_determinism suite
• Run make lint — zero violations
• Execute a multi-step workflow with awf run <workflow> --verbose and confirm --- Execution Details --- steps appear in workflow-defined order, not random map order, across multiple invocations
• Execute awf resume <id> on a completed workflow and verify execution summary uses the same deterministic ordering

Closes #341

---

Generated with awf commit workflow