@dxos/app-framework 0.10.0 → 0.11.0

package/.storybook/main.mts

@@ -2,7 +2,7 @@
 // Copyright 2025 DXOS.org
 //
 
-import { createConfig } from '../../../../tools/storybook-react/.storybook/main';
+import { createConfig } from '../../../../tools/storybook-react/.storybook/main.ts';
 
 export const stories = ['../src/**/*.stories.tsx'];
 

package/.storybook/preview.mts

@@ -2,7 +2,7 @@
 // Copyright 2025 DXOS.org
 //
 
-import { preview } from '../../../../tools/storybook-react/.storybook/preview';
+import { preview } from '../../../../tools/storybook-react/.storybook/preview.ts';
 
-export * from '../../../../tools/storybook-react/.storybook/preview';
+export * from '../../../../tools/storybook-react/.storybook/preview.ts';
 export default preview;

package/CHANGELOG.md

@@ -0,0 +1,93 @@
+# @dxos/app-framework
+
+## 0.11.0
+
+### Minor Changes
+
+- 2048cb3: Replace `Surface.isAvailable` with `Surface.useIsAvailable`, a hook returning a stable, memoized function. Surfaces and graph extensions with an invalid (non-camelCase) local id are now dropped with a warning instead of throwing and crashing plugin activation.
+- ed992c2: `Surface.create` accepts an optional `props` mapper, so a container can be registered directly
+  instead of being wrapped in an adapter that unpacks the surface's `data` envelope:
+
+  ```ts
+  Surface.create({
+    id: 'defaultPluginSettings',
+    filter: AppSurface.settings(AppSurface.Article),
+    component: DefaultSettings,
+    props: ({ data: { subject } }) => ({ subject }),
+  });
+  ```
+
+  The mapper's input type derives from the same `filter` that defines the surface's data shape, so the
+  unpacking is type-checked rather than restated by hand, and is exported as `Surface.ComponentProps`
+  for components that consume the whole envelope. `component` accepts any `ComponentType`, so a
+  container re-exported through a `lazy()` barrel needs no cast. Additive: definitions without `props`
+  receive the full surface props exactly as before.
+
+- 08a3eea: Plumb ephemeral trace events through the swarm (DX-1125).
+
+  Adds tag-based broadcast pub/sub over the existing swarm messaging layer (spec 1): a message may carry `tags` instead of a single `recipient`, and a subscriber registers a tag set and receives any broadcast whose tags intersect (logical OR). New wire fields (`signal.Message.tags`, `signal.SubscribeMessagesRequest`, `messenger.Message.tags`, `SwarmRequest.SUBSCRIBE`/`subscribe_tags`) and a dedicated `onBroadcast` channel keep broadcasts off the point-to-point path.
+
+  On top of that (spec 2), remote runtimes broadcast their ephemeral trace messages so clients can watch live progress: `Trace.messageToTags`/`Filter`/`matchesFilter`/`encodeTraceMessage`, a `SwarmTraceSink` producer, `Process.Monitor.subscribeToTraceMessages(filter)`, a `RemoteTraceMonitor` swarm source merged into the aggregate monitor, and a plugin-client consumer that projects remote `status.update` events into the progress registry.
+
+### Patch Changes
+
+- Updated dependencies [aea1e6e]
+- Updated dependencies [9da013f]
+- Updated dependencies [e0e1a9f]
+- Updated dependencies [ed992c2]
+- Updated dependencies [1a9bca1]
+- Updated dependencies [ed992c2]
+- Updated dependencies [bf013a1]
+- Updated dependencies [a19443b]
+- Updated dependencies [3f1fc67]
+- Updated dependencies [962c8cd]
+- Updated dependencies [6a03a30]
+- Updated dependencies [2fe5a7a]
+- Updated dependencies [277e365]
+- Updated dependencies [d958118]
+- Updated dependencies [2a68c3b]
+- Updated dependencies [e65432c]
+- Updated dependencies [f6a01e3]
+- Updated dependencies [c9651f1]
+- Updated dependencies [5e7839e]
+- Updated dependencies [c727a43]
+- Updated dependencies [6067460]
+- Updated dependencies [717edc0]
+- Updated dependencies [51aaffe]
+- Updated dependencies [f7d7735]
+- Updated dependencies [114fb98]
+- Updated dependencies [37874ce]
+- Updated dependencies [b591791]
+- Updated dependencies [848ba1b]
+- Updated dependencies [bf055c8]
+- Updated dependencies [55bb048]
+- Updated dependencies [c727a43]
+- Updated dependencies [4df6cf3]
+- Updated dependencies [7b270f2]
+- Updated dependencies [37c17cc]
+- Updated dependencies [08a3eea]
+- Updated dependencies [ed992c2]
+- Updated dependencies [ed992c2]
+- Updated dependencies [c58ebb7]
+  - @dxos/async@0.11.0
+  - @dxos/react-ui-list@0.11.0
+  - @dxos/react-ui@0.11.0
+  - @dxos/compute-runtime@0.11.0
+  - @dxos/compute@0.11.0
+  - @dxos/util@0.11.0
+  - @dxos/protocols@0.11.0
+  - @dxos/keys@0.11.0
+  - @dxos/ui-theme@0.11.0
+  - @dxos/log@0.11.0
+  - @dxos/edge-client@0.11.0
+  - @dxos/operation@0.11.0
+  - @dxos/react-error-boundary@0.11.0
+  - @dxos/react-hooks@0.11.0
+  - @dxos/context@0.11.0
+  - @dxos/effect@0.11.0
+  - @dxos/storybook-addon-logger@0.11.0
+  - @dxos/debug@0.11.0
+  - @dxos/errors@0.11.0
+  - @dxos/invariant@0.11.0
+  - @dxos/web-context@0.11.0
+  - @dxos/web-context-react@0.11.0

package/TASKS.md

@@ -0,0 +1,11 @@
+# app-framework — Tasks
+
+## Capability API
+
+- [ ] **Review `useCapability` vs `useCapabilities` selection** — `useCapability` throws when no
+      contribution exists, so every optional-capability consumer has drifted to the
+      `useCapabilities(...)[0]` / `getAll(...)[0]` idiom (MarkdownArticle `EditorBindingHook`,
+      `useSelectionContext` ViewState, markdown `get-selection` handler), which mis-states
+      at-most-one semantics. Consider an optional-singleton accessor (`useCapability(cap,
+{ optional: true })` or `useCapabilityMaybe`) returning `T | undefined`, plus a dev warning
+      when contributions > 1; then migrate the `[0]` sites.