# 0.1.1 — Managed-install packaging fix

## Fix

The published `0.1.0` server plugin could fail to load with:

```text
Cannot find package '@jmfederico/pi-web'
imported from .../@compn3rd/pi-web-automations/dist/server-plugin.js
```

Pi-managed installs intentionally disable automatic peer installation. The running host's separate installation is not necessarily resolvable from the plugin directory. The original install validator allowed npm to install peers and missed this layout.

This patch bundles the public PI WEB capability helpers and their upstream parsers into the server entry, retaining the upstream MIT notice. Emitted JavaScript no longer imports either host peer at runtime. Native SQLite and Croner remain external runtime dependencies; host versions and exact capability requirements are unchanged.

Distribution checks now reject runtime host imports, including the previously allowed capability imports. The clean tarball-install validator uses `--legacy-peer-deps`, asserts that neither host peer is installed, and checks server/companion imports, exact capability requirements, and invalid-value rejection.

## Update

Update the package to `@compn3rd/pi-web-automations@0.1.1` through the target machine's **Settings → Pi packages**. Keep the companion extension trusted/enabled and the `automations` plugin enabled. Restart the target session daemon only when safe, then reload the browser. A daemon restart can interrupt active sessions and terminals; updating the package alone does not activate server changes.

No database migration, scheduler behavior change, or automatic daemon restart is included. This fix addresses the Automations plugin import failure, not a separate web-to-daemon connection failure. Requirements and operating limitations from [0.1.0](0.1.0.md) still apply.

## Validation

Local Windows / Node 24.19.0 verification passed typecheck, lint, all 90 tests, clean build, distribution validation, tarball allowlist validation, and a production-only managed-style tarball install without host peers. CI covers Windows and Linux on Node 22.19.0 and 24; consult the release commit's CI results for that matrix. These checks do not constitute a full live-provider scheduler smoke test.