Skip to content

Refresh SOVP listing against released bridge 0.1.1 - #220

Merged
imran-siddique merged 1 commit into
mainfrom
fix/217-sovp-listing
Sep 24, 2026
Merged

imran-siddique merged 1 commit into
mainfrom
fix/217-sovp-listing

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

The SOVP listing still documented a Git install and TRACE 0.9.0. Update it to the released bridge 0.1.1 with the exact tested TRACE 0.10.0 and conformance-suite 0.5.1 versions, and pin the source example used for reproduction. Fixes #217; credit @litzki-systems for the report and upstream fix.

Fresh Windows Python 3.12 installation: the installed bridge CLI emits a record that passes all eight Level 0 checks, including Ed25519 signature verification. Direct verification also passes; changing the signed subject is rejected with InvalidSignature. pip check passes. This rechecks the existing Verified listing at Level 0; it establishes no hardware or SOVP deployment assurance.

All 41 integration manifests and compatibility validation pass. Marketplace/index regeneration leaves no semantic changes; git diff --check passes. Compatibility validation initially lacked a local dependency; after installing packaging, it passed. CI and independent review remain required.

Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
@imran-siddique
imran-siddique merged commit 0e5a735 into main Sep 24, 2026
12 checks passed
@imran-siddique
imran-siddique deleted the fix/217-sovp-listing branch September 24, 2026 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

litzki-systems-sovp marketplace listing is stale (tested_against, install command, Verified basis)

2 participants