test(protocol): publish a black-box conformance suite for independent implementations

[enliven17]

Summary

Publish implementation-neutral fixtures and a runner that verifies complete Harpocrates protocol behavior at public boundaries.

Motivation

Harpocrates needs this capability to become a production-grade, interoperable evidence protocol while preserving privacy, deterministic verification, and safe failure behavior. The implementation must reuse existing metadata, manifest, ZK, backend, frontend, and Soroban boundaries instead of creating parallel truth sources.

Scope

• Cover metadata envelopes, proof manifests, public inputs, receipts, Stellar encodings, events, status semantics, revocation/expiry, lineage-ready extension handling, and network guards.
• Provide positive, negative, boundary, malformed, and unsupported-version vectors.
• Define machine-readable expected outcomes and stable reason/error codes.
• Run the suite against frontend libraries, backend, CLI/SDK, and deployed test harnesses where applicable.
• Version fixtures and prevent silent regeneration.

Acceptance criteria

• A third-party implementation can run the suite without repository-internal imports.
• Cross-language encoding differences and canonicalization bugs are detected.
• Fixtures contain only synthetic non-sensitive evidence.
• CI publishes a conformance report and compatibility matrix.
• Existing lint, type checks, tests, builds, contract checks, and privacy guarantees remain green.

Engineering expectations

Use versioned canonical encodings, explicit error/status types, bounded resource consumption, idempotent operations, and privacy-safe observability. Schema, contract, circuit, or artifact changes require migration and compatibility analysis. Cryptographic changes require stable vectors and a written threat model.

Out of scope

Live production deployment, real credentials or sensitive media, unrelated visual redesigns, and broad dependency upgrades not required by this objective.

Definition of done

A maintainer can reproduce success and adversarial failure paths locally, understand the trust and privacy boundaries, operate the feature safely, and roll it back without undocumented state repair.

[obedojukwu16-jpg]

@obedojukwu16-jpg has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I will like to work on this issue, I know exaxtly what to do and I will deliver efficiently

ℹ️ Repo Maintainers: To accept this application, review their application or assign @obedojukwu16-jpg to this issue.

[drips-wave]

Congratulations, @obedojukwu16-jpg! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @obedojukwu16-jpg: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊