CONFIG
Implementation: exploratory · Proposal: draft (status checked 2026-10-31). Configuration binding is tested, but the upstream draft is marked MAY DEFER; use for design exploration. All capabilities remain subject to change. Maturity and opt-in policy.
Declarative per-napplet configuration (JSON Schema-driven). The shell renders the settings UI, validates, persists, and pushes live values; the shell is the sole writer.
ts
const sub = window.napplet.config.subscribe((values) => applyTheme(values.theme as string));
window.napplet.config.openSettings({ section: 'appearance' });This non-normative guide defers to the living NAP-CONFIG proposal. Feature-gate with if (window.napplet?.config) before use; the runtime injects only available domains. Typed helpers ship from @napplet/nap/config and @napplet/sdk.