# 0.1.0 — Initial npm release

## Features

- Durable, machine-local automation definitions, schedules, revisions, and SQLite run/attempt history.
- Manual runs, one-time schedules, intervals, and six-field cron schedules with explicit IANA time zones.
- Paired PI WEB browser/server plugin and bundled Pi companion extension using upstream's public cooperative session APIs.
- Disabled drafts and successful-test requirements before enabling a schedule; revision checks protect concurrent edits.
- Machine-default or explicit provider/model policies, with validation and no silent fallback.
- Visible, user-owned sessions with links from definition cards, run rows, and timeline blocks.
- Continuous top-to-bottom run timeline with one column per automation, stable colors, and side-by-side overlapping runs.
- Estimated total and average costs across all retained runs, with usage coverage counts and explicit partial-accounting labels.
- Archival deletion of inactive definitions, including those with historical unknown outcomes, while retaining run/attempt history and session IDs.

## Requirements and installation

- Node.js 22.19 or newer.
- Compatible PI WEB: npm peer range `^1.202609.1`, public browser API v4 and server API v3. PI WEB 1.202609.0 is incompatible.
- Compatible Pi coding agent; the companion was developed against `@earendil-works/pi-coding-agent@^0.87.1`.

Install `@compn3rd/pi-web-automations@0.1.0` through the target machine's **Settings → Pi packages**. Trust/enable the bundled Pi extension and enable the `automations` PI WEB plugin. A plugin-only symlink is not enough. Restart the target session daemon only when safe, reload the browser, then manually test a disabled draft before enabling its schedule.

## Operating limitations

- Sessions belong to the user, not an exclusive background runtime. Cancellation is cooperative and cannot undo completed effects or guarantee forced termination.
- Unconfirmed execution becomes `unknown`, pauses the definition, and blocks new execution even after edits or restarts. Inspect Sessions before creating a replacement; deleting a definition does not stop uncertain work.
- Usage and cost figures are partial assistant-message estimates, not complete billing totals. The timeline displays the latest 200 workspace runs; cost summaries cover all retained runs.
- Each machine owns its installation, credentials, schedules, and state. No automatic migration, failover, or copying of definitions is provided.
- Plugins and prompts execute with the target machine account's permissions. Review sources and prompts, and protect history and backups.

Read the [migration and compatibility report](../migration.md) before moving existing state. Its historical evaluation and unverified scenarios remain applicable.

## Release validation

Local Windows / Node 24.19.0 verification passed typecheck, lint, all 87 tests, clean build, distribution-entry validation, tarball allowlist validation, and a clean production-only tarball install with server/companion imports. CI additionally checks Windows and Linux on Node 22.19.0 and 24; consult the release commit's CI results for that matrix. These checks do not establish full live-provider coverage or forced cancellation guarantees.