feat: add ProofCore Notary plugin package v0.0.2

[ProofCore-Protocol]

Plugin Submission

Plugin information

• Author: ProofCore-Protocol
• Plugin name: proofcore_notary
• Version: 0.0.2
• Source repository: https://github.com/ProofCore-Protocol/dify-proofcore-plugin
• Contact: sealit@proofcore.org

Submission type

• New plugin
• Version update

What changed

Initial release of the ProofCore Notary plugin (v0.0.2).

• Enables autonomous Dify agents and workflows to cryptographically seal and verify reports, audits, and outputs on the TON Blockchain.
• Features Zero-Auth architecture, instant Ed25519 notary attestation, SHA-256 Merkle tree batching, and programmatic A2A (Agent-to-Agent) verification via seal_content and verify_content tools.

Risk level

• Low risk
• Medium risk
• High risk

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

Interacts with the public ProofCore HTTPS API gateway (https://api.proofcore.org/api/v0.1/seal and https://api.proofcore.org/api/v0.1/verify) to submit content hashes for on-chain anchoring.

• Zero-Storage architecture: raw payloads are not persisted.
• No local secrets, credentials, or privileged OS-level capabilities required.

Local validation

• Packaged as a clean .difypkg package containing only runtime source files (manifest.yaml, main.py, requirements.txt, icon.png, README.md, PRIVACY.md).
• Verified tool execution on Dify tool provider sandbox.

Reviewer notes

This PR contains strictly one .difypkg file change (proofcore_notary-0.0.2.difypkg) placed in ProofCore-Protocol/proofcore_notary/ as per CI pipeline guidelines.

[crazywoola]

Closing this PR because the current Pre Check Plugin / pre-check-plugin CI run failed.

CI summary:

• Manifest is missing plugins, privacy, repo, contact, meta.version, meta.arch, and runner language/version/entrypoint; type must be plugin.
• Icon validation could not find _assets/_assets/icon.png.
• Installation failed with ModuleNotFoundError: No module named requests.
• Packaging failed manifest validation, including required resource memory and creation timestamp fields.

Failed CI job

Please address the reported failures (or rerun CI if the failure was transient) before requesting reopening or resubmitting.