fix: preserve safety modes across session flows

[Sayt-0]

Summary

• preserve stored autonomous and legacy approval state during plain session resume
• carry explicit safety policy and YOLO toggle-back state through /new
• keep wrapped tool-confirmation actions clickable across terminal widths
• synchronize the cached YOLO indicator when a confirmation switches the session to Balanced

Context

Follow-up to #3835. The safety-mode implementation introduced session-state preservation gaps and two classic TUI regressions around wrapped confirmation actions and Balanced-mode state display.

Changes

Area	Fix
Session resume	Safety state changes only when --safety or --yolo is explicitly supplied. Plain resume preserves both explicit autonomous state and legacy tools_approved state.
/new	Preserves effective SafetyPolicy and PriorSafetyPolicy, including toggle-back behavior after an Autonomous escalation.
Confirmation TUI	Lays out complete action segments across rows, uses terminal-cell hit maps, truncates display-only labels when necessary, and preserves the full permission pattern.
YOLO indicator	Clears cached YOLO state when selecting Balanced from a hook-forced confirmation.

Validation

• go build ./...
• go test ./pkg/tui/... ./pkg/leantui/... ./cmd/root/... ./pkg/app/...
• go test -race ./pkg/tui/dialog ./pkg/tui/components/toolconfirm ./cmd/root ./pkg/app
• go vet ./pkg/tui/... ./pkg/leantui/... ./cmd/root/... ./pkg/app/...
• golangci-lint run
• go run ./lint .
• go mod tidy --diff

Full go test ./... was also run. Only environment-specific SSRF tests failed in pkg/config, pkg/httpclient, and pkg/tools/builtin/{api,fetch,openapi} because private-address traffic is intercepted by the sandbox network; all changed and related packages passed.