Combined test branch: batch 2 plus all open PRs (2026-10-05)

.dagger/src/index.ts

@@ -542,6 +542,11 @@ export class AtomicServer {
           dag.cacheVolume('flutter-pub-cache'),
         )
         .withDirectory('/workspace/flutter', this.source.directory('flutter'))
+        // `flutter/pubspec.yaml` points at ../packages/atomic_flutter.
+        .withDirectory(
+          '/workspace/packages',
+          this.source.directory('packages'),
+        )
         .withWorkdir('/workspace/flutter')
         .withExec([
           'bash',
@@ -818,6 +823,11 @@ export class AtomicServer {
         ])
         .withDirectory('/workspace/lib', this.source.directory('lib'))
         .withDirectory('/workspace/flutter', this.source.directory('flutter'))
+        // `flutter/pubspec.yaml` points at ../packages/atomic_flutter.
+        .withDirectory(
+          '/workspace/packages',
+          this.source.directory('packages'),
+        )
         .withMountedCache('/workspace/flutter/rust/target', flutterRustTarget, {
           sharing: CacheSharingMode.Locked,
         })

.github/workflows/atomic-flutter.yml

@@ -0,0 +1,22 @@
+name: Atomic Flutter package
+on:
+  pull_request:
+    paths: ['packages/atomic_flutter/**', 'flutter/**', '.github/workflows/atomic-flutter.yml']
+  push:
+    paths: ['packages/atomic_flutter/**', 'flutter/**', '.github/workflows/atomic-flutter.yml']
+jobs:
+  package:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: subosito/flutter-action@v2
+        with:
+          flutter-version: '3.44.7'
+          channel: stable
+          cache: true
+      - run: flutter pub get
+        working-directory: packages/atomic_flutter
+      - run: flutter analyze
+        working-directory: packages/atomic_flutter
+      - run: flutter test
+        working-directory: packages/atomic_flutter

.gitignore

@@ -19,6 +19,7 @@ server/assets_tmp
 # Same, for the plugin assets `build.rs` stages before embedding them.
 server/integrations_assets_tmp
 server/js-build.log
+server/js-inputs.hash
 .netlify
 scratchpad
 # Local Claude Code state stays out; the shared cloud-session hook is tracked.

AGENTS.md

@@ -162,6 +162,15 @@ After touching anything that renders text, read the `.po` diff by hand: a
 guarded element can silently drop sibling strings, and entries re-key when an
 icon moves into a message.
 
+## Running a branch for another device
+
+`scripts/run-branch.sh <branch> [--tunnel]` builds a branch in its own worktree and target dir and serves it on 0.0.0.0.
+
+- The app needs a secure origin (OPFS). Plain http works on `http://localhost` only; from a phone or tablet over `http://<lan-ip>` it fails with "This browser could not open local storage". Use `--tunnel` (cloudflared quick tunnel, public while it runs) or the Chrome flag `unsafely-treat-insecure-origin-as-secure`.
+- The server derives the origin it accepts logins for from `ATOMIC_DOMAIN` (+ port, http). Behind a tunnel set `ATOMIC_DOMAIN` to the public host, otherwise the websocket auth fails with "does not name this server". `ATOMIC_SERVER_URL` is not read.
+- Do not use tunnelto: it drops the websocket and the app stays on "Loading".
+- A global `build-dir` in `~/.cargo/config.toml` is shared by every repo and carries one lock. A running `cargo run` then blocks every other cargo (also the one inside `wasm-pack`) silently at 0% CPU, which looks like a hung build. Set `CARGO_BUILD_BUILD_DIR` to a private dir, as the script and `build:wasm` do.
+
 ## Quick Dev Setup
 
 Use the Charlotte MCP server and navigate to `http://localhost:6747/app/dev-drive` to instantly create a fresh agent.

CHANGELOG.md

@@ -7,6 +7,31 @@ See [STATUS.md](server/STATUS.md) to learn more about which features will remain
 
 ## UNRELEASED
 
+- `--served-domain-suffix` / `ATOMIC_SERVED_DOMAIN_SUFFIX` takes a comma-separated list (`atomicserver.eu,atomic.place`), so a node can answer under two domains while it moves from one to the other.
+- MCP endpoint: `POST /mcp` (Streamable HTTP) is the one implementation of the
+  MCP tools, for clients that cannot run a local process, such as claude.ai, and
+  for the local `@tomic/mcp`, which now only bridges to it. It is an OAuth 2.1
+  resource server (RFC 9728 metadata at `/.well-known/oauth-protected-resource`)
+  with the node as authorization server (`/oauth/register`, `/oauth/authorize`,
+  `/oauth/token`, PKCE S256, dynamic client registration, `resource` checked).
+  The person approves in the app (`/app/authorize-mcp`): which drives, and read
+  only or read and edit. Reading is as an issued agent under the normal rights
+  checks. If editing was allowed, `edit_resource`, `create_resource` (documents
+  take Markdown as `_documentText`) and `delete_resource` exist, and the node
+  signs those commits as that issued agent, never as the person. Revoking is
+  removing it under Connected apps. `list_drives`, `get_resource`, `search`,
+  `query`, `get_user_classes` and `get_schema` are the read tools.
+  `--app-url` / `ATOMIC_APP_URL` says where the approval page lives when the app
+  is not served by this node.
+- The approval page only works with a node the person is already using: a link
+  naming another server is refused, and the redirect back to the client must be
+  exactly the one registered, so a crafted link cannot grant access to someone
+  else's key or run script in the app.
+
+- `atomic-cli connect`: connect the CLI with a key made on this machine,
+  approved in the app (`/app/connect-agent`), instead of pasting your agent
+  secret. Without a config file, the CLI now points you to it rather than
+  asking for the secret.
 - Forms (beta): guests can fill in a form without an account, and each answer
   becomes a row in a Table. New default ontology `forms`
   (`lib/defaults/forms.json`: `Form`, `FormPage`, `FormField`, `FormHeading`,
@@ -38,6 +63,13 @@ See [STATUS.md](server/STATUS.md) to learn more about which features will remain
   recipient could hold. Read rights are checked per subscriber against the
   resource when it is sent, and a connection already reached through the
   resource or its drive doesn't get it twice.
+- End-to-end encrypted conversations. `atomic_lib::conversation` derives an
+  agent's X25519 `encryptionKey`, keeps a conversation's keys in a keyring
+  wrapped to each member, and seals and opens messages; the WASM build exports
+  it. New default ontology `conversations` (`lib/defaults/conversations.json`)
+  with the `Conversation` and `SealedMessage` classes. New endpoint
+  `/conversations` lists the conversations on the server the requesting agent
+  is a member of. See `planning/encrypted-conversations.md`.
 
 - New default ontology `notifications` (`lib/defaults/notifications.json`):
   the `Inbox` and `Notification` classes, and an `inbox` property the private

TESTING_COVERAGE.md

@@ -2580,3 +2580,13 @@ refused subscribe is dropped.
 - The paired SaaS `portal/e2e/onboarding.spec.ts` closes the original context,
   downloads the vault into a fresh browser, verifies the saved document and
   profile, requires a clean console, and budgets metadata reads after reload.
+
+## Flutter account package (draft)
+
+`packages/atomic_flutter/test/account_test.dart` covers device approval, provider
+origin binding, redirect refusal, account/backup mismatch, authenticated discovery,
+AES-GCM envelope compatibility with an independently generated Node fixture,
+tamper rejection, and closing during a pending request. Atomic Audio additionally
+checks isolated native identity installation and actual bidirectional iroh/Loro
+with BLAKE3 files introduced after pairing. Production account approval, Vault
+transport and recovery on a physical device are not covered by these tests.