docs(exploration): explore running an xNet hub on a Raspberry Pi - #477
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: xNet Test <test@xnet.dev>
Contributor
|
Preview removed for PR #477. |
crs48
added a commit
that referenced
this pull request
Jul 12, 2026
) ## Summary Docs-only PRs to main were structurally unmergeable without `gh pr merge --admin`: [ci.yml](.github/workflows/ci.yml) path-ignores `docs/**`, `*.md`, `**/*.md`, `.github/*.md` on the `pull_request` trigger, while the main-branch ruleset requires the contexts `lint`, `typecheck`, `test (1/3)`–`test (3/3)`, `editor-ux`, and `changelog-section`. On a docs-only PR those workflows never run, the contexts never report, and `mergeStateStatus` stays **BLOCKED** forever — hit on #477, same failure shape as exploration 0265's release-PR stall. ## Fix GitHub's documented paired no-op pattern ("Handling skipped but required checks"): - New **`ci-docs-noop.yml`** with the SAME job names (`lint`, `typecheck`, `test` sharded `1/3`–`3/3`, `editor-ux`), triggered by `paths:` matching exactly what ci.yml ignores; every job just exits 0. A required context is satisfied by a passing check run of that name from either workflow. - `changelog-section` is **not** twinned: `changelog-check.yml` has no paths filter and already reports on docs-only PRs (fragment or `skip-changelog` label as usual). - Both workflows carry `KEEP IN SYNC` comments pointing at each other so the `paths` / `paths-ignore` lists don't drift. - Mixed PRs (docs + code) trigger both workflows; the real ci.yml run completes after the seconds-long no-op and GitHub surfaces the most recent check run per context, so the real result gates the merge. Per the 0294 policy: the named consumer is the main ruleset itself; the pass condition is decidable by construction (always green). ## Verification - actionlint 1.7.12 passes on both workflow files. - After merge: a throwaway docs-only PR will be opened to confirm `mergeStateStatus` reaches CLEAN/UNSTABLE instead of BLOCKED (this PR touches workflows, so it runs the full real CI and can't exercise the docs-only path itself). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
crs48
added a commit
that referenced
this pull request
Jul 12, 2026
…ion) (#483) 0300 was already claimed by the Raspberry Pi hub exploration (#477) merged from a parallel worktree, and 0301/0302 are taken — the known cross-worktree numbering gotcha. Renames the doc and updates exploration-number references in code comments and CLAUDE.md. Comment-only for publishable packages (empty changeset). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
crs48
pushed a commit
that referenced
this pull request
Jul 12, 2026
…→0306 (epoch arbitration) Parallel worktree sessions produced duplicate exploration numbers: 0300 was claimed by both RUNNING_AN_XNET_HUB_ON_A_RASPBERRY_PI (#477) and HASH_GRINDING_MITIGATION (#482); 0301 by both ATPROTO_INTEGRATION (#476) and EPOCH_RESOLVED_HUB_ARBITRATION (#482). The later-merged docs (both from #482) move to the next free numbers. 0304 is skipped: an open local branch (claude/schema-auth-crud-166c96) already claims it for the schema-authz CRUD-split exploration, so the free numbers are 0305 and 0306 (verified against main, all remote branches, and all local branches/worktrees). Updates every reference that means the renamed docs: grinding-related code/test comments across core/sync/data/sqlite/runtime/hub/telemetry, the Rust kernel, the protocol spec (02-data-model.md §7 and the epoch pointer), the pending hash-grinding changeset, and the epoch doc's companion links. Also fixes the stale "exploration 0300 — Effect Tier 0" citations in package CHANGELOGs to 0303 (renumbered in #483). References to 0300/0301 meaning the Raspberry Pi and ATProto docs are left untouched. Comment-only package changes — empty changeset. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: xNet Test <test@xnet.dev>
crs48
added a commit
that referenced
this pull request
Jul 12, 2026
…→0306 (epoch arbitration) (#486) ## Summary Parallel worktree sessions left two more duplicate exploration numbers after the Effect doc's renumber in #483: | Number | Kept (earlier merge) | Renumbered (later merge, both from #482) | |---|---|---| | 0300 | `RUNNING_AN_XNET_HUB_ON_A_RASPBERRY_PI` (#477) | `HASH_GRINDING_MITIGATION` → **0305** | | 0301 | `ATPROTO_INTEGRATION_IDENTITY_SYNC_AND_HUB_AS_PDS` (#476) | `EPOCH_RESOLVED_HUB_ARBITRATION` → **0306** | **Why not 0304:** an open local branch (`claude/schema-auth-crud-166c96`) already claims 0304 for the schema-authz CRUD-split exploration. 0305/0306 verified free on main, every remote branch, and every local branch/worktree. ## Reference mapping Every `0300`/`0301` mention in the repo was classified by which doc it actually cites before rewriting: - **→ 0305** (hash grinding): comments/tests in `core` (lww), `sync` (clientid-attestation, chain, clock, serializers/v4, features), `data` (store, hydration, sqlite-adapter, types, conformance tests), `sqlite` (schema), `runtime` (conformance), `hub` (node-relay fix G, shard ring), `telemetry` test, the Rust kernel (`rust/xnet-core/src/lib.rs`), `docs/specs/protocol/02-data-model.md` §7, `tests/reliability`, the pending `.changeset/hash-grinding-mitigation.md`, and all companion references inside the epoch doc (whose link also gets the correct `[x]` status marker). - **→ 0306** (epoch arbitration): the pointer in `docs/specs/protocol/02-data-model.md`. - **→ 0303** (drive-by fix): four `packages/*/CHANGELOG.md` entries from #480 still said "exploration 0300 — Effect Tier 0"; the Effect doc is 0303 since #483. - **Left alone**: `.changeset/silly-trams-help.md` narrative (0300 = Raspberry Pi, 0301 = ATProto — still accurate), and everything citing the Raspberry Pi / ATProto docs. Replacements were digit-boundary-guarded so timestamps/unicode ranges are untouched. Comment-only changes to publishable packages → empty changeset (a bot may re-add patch bumps; drop at the release PR). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
crs48
added a commit
that referenced
this pull request
Jul 13, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @xnetjs/core@1.0.0 ### Major Changes - [#482](#482) [`e6b4c6f`](e6b4c6f) Thanks [@crs48](https://github.com/crs48)! - Grinding-resistant Last-Write-Wins tiebreak (protocol v4, exploration 0305) The final LWW conflict tiebreak was the raw author DID ("higher DID wins"). Because a `did:key` is a free, attacker-chosen function of a keypair, an attacker could grind a vanity DID that sorts highest and win **every** concurrent-write tie against every honest peer, permanently. Protocol v4 replaces that final rung with a per-conflict key, `blake3(authorDID ‖ property ‖ value)` (`computeLwwTiebreakKey` in `@xnetjs/core`), so the winner of a tie is a random-oracle function of _what is written_ — a ground identity wins no durable, universal advantage. The key is gated on both changes being v4 (legacy changes fall back to the author DID), is derived at resolution time (never part of the change hash or wire format), and is threaded through `PropertyTimestamp`, the SQLite `node_properties` guard (new nullable `tiebreak_key` column, schema v8), and every conformance kernel. BREAKING: `CURRENT_PROTOCOL_VERSION` is now `4` and new changes are stamped v4. The LWW golden vectors gain `0005-tie-grinding-resistant-key`; `LwwStamp` / `PropertyTimestamp` gain an optional `tiebreakKey`. Mixed fleets converge on exact `{lamport, wallTime}` ties only once both peers are on v4 — a transient rollout window affecting rare exact ties. ### Minor Changes - [#488](#488) [`1de6587`](1de6587) Thanks [@crs48](https://github.com/crs48)! - Schema authorization gains `create` and `update` actions — optional refinements of `write` (exploration 0304). A schema may now split its mutation policy into who may **add** nodes vs. who may **modify** existing ones; when a refinement is absent it falls back to the schema's `write` expression, so existing schemas behave identically. - `@xnetjs/core`: `AUTH_ACTIONS` includes `create`/`update`; new `actionExpressionOrder()` and `grantActionSatisfies()` helpers (a `write` grant covers both refinements; granular grants cover only themselves). - `@xnetjs/data`: the policy evaluator resolves actions with the fallback and evaluates `create` against the draft node built from the payload (container relations resolve membership, so creation into a shared Space is genuinely gated); `NodeStore` checks the precise verbs, and remote creates are inferred and checked as `create` instead of failing closed on a not-yet-existing node. New `spaceContributorAuthorization()` cascade — adopted by `ChatMessage` and `Comment` — expresses "members may post, only the author (or space admins) may edit". `StoreAuthAPI.can` accepts an optional draft `node`. - `@xnetjs/react`: new `useCanCreate(schemaId, properties)` hook; `useCan`/`useCanEdit` check the precise `update` verb. - `@xnetjs/runtime`: conformance corpus gains the `authz-actions` suite pinning the fallback table. ### Patch Changes - [#483](#483) [`38fd26f`](38fd26f) Thanks [@crs48](https://github.com/crs48)! - docs(exploration): renumber Effect adoption doc 0300 -> 0303 (collision) Exploration numbers collided across parallel worktrees again (0301 gotcha): 0300 was already taken by RUNNING_AN_XNET_HUB_ON_A_RASPBERRY_PI ([#477](#477)) and 0301/0302 are claimed. Renames the doc and updates the exploration-number references in code comments and CLAUDE.md; no code change (empty changeset). Signed-off-by: xNet Test <test@xnet.dev> ## @xnetjs/data@1.0.0 ### Major Changes - [#482](#482) [`e6b4c6f`](e6b4c6f) Thanks [@crs48](https://github.com/crs48)! - Grinding-resistant Last-Write-Wins tiebreak (protocol v4, exploration 0305) The final LWW conflict tiebreak was the raw author DID ("higher DID wins"). Because a `did:key` is a free, attacker-chosen function of a keypair, an attacker could grind a vanity DID that sorts highest and win **every** concurrent-write tie against every honest peer, permanently. Protocol v4 replaces that final rung with a per-conflict key, `blake3(authorDID ‖ property ‖ value)` (`computeLwwTiebreakKey` in `@xnetjs/core`), so the winner of a tie is a random-oracle function of _what is written_ — a ground identity wins no durable, universal advantage. The key is gated on both changes being v4 (legacy changes fall back to the author DID), is derived at resolution time (never part of the change hash or wire format), and is threaded through `PropertyTimestamp`, the SQLite `node_properties` guard (new nullable `tiebreak_key` column, schema v8), and every conformance kernel. BREAKING: `CURRENT_PROTOCOL_VERSION` is now `4` and new changes are stamped v4. The LWW golden vectors gain `0005-tie-grinding-resistant-key`; `LwwStamp` / `PropertyTimestamp` gain an optional `tiebreakKey`. Mixed fleets converge on exact `{lamport, wallTime}` ties only once both peers are on v4 — a transient rollout window affecting rare exact ties. ### Minor Changes - [#488](#488) [`1de6587`](1de6587) Thanks [@crs48](https://github.com/crs48)! - Schema authorization gains `create` and `update` actions — optional refinements of `write` (exploration 0304). A schema may now split its mutation policy into who may **add** nodes vs. who may **modify** existing ones; when a refinement is absent it falls back to the schema's `write` expression, so existing schemas behave identically. - `@xnetjs/core`: `AUTH_ACTIONS` includes `create`/`update`; new `actionExpressionOrder()` and `grantActionSatisfies()` helpers (a `write` grant covers both refinements; granular grants cover only themselves). - `@xnetjs/data`: the policy evaluator resolves actions with the fallback and evaluates `create` against the draft node built from the payload (container relations resolve membership, so creation into a shared Space is genuinely gated); `NodeStore` checks the precise verbs, and remote creates are inferred and checked as `create` instead of failing closed on a not-yet-existing node. New `spaceContributorAuthorization()` cascade — adopted by `ChatMessage` and `Comment` — expresses "members may post, only the author (or space admins) may edit". `StoreAuthAPI.can` accepts an optional draft `node`. - `@xnetjs/react`: new `useCanCreate(schemaId, properties)` hook; `useCan`/`useCanEdit` check the precise `update` verb. - `@xnetjs/runtime`: conformance corpus gains the `authz-actions` suite pinning the fallback table. ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`3bc1b5f`](3bc1b5f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sync@1.0.0 - @xnetjs/sqlite@1.0.0 - @xnetjs/crypto@1.0.0 - @xnetjs/identity@1.0.0 - @xnetjs/storage@1.0.0 ## @xnetjs/sqlite@1.0.0 ### Major Changes - [#482](#482) [`e6b4c6f`](e6b4c6f) Thanks [@crs48](https://github.com/crs48)! - Grinding-resistant Last-Write-Wins tiebreak (protocol v4, exploration 0305) The final LWW conflict tiebreak was the raw author DID ("higher DID wins"). Because a `did:key` is a free, attacker-chosen function of a keypair, an attacker could grind a vanity DID that sorts highest and win **every** concurrent-write tie against every honest peer, permanently. Protocol v4 replaces that final rung with a per-conflict key, `blake3(authorDID ‖ property ‖ value)` (`computeLwwTiebreakKey` in `@xnetjs/core`), so the winner of a tie is a random-oracle function of _what is written_ — a ground identity wins no durable, universal advantage. The key is gated on both changes being v4 (legacy changes fall back to the author DID), is derived at resolution time (never part of the change hash or wire format), and is threaded through `PropertyTimestamp`, the SQLite `node_properties` guard (new nullable `tiebreak_key` column, schema v8), and every conformance kernel. BREAKING: `CURRENT_PROTOCOL_VERSION` is now `4` and new changes are stamped v4. The LWW golden vectors gain `0005-tie-grinding-resistant-key`; `LwwStamp` / `PropertyTimestamp` gain an optional `tiebreakKey`. Mixed fleets converge on exact `{lamport, wallTime}` ties only once both peers are on v4 — a transient rollout window affecting rare exact ties. ## @xnetjs/sync@1.0.0 ### Major Changes - [#482](#482) [`e6b4c6f`](e6b4c6f) Thanks [@crs48](https://github.com/crs48)! - Grinding-resistant Last-Write-Wins tiebreak (protocol v4, exploration 0305) The final LWW conflict tiebreak was the raw author DID ("higher DID wins"). Because a `did:key` is a free, attacker-chosen function of a keypair, an attacker could grind a vanity DID that sorts highest and win **every** concurrent-write tie against every honest peer, permanently. Protocol v4 replaces that final rung with a per-conflict key, `blake3(authorDID ‖ property ‖ value)` (`computeLwwTiebreakKey` in `@xnetjs/core`), so the winner of a tie is a random-oracle function of _what is written_ — a ground identity wins no durable, universal advantage. The key is gated on both changes being v4 (legacy changes fall back to the author DID), is derived at resolution time (never part of the change hash or wire format), and is threaded through `PropertyTimestamp`, the SQLite `node_properties` guard (new nullable `tiebreak_key` column, schema v8), and every conformance kernel. BREAKING: `CURRENT_PROTOCOL_VERSION` is now `4` and new changes are stamped v4. The LWW golden vectors gain `0005-tie-grinding-resistant-key`; `LwwStamp` / `PropertyTimestamp` gain an optional `tiebreakKey`. Mixed fleets converge on exact `{lamport, wallTime}` ties only once both peers are on v4 — a transient rollout window affecting rare exact ties. ### Minor Changes - [#487](#487) [`3bc1b5f`](3bc1b5f) Thanks [@crs48](https://github.com/crs48)! - Harden the sync-integrity primitives so look-alike helpers no longer give false assurance (exploration 0307): - `verifyIntegrity` now performs **real Ed25519 signature verification** against the key recovered from each change's author DID (previously it only checked that the signature field was non-empty). It accepts an optional `resolveKey` override; the default is self-certifying `did:key` resolution. - `attemptRepair`'s `recompute-hash` action — which overwrites a change's stored hash and can launder tampered payloads — is now gated behind an explicit `{ trustHashRecompute: true }` opt-in and refused by default. - `AuthorizedYjsSyncProvider.handleRemoteUpdate` now enforces the Yjs update size cap before applying, and `validateChain` / the handler registry / `quickIntegrityCheck` document that they are structural-only and do not authenticate authorship. ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/crypto@1.0.0 - @xnetjs/identity@1.0.0 ## @xnetjs/react@1.0.0 ### Minor Changes - [#494](#494) [`6acf14b`](6acf14b) Thanks [@crs48](https://github.com/crs48)! - New `usePresence<T>(awareness, initialState)` hook: typed, throttled (~30fps) ephemeral peer state over Yjs Awareness. Pairs with `useNode().awareness` for live cursors, positions, and "who's here" UI without writing the persisted change log. Peers are evicted on disconnect; unmount retracts only the fields the hook owns. - [#488](#488) [`1de6587`](1de6587) Thanks [@crs48](https://github.com/crs48)! - Schema authorization gains `create` and `update` actions — optional refinements of `write` (exploration 0304). A schema may now split its mutation policy into who may **add** nodes vs. who may **modify** existing ones; when a refinement is absent it falls back to the schema's `write` expression, so existing schemas behave identically. - `@xnetjs/core`: `AUTH_ACTIONS` includes `create`/`update`; new `actionExpressionOrder()` and `grantActionSatisfies()` helpers (a `write` grant covers both refinements; granular grants cover only themselves). - `@xnetjs/data`: the policy evaluator resolves actions with the fallback and evaluates `create` against the draft node built from the payload (container relations resolve membership, so creation into a shared Space is genuinely gated); `NodeStore` checks the precise verbs, and remote creates are inferred and checked as `create` instead of failing closed on a not-yet-existing node. New `spaceContributorAuthorization()` cascade — adopted by `ChatMessage` and `Comment` — expresses "members may post, only the author (or space admins) may edit". `StoreAuthAPI.can` accepts an optional draft `node`. - `@xnetjs/react`: new `useCanCreate(schemaId, properties)` hook; `useCan`/`useCanEdit` check the precise `update` verb. - `@xnetjs/runtime`: conformance corpus gains the `authz-actions` suite pinning the fallback table. ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`3bc1b5f`](3bc1b5f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sync@1.0.0 - @xnetjs/data@1.0.0 - @xnetjs/plugins@1.0.0 - @xnetjs/runtime@0.4.0 - @xnetjs/crypto@1.0.0 - @xnetjs/data-bridge@1.0.0 - @xnetjs/history@1.0.0 - @xnetjs/identity@1.0.0 ## @xnetjs/runtime@0.4.0 ### Minor Changes - [#488](#488) [`1de6587`](1de6587) Thanks [@crs48](https://github.com/crs48)! - Schema authorization gains `create` and `update` actions — optional refinements of `write` (exploration 0304). A schema may now split its mutation policy into who may **add** nodes vs. who may **modify** existing ones; when a refinement is absent it falls back to the schema's `write` expression, so existing schemas behave identically. - `@xnetjs/core`: `AUTH_ACTIONS` includes `create`/`update`; new `actionExpressionOrder()` and `grantActionSatisfies()` helpers (a `write` grant covers both refinements; granular grants cover only themselves). - `@xnetjs/data`: the policy evaluator resolves actions with the fallback and evaluates `create` against the draft node built from the payload (container relations resolve membership, so creation into a shared Space is genuinely gated); `NodeStore` checks the precise verbs, and remote creates are inferred and checked as `create` instead of failing closed on a not-yet-existing node. New `spaceContributorAuthorization()` cascade — adopted by `ChatMessage` and `Comment` — expresses "members may post, only the author (or space admins) may edit". `StoreAuthAPI.can` accepts an optional draft `node`. - `@xnetjs/react`: new `useCanCreate(schemaId, properties)` hook; `useCan`/`useCanEdit` check the precise `update` verb. - `@xnetjs/runtime`: conformance corpus gains the `authz-actions` suite pinning the fallback table. ### Patch Changes - [#483](#483) [`38fd26f`](38fd26f) Thanks [@crs48](https://github.com/crs48)! - docs(exploration): renumber Effect adoption doc 0300 -> 0303 (collision) Exploration numbers collided across parallel worktrees again (0301 gotcha): 0300 was already taken by RUNNING_AN_XNET_HUB_ON_A_RASPBERRY_PI ([#477](#477)) and 0301/0302 are claimed. Renames the doc and updates the exploration-number references in code comments and CLAUDE.md; no code change (empty changeset). Signed-off-by: xNet Test <test@xnet.dev> - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`3bc1b5f`](3bc1b5f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sync@1.0.0 - @xnetjs/data@1.0.0 - @xnetjs/plugins@1.0.0 - @xnetjs/crypto@1.0.0 - @xnetjs/data-bridge@1.0.0 - @xnetjs/history@1.0.0 - @xnetjs/identity@1.0.0 - @xnetjs/storage@1.0.0 ## @xnetjs/abuse@1.0.0 ### Patch Changes - Updated dependencies []: - @xnetjs/crypto@1.0.0 - @xnetjs/identity@1.0.0 ## @xnetjs/cli@0.1.6 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`3bc1b5f`](3bc1b5f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sync@1.0.0 - @xnetjs/data@1.0.0 - @xnetjs/sqlite@1.0.0 - @xnetjs/plugins@1.0.0 - @xnetjs/runtime@0.4.0 - @xnetjs/crypto@1.0.0 - @xnetjs/identity@1.0.0 ## @xnetjs/crypto@1.0.0 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 ## @xnetjs/data-bridge@1.0.0 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`3bc1b5f`](3bc1b5f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sync@1.0.0 - @xnetjs/data@1.0.0 - @xnetjs/sqlite@1.0.0 ## @xnetjs/history@1.0.0 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`3bc1b5f`](3bc1b5f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sync@1.0.0 - @xnetjs/data@1.0.0 ## @xnetjs/identity@1.0.0 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/crypto@1.0.0 ## @xnetjs/plugins@1.0.0 ### Patch Changes - [#483](#483) [`38fd26f`](38fd26f) Thanks [@crs48](https://github.com/crs48)! - docs(exploration): renumber Effect adoption doc 0300 -> 0303 (collision) Exploration numbers collided across parallel worktrees again (0301 gotcha): 0300 was already taken by RUNNING_AN_XNET_HUB_ON_A_RASPBERRY_PI ([#477](#477)) and 0301/0302 are claimed. Renames the doc and updates the exploration-number references in code comments and CLAUDE.md; no code change (empty changeset). Signed-off-by: xNet Test <test@xnet.dev> - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/data@1.0.0 - @xnetjs/abuse@1.0.0 ## @xnetjs/storage@1.0.0 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/core@1.0.0 - @xnetjs/sqlite@1.0.0 - @xnetjs/crypto@1.0.0 ## xnet-cloud@0.0.17 ### Patch Changes - Updated dependencies []: - @xnetjs/cloud@0.0.1 - @xnetjs/crypto@1.0.0 ## xnet-demos@0.1.1 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`6acf14b`](6acf14b), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/react@1.0.0 - @xnetjs/identity@1.0.0 ## @xnetjs/brain@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/vectors@0.0.1 ## @xnetjs/comms@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/crypto@1.0.0 ## @xnetjs/dashboard@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`6acf14b`](6acf14b), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/react@1.0.0 - @xnetjs/plugins@1.0.0 - @xnetjs/social@0.0.18 ## @xnetjs/labs@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/plugins@1.0.0 ## @xnetjs/licenses@0.0.18 ### Patch Changes - Updated dependencies []: - @xnetjs/crypto@1.0.0 ## @xnetjs/maps@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 ## @xnetjs/meetings@0.0.11 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`38fd26f`](38fd26f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/plugins@1.0.0 ## @xnetjs/server@0.0.17 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/crypto@1.0.0 - @xnetjs/data-bridge@1.0.0 - @xnetjs/identity@1.0.0 ## @xnetjs/social@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 - @xnetjs/crypto@1.0.0 ## @xnetjs/unreal@0.0.18 ### Patch Changes - Updated dependencies [[`e6b4c6f`](e6b4c6f), [`1de6587`](1de6587)]: - @xnetjs/data@1.0.0 ## xnet-desktop@1.0.0 Desktop shell release riding the @xnetjs/core 1.0.0 train. Desktop-specific changes are not tracked here; see the core packages' changelogs for what shipped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Exploration 0300: can a Raspberry Pi be a first-class home for a self-hosted xNet hub?
hub-release.ymlalready publishes multi-arch (linux/amd64,linux/arm64) images to ghcr, andlitestream-entrypoint.shis arch-aware. Blessed recipe: Pi 5 8GB + NVMe (~$150), Raspberry Pi OS 64-bit, existing compose file + Litestream to any S3-compatible bucket, Tailscale as default exposure.npx @xnetjs/hubpath is impossible (private: true, unpublished); the arm64 image is QEMU-built and never booted in CI; the disk watchdog is demo-mode-only while the CRDT log has no per-user quota (0291); the deployed web app's CSPconnect-srcblocks custom hub hosts (Electron unaffected).HUB_DISK_LIMIT,HUB_MAX_WARM_DOCS, arm64 CI boot smoke, guide section, CSP product decision).Docs-only — no code changes.
🤖 Generated with Claude Code