Local-first, dids, wasm + OPFS, flutter, iroh, dht

.cargo/config.toml

@@ -0,0 +1,2 @@
+[alias]
+bin = ["run", "--package", "cargo-bin", "--"]

.config/nextest.toml

@@ -0,0 +1,34 @@
+# See https://nexte.st/book/configuration.html
+
+[profile.default]
+# Many integration tests spin up an actix HTTP server on a unique port.
+# Running them all in parallel (default = num CPUs) saturates the runtime
+# and surfaces flakes in `query_subscribe`, `blob_sync`, and `search`.
+# 2 threads is the sweet spot for the rest of the suite; the search test
+# below needs serial isolation specifically.
+test-threads = 2
+retries = 2
+
+# Serialize the tantivy-backed search test — its `IndexReader::reload()`
+# can return before a fresh searcher is visible if CPU is contested,
+# making `Updated Title` appear missing despite the writer having
+# committed it.
+[[profile.default.overrides]]
+# Use `package(atomic-server)` rather than `binary(=atomic-server)` —
+# the latter matches the binary *name* not binary-id, and silently
+# fails to match the lib-unit-test binary in this workspace
+# (verified via `cargo nextest run -E '...'`: package() returns the
+# test, binary() returns 0). Symptom of the wrong syntax: nextest
+# parses the override but the filter matches no tests, so the
+# test-group + retries override never applies in practice.
+filter = 'package(atomic-server) and test(=search::tests::test_update_resource)'
+test-group = 'serial'
+# This test hits a tantivy reload race under heavy parallel CI load
+# (the reader uses `OnCommitWithDelay` and the background segment-merge
+# thread can starve when 20+ actix HTTP servers are spinning up). The
+# in-test poll loop already waits 30s; allow more retries on top so a
+# truly unlucky run still has a fallback before the hard fail.
+retries = 5
+
+[test-groups]
+serial = { max-threads = 1 }

.dagger/.gitattributes

@@ -1 +1,2 @@
 /sdk/** linguist-generated
+tar