fix(capsules): report engine divergence before baseline shape

[johnny4young]

Summary

lingua capsule verify refuses Python, Go and web Ruby recordings because their app engine (Pyodide, Go WASM, Ruby WASM) differs from the CLI runtime. But the baseline-shape checks ran first, and a real recording from the app always carries per-line results and rich outputs. So every real Python capsule was refused as unsupported-baseline-output ("cannot supply a complete successful stdout/stderr baseline"), and the actual reason never appeared.

Found while preparing the 1.6.0 announcement: a Python capsule exported from production app.linguacode.dev 1.6.0 (print("sum =", total)) never showed the engine message.

This PR checks engine divergence first in capsuleStrictVerificationRefusal. The regression-suite export dialog uses the same function, so it now shows its existing engine message instead of the generic "incomplete" one.

• Verdict and exit code are unchanged: inconclusive, exit 6. Only reason / detail change for these recordings.
• Browser preview keeps its current position and exit 3; reordering it would change its exit code and is a separate decision.

Validation

• Live, against the real production capsule (appVersion 1.6.0, python, web):
  • branch build dist/cli/lingua.cjs → error[engine-divergent-baseline], exit 6 (JSON reason: "engine-divergent-baseline");
  • published @linguacode/cli@1.6.0 → error[unsupported-baseline-output], exit 6;
  • the JavaScript example capsule still passes with exit 0.
• New CLI test (real-shaped Python web recording with line results, and with a failed status) and new dialog test; both fail without the fix.
• tsc --noEmit, typecheck:tests, lint, check:i18n, check:i18n:copy, changelog:check; tests/cli, tests/shared, tests/components/CapsuleList, tests/renderer: 151 files, 2421 tests passed.
• The dialog change is covered by its component test only. It sits behind the Pro capsule browser and needs Python recordings that dev:web cannot run, and no copy changed.