chore(devx): retain proof artifacts with explicit privacy rules

[enliven17]

Goal

Retain proof artifacts with explicit privacy rules so Harpocrates remains privacy-preserving, interoperable, and safe at its public boundaries.

Scope

• Work within repository workflows, CLI/release tooling, deployment packaging, interoperability fixtures, and security operations.
• Reuse the existing canonical metadata, proof, contract, and deployment boundaries; do not create a second protocol truth.
• Define behavior for malformed, oversized, expired, revoked, unsupported, and dependency-failure inputs as applicable.

Acceptance criteria

• The requested behavior is available through the current interface without breaking compatible callers or stored evidence.
• Failure responses are stable and privacy-safe; real media, secrets, witness values, and private keys are never logged.
• Version, migration, threat-model, and compatibility notes are included when the change affects a protocol or artifact.

Test expectations

• Add focused positive, negative, boundary, and regression coverage. Add a reproducible command or CI fixture; do not use real sensitive media or credentials.
• Keep the relevant lint, typecheck, build, circuit, contract, and integration checks green.

Out of scope

• Unrelated dependency upgrades, real sensitive media, production credentials, broad visual redesigns, and undocumented protocol changes.

Wave notes

Please link the pull request to this issue and explain trust-boundary, privacy, migration, and rollback implications in the PR.

[3nity610]

@3nity610 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi Maintainer, I’ve read through the issue and have a good understanding of the expected result. I’d love to work on this one.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @3nity610 to this issue.

[drips-wave]

Congratulations, @3nity610! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @3nity610: 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 🌊

[enliven17]

Hi @3nity610, thanks for applying! This issue is now assigned to you. Please open a PR referencing this issue when ready. Good luck!