Repository navigation
Releases
ElastOS 2.0.1
ElastOS 2.0.1 makes Browser ask before it goes online, brings Browser to the Jetson and other Linux ARM computers, and fixes updates, Undo and staying connected.
Install
curl -fsSL https://elastos.elacitylabs.com/install.sh | bash
Runs on Apple Silicon Macs and on Linux (x86-64 and ARM64, including NVIDIA Jetson). When the installer says "ElastOS 2.0.1 is ready", run the Open Home command it prints, then create your passkey.
What's new
These are the same notes System shows when the update is ready.
Added
- Browser runs on a Jetson and other Linux ARM computers with KVM. Turn it on once with elastos setup --browser, which asks before its one-time administrator step, then restart Home.
- System, About lets you choose Stable or Test versions for updates. Your passkey confirms the change, and switching never installs an older version.
Changed
- On a Jetson, Browser uses more of the processor, so scrolling is about twice as smooth.
- On Linux, the install command no longer sets up Browser or downloads it. Browser is turned on when you choose it.
- Known issue: on a Jetson, Browser scrolls much more slowly than a browser running directly on the computer (#90).
Fixed
- Open apps, including Chat, stay connected while Home runs, and reconnect by themselves after a network drop or a restart.
- Assistant keeps a finished answer in view, also while you type a longer question.
- Assistant follows a growing answer only while you are at the end, and Jump to latest no longer flashes while an answer streams.
- A busy Home no longer tells people that their shared model access is inactive.
- When a Browser session has expired, Browser says so instead of showing a connection message.
- The install command repairs file permissions in an older Linux or Jetson Home that you own, and shows one command for files owned by the administrator.
- The install command works whatever language the computer is set to.
- Closing Browser no longer fails when another program uses a port Browser's media relay may need.
- When an update check gets no answer, Home tries once more on a new connection.
- When a Linux computer is short of free space, Browser says how much it needs to open.
- Updating, or using Undo, on a computer where Browser is set up no longer stops with "installed release support changed". Browser's Python no longer changes ElastOS's own files.
Security
- Browser opens websites only after you allow internet access with your passkey in Inbox, where you can also turn it off.
- Known issue: Home itself shows the approval, not a separate ElastOS screen, so read the request before you confirm with your passkey (#178).
- Known issue: after Undo to 2.0.0, Browser goes online again without asking (#559).
- Community room access ends when your sign-in ends.
Updating
- From 2.0.0: update in System, About. Your data stays. The first time you open a website afterwards, Browser asks in Inbox; allow it with your passkey.
- From a test version (2.0.1-rc.1 or rc.2): update in System, About. To get only Stable versions from now on, choose Stable there; switching never installs an older version.
- If you ran the install command between 9 and 11 November, you got a test version: check System, About and choose Stable if you want only Stable versions.
- A Home that stopped with "installed release support changed" on 2.0.1-rc.1 needs a manual repair first. Ask in #535.
- From anything older than 2.0.0: follow Updating on the 2.0.0 page.
- On a Jetson or another Linux ARM computer with KVM, Browser stays off until you run
elastos setup --browseronce. It asks before its one-time administrator step and downloads about 900 MB. Then restart Home. Browser is not available on Linux x86-64. - Undo runs in a terminal, returns to the version you had before and leaves Home stopped (#509). After Undo to 2.0.0, Browser goes online again without asking (#559).
Known issues
Found after the in-app notes were final, so System does not show them:
-
Direct messages between two Homes on different home networks stay at Sending: Homes connect to each other directly, and the shared meeting point that lets two Homes behind routers reach each other is not in this release (#345). Restarting does not help. Posts in Community reach everyone; they pass through the main Community node, which can read them.
-
Browser on a Jetson was not tried on this final build. It worked, slowly, on an earlier 2.0.1 test build (#90).
-
Browser's permission has rough edges, each with a simple way out (#566):
- after Don't Allow or Turn Off, an address you typed is not opened when you then allow access: press Return on it again;
- if Home stops answering for a moment while Browser waits for your answer, that Browser window stops noticing your answer: close it and open Browser again;
- a Browser window in full screen is not brought back after you allow access: click Browser in the Dock;
- a request left unanswered for 30 minutes leaves nothing to allow in Inbox: press Return in Browser again.
Fixes are planned for 2.0.2.
-
A component Home uses to look up internet addresses has published flaws (RUSTSEC-2026-0487 to 0491). The one that applies to Home lets a tampered address reply make Home use too much memory. It cannot read your data. 2.0.0 has the same component. A fix is planned for 2.0.2 (#569).
Still open from 2.0.0:
- While a Test version is out, a Stable Home says "Could not check for updates" (#564).
- On a Mac that uses local AI on 2.0.0-rc.1 or an earlier test version, updating fails and keeps your version. The workaround is in #515.
- After
elastos updateor Undo in a terminal, Home stays stopped. Start it withelastos home --browser(#509). - AI models cannot read files, open websites or send messages. The small SmolLM2 135M model often pretends it did (#455).
- Library can lose a save if a file is saved from two places at once, or renamed, moved or deleted meanwhile (#480).
- Unsaved Documents edits are lost when sign-in ends after 12 hours without Home running (#497). Importing a Recovery Kit does not ask for your passkey (#403).
- Browser has no Chinese, Japanese or Korean fonts.
- Not done yet: Home can still use every app's permissions, and background services run with your account's rights (#173).
The developer detail is in the changelog.
Check what you install
The installer checks the release signature and each file's checksum. To check by hand:
- Signer:
did:key:z6MkgwHd2BCWe1jHMXPiR6H1q1RFPcv1YzhMbK5G1kBarbfe - Signed release:
QmNkZQSd8t7EJbdtN23h9XXxy45o5NNQcoLt7ivxPn4Xtg, named inrelease-head.json(attached, and served at https://elastos.elacitylabs.com/release-head.json) - Source: tag
v2.0.1, commitbde18c7bae6564db934cd406c1070b32499473ec - Build: package run 42969056808
SHA256SUMSlists all 156 signed files. The attachedinstall.shand Runtime binaries (elastos-aarch64-darwin,elastos-aarch64-linux,elastos-x86_64-linux) are the same bytes the installer downloads. To install, use the command above.- Each
build-receipt-<platform>.jsonlists every file built for that platform with its sha256, and GitHub's attestation shows the release workflow made it from the tagged commit:
gh attestation verify build-receipt-aarch64-darwin.json \
--bundle build-receipt-aarch64-darwin.sigstore.jsonl \
--repo elastos/elastos-runtime
Report problems in issues.
Full changelog: v2.0.0...v2.0.1
ElastOS 2.0.0
ElastOS 2.0.0 is the first stable release of Home: a desktop in your browser that runs on your own computer, with your people and your AI.
Install
curl -fsSL https://elastos.elacitylabs.com/install.sh | bash
Runs on Apple Silicon Macs and on Linux (x86-64 and ARM64, including NVIDIA Jetson). When the installer says "ElastOS 2.0.0 is ready", run the Open Home command it prints, then create your passkey.
What you get
- Your Home joins the shared Community. Add someone by their DID from People, a Chat profile card or a message, and share a file of up to 8 MiB with your contacts from Library. To stay out of Community, run
elastos setup --isolatedbefore Home first starts, or an admin leaves in System > Security. - Assistant chats with an AI model that runs on your own computer. On a Mac, admins can also add a Venice or OpenRouter key in System > Models; nothing is sent until you approve it in Inbox.
- Browser on Apple Silicon Macs opens web pages in a separate sandbox, fits any window size and runs Chromium 155. It is a download of about 900 MB.
- You can add a second passkey, such as another device or a security key, in System > Accounts. When sign-in fails, the lock screen says why.
- A link in Chat or Documents opens only after you see its address and choose Open.
- Small screens get a touch layout with a Dock. A phone still needs an HTTPS address for Home, which 2.0.0 does not set up.
- Releases are signed with a new key kept off the public server. Updating in System keeps your data.
Updating
- From a test version (0.8.0-alpha.24 or later): update in System, except on a Mac that uses local AI on 2.0.0-rc.1 or older (see Known issues). Your Home stays on the test channel; run the install command to move to stable.
- From 0.7.1 or earlier, or a test version older than 0.8.0-alpha.24: run the install command once and do not use Undo. Your Home keeps its data.
Known issues
- On a Mac that uses local AI on 2.0.0-rc.1 or an earlier test version, the update fails and keeps your version. The workaround is in #515; a fix is planned for 2.0.1.
- On Linux or a Jetson with an older install, the installer can refuse with "installation file is unsafe" or "Operation not permitted". The workaround is in #516; a fix is planned for 2.0.1.
- After
elastos updateor Undo in a terminal, Home stays stopped. Start it withelastos home --browser(#509). - On a computer whose time format is not English, the install command can refuse while Home is running ("does not match format"). Stop Home first, or run
curl -fsSL https://elastos.elacitylabs.com/install.sh | LC_ALL=C bash(#517). - AI models cannot read files, open websites or send messages. The small SmolLM2 135M model often pretends it did (#455).
- Browser runs only on Apple Silicon Macs and has no Chinese, Japanese or Korean fonts.
- On a Jetson, getting the Qwen model takes about 43 minutes and its first reply about 22 seconds.
- Library can lose a save if a file is saved from two places at once, or renamed, moved or deleted meanwhile (#480).
- Unsaved Documents edits are lost when sign-in ends after 12 hours without Home running, such as while the computer sleeps (#497).
- Posts between networks pass through the main Community node, which can read them until a relay arrives in a later release. Direct messages need a direct connection, which some networks block; if one stays at Sending, restart either Home (#451).
- Not done yet: Home can still use every app's permissions, background services run with your account's rights, and approvals do not have a screen only ElastOS controls (#173). Importing a Recovery Kit does not yet ask for your passkey again (#403).
The full release notes, including what 2.0.0 hides and the developer detail, are in the changelog.
Check what you install
The installer checks the release signature and each file's checksum. To check by hand:
- Signer:
did:key:z6MkgwHd2BCWe1jHMXPiR6H1q1RFPcv1YzhMbK5G1kBarbfe - Signed release:
QmfKYcyaECzckWSHHXbWTdQHc4FNRQXjz2vh3YQ4RCQon8, named inrelease-head.json(attached, and served at https://elastos.elacitylabs.com/release-head.json) - Source: tag
v2.0.0, commit7bc3704b5e181e5aa435c2b2cafbd73a996932ef - Build: package run 41375420248
SHA256SUMSlists all 155 signed files. The attachedinstall.shand Runtime binaries (elastos-aarch64-darwin,elastos-aarch64-linux,elastos-x86_64-linux) are the same bytes the installer downloads. To install, use the command above.- Each
build-receipt-<platform>.jsonlists every file built for that platform with its sha256, and GitHub's attestation shows the release workflow made it from the tagged commit:
gh attestation verify build-receipt-aarch64-darwin.json \
--bundle build-receipt-aarch64-darwin.sigstore.jsonl \
--repo Elacity/elastos-runtime
The build ran before this repository moved from Elacity/elastos-runtime, so its attestation names the old name.
Report problems in issues.
Full changelog: v0.7.1...v2.0.0
ElastOS Runtime v0.7.1
Monthly developer release of the 0.7.1 work line. It is a source snapshot for
developers and testers, not a release for users. The workspace version moves
to 0.7.1; capsule manifest versions do not change. The GitHub binaries are
unsigned source builds and report 0.7.1-dev. The signed installer and the
update channel do not change. An earlier signed preview build also reports
0.7.1; it is older code, and the next signed release replaces it. The first
release for users is planned as 0.8.0, and issues #83 to #93 track what it
still needs.
Added
- Local models: signed model catalogue metadata, verified model content that
is prepared, admitted, kept and retired through Marketplace and System
controls, and a bounded local llama engine with recovery. Local chat is
bound to the engine's context limit and keeps the negotiated chat roles. - Remote and hosted models: granted remote model offers and runs travel over
Carrier and are authorised on the owning Runtime. Hosted runs support
Responses with honest cancellation, keep repeatable connections and their
secrets on this Home, and show the offer and selection facts in Assistant. - Home: first run seeds an empty desktop and pins Marketplace; new lock face;
storefront and one Home entry; the recovery kit comes before passkey setup;
apps declare their own window policy; the Home Agent runs as its own capsule
on the typed model contract. - Browser: remote Engine sessions go through Runtime authority; the local
Engine image dependencies are verified; scoped operator inspection and
reference fill need approval. - Services shows the AI model service beside Engine and Exit.
- Protected content: installed custody and chain prerequisites can be
provisioned. The protected-content path stays inactive.
Fixed
- Update tests observe isolated CLI and operator update hops accurately
(#74, #79). - The x264 build fetch is pinned to its commit and tree (#119).
- Browser, model, setup, Services and Assistant fixes; see the commit log
since v0.7.0.
Known limits
- A hosted model route set up explicitly by an operator on a Mac can skip
Inbox (#85). - Signed updates have open defects (#107). A later update may need a
reinstall. - Chat sign-up is hard to find (#86).
- The Jetson Runtime install and its visible Assistant reply are not proven
yet (#90, #97).
Full changelog: v0.7.0...v0.7.1
ElastOS Runtime v0.7.0
ElastOS 0.7 - Protected Content Ecosystem & Collaboration Platform
Overview
ElastOS 0.7 introduces a complete Web3-native ecosystem for digital content management, rights management, and secure collaboration. This release enables creators to mint, trade, and monetize digital assets with cryptographic proof of ownership.
Core Features by Component
📦 Protected Content & Digital Rights
- Content Identity & Ownership: Canonical content identities, rights grants, and release contracts (PR #29)
- Cryptographic Rights Management: Chain-based rights evidence with typed decision support (PR #35)
- Release Authority & Lifecycle: Runtime release authority with persisted state management (PR #34)
- Custody & Key Security: Threshold custody envelopes with key reconstruction for secure asset storage (PR #30)
- Bridge Authentication: Bridge-authenticated release reconstruction for verifiable content access (PR #31)
💰 Transaction & Monetization Lifecycle
- Complete Purchase Flow: Runtime lifecycle covering mint, buy, play, and purchase closeout (PR #36)
- Wallet Integration: Cryptographic signing of rights requests with Wallet support (PR #33)
🤝 Secure Collaboration
- Network Protocol: Signed network protocol with Carrier transport for peer-to-peer communication (PR #27)
- Identity & Authority: Profile authority system for authenticating collaborators (PR #27)
- UI & Social Features: Profile/Chat product UI and Home window chrome for seamless interaction (PR #28)
🔐 Security Foundation
- Distributed Key Management: dKMS/dDRM foundation on ESP substrate with key reconstruction capabilities (PR #15)
- Custody Protocols: Custody provider protocol and process with integrated workflows (PR #32)
🏠 User Interface & Experience
- Full UI/UX Reconstruction: Complete redesign with improved usability and navigation (PR #39)
- Archive Manager Integration: Simplified content organization and management (PR #39)
- Assistant Workspace: AI-powered workspace for content management and collaboration (PR #39)
- Home Menu Protocol: Modern navigation and windowing system (PR #39)
🛠️ Infrastructure & Content
- AI Model Integration: Model provider with OpenAI compatibility and H3 Video adapters (PR #17)
- Logging Infrastructure: Elastos-logger crate for system monitoring and debugging (PR #25)
- Content Capsules: GBA nonogram content demonstration (PR #26)
- Streaming Support: MPEG-DASH compliance for video content delivery (PRs #11, #12)
🔧 Runtime & Platform
- Mandate Engine: Flint mandate engine for delegated permissions without key exposure (PR #13)
- Browser Integration: Browser lifecycle management and process handling (PR #24)
- CI/CD Pipeline: Updated build pipeline for source-gate and source-home on modern platforms (PR #19)
📚 Documentation & Setup
- Implementation Guides: Mint→sell→buy→play journey implementation plan (PR #22)
- Developer Environment: Cursor Cloud environment setup notes (PR #21)
- System Architecture: Architecture documentation (PR #18)
Integration & Consolidation
- Core Consolidation: Unified flint-0.5 branch with marketplace, streaming, and restoration features (PR #12)
- Collaboration Foundation: Integrated collaboration implementation (PR #16)
- Bug Fixes & Stability: Protected content completion mark recovery (PR #43)
Summary
This milestone delivers a production-ready ecosystem combining cryptographic content rights, secure peer-to-peer collaboration, and a complete monetization framework—enabling trustless Web3-native digital commerce.
ElastOS Runtime v0.4.0
Added
- Added the provider-backed Library release slice with desktop-style navigation, upload/download, preview/open, publish/share/status/repair, Trash, Archive handoff, Spaces, context menus, object events, and Runtime-scoped provider authority.
- Added
object-provideras the mutable principal-root object provider for Library objects, Desktop/Documents/Public roots, protected-root object envelopes, object events, and WebSpace resolver routing. - Added Runtime provider-to-provider invocation foundations, typed transfer receipts, stream sessions, and Carrier-backed provider invocation for content availability, repair, and exact-CID byte fallback.
- Added WebSpace federation foundations with
localhost://WebSpaces/*as the local mounted resolver view and provider targets kept resolver-private. - Added the Archive capsule, Marketplace capsule, capsule catalog routes, typed affordance descriptors, and interface invocation surfaces so first-party apps are packaged as launchable Runtime capsules.
- Added content availability, quota, repair, operator dashboard, storage-market posture, admission preflight, block-graph repair, and federation policy metadata surfaces for operator inspection.
Changed
- Standardized first-party browser-facing apps as WASM capsule packages with bundled browser surfaces materialized by Home before launch.
- Reworked Home desktop projection so Home displays provider-backed objects while mutation authority stays inside Library/object-provider.
- Moved Library, Archive, Marketplace, Spaces, Trash, and published/shared content flows toward object/provider contracts rather than app-visible host paths or raw infrastructure details.
- Updated runtime docs, namespace docs, capsule model docs, changelog, and release scripts around the 0.4 capsule/object/provider direction.
Notes
v0.4.0is the Library, Marketplace, Archive, Spaces, Trash, and capsule-packaging release. It moves the runtime closer to plug-and-play capsules, provider-owned object authority, and SmartWeb/WebSpace-oriented file handling.- Typed affordances/interface descriptors are included as the first concrete interface layer. The broader COMO/interface-registry direction remains the next hardening layer above this foundation.
- Local release checks passed on commit
cae83c3: Home entropy, Browser entropy, WCI alignment, formatter check, andcargo test --manifest-path elastos/Cargo.toml -p elastos-common -p elastos-runtime -p elastos-server.
ElastOS Runtime v0.3.0
Added
- Added Browser as a first-class ElastOS app, routed through Runtime Browser, Net, Exit, Browser Engine, Wallet, and Inbox provider contracts instead of raw host browser authority.
- Added the Wallet app as the main blockchain authority surface with built-in managed accounts, receive/send flows, account recovery, transaction activity, MetaMask connector support, UniSat/Bitcoin groundwork, and Wallet-owned approval methods.
- Added passkey-first Home authentication with principal-scoped user roots, admin/guest policy, account recovery/reassignment, full Recovery Kit export/import, and protected root metadata.
- Added Inbox-backed wallet approval flows so browser and capsule-originated signing and transaction requests are reviewed through Runtime-owned approval paths.
- Added typed Chain Provider support for proof, transaction prepare, broadcast, sync health, and node lifecycle operations without exposing raw chain RPC to apps.
- Added Availability, Rights, Key, DRM, and Decrypt provider contracts as the protected-content and dDRM foundation, including sealed-object direction and PQ-hybrid algorithm metadata.
- Added Net and Exit provider foundations for Browser networking policy, exit routing, and fail-closed external network access.
- Added PC2 convergence documentation covering wallet bridge, IPFS/content availability, dDRM, provider mappings, and SmartWeb alignment.
Changed
- Reframed Home, System, Inbox, Wallet, Browser, and Chat Room as first-party capsules operating behind Runtime authority boundaries.
- Split large gateway surfaces into focused gateway modules for Home/System, Wallet, Browser, Inbox, Room, Site, provider proxy, models, and tests.
- Moved wallet, chain, browser, pricing, content, and protected-content operations toward typed provider calls and
elastos://contracts instead of app-visible raw APIs. - Updated System to focus on runtime/account policy and Webspace/provider visibility while Wallet owns wallet accounts, methods, requests, and transaction flows.
- Reworked Home realtime behavior toward scoped Runtime events and reduced fixed-interval polling that slowed the desktop when multiple apps were open.
- Updated README, ROADMAP, TASKS, architecture docs, glossary, provider docs, changelog, and state docs to reflect the 0.3 Runtime model.
- Expanded release verification with Home entropy, Browser entropy, WCI alignment, auth/wallet focus smoke, wallet product safety smoke, browser/provider smoke, and protected-content smoke checks.
Fixed
- Fixed passkey and Recovery Kit flows so protected roots and built-in Wallet keys can be recovered under a new passkey when appropriate, while external wallet private keys remain outside ElastOS custody.
- Fixed guest/admin policy issues, including scoped account roots, safer passkey management, and clearer promotion/demotion behavior.
- Fixed wallet account creation, recovery import/export, built-in send signing, transaction activity, default wallet selection, and browser wallet defaults.
- Fixed browser wallet compatibility paths for external sites by routing account discovery, chain reads, signing, and transaction approvals through Runtime Wallet/Inbox/Chain providers.
- Fixed Browser session handling to support scoped page/session state, independent page capacity accounting, runtime-scoped input/WebRTC signaling, and fail-closed engine/exit behavior.
- Fixed unsafe or stale authority patterns: hidden request fields are rejected, raw runtime control APIs are blocked, raw RPC/private-key exposure is avoided, and WalletConnect stays hidden/fail-closed until pinned operator configuration exists.
- Fixed CI clippy warnings in Home realtime tests after the 0.3 merge.
Notes
v0.3.0is the first integrated SmartWeb runtime release: passkey Home, built-in Wallet, Browser, Inbox approvals, typed providers, Carrier-shaped capability boundaries, and protected-content foundations are now part of one coherent runtime direction.- Browser is now a real first-party app and provider-mediated browsing path, but the product browser engine strategy remains an active area. Hosted Browser/Selkies is accepted as the current proof path, not the final browser architecture.
- CI is green on the release commit
8acb72d.
ElastOS Runtime v0.2.0
Added
- Added the Home browser shell capsule,
home-cli, and theelastos homecommand path as the visible front door. - Added first-party System, Inbox, Library, Documents, Chat Room, GBA Emulator, and uCity browser/content capsules to the shipped Home catalog.
- Added runtime-owned browser capsule routing, object/viewer launch foundations, and app-scoped launch tokens for Home-launched surfaces.
- Added Documents provider APIs for summary, create, get, save, save-as, publish, unpublish, delete, and immutable
elastos://<cid>document opens. - Added Library document browsing and Chat Room attachment flow through Home orchestration instead of browser file upload.
- Added Chat Room browser-session pairing, same-browser Home session reuse, guest identity separation, guest kick controls, and runtime member invite/block controls.
- Added System appearance controls for wallpaper, reset, overlay toggle, and overlay opacity.
- Added Home PWA metadata, mobile fullscreen support, touch-first desktop icon behavior, reversible desktop icons, and mobile-safe window behavior.
- Added GBA save-state persistence, mobile touch controls, keyboard mapping labels, fullscreen ratio handling, compact controls, and fail-fast unsupported-WebView detection.
- Added shared first-party design-system docs and
scripts/home-entropy-check.mjsfor UI, naming, authority, and stale-copy drift checks.
Changed
- Renamed the visible product front door from PC2 to Home and aligned setup profiles, proof scripts, docs, and CLI smoke tests around the Home naming.
- Replaced
md-viewerwith Documents androom-browserwith Chat Room. - Split setup profiles more explicitly between the core Home path, the broader demo surface, and the explicit operator lane.
- Hardened release proofing around clean-home setup, the PTY Home front door,
chat-roompackaging, source-local trusted-source checks, and Home/browser journey smoke coverage. - Moved Home wallpaper and contrast overlay configuration into
System -> Appearancebacked by the runtime appearance store. - Made Documents object-first: DID-backed document identity is the mutable object,
localhost://Users/self/Documents/...is only the local working copy, andelastos://<cid>is the immutable published revision. - Made Library content-first around documents and typed content instead of raw working-copy paths.
- Moved Inbox list rendering, read state, approval, denial, dismissal, and source-app open actions into the Inbox capsule; Home now owns only badge and launch.
- Aligned first-party capsule UI colors, spacing, mobile padding, and accessible controls with the shared light capsule token set.
- Aligned roadmap, principles, architecture, namespaces, and security docs around the four quadrants, object/capsule/space ontology, and capability-scoped Carrier/provider boundary.
Fixed
- Unified main DID derivation with the device key and aligned local nickname persistence onto one shared codec.
- Removed stale live-host conflicts so managed Home/chat lanes and the explicit operator lane do not silently share one home.
- Cleaned up the public room naming so the shipped
chat-roomroute, packaging, and proof tooling all agree. - Moved Documents publish/unpublish IPFS-specific logic out of the gateway edge into the provider plane.
- Removed the gateway-owned IPFS provider bridge path; public CID reads now use cached content or the runtime provider registry and fail closed otherwise.
- Required Home authority before minting app launch tokens, app-scoped launch tokens for System and Inbox APIs, and browser-context-bound chat-room access polling.
- Redacted room bearer tokens from public/Home summaries and preferred the native Home room session over paired browser identity when both exist in one browser profile.
- Fixed browser Chat Room identity handling so messages from the native Home member no longer appear as the browser guest's own messages.
- Fixed Documents publish/unpublish behavior so unchanged content does not produce unnecessary new published revisions.
- Fixed document delete confirmation to use in-surface UI instead of browser alerts.
- Fixed Home window dragging so windows can move partially offscreen without jumping back when their title bar is clicked.
- Fixed desktop drag selection, desktop icon removal/re-add, mobile launcher focus, and maximized-window coverage over Home chrome.