@dxos/app-framework 0.8.4-staging.60fe92afc8 → 0.9.1-main.c7dcc2e112

package/docs/registry-spec.md

@@ -0,0 +1,331 @@
+# Plugin Registry Spec
+
+## Overview
+
+The DXOS plugin registry is **AT Protocol-native**: there is no central registry database that
+authors submit to. Instead, each publisher writes a small set of records to **their own** AT
+Protocol repository (PDS), and a DXOS-operated **app-view** (in AT Protocol terms — the edge service
+that indexes the firehose and serves a derived view) ingests those records, gates them by trust
+attestations, and serves the resulting catalog to Composer.
+
+This document specifies the four lexicons that make up the registry, the rkey conventions, the
+trust/curation model, the integrity model, and the data flow from authoring to discovery. It is the
+design reference for the machine-readable lexicons and the implementations that produce and consume
+them.
+
+Goals:
+
+- **Publisher-owned data.** Records live in the publisher's repo; updating or removing a plugin is a
+  record write or delete on their side, not a request to DXOS.
+- **Curated discovery.** Only publishers a trusted verifier has vouched for are surfaced, keeping
+  the catalog trustworthy without DXOS owning the data.
+- **Standard tooling.** Records are plain AT Protocol records, readable by any ATProto client and
+  written via standard XRPC (`com.atproto.repo.*`).
+
+## Status
+
+Experimental. The `experimental` segment in every NSID is intentional — these schemas are unstable
+and will be renamed to a final namespace before promotion (see [Versioning](#versioning)).
+
+## Source of truth
+
+The machine-readable lexicons are the canonical definition:
+
+- **Lexicon JSON** — `packages/sdk/edge-protocol/lexicons/org.dxos.experimental/*.json` (edge repo).
+  These are the source of truth.
+- **Effect-Schema validators** — `packages/sdk/edge-protocol/src/registry.ts`
+  (edge repo). Decoders used at the indexing/validation seam to reject malformed records before they
+  enter the store. These mirror the JSON lexicons and live alongside them in the protocol package.
+- **`PluginView`** — `packages/core/protocols/src/edge/registry.ts` (dxos repo). The catalog shape
+  the indexer serves to Composer.
+- **CLI writers** — `packages/plugins/plugin-registry/src/commands/registry/` (dxos repo). The `dx`
+  CLI assembles record bodies and writes them via XRPC.
+- **App-view / indexer** — `packages/services/registry-service/src/registry/atproto/{indexer,curator,backfill}.ts`
+  (edge repo). The `RegistryIndexer` Durable Object is the registry app-view: it ingests records,
+  enforces what the registry serves, and returns the catalog.
+
+## Architecture
+
+```
+┌──────────────────┐   putRecord/    ┌─────────────┐   Jetstream    ┌──────────────────┐   GET /registry  ┌──────────┐
+│  dx CLI          │   deleteRecord  │ Publisher   │   firehose +   │ RegistryIndexer  │   /plugins       │ Composer │
+│ (plugin-registry)│──────XRPC──────▶│ PDS (repo)  │───backfill────▶│ DO (edge)        │─────────────────▶│          │
+└──────────────────┘                 └─────────────┘                └──────────────────┘                  └──────────┘
+                                          ▲                               │
+                                  verifier│verification           verified-DID gate
+                                          │                               │
+                                   ┌─────────────┐                        │
+                                   │ Verifier PDS│────────────────────────┘
+                                   └─────────────┘
+```
+
+1. A publisher writes `package.profile` / `package.release` records (and a one-time
+   `publisher.profile`) to their own PDS using the `dx` CLI.
+2. A verifier writes `publisher.verification` records, one per trusted DID, to their own PDS.
+3. The indexer learns the verified-DID set, then ingests matching records from verified publishers —
+   live via the Jetstream firehose and via periodic backfill sweeps.
+4. Composer queries the indexer for the catalog and loads each plugin's bundle on demand from its
+   `moduleUrl`.
+
+## Records
+
+| NSID                                           | rkey              | Author    | Purpose                                |
+| ---------------------------------------------- | ----------------- | --------- | -------------------------------------- |
+| `org.dxos.experimental.publisher.profile`      | `self`            | publisher | Identity-level publisher metadata.     |
+| `org.dxos.experimental.publisher.verification` | `<verified DID>`  | verifier  | A trust attestation about a publisher. |
+| `org.dxos.experimental.package.profile`        | `<key>`           | publisher | Plugin metadata (one per key per DID). |
+| `org.dxos.experimental.package.release`        | `<key>:<version>` | publisher | A versioned artifact of a package.     |
+
+All record bodies carry a `$type` field set to the NSID (standard ATProto convention; stamped by
+the CLI on write). All records live in the author's own repo and are therefore mutable by that
+author at the AT Protocol level; the **app-view** enforces immutability for what it serves (see
+[Integrity & tamper detection](#integrity--tamper-detection)).
+
+### `publisher.profile`
+
+Identity-level metadata about a publisher. One record per DID, `rkey = self`.
+
+| Field         | Required | Type         | Constraints | Notes                                     |
+| ------------- | -------- | ------------ | ----------- | ----------------------------------------- |
+| `displayName` | yes      | string       | 1–128 chars | Shown alongside the publisher's packages. |
+| `bio`         | no       | string       | ≤512 chars  | Short description.                        |
+| `homepageUrl` | no       | string (uri) |             | Canonical homepage.                       |
+| `contact`     | no       | string       | ≤256 chars  | Contact channel (email, handle, etc.).    |
+
+Written by `dx registry publish-publisher`.
+
+### `publisher.verification`
+
+A trust attestation that one identity (the verifier) vouches for a publisher. `rkey = <verified DID>`
+by convention; `subject` is the authoritative field.
+
+**Anyone can author verification records** — they are ordinary public AT Protocol records. Trust is a
+policy applied at indexing time, not a write-time restriction (see [Trust model](#trust-model)).
+
+| Field         | Required | Type              | Constraints | Notes                                                                                     |
+| ------------- | -------- | ----------------- | ----------- | ----------------------------------------------------------------------------------------- |
+| `subject`     | yes      | string (did)      |             | DID of the verified publisher. Should match the rkey.                                     |
+| `handle`      | yes      | string (handle)   |             | Publisher's handle at verification time; re-issued on change. Display-only, may be stale. |
+| `displayName` | yes      | string            | 1–128 chars | Display name bound by this verification.                                                  |
+| `createdAt`   | yes      | string (datetime) |             |                                                                                           |
+
+Written by `dx registry verify`.
+
+### `package.profile`
+
+Mutable metadata for a discoverable plugin. `rkey = <key>` (reverse-domain NSID, e.g.
+`org.dxos.plugin.excalidraw`). The `key` field is the plugin's globally-unique identifier and
+matches the `key` in `dx.config.ts`.
+
+| Field         | Required | Type                  | Constraints               | Notes                                                                                             |
+| ------------- | -------- | --------------------- | ------------------------- | ------------------------------------------------------------------------------------------------- |
+| `key`         | yes      | string                | 1–63 chars                | Reverse-domain NSID; equals the rkey (e.g. `org.dxos.plugin.excalidraw`).                         |
+| `name`        | yes      | string                | 1–128 chars               | Display name.                                                                                     |
+| `description` | no       | string                | ≤512 chars                | Shown in listings.                                                                                |
+| `homePage`    | no       | string (uri)          |                           | Canonical homepage or documentation URL.                                                          |
+| `source`      | no       | string (uri)          |                           | Public source repository.                                                                         |
+| `tags`        | no       | string[]              | ≤16 items, item ≤32 chars | Discovery tags.                                                                                   |
+| `screenshots` | no       | `{ light?, dark? }[]` | item urls                 | Preview images; each entry is a record of theme-specific URLs.                                    |
+| `icon`        | no       | `{ key, hue? }`       |                           | [Phosphor](https://phosphoricons.com) icon name (e.g. `ph--compass-tool--regular`) + palette hue. |
+| `dependsOn`   | no       | string[]              |                           | Plugin keys this plugin depends on at runtime (author-declared, version-independent NSIDs).       |
+| `spec`        | no       | string                |                           | Relative path inside the bundle to a bundled MDL spec file (e.g. `PLUGIN.mdl`).                   |
+| `createdAt`   | yes      | string (datetime)     |                           |                                                                                                   |
+
+Written by `dx registry publish` (from the manifest emitted by `composerPlugin` reading `dx.config.ts`)
+or `dx registry publish-package`.
+
+### `package.release`
+
+A record for one version of a package. `rkey = <key>:<version>`. Conceptually append-only: a new
+version is a new record, and the registry treats the first release seen per `(did, key, version)`
+as canonical — but the author technically retains write access to it (see
+[Integrity & tamper detection](#integrity--tamper-detection)).
+
+| Field          | Required | Type              | Constraints | Notes                                                                                                             |
+| -------------- | -------- | ----------------- | ----------- | ----------------------------------------------------------------------------------------------------------------- |
+| `package`      | yes      | string            | ≤63 chars   | Key of the parent `package.profile` authored by the same DID.                                                     |
+| `version`      | yes      | string            | ≤32 chars   | Semver subset without build metadata; pre-release suffixes allowed (`1.2.3-rc.1`). Taken from `package.json`.     |
+| `moduleUrl`    | yes      | string (uri)      | non-empty   | HTTPS URL of the module entrypoint / `manifest.json`. v0 trusts the publisher; content addressing is a follow-on. |
+| `manifestHash` | no       | string            | ≤256 chars  | Integrity hash of the module manifest, e.g. `sha256-<base64>`.                                                    |
+| `createdAt`    | yes      | string (datetime) |             |                                                                                                                   |
+
+Written by `dx registry publish`.
+
+> The release rkey uses `<key>:<version>` (colon), matching the emdash prior art. `:` is a legal
+> record-key character per the AT Protocol record-key grammar, and the key (a reverse-domain NSID
+> using only `[a-z0-9.]`) and version charset do not contain it, so the separator is unambiguous.
+
+## Trust model
+
+Verification records are public and unrestricted — anyone may author a `publisher.verification`. What
+makes the catalog trustworthy is the **indexing policy**, not a write gate:
+
+- **Today (single verifier).** The indexer is configured with one trusted verifier DID
+  (`REGISTRY_CURATOR_DID`) and honors `publisher.verification` records **only** from that DID. The
+  verified-DID set is the set of `subject`s across that verifier's records. A `package.*` or
+  `publisher.profile` record is indexed only if its author DID is in the verified set. This is a
+  deliberate moderation simplification while the registry is young — not a protocol restriction.
+- **Revocation.** Deleting the verification record removes the publisher from the verified set on the
+  next backfill sweep; the indexer unindexes their records.
+- **Later (multiple verifiers / moderation).** The single-verifier gate is intended to generalize to
+  multiple independent verifiers and moderation labels, similar to Bluesky's labeler model: clients
+  (or the indexer) subscribe to a set of verifiers/labelers they trust, and a publisher is shown if
+  any trusted verifier vouches for them. Until that moderation surface exists, DXOS only indexes
+  records from publishers DXOS itself has verified.
+
+A publisher may write their records before being verified — they simply won't appear in Composer
+until a trusted verifier vouches for them.
+
+## Integrity & tamper detection
+
+Immutability is an **app-view guarantee, not an AT Protocol one.** Like every AT Protocol repo, a
+publisher owns their PDS records and can mutate or delete any of them — including `package.release` —
+and no protocol mechanism makes a record cryptographically immutable. Enforcement therefore lives at
+the **registry app-view** (the edge service that indexes the firehose and serves the catalog to
+Composer): the PDS is the mutable source, and the app-view is the canonical, immutable view of what
+the registry serves.
+
+What the app-view enforces:
+
+- **Hosted bundles are immutable (enforced today).** Edge's `/registry/upload` rejects re-uploading an
+  existing `(slug, version)` with a `409` (outside dev), so the code/assets behind a published version
+  cannot be overwritten. A publisher self-hosting via `--asset-base-url` opts out of this guarantee.
+- **First-seen release pinning (enforced today).** The app-view pins the first `(did, slug:version)`
+  release it observes and ignores subsequent mutations to that record (`RegistryIndexer._writeRecord`),
+  so a publisher who repoints or rewrites a published release on their PDS cannot change what the
+  registry serves. A delete unindexes (clears the pin); a later recreate at the same rkey re-pins to the
+  new value. The pin lives in DO storage — a full DO eviction re-pins from current PDS state on the next
+  backfill (durable cross-eviction pinning is a follow-on).
+
+What stays mutable (the AT Protocol layer):
+
+- The PDS `package.release` record is written with `putRecord` (upsert), and the publisher can change
+  its `moduleUrl` / `manifestHash` at will. That is fine — the app-view's pin means such a change is not
+  re-served (the PDS is the mutable source; the app-view is the canonical view).
+
+Detectability (planned):
+
+- **Client-side verification.** Composer should verify the bundle it loads against the app-view's
+  pinned `manifestHash` and refuse to load on mismatch.
+- **Content addressing & signatures.** Longer term, address bundles by content hash and/or sign
+  release records so any party can verify integrity independently of the app-view.
+
+Until first-seen pinning and client-side verification land, treat a release's `moduleUrl` as
+publisher-trusted at the record level (the hosted bundle itself is already immutable).
+
+## Indexing
+
+- **Bootstrap / backfill.** On first run (and periodically), the indexer walks the verifier's repo
+  for verification records to compute the verified-DID set, then lists each verified publisher's repo
+  for `package.*` records (`runBackfill`). The catalog (`GET /registry/plugins`) collects releases
+  per `(authorDid, package-key)` — grouped by the release's `package` field, **not** by parsing the
+  rkey — newest-first, anchored by `at://<authorDid>/org.dxos.experimental.package.profile/<key>`.
+- **Live updates.** The indexer subscribes to the Jetstream firehose; commits for the four NSIDs are
+  validated (Effect-Schema) and written/deleted in DO storage, keyed by `record:<nsid>|<did>|<rkey>`.
+- **Validation seam.** Malformed records are rejected at ingestion against the Effect-Schema mirrors
+  of the JSON lexicons; they never enter the store.
+
+## Authoring
+
+The `dx` CLI writes records to the publisher's PDS over standard XRPC (`com.atproto.repo.putRecord`,
+`deleteRecord`, `listRecords`). It supports two auth modes (see
+[Publishing a Plugin](/docs/composer/publishing-plugins) for the user-facing flow):
+
+- **Logged-in identity (default).** After `dx account login`, writes are DPoP-signed by DXOS edge
+  using the AT Protocol account connected to the user's identity (the "Atmosphere" integration in
+  their personal space) — no app password.
+- **App password (headless).** `--handle` / `--app-password` (or `$ATPROTO_HANDLE` /
+  `$ATPROTO_APP_PASSWORD`) authenticate directly against the PDS.
+
+## Versioning
+
+Every NSID is under `org.dxos.experimental.*`. The namespace is deliberately marked unstable: fields
+and record shapes may change without migration guarantees. A final namespace
+(`org.dxos.registry.*` or similar) will be minted before promotion, at which point the experimental
+lexicons are frozen and the indexer dual-reads during a migration window.
+
+Package and publisher profiles are mutable (last-write-wins per rkey). Releases are conceptually
+single-write per version but not enforced (see [Integrity & tamper detection](#integrity--tamper-detection)).
+There is no in-band schema-version field on records — the NSID encodes the version.
+
+## SDK compatibility & the upgrade train
+
+Composer plugins **externalize `@dxos/*`** — at runtime they use the host's copy, so a plugin only
+works if it was built against an SDK compatible with what Composer ships. DXOS ships all `@dxos/*` as
+**one unit at one version** (`DXOS_VERSION`).
+
+**Mechanism — the manifest dependency snapshot.** The build (`composerPlugin`) auto-populates a
+`dependencies` map into the plugin's `manifest.json`: every declared dependency resolved to its
+concrete installed version (`{ "@dxos/app-framework": "0.8.3", "react": "19.2.0", … }`). This flows
+into the `package.release` record and the catalog (`PluginRelease.dependencies`). The host computes
+compatibility from the **subset it shares with the plugin** — the externalized `@dxos/*` packages —
+comparing each against its own shipped version under a policy (pre-1.0: **same minor**; post-1.0:
+caret). The remaining (bundled) deps are recorded for transparency/audit. A release with no
+`dependencies` is treated as "unknown" (legacy) and not gated.
+
+**Rollout-decoupling.** Because each release records the SDK it built against, a **stable Composer
+ignores plugin versions built for a newer SDK** — they don't surface as available upgrades. This lets
+plugin authors publish new versions _ahead_ of the stable Composer release without breaking users on
+the current version; those users pick the new versions up only once their Composer catches up.
+
+**The upgrade train** (operationalized in the plugins monorepo's `RELEASING.md`):
+
+1. **Continuous tracking (never released).** A nightly job points the monorepo's SDK catalog at the
+   latest DXOS `main` via `pkg.pr.new` and opens/updates an "SDK upgrade" PR; CI builds all plugins.
+   These prerelease pins may land on `main` to keep pace, but a **release guard forbids publishing**
+   against a non-released SDK.
+2. **On a cut SDK npm release.** A separate job bumps the catalog to the npm version, a **Composer
+   beta** ships on it, and new plugin versions are published against it (their manifests now declare
+   the new SDK).
+3. **Migration window (risk-scaled).** Hold before promoting the new SDK/Composer to stable; the
+   window scales with risk (longer for breaking changes) so authors can migrate, while the
+   compatibility gate keeps old and new users on the right versions. Exact windows are TBD.
+
+## Prior art
+
+These lexicons are modeled on the emdash RFC:
+
+- RFC: [emdash-cms/emdash#694](https://github.com/emdash-cms/emdash/pull/694) — design rationale,
+  trust-model trade-offs, rkey conventions, and the `experimental` namespace strategy.
+- Implementation: [emdash-cms/emdash#923](https://github.com/emdash-cms/emdash/pull/923).
+
+Difference from emdash's `com.emdashcms.experimental.*`: `releaseExtension` / `declaredAccess`
+records (sandbox manifest, granular permissions) are **not** in v0; they are a follow-on once the
+runtime sandbox surface is defined. (rkey conventions now match emdash, including `<slug>:<version>`.)
+
+## Schema reconciliation
+
+The JSON lexicons, the Effect-Schema validators, `PluginView`, and the CLI previously had field-level
+drift on `package.profile`. All items listed here are resolved.
+
+- **`slug` → `key`** — the identity field on `package.profile` is now named `key` everywhere: the
+  lexicon, the Effect-Schema validator, `PluginProfileSchema` in `@dxos/protocols`, the CLI flags
+  (`--key`), and the runtime `Plugin.Meta.profile.key`.
+- **`homepage` → `homePage`** — camelCase alignment across the lexicon, validator, `PluginProfileSchema`,
+  and `dx.config.ts`.
+- **`icon`** — unified as `{ key, hue? }` (object form) across `dx.config.ts`, `PluginProfileSchema`,
+  the validator, and the indexer projection. The CLI writes and the indexer stores the structured object.
+- **`screenshots`** — unified as `{ light?, dark? }[]` (object-only form) across `dx.config.ts`,
+  `PluginProfileSchema`, the validator, and the indexer projection. Plain URL strings are no longer
+  accepted at authoring time; use `{ dark: 'url' }` or `{ light: 'url', dark: 'url' }`.
+- **`dependsOn`** — added to `package.profile` (author-declared runtime plugin deps, NSIDs),
+  `PluginProfileSchema`, the validator, and `dx.config.ts`.
+- **`spec`** — added to `package.profile` (relative path to a bundled MDL spec),
+  `PluginProfileSchema`, the validator, and `dx.config.ts`.
+- **`dependencies`** (SDK-compat snapshot on `package.release`) — `composerPlugin` emits the full
+  resolved dependency map into `manifest.json`; the CLI writes it into the `package.release` record;
+  the validator preserves it in storage; `PluginReleaseSchema` in `@dxos/protocols` types it.
+
+## Open questions & follow-ons
+
+- **Integrity / tamper detection** — first-seen release pinning is enforced at the app-view; still to
+  do (see [Integrity & tamper detection](#integrity--tamper-detection)): client-side `manifestHash`
+  verification, durable pinning across full DO eviction, and longer term content addressing + signed
+  release records.
+- **Multiple verifiers / moderation** — generalize the single-verifier gate to a trusted-verifier set
+  / labeler model.
+- **Sandbox & permissions** — `releaseExtension` / `declaredAccess` lexicons, deferred until the
+  plugin runtime sandbox and permission model are defined.
+- **Namespace promotion** — finalize the stable namespace and the dual-read migration plan.
+- **Production proxy auth** — the edge `/atproto/proxy` route used by the logged-in DPoP write path
+  currently runs `skipAuth` in dev; production must require the caller's verifiable presentation.

package/moon.yml

@@ -22,6 +22,7 @@ tasks:
       - '--entryPoint=src/testing/index.ts'
       - '--entryPoint=src/testing/react.tsx'
       - '--entryPoint=src/core/url-loader.ts'
+      - '--entryPoint=src/config/index.ts'
     deps:
       - compile-plugin
   compile-plugin:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dxos/app-framework",
-  "version": "0.8.4-staging.60fe92afc8",
+  "version": "0.9.1-main.c7dcc2e112",
   "description": "A framework for building applications from composible plugins.",
   "homepage": "https://dxos.org",
   "bugs": "https://github.com/dxos/dxos/issues",
@@ -61,6 +61,11 @@
       "node": "./dist/lib/node-esm/url-loader/index.mjs",
       "types": "./dist/types/src/url-loader/index.d.ts"
     },
+    "./config": {
+      "browser": "./dist/lib/browser/config/index.mjs",
+      "node": "./dist/lib/node-esm/config/index.mjs",
+      "types": "./dist/types/src/config/index.d.ts"
+    },
     "./vite-plugin": {
       "import": "./dist/plugin/node-esm/index.mjs",
       "types": "./dist/types/src/vite-plugin/index.d.ts"
@@ -99,29 +104,29 @@
     "@effect/platform": "0.96.1",
     "babel-preset-solid": "^1.9.9",
     "cjs-module-lexer": "^2.2.0",
-    "esbuild": "0.28.0",
+    "esbuild": "0.28.1",
     "idb-keyval": "^6.2.1",
     "solid-js": "^1.9.11",
-    "@dxos/async": "0.8.4-staging.60fe92afc8",
-    "@dxos/compute-runtime": "0.8.4-staging.60fe92afc8",
-    "@dxos/context": "0.8.4-staging.60fe92afc8",
-    "@dxos/debug": "0.8.4-staging.60fe92afc8",
-    "@dxos/effect": "0.8.4-staging.60fe92afc8",
-    "@dxos/errors": "0.8.4-staging.60fe92afc8",
-    "@dxos/edge-client": "0.8.4-staging.60fe92afc8",
-    "@dxos/invariant": "0.8.4-staging.60fe92afc8",
-    "@dxos/keys": "0.8.4-staging.60fe92afc8",
-    "@dxos/log": "0.8.4-staging.60fe92afc8",
-    "@dxos/operation": "0.8.4-staging.60fe92afc8",
-    "@dxos/react-error-boundary": "0.8.4-staging.60fe92afc8",
-    "@dxos/protocols": "0.8.4-staging.60fe92afc8",
-    "@dxos/react-hooks": "0.8.4-staging.60fe92afc8",
-    "@dxos/ui-theme": "0.8.4-staging.60fe92afc8",
-    "@dxos/util": "0.8.4-staging.60fe92afc8",
-    "@dxos/react-ui": "0.8.4-staging.60fe92afc8",
-    "@dxos/web-context": "0.8.4-staging.60fe92afc8",
-    "@dxos/web-context-react": "0.8.4-staging.60fe92afc8",
-    "@dxos/compute": "0.8.4-staging.60fe92afc8"
+    "@dxos/async": "0.9.1-main.c7dcc2e112",
+    "@dxos/compute-runtime": "0.9.1-main.c7dcc2e112",
+    "@dxos/compute": "0.9.1-main.c7dcc2e112",
+    "@dxos/context": "0.9.1-main.c7dcc2e112",
+    "@dxos/debug": "0.9.1-main.c7dcc2e112",
+    "@dxos/edge-client": "0.9.1-main.c7dcc2e112",
+    "@dxos/effect": "0.9.1-main.c7dcc2e112",
+    "@dxos/errors": "0.9.1-main.c7dcc2e112",
+    "@dxos/operation": "0.9.1-main.c7dcc2e112",
+    "@dxos/invariant": "0.9.1-main.c7dcc2e112",
+    "@dxos/keys": "0.9.1-main.c7dcc2e112",
+    "@dxos/log": "0.9.1-main.c7dcc2e112",
+    "@dxos/protocols": "0.9.1-main.c7dcc2e112",
+    "@dxos/react-error-boundary": "0.9.1-main.c7dcc2e112",
+    "@dxos/react-hooks": "0.9.1-main.c7dcc2e112",
+    "@dxos/react-ui": "0.9.1-main.c7dcc2e112",
+    "@dxos/util": "0.9.1-main.c7dcc2e112",
+    "@dxos/ui-theme": "0.9.1-main.c7dcc2e112",
+    "@dxos/web-context": "0.9.1-main.c7dcc2e112",
+    "@dxos/web-context-react": "0.9.1-main.c7dcc2e112"
   },
   "devDependencies": {
     "@effect-atom/atom-react": "^0.5.0",
@@ -135,11 +140,11 @@
     "typedoc": "0.28.1",
     "vite": "^8.0.16",
     "vite-plugin-solid": "^2.11.12",
-    "@dxos/echo-client": "0.8.4-staging.60fe92afc8",
-    "@dxos/random": "0.8.4-staging.60fe92afc8",
-    "@dxos/storybook-utils": "0.8.4-staging.60fe92afc8",
-    "@dxos/brand": "0.8.4-staging.60fe92afc8",
-    "@dxos/test-utils": "0.8.4-staging.60fe92afc8"
+    "@dxos/brand": "0.9.1-main.c7dcc2e112",
+    "@dxos/echo-client": "0.9.1-main.c7dcc2e112",
+    "@dxos/random": "0.9.1-main.c7dcc2e112",
+    "@dxos/test-utils": "0.9.1-main.c7dcc2e112",
+    "@dxos/storybook-utils": "0.9.1-main.c7dcc2e112"
   },
   "peerDependencies": {
     "@effect-atom/atom-react": "^0.5.0",

package/src/cli/cli.ts

@@ -15,7 +15,7 @@ const defaultPluginLoader =
   (plugins: Plugin.Plugin[]): PluginManager.ManagerOptions['pluginLoader'] =>
   (id: string) =>
     Effect.sync(() => {
-      const plugin = plugins.find((plugin) => plugin.meta.id === id);
+      const plugin = plugins.find((plugin) => plugin.meta.profile.key === id);
       invariant(plugin, `Plugin not found: ${id}`);
       return { plugin };
     });
@@ -43,7 +43,7 @@ export type CreateCliAppOptions = {
  *
  * @param options.pluginManager Optional existing PluginManager instance.
  * @param options.pluginLoader Function to load plugins by ID.
- * @param options.plugins All plugins available to the application. Plugins whose `meta.tags` includes `'system'` are treated as core.
+ * @param options.plugins All plugins available to the application. Plugins whose `meta.profile.tags` includes `'system'` are treated as core.
  * @param options.enabled Enabled plugins.
  * @param options.safeMode Whether to enable safe mode, which disables optional plugins.
  */

package/src/common/activation-events.ts

@@ -16,7 +16,7 @@ export const Startup = ActivationEvent$.make('org.dxos.app-framework.event.start
 /**
  * Fired to load any newly available surfaces.
  */
-export const SetupReactSurface = ActivationEvent$.make('org.dxos.app-framework.event.setup-react-surface');
+export const SetupReactSurface = ActivationEvent$.make('org.dxos.app-framework.event.setupReactSurface');
 
 /**
  * Fired before the process manager is created.
@@ -25,7 +25,7 @@ export const SetupReactSurface = ActivationEvent$.make('org.dxos.app-framework.e
  * process manager's {@link ServiceResolver} and {@link OperationInvoker} pick
  * them up at construction time.
  */
-export const SetupProcessManager = ActivationEvent$.make('org.dxos.app-framework.event.setup-process-manager');
+export const SetupProcessManager = ActivationEvent$.make('org.dxos.app-framework.event.setupProcessManager');
 
 //
 // Triggered Events
@@ -36,4 +36,4 @@ export const SetupProcessManager = ActivationEvent$.make('org.dxos.app-framework
  * (`ProcessManagerRuntime`, `ServiceResolver`, `ProcessMonitor`, `OperationInvoker`)
  * have been contributed.
  */
-export const ProcessManagerReady = ActivationEvent$.make('org.dxos.app-framework.event.process-manager-ready');
+export const ProcessManagerReady = ActivationEvent$.make('org.dxos.app-framework.event.processManagerReady');

package/src/common/capabilities.ts

@@ -41,13 +41,13 @@ export const Null = Capability$.make<null>('org.dxos.app-framework.capability.nu
  * @category Capability
  */
 export const PluginManager = Capability$.make<PluginManager$.PluginManager>(
-  'org.dxos.app-framework.capability.plugin-manager',
+  'org.dxos.app-framework.capability.pluginManager',
 );
 
 /**
  * @category Capability
  */
-export const AtomRegistry = Capability$.make<Registry.Registry>('org.dxos.app-framework.capability.atom-registry');
+export const AtomRegistry = Capability$.make<Registry.Registry>('org.dxos.app-framework.capability.atomRegistry');
 
 export type ReactContext = Readonly<{
   id: string;
@@ -58,14 +58,14 @@ export type ReactContext = Readonly<{
 /**
  * @category Capability
  */
-export const ReactContext = Capability$.make<ReactContext>('org.dxos.app-framework.capability.react-context');
+export const ReactContext = Capability$.make<ReactContext>('org.dxos.app-framework.capability.reactContext');
 
 export type ReactRoot = Readonly<{ id: string; root: FC<PropsWithChildren> }>;
 
 /**
  * @category Capability
  */
-export const ReactRoot = Capability$.make<ReactRoot>('org.dxos.app-framework.capability.react-root');
+export const ReactRoot = Capability$.make<ReactRoot>('org.dxos.app-framework.capability.reactRoot');
 
 /**
  * Surface definitions that can be either React components or Web Components.
@@ -75,7 +75,7 @@ export type ReactSurface = Surface.Definition | readonly Surface.Definition[];
 /**
  * @category Capability
  */
-export const ReactSurface = Capability$.make<ReactSurface>('org.dxos.app-framework.common.react-surface');
+export const ReactSurface = Capability$.make<ReactSurface>('org.dxos.app-framework.capability.reactSurface');
 
 export type AnyCommand = Command$.Command<any, any, any, any>;
 
@@ -98,7 +98,7 @@ export const Layer = Capability$.make<Layer$.Layer<any, any, any>>('org.dxos.app
  *
  * @category Capability
  */
-export const LayerSpec = Capability$.make<LayerSpec$.LayerSpec>('org.dxos.app-framework.capability.layer-spec');
+export const LayerSpec = Capability$.make<LayerSpec$.LayerSpec>('org.dxos.app-framework.capability.layerSpec');
 
 /**
  * Context passed to {@link TraceSinkFactory} implementations when the
@@ -133,7 +133,7 @@ export type TraceSinkFactory = (ctx: TraceSinkFactoryContext) => Trace$.Sink;
  *
  * @category Capability
  */
-export const TraceSink = Capability$.make<TraceSinkFactory>('org.dxos.app-framework.capability.trace-sink');
+export const TraceSink = Capability$.make<TraceSinkFactory>('org.dxos.app-framework.capability.traceSink');
 
 /**
  * Service resolver backing the shared {@link ProcessManagerRuntime}.
@@ -157,7 +157,7 @@ export const TraceSink = Capability$.make<TraceSinkFactory>('org.dxos.app-framew
  * @category Capability
  */
 export const ServiceResolver = Capability$.make<ServiceResolver$.ServiceResolver>(
-  'org.dxos.app-framework.capability.service-resolver',
+  'org.dxos.app-framework.capability.serviceResolver',
 );
 
 /**
@@ -167,7 +167,7 @@ export const ServiceResolver = Capability$.make<ServiceResolver$.ServiceResolver
  *
  * @category Capability
  */
-export const ProcessMonitor = Capability$.make<Process$.Monitor>('org.dxos.app-framework.capability.process-monitor');
+export const ProcessMonitor = Capability$.make<Process$.Monitor>('org.dxos.app-framework.capability.processMonitor');
 
 /**
  * Services that are always available when running effects through a {@link ProcessManagerRuntime}.
@@ -207,7 +207,7 @@ export interface ProcessManagerRuntime {
  * @category Capability
  */
 export const ProcessManagerRuntime = Capability$.make<ProcessManagerRuntime>(
-  'org.dxos.app-framework.capability.process-manager-runtime',
+  'org.dxos.app-framework.capability.processManagerRuntime',
 );
 
 export type ManagedRuntime = ManagedRuntime$.ManagedRuntime<any, any>;
@@ -215,14 +215,14 @@ export type ManagedRuntime = ManagedRuntime$.ManagedRuntime<any, any>;
 /**
  * @category Capability
  */
-export const ManagedRuntime = Capability$.make<ManagedRuntime>('org.dxos.app-framework.capability.managed-runtime');
+export const ManagedRuntime = Capability$.make<ManagedRuntime>('org.dxos.app-framework.capability.managedRuntime');
 
 //
 // Operation System Capabilities
 //
 
 export const OperationHandler = Capability$.make<OperationHandlerSet.OperationHandlerSet>(
-  'org.dxos.app-framework.capability.operation-handler',
+  'org.dxos.app-framework.capability.operationHandler',
 );
 
 export type UndoMapping = UndoMapping$.UndoMapping;
@@ -231,7 +231,7 @@ export type UndoMapping = UndoMapping$.UndoMapping;
  * Undo mapping registration - contributed by plugins.
  * @category Capability
  */
-export const UndoMapping = Capability$.make<UndoMapping[]>('org.dxos.app-framework.capability.undo-mapping');
+export const UndoMapping = Capability$.make<UndoMapping[]>('org.dxos.app-framework.capability.undoMapping');
 
 /**
  * Operation invoker backed by the process manager. Spawns a process per
@@ -244,7 +244,7 @@ export type OperationInvoker = OperationInvoker$.OperationInvoker;
  * @category Capability
  */
 export const OperationInvoker = Capability$.make<OperationInvoker>(
-  'org.dxos.app-framework.capability.operation-invoker',
+  'org.dxos.app-framework.capability.operationInvoker',
 );
 
 export type UndoRegistry = UndoRegistry$.UndoRegistry;
@@ -253,7 +253,7 @@ export type UndoRegistry = UndoRegistry$.UndoRegistry;
  * Undo registry - provided by ProcessManagerPlugin.
  * @category Capability
  */
-export const UndoRegistry = Capability$.make<UndoRegistry>('org.dxos.app-framework.capability.undo-registry');
+export const UndoRegistry = Capability$.make<UndoRegistry>('org.dxos.app-framework.capability.undoRegistry');
 
 export type HistoryTracker = HistoryTracker$.HistoryTracker;
 
@@ -261,7 +261,7 @@ export type HistoryTracker = HistoryTracker$.HistoryTracker;
  * History tracker - provided by ProcessManagerPlugin.
  * @category Capability
  */
-export const HistoryTracker = Capability$.make<HistoryTracker>('org.dxos.app-framework.capability.history-tracker');
+export const HistoryTracker = Capability$.make<HistoryTracker>('org.dxos.app-framework.capability.historyTracker');
 
 //
 // Atom Capability Helpers

package/src/config/index.ts

@@ -0,0 +1,5 @@
+//
+// Copyright 2026 DXOS.org
+//
+
+export { Config2 } from '@dxos/protocols';