Polymorph Bridge 0.4.0a9

The own-data path is now the front door

Polymorph Bridge 0.4.0a9 turns the safest useful workflow into the shortest workflow:

py -m pip install "https://github.com/IamAngusU/polymorph/releases/download/v0.4.0a9/polymorph_bridge-0.4.0a9-py3-none-any.whl"
polymorph trial your-data.csv --open

The trial runs locally, does not write to the source or destination, does not use the network, and emits a metadata-only HTML/JSON report without record values.

Changes

• Added polymorph trial FILE and polymorph trust ... to the primary CLI while retaining the existing compatibility commands.
• Added a real product screenshot and direct no-clone install path to the English and German READMEs.
• Reworked the roadmap around evidence-backed status instead of stale version promises.
• Corrected CI documentation: workflow definitions are prepared, but repository GitHub Actions remain disabled.
• Added structured bug, connector, and evidence contribution forms.
• Updated the Trust Center documentation so current releases no longer look pinned to a stale version.
• Kept the repository image-efficient: the product screenshot is WebP, with no redundant PNG tracked.

Local release evidence

• Source commit: 15f391d392c74f2c1fbda7645402cdbff5189775
• Full suite: 1,251 passed, 8 skipped, 0 failed.
• Repeated end-to-end workflow: 365.20 to 375.54 rows/s; median 369.77 rows/s.
• Maximum measured peak RSS: 83.18 MiB.
• Ruff, formatting, strict mypy, package build, Twine checks, clean-wheel install, primary CLI trial, SBOM generation, Trust Center generation, and release-manifest verification passed locally.
• GitHub Actions were disabled and were not used for this evidence.

The attached release manifest binds every downloadable artifact to its SHA-256 digest and this source commit. Measurements describe this specific local Windows host and corpus; they are evidence, not universal performance promises.