fix(cli): project turn.stop inputs to protocol fields

[jsiu93]

Summary

Send turn.stop with a fresh object containing only sessionId, turnId, and runId. The active Turn's local outcome classifier stays outside the protocol payload, so timeout and SIGINT requests reach the Host and abort the foreground tool.

Add strict fixture validation to the existing stop-before-start test. The fixture rejects every extra turn.stop field and records the exact accepted payload. Scope is limited to the #stopTurn projection and strictTurnStopInput fixture.

Fixes #4304

Verification

mise exec node@24.19.0 -- npx -y npm@11.19.0 --workspace maka-agent run build
mise exec node@24.19.0 -- node --test --test-name-pattern "stops a Turn that starts after cancellation was requested" packages/cli/dist/__tests__/runtime-host-run-command.test.js
Before fix: 0 pass, 1 fail, exit 1
After fix: 1 pass, 0 fail, exit 0

Before the fix, the strict fixture rejected outcome as an unknown turn.stop input field.

mise exec node@24.19.0 -- node --test packages/cli/dist/__tests__/runtime-host-run-command.test.js
35 pass, 0 fail, exit 0

A live maka run --yolo --timeout 10 returned 1 in 10.949 seconds. The marker was absent at return and remained absent after 45 seconds.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: pi (gpt-5.6-sol), human-reviewed

Checklist

• Tests cover the change, with a red test recorded before the fix
• The CLI build and affected test file pass locally

Does this PR entail a change in behavior?

• Yes, described under Summary above
• No