Module addons 

Addon ecosystem: community extensions for lean-ctx (#858).

An addon packages an external MCP server (+ metadata) behind a small lean-ctx-addon.toml manifest, so a third-party tool plugs into lean-ctx’s MCP gateway with a single lean-ctx addon add — no fork, no recompile. Addons are user-global and reuse the gateway trust model ([gateway] is global-only and opt-in; see crate::core::gateway).

Layers:

• manifest — the lean-ctx-addon.toml contract (also the registry entry shape).
• registry — the curated catalog (bundled, with optional user override).
• store — what is installed locally (<data_dir>/addons/installed.json).
• install — wires an addon into the gateway and records it in the store.
• scaffold — addon init starter manifest generator (DX, P4).

Security (#863, P1):

• capabilities — the declared [capabilities] permission model that drives the per-addon sandbox + env allowlist + install consent.
• trust — trust tier (verified) + static risk assessment of the wiring.
• audit — capability-coherence + malware heuristics + the verified/paid gate (#403): does the declared [capabilities] match the wiring, and is the wiring free of malicious patterns?
• commerce — sellable-addon model ([pricing]) + the mandatory paid listing gate (Track B): no addon is sold without clearing the audit.
• binhash — SHA-256 binary pinning for stdio addons (refuse a swapped executable at spawn).
• policy — the global-only [addons] install policy floor + the gate.
• signing — Ed25519 signing for the user-override registry.
• revocation — central kill-switch that blocks a revoked addon from running (install, catalog build, every proxy call).
• integrity — install-time wiring hash + local re-verify (the lockfile).
• meter — per-addon / per-tool usage metering (analytics + billing base, P5).
• sandbox — per-addon OS sandbox for spawned stdio servers.
• runtime — redaction + audit of untrusted addon tool output.

Re-exports

pub use audit::AuditReport;

pub use audit::AuditVerdict;

pub use capabilities::AddonCapabilities;

pub use capabilities::FilesystemAccess;

pub use capabilities::NetworkAccess;

pub use commerce::AddonPricing;

pub use commerce::PaidGate;

pub use commerce::PricingModel;

pub use commerce::paid_listing_gate;

pub use manifest::AddonManifest;

pub use manifest::AddonMcp;

pub use manifest::AddonMeta;

pub use policy::AddonPolicy;

pub use policy::AddonsConfig;

pub use sandbox::SandboxMode;

pub use store::InstalledAddon;

pub use store::InstalledStore;

pub use trust::RiskFinding;

pub use trust::RiskLevel;

pub use trust::TrustTier;

Modules

audit

Capability audit + publish gate for addons (P3, #403 — the gate before paid).

binhash

Binary-hash pinning for stdio addons (P3 — supply-chain hardening).

capabilities

Declared capability model for addons (P1 — platform keystone).

commerce

Sellable-addon commerce model (Track B — generalising the ctxpkg paid artifact to addons).

env_scrub

Environment scrubbing for spawned stdio addons (P1).

install

Install / remove logic: wire an addon’s MCP server into the global gateway and record it in the installed store.

integrity

Addon integrity pinning + local re-verify (P2 — the lockfile half).

manifest

The lean-ctx-addon.toml manifest — the contract an addon author writes.

meter

Per-addon / per-tool usage metering (P5 — discovery & observability).

policy

Install policy for addons — the org-controllable floor (#865).

registry

The curated addon catalog.

revocation

Central addon revocation / kill-switch (P2).

runtime

Runtime safeguards for addon tool output (#866).

sandbox

Opt-in OS sandbox for the stdio MCP servers an addon spawns (#865).

scaffold

lean-ctx addon init scaffolding (P4 — lower the floor).

signing

Detached Ed25519 signing for the user-override registry (#865).

store

Installed-addon state: <data_dir>/addons/installed.json.

trust

Trust tiers + static risk assessment for addons (#864).