Preserve nominal viewer identities across test and MCP boundaries

[trissim]

Summary

• migrate the Official30 viewer-variant helper and assertions from flattened strings to authoritative ViewerType identities
• make McpViewerConnectionToolFields the declared owner of the viewer connection tool signature
• derive the MCP transport enum schema from that dataclass and reconstruct TransportMode from wire text through python-introspect

Why

The configuration ownership refactor correctly preserves nominal transport/viewer types. Two stale boundaries remained:

1. an Official30 integration assertion expected "fiji" instead of ViewerType.FIJI;
2. the MCP viewer tool manually advertised plain text and passed that text into strict ExecutionConnectionSpec, breaking the installed Windows demo.

Verification

• focused registered-viewer projection integration test passes
• MCP wire reconstruction and generated schema tests pass
• generated viewer tool schema exposes TransportMode choices tcp and ipc
• Ruff and diff checks pass

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[augmentcode]

^{PR Risk Analyzer Agent🛡️}

Risk Analysis 🛡️ · Low Risk

✅ Approved — Low-Risk Change

Details

Test-only change to tests/integration/test_cellprofiler_official30_zmq.py (+6/-6). It migrates dict keys and set comparisons from the flattened spec.viewer_type.value string to the authoritative ViewerType enum. Since the produced config.viewer_type is an enum, the prior string-based assertions could never match — this is a correctness fix that keeps the equality checks equally strict. No production code, schemas, migrations, infra, auth, security, or AI prompts are affected.

[augmentcode]

^{Deep Code Review Agent🐛}

Review completed with 0 suggestions.