Install and smoke-test every supported wheel target

## Parent

- #2

## What to build

Install each advertised artifact into clean environments and execute shared conformance, package-boundary, typing, and concurrency smoke tests before release publication.

## Frozen verification boundary

- Smoke tests import the installed wheel, never the source checkout.
- Core-only, `[cli]`, and `[tui]` environments prove RFC-0004 dependency isolation and entry-point behavior.
- Ordinary CPython targets prove Engine result, error, GIL-release, and cancellation behavior.
- Free-threaded CPython is not advertised or published until PyO3 is at least 0.23, exposed classes satisfy its model, and the dedicated concurrency suite passes.
- Any unsupported or unverified target is removed from wheel jobs and public compatibility claims.

## Acceptance criteria

- [ ] Every advertised OS, architecture, and Python target has an isolated installation result.
- [ ] Core, CLI, and TUI wheel environments pass their exact import/entry-point smoke sets.
- [ ] Installed target typing and runtime exports agree with the RFC-0004 manifest.
- [ ] Concurrency smoke covers shared immutable Engine calls and cross-thread cancellation.
- [ ] `cp313t` or later free-threaded artifacts are gated on the PyO3 upgrade and free-threaded suite, not merely a build tag.
- [ ] Release publication depends on successful wheel smoke artifacts.

## Blocked by

- #2
- #19
- #22
- #10

## RFC-0005 contract

Support begins with isolated installation, not a successful cross-build. Implement the required/build-only matrix and emit the `wheel_smoke` evidence record consumed by the M4+ release contract. Free-threaded artifacts remain unpublished until the RFC-0004 concurrency boundary and the dedicated runtime suite pass.

Start by reviewing the RFC-0004 and RFC-0005 contracts and the blocked issues #2, #19, #22, and #10 to identify the required wheel matrix and smoke boundaries. Implement isolated installation checks that emit the `wheel_smoke` evidence record, then verify core, CLI, TUI, typing, runtime, and concurrency acceptance criteria before release publication.

Written by the indexing model from the issue text.