Add Engram plugin (lumetra/engram v0.0.2)

[brutus-gr]

Plugin Submission Form

1. Metadata

• Plugin Author: lumetra
• Plugin Name: engram
• Repository URL: https://github.com/lumetra-io/engram-dify

2. Submission Type

• New plugin submission
• Version update for existing plugin

3. Description

First-party Dify plugin for Engram — durable, explainable memory for AI agents. Six tools call the hosted Engram REST API at api.lumetra.io directly:

• store_memory(content, bucket?) — save an atomic fact
• query_memory(question, bucket?) — natural-language Q&A with citations
• list_memories(bucket?, limit?) — newest-first memory list
• list_buckets(limit?, offset?) — list buckets in the tenant
• delete_memory(memory_id, bucket) — remove one memory
• clear_memories(bucket) — empty a bucket (destructive)

Auth: single bearer-token field (engram_api_key) configured at the provider Authorize step. Credential validation pings GET /v1/buckets so invalid keys are caught immediately. Optional engram_api_base field lets users point at self-hosted Engram.

4. Checklist

• I have read and followed the Publish to Dify Marketplace guidelines
• I have read and comply with the Plugin Developer Agreement
• I confirm my plugin works properly on both Dify Community Edition and Cloud Version
• I confirm my plugin has been thoroughly tested for completeness and functionality
• My plugin brings new value to Dify

5. Documentation Checklist

• Step-by-step setup instructions
• Detailed usage instructions
• All required APIs and credentials are clearly listed
• Connection requirements and configuration details
• Link to the repository for the plugin source code

6. Privacy Protection Information

Data Collection

The plugin transmits only the parameters the agent passes to its tools (content, question, bucket, memory_id, limit, offset) to the Engram REST API at api.lumetra.io (or the self-hosted base URL the operator configured). The plugin does not read other Dify resources (datasets, conversations, files) and does not transmit data to any third party besides the Engram service the operator has authorized via API key.

For Engram's data-handling and retention policy, see https://lumetra.io/privacy.

Privacy Policy

• I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

[crazywoola]

❌ Request Changes

Decision: Request changes

Failed Checks

Check	Status	Detail	Required action
dify_plugin version	❌ Fail	dify_plugin must be installed and >= 0.5.0, but it was not found.	Use dify_plugin >= 0.5.0 in the packaged plugin environment.

Full Check Results

Check	Status	Detail	Required action
PR content language	✅ Pass	PR title/body CJK ratio=0.0% (zh=0, en=1873, ignored_zh=0, allowed_zh<=0)	None.
Project structure	✅ Pass	All expected files present: manifest.yaml, README.md, PRIVACY.md. _assets/: yes.	None.
Manifest author	✅ Pass	author is valid.	None.
Icon validation	✅ Pass	icon exists: _assets/icon.svg	None.
Version check	✅ Pass	version 0.0.2 is available.	None.
README language	✅ Pass	README.md CJK ratio=0.0% (zh=0, en=1871, allowed_zh<=0)	None.
PRIVACY.md	✅ Pass	PRIVACY.md exists and is non-empty.	None.
Dependency install	✅ Pass	requirements.txt not found; skipped.	None.
dify_plugin version	❌ Fail	dify_plugin must be installed and >= 0.5.0, but it was not found.	Use dify_plugin >= 0.5.0 in the packaged plugin environment.
Install test	✅ Pass	requirements.txt not found; skipped.	None.
Packaging test	✅ Pass	packaging check passed.	None.

Next steps

• dify_plugin version: Use dify_plugin >= 0.5.0 in the packaged plugin environment.

Please address these issues and push an update.