Repository navigation
chore(marketplace): verify parmana-server - #314
Conversation
Reproduced the README steps on released parmana 1.6.0 and agentrust-trace 0.11.0 after #313: four references emitted, fixtures regenerate byte for byte, 18 tests pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>
|
I’ll review the offline reproduction and Verified-tier claims at 6315271, including the released-package fixture path and catalog consistency. |
noah-ing
left a comment
There was a problem hiding this comment.
Reviewed 6315271; no blocking findings for the explicitly scoped offline-fixture promotion.
Reproduced the README in a fresh Python 3.12 environment with released parmana==1.6.0 and agentrust-trace==0.11.0: four references emitted, references.json unchanged byte for byte, and all 18 integration tests passed. The tests verify the decision and approver signatures and reject altered amounts, outcomes, approval limits and the wrong signing key.
The 28 repository validation tests passed, as did manifest/compatibility validation, generated index/catalog checks, diff checks and a merge simulation against af507cb. The manifest correctly declares an external-evidence-source without a TRACE conformance level.
This supports the README's offline scope only: I did not rerun the originating Parmana server evaluation or exercise a real payment connector. The mock/no-observed-effect, supplied-key and example-resolver limitations remain explicit. Maintainers retain the tier/merge decision.
Flips parmana-server to Verified after #313. Reproduction steps from its README run clean on released packages; details are in the new README section.
🤖 Generated with Claude Code