MeatGrinderCurrent status
Wurster 0.33.2 is pre-1.0 but intended for real integration work. Presence of code is not the same as a stable contract; this page is the short maturity map.
| Area | 0.33.2 status | Current boundary |
|---|---|---|
| Windows Desktop | release lane | shared Electron runtime |
| macOS arm64/x64 | release lane | signed/notarized workflow |
| Wurster Web | release lane | browser runtime and <wurst-embed> |
| Linux Desktop | development lane | build path exists |
| Desktop auto-update | release lane | default-on GitHub Release checks on packaged macOS/Windows; user opt-out in Settings |
| iOS / Android | reserved | no conforming release yet |
| PigFS | functional / pre-stable | files, directories, stable IDs, transactions, snapshots, quotas, symlinks, watches, realms, encryption and compaction |
| PigLink | functional / pre-stable | typed Actions/Events across UI, Desktop, Web and headless paths |
| Piglet | functional / pre-stable | stable Wurst Object IDs, object-backed mutable Child state, deterministic Desktop virtual routes, universal Views and shared machine/View sessions |
| Pigsty | experimental / coming soon | contracts/adapters exist; native Edge/WASIX runtime is not a normal release dependency |
Desktop updates
Packaged Wurster Desktop builds on macOS and Windows check the public WRST-IO/Wurster-Lab GitHub Releases channel at startup by default. When a newer stable release is available, Wurster shows its own update view, downloads the platform update, then hands installation to the Electron updater.
Automatic updates are a local Wurster setting and can be disabled under Settings → Updates to intentionally remain on an older runtime. Development/unpackaged runs never auto-update, and a failed update check falls back to normal startup instead of blocking Wurster.
Important 0.33.2 limits
- Desktop serves
wurst://runtime/__wurster/<session>/...directly from its active Piglet session/source layer. Desktop Child rendering does not depend on Service Worker controller takeover; browser Wurster keeps the Service Worker route. - Persistent mutable Children use the Root Wurst Object Store: immutable signed Base bytes remain independent from mutable object state, Child writes publish through Root Commits, and ancestor Wursts are not reserialized for a deep Child state change.
- Parent PigFS file identity (
storageObjectId), Wurst Object ID, Application ID, package digest and Session ID are separate identities. Renaming a PigFS-held Child does not create a second Wurst Object instance. - Multiple Views and in-runtime machine clients of the same Child share one durable Wurst session and revision-safe PigFS state.
- A browserless Parent Wurst can use Child Wursts as PigLink subtools without a DOM.
- A separately launched CLI/MCP process cannot yet attach to a Desktop/Web session already owned by another Wurster process. That external machine broker is still open work.
- The generic CLI Child-subtool path does not yet have full writable nested-Child PigFS and Parent-service parity with Desktop/Web.
- Pigsty's development worker is not the final hostile-code production sandbox.
Pre-1.0 contracts may still change cleanly. Discarded designs are removed rather than preserved through compatibility shims.