# @signalridge/pi-analytics ## 1.3.3 ### Patch Changes - 3364cc0: Require a current observed dispatch before attributing assistant failures to a physical provider, and ignore idle cache-warming provider hooks so they cannot create phantom response cycles. - 3364cc0: Treat raw provider hooks as ambiguous after extension reload because retained in-flight cache warmers can deliver delayed callbacks to fresh extension factories. Keep pre-dispatch router failures unattributed without phantom generations or warm HTTP errors, while preserving normal startup/new-session defaults and successful generation and tool attribution. - 3364cc0: Use patched Vitest 4.1.11 for development and regression testing without moving to a new major version. Refresh compatible transitive dependencies to include fixed source-map and brace-expansion releases. - 3364cc0: Preserve pre-request route failures and finalized physical dispatch attribution in analytics, normalize skill read paths, and account for direct tool usage and dispatched thinking levels with a rebuilt usage cache and Pi's public agent-directory resolver. Capture sanitized terminal deferred assistant stamps and use finalized tool outcomes while retaining execution timings. - 3364cc0: Adopt Pi 1.0.4's host-provided dependency contract: declare imported Pi and TypeBox modules as `*` peers rather than installing duplicate runtime modules, and align Pi development pins with the repository's tested 1.0.4 baseline. The wildcard identifies host module ownership; it does not promise compatibility with every Pi version. - 3364cc0: Keep live native prompt history ahead of deferred cross-session scans without remounting the editor, while retaining cached prompts for Ctrl+R. Exclude streaming cache warming from assistant generations and reliability, preserve finalized model attribution across sequential tools and skill reads, and conservatively avoid dispatch attribution from untagged overlapping provider hooks. - Updated dependencies [3364cc0] - Updated dependencies [3364cc0] - Updated dependencies [3364cc0] - @signalridge/pi-ui@1.3.3 ## 1.3.2 ### Patch Changes - 8190516: Clarify that provider response/error metrics count only Pi hook observations, not every internal HTTP retry, and that cache-warming usage outside assistant turns is not imported into the event-based analytics store. - 8190516: Extend the tested Pi host compatibility range through 0.87.x while retaining supported older hosts. Validate the published extensions against Pi 0.87.1 and adapt changed provider, session-context, and lifecycle contracts where necessary. - 8190516: Add Pi 0.99.1 to the supported host peer ranges while retaining Pi 0.84–0.87 compatibility. Align Pi development dependency pins with 0.99.1 for validation against the new host. - Updated dependencies [8190516] - Updated dependencies [8190516] - @signalridge/pi-ui@1.3.2 ## 1.3.1 ### Patch Changes - 1f586f8: Expand Pi peer support to `^0.84.0 || ^0.85.0`, retaining 0.84 compatibility while admitting 0.85 releases. The previous zero-major caret range excluded Pi 0.85.1. Update existing Pi development dependency pins to 0.85.1. - d9219d4: Converge every README on one house style: plain sentence-case headings, no decorative emoji. Ten packages carried an emoji heading scheme inherited from their upstream forks while the other nineteen used plain headings, so the same monorepo rendered as two unrelated projects on npmjs.com. Headings are now emoji-free and titles are sentence case. Also removes the `Keywords` section from those ten. It duplicated each package's `package.json` `keywords` field, which is what npm actually indexes, and no plain-style README carried one. `Installation` is now `Install` everywhere. Headings that were Title Case are sentence case too, so one convention now covers the whole monorepo. Existing in-page anchor links are unaffected: GitHub lowercases heading slugs already. Documentation only — no runtime change. - Updated dependencies [1f586f8] - Updated dependencies [1f586f8] - Updated dependencies [1f586f8] - Updated dependencies [1f586f8] - @signalridge/pi-ui@1.3.1 ## 1.3.0 ### Minor Changes - 07350d4: Standardize extension-owned popup surfaces with an idempotent Pi-style border adapter. Native Pi dialogs retain their built-in framing and RPC behavior; custom menus and overlays gain consistent border rules. ### Patch Changes - Updated dependencies [07350d4] - @signalridge/pi-ui@1.3.0 ## 1.2.3 ### Patch Changes - f714ea0: Publish the package versions already prepared by the previous release transition after its first publish attempt was blocked before npm publication. ## 1.2.2 ### Patch Changes - b6cf242: Peer dependency ranges now name the versions actually validated against, so an untested host combination fails at install time instead of silently at runtime: `@earendil-works/pi-coding-agent`, `pi-ai`, `pi-tui`, and `pi-agent-core` move from `"*"` to `^0.84.0`, and `typebox` from `"*"` to `^1.3.11`. Shared dependencies now carry ONE declared range across every package that uses them, and `bun run check:shared-deps` keeps it that way. `@narumitw/pi-tui-kit` was declared at three disjoint floors — `^0.54.0`, `^0.51.0`, and `^0.49.1` across nine packages — and the lockfile duly resolved three copies (0.54.0, 0.51.0, 0.49.3) installed side by side. For a shared rendering surface drawing into one terminal inside one host process, that means a theme rendering one way in one extension and another way in the next, with nothing failing at install to say so. All nine now declare `^0.54.0` and the install resolves a single copy. `@sinclair/typebox` likewise converges on `^0.34.50`. The new check covers `dependencies` and `peerDependencies` and compares range strings rather than their semantics: two ranges that merely overlap are still a finding, because the goal is one intentional answer per dependency rather than an accidental intersection. `devDependencies` are deliberately out of scope — a build tool is not a shared surface, and `pi-subagents` intentionally carries its own toolchain. `docs/package-boundaries.md` documents the Kit as a shared surface for the first time. ## 1.2.1 ### Patch Changes - 24a8af4: Remove references to the maintainer's personal dotfile setup from shipped docs and source comments. Each constraint is restated as a property of the package itself: which manager owns a settings file, whether a project permits git worktrees, and installing a package from a single source. No runtime behavior changes. ## 1.0.0 ### Major Changes - Adopt a unified 1.0.0 across every published package. The version numbers no longer track their upstream forks individually; from this release each package is versioned on its own merit against the Signalridge line, and 1.0.0 is the shared starting point. Packages whose behavior changed in this release document that change in their own changeset entries; the remainder are re-released unchanged so the whole set shares one baseline. ## 0.49.6 ### Patch Changes - 3344477: Use Pi TUI Kit's published standalone confirmation for analytics deletion so Back remains side-effect free, TUI Ctrl+C closes the dashboard, and stale or failed confirmation cannot clear data. ## 0.49.5 ### Patch Changes - 4a9c94b: Preserve analytics write timeout errors when Node wraps aborted filesystem operations. - Updated dependencies [2d79365] - @narumitw/pi-tui-kit@0.50.0 ## 0.49.4 ### Patch Changes - d7b1c3f: Allow local analytics writes more time to complete during transient filesystem stalls.