[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.1.0-alpha.4":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.1.0-alpha.4","L4 0.1.0-alpha.4","L4 now deploys autonomous Servers. Each Server owns its accounts, login, client, community data and independent storage. The optional web\u002FPWA\u002FTelegram Shell connects directly to these Servers.","2026-10-18","\u002Fchangelog\u002Fv0.1.0-alpha.4","\u002Fchangelog\u002Fv0.1.0-alpha.4.md",true,"\u003Cp>L4 now deploys autonomous Servers. Each Server owns its accounts, login, client, community data and independent storage. The optional web\u002FPWA\u002FTelegram Shell connects directly to these Servers.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Removed the Instance runtime, pairing, identity assertions and proxy tier. One Server needs one application Worker; there is no master Server or shared account requirement.\u003C\u002Fli>\n\u003Cli>A persistent UUIDv4 identifies each Server before owner setup and serves as its internal workspace ID, public routing identity and realtime\u002Fstorage namespace. There is no \u003Ccode>main\u003C\u002Fcode> workspace identity.\u003C\u002Fli>\n\u003Cli>Added local discovery, permitted embedding, direct invitation links, local account recovery keys and a one-use S256 login handoff with signed sessions for browsers restricting embedded cookies.\u003C\u002Fli>\n\u003Cli>Held WebSocket connections retain their local session identity and recheck it before writes and private fanout. Logout and account recovery revoke held-socket access; another valid session of the same user remains usable.\u003C\u002Fli>\n\u003Cli>The Shell keeps a flat list of saved Server connections, independent sessions and deep links. Saved connections and matching emails never grant community membership; DMs remain inside their Server.\u003C\u002Fli>\n\u003Cli>Cloudflare installation configures Git-connected Workers Builds and pins a published immutable Server release. The Cloudflare account needs the repository integration, an eligible deployment token and Builds administrative permissions. The Server runtime does not retain installer provisioning credentials.\u003C\u002Fli>\n\u003Cli>Release bundle schema 2 contains Server, Shell\u002Fsite, client assets and Docs. The retired Instance baseline and all previously published release artifacts remain unchanged.\u003C\u002Fli>\n\u003Cli>Standalone Compose runs one Server. Live files and backups use separate storage destinations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The alpha.3 candidate was never published: its release workflow was cancelled before creating a tag or assets after the held-socket defect was reproduced. Alpha.4 includes the correction.\u003C\u002Fp>\n\u003Cp>This transition installs fresh standalone databases. There are no running Instances to migrate; the appended migration rejects an existing Instance-bound workspace. Archived prototype databases have no upgrade path.\u003C\u002Fp>\n\u003Cp>Validation includes 515 unit tests, type and lint checks, immutable migration validation, a two-Server runtime fixture, Chromium Shell navigation and popup login, and isolated Cloudflare Workers Builds Preview verification. Cloudflare is the primary acceptance target. Physical-device testing and native iOS\u002FmacOS packaging remain deferred; mail, inference and RealtimeKit require independent provider configuration and acceptance.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.1.0-alpha.5","\u002Fchangelog\u002Fv0.1.0-alpha.5",{"title":16,"url":17},"L4 0.1.0-alpha.2","\u002Fchangelog\u002Fv0.1.0-alpha.2",1793335827542]