Introduces a dedicated Pi adapter path in claude-mem’s CLI adapter layer so Pi hook events are routed through worker-side handling and normalized to a consistent `pi` platform source.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Added and registered a Pi worker adapter plus `getPlatformAdapter()`/`normalizePlatformSource()` updates to normalize `pi-mono` to `pi`, enabling Pi session events from the new Pi hook integration to be ingested and stored in existing claude-mem workflows.
Pi operators and integrators can now keep Pi event and observation flow inside the same claude-mem pipeline used by other platforms, so Pi-driven sessions become trackable and queryable without adding bespoke installer logic in this repository. The adapter accepts both Pi native and canonical input shapes, preserves existing hook output fields, and maps legacy `pi-mono` slugs to `pi`, which should reduce onboarding friction for teams testing the upcoming Pi extension package, but watch for schema drift between the future extension package and the worker contract because mismatched payload shapes could silently drop observations.
Pi operators and integrators can now keep Pi event and observation flow inside the same claude-mem pipeline used by other platforms, so Pi-driven sessions become trackable and queryable without adding bespoke installer logic in this repository. The adapter accepts both Pi native and canonical input shapes, preserves existing hook output fields, and maps legacy `pi-mono` slugs to `pi`, which should reduce onboarding friction for teams testing the upcoming Pi extension package, but watch for schema drift between the future extension package and the worker contract because mismatched payload shapes could silently drop observations.