Adoption evidence and gate review
BetaWrengle's plugin surface stays in local developer-preview until adoption and trust evidence justify broader platform work.
Current gate decision
As of June 4, 2026, the adoption gate does not pass. Wrengle continues to support the local developer-preview workflow for trusted WASM editor actions and view-only plugin tabs. It does not promise distribution, public stability, or additional contribution points.
The June 21 local grants and creator work improves the local-preview authoring loop: manifests can declare capability needs, users can grant or deny those needs per local app install, and write capabilities create app-mediated write proposals. That work does not change the gate decision or create marketplace, remote-install, or public-stability commitments.
Evidence gate
Both conditions must be true before broader plugin work starts:
| Condition | Current evidence | Result |
|---|---|---|
| At least three real external or local authors build working local plugins without direct maintainer hand-holding. | No qualifying non-maintainer attempts are recorded yet. The echo action and generated scaffold are maintainer-authored references. | Not met |
| The team has made one concrete distribution/trust decision: who distributes plugins, who can install them, and who is responsible for trusting code and capabilities. | Current docs describe local trusted-code loading only. Grants are local app-install decisions, not a distribution trust policy. No broader distribution or trust decision is recorded. | Not met |
What remains intentionally out of scope
- Security and permission model expansion beyond the current local-preview safety rules.
- Packaging and distribution.
- Public stability-promised contribution contracts.
- Additional contribution points such as themes, editor extensions, snippets, process plugins, MCP servers, or language servers.
Those areas need separate specs after the gate passes. They should not be added to the local developer-preview workflow by implication.
Feedback template
For each local authoring attempt, capture:
- Author class and maintainer involvement.
- Plugin goal and source path type.
- Wrengle version or commit, operating system, and commands run.
- Whether reload succeeded and whether the action or view opened successfully.
- Manifest, build, reload, diagnostics, editor-run, documentation, and trust blockers.
- Whether the attempt counts toward the evidence gate and why.
Repository maintainers track the detailed templates, attempts list, and gate
review under docs/plugins/.