Make represented workflow Thinking progress meaningful

[witbrock]

What changed

• project represented-workflow execution into the existing semantic Thinking contract
• show bounded workflow-authored progress facts, human workflow/state labels, outcome, effect and recovery information
• retain the selected workflow summary in completed diagnostics and expose exact state/action identifiers only in Expert/Debug
• add backend and frontend regression coverage for live and stored Thinking cards

Why

Default Thinking cards named represented workflows but did not say what a workflow was doing, what it found, or how it ended. Users therefore saw opaque workflow identifiers instead of useful live-work progress.

User impact

A represented workflow now remains understandable in Default mode, including after the turn is reloaded. Expert and Debug retain the same semantic account and add exact identifiers for diagnosis.

Validation

• tests/backend/test_adaptive_turn_service.py: 134 passed
• tests/backend/test_thinking_llm_call_timestamps_and_precedence.py and tests/backend/test_tool_progress_liveness.py: 56 passed
• complete chatTab.test.js suite: 257 passed
• Python compilation and git diff --check: passed
• live Luna browser replay: completed workflow name, final step and stored-card reload verified; Expert exact state/action identifiers verified

Jira: JVNAUTOSCI-2619