ryu-warmup v0.1.2

Highlights

Remote access and permission levels

Core now mints a 256-bit node token on first boot, so it can start without an operator-provisioned credential, and surfaces that cannot read the token file authenticate through a device-code pairing flow. Operators can grant resources at specific permission levels, so browser.view and browser.control are distinct grants rather than a single blanket allowance.

The desktop app exposes Node Access, Node Permissions, and Resource Permissions settings, and the webapp, TUI, MCP, and Island targets resolve the new node-token and pairing clients. Mesh mode still demands an operator-provisioned RYU_TOKEN because peers share a token, while a minted token secures a non-loopback bind.

Affected packages: @ryu/warmup

Changelog

@ryu/warmup@0.1.2

Minor changes

• Updated the warmup app's manifest to carry the new permission-level declarations. (540a585)

Patch changes

• Added manifest-declared data categories to the warmup manifest. (dac1ee6)

Full changelog: v0.1.1...v0.1.2