# 0.2.2 — Exact-workspace automation discovery

## Changes

- Fix #3: `list` accepts both exact `projectId` and `workspaceId`, skipping unrelated project/workspace catalog and authority reads.
- Fresh authority is required for the requested workspace. Denial, mismatched IDs and provider failure remain explicit errors, not empty success.
- Tool schema, guidance and regression tests cover scoped discovery, including empty workspaces, revoked authority and stalled providers.
- ID-free machine-wide listing and mutation safeguards are unchanged.

## Compatibility and limits

Node.js 22.19+, PI WEB `^1.202610.9` and Pi coding agent `^1.4.0` remain required. Storage schema and execution protocol are unchanged.

Exact-scope listing requires known IDs, such as those from a trusted workspace panel URL. Requests use the chat session's hosting machine; this release does not add cross-machine routing. The underlying live provider stall remains undiagnosed. The requested authority must still respond; machine-wide timeout behavior is unchanged.

## Validation

The implementation passed independent correctness, test and API-contract reviews, plus `npm run verify` with 180 tests, typecheck, lint, build, distribution/package and isolated installation checks. Focused parent validation passed 81 tests and typecheck. Consult the tagged GitHub Actions workflow for release-artifact verification. Simulated hosted fixtures do not establish live remote-provider health.

## Upgrade

Install `@compn3rd/pi-web-automations@0.2.2` through the target machine's Settings → Pi packages, keeping the companion trusted/enabled and Automations plugin enabled. Apply server changes at a safe operator-controlled restart, then reload the browser. Restarting interrupts active sessions and terminals; publication itself performs no restart or live-state migration.