ryu-monitors 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/monitors

App-declared quotas and MCP bridge

Tier quotas are no longer a fixed table in core auth: kernel-level quotas stay in code, while app quotas such as maxMonitors and meetingRetentionDays are declared in the owning app's manifest. Every existing limit value round-trips unchanged, and PlanLimitField is now derived from the quota registries.

Developer Mode can arm a loopback MCP bridge so an agent can drive a stable release build. Arming is single-shot, the bridge state is reconciled app-wide rather than from the settings tab, and the bridge section appears whenever the socket is live, noting that it accepts uncredentialed local connections.

Affected packages: @ryu/monitors

Changelog

@ryu/monitors@0.1.2

Minor changes

• Added the permission-level declarations to the monitors app's manifest. (540a585)
• Declared the monitors app's quota fields in its manifest instead of in core auth plan code. (e14e158)

Patch changes

• Updated the monitors manifest to declare its data categories. (dac1ee6)

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