# Changelog

## 0.2.2

### Pi runtime environment

- Support an optional bootstrap `EXTRA_PATH` setting, prepended only when validating or launching Pi. This permits package-manager Pi shims to find their runtime under a minimal service PATH.

## 0.2.1

### Setup UX

- Setup asks for the trusted user first, uses visible token entry, reports bounded validation progress, repairs safe same-user modes, and never installs or starts the daemon service automatically.

## 0.2.0 — breaking single-conversation release

This Linux-only alpha release hard-cuts to one configured public/private Slack conversation and one daemon-owned persistent pi RPC session.

### Breaking changes

- Slack admission now requires the configured `C...` or `G...` conversation, a trusted sender at event time, and a real bot mention on every new message and thread reply.
- Runtime interaction is through the daemon-owned inbox, task, schedule, Slack, trust, configuration, and session CLI groups. Pi output remains session-local unless pi explicitly uses `slack send` or `inbox respond`.
- Bootstrap configuration is limited to Slack tokens and the `PI_TAG_SLACK_CONFIG` / `PI_TAG_SLACK_DATA_DIR` deployment path overrides. Operational settings are persisted by the gateway.
- The Slack app manifest has changed. Reapply `manifest.yaml`, then reinstall/approve the Slack app.
- Removed obsolete runtime declarations for `@slack/types`, `minimatch`, and `pino-pretty`. Exact-pinned Pi packages remain development-only; runtime integration is exclusively through the configured `pi` executable.

### Required migration

1. Stop the old daemon/service.
2. Preserve the old data directory, bootstrap config, and session directories. Never delete legacy sessions or reset backup bundles.
3. Install this release and run the new `pi-tag-slack setup` for the intended conversation and initial trusted user.
4. Reapply `manifest.yaml` and reinstall/approve the Slack app.
5. Reinstall and start the service:

   ```bash
   pi-tag-slack daemon uninstall
   pi-tag-slack daemon install
   pi-tag-slack daemon start
   ```

This release does not migrate or silently adopt prior gateway state. `setup --reset --yes` is an explicit replacement operation and creates a backup bundle; it is not a cleanup instruction.

### Alpha operational limitations

- Trusted Slack users can influence agent decisions and tool use with the daemon account's local capabilities. Slack trust is remote authority over that account.
- Pi runs headlessly over RPC. Project or user extensions that require interactive UI/dialog input can block the persistent session and should be disabled for this daemon.
- Upload path checks reduce accidental races but cannot prevent a same-UID process from changing a file after the final check and before the Slack library opens it.
- Linux is the only supported platform for this alpha. macOS/launchd is unvalidated and out of release scope.
- Log rotation is deferred for alpha and uses host `journald` retention. Archive and media retention settings do not cover logs.

## Earlier releases

Earlier alpha releases used a different deployment model and are not compatible with this release. Preserve their data for rollback; do not expect this daemon to adopt it.