Current Version: v0.1.0-dev
Parent: Main Roadmap
Process: SDD → BDD → TDD → DDD (Workflow Guide)
Scope: Establish the core JSON-LD schema for plugin metadata and capability requests.
Gate: Verified manifest validation logic and schema consistency.
- Spec: JSON-LD based manifest structure.
- Spec: Capability request definitions (factors).
- Spec: WIT interface mappings for WASM plugins.
- Integration: Valid manifest correctly identified by
Registry. - Integration: Capability mismatches correctly rejected.
- Integration: Multi-runtime types (Browser, Node.js, Workers) defined.
- Unit: Manifest validation against JSON schema.
- Unit: Fixture-based tests for correct and incorrect manifests.
- Coverage: >90% (Contract Critical)
- Domain: Core
PluginManifestvalidation logic. - Infra: TypeScript library distribution.
Scope: Formalizing host capability negotiation and runtime support.
- Implementation of Runtime Specification: Explicit support for
main,worker,service-worker, andedgeexecution contexts. - Dependency Matching: Ensuring plugin manifests correctly specify
refarmengine version and contract dependencies.
Scope: Enabling runtime negotiation of optional capabilities.
- Implementation of Optional Factors: Standardizing how a manifest requests optional host capabilities (e.g.
notification-api). - Interactive Manifests: Supporting progressive disclosure of required capabilities.
- See packages/plugin-manifest/src/types.js for core structure.
- The "Digital Deed" for every Refarm plugin.