# v0.2.1 npm Release Validation — 2026-07-12

Scope: npm-only patch release for the compact footer display. No GitHub push,
tag, release, or announcement was performed.

## Change

The compact footer now displays the approximate native compaction trigger as a
percentage of the active model context window, for example:

```text
Continuity @ ~75.0%
```

Fixed `reserveTokens` and `keepRecentTokens` remain authoritative. Changing the
active model recalculates the displayed percentage without rewriting those token
values.

## Package gates

- `npm test`: **PASS** — 7 files, 55 tests.
- `npm run typecheck`: **PASS**.
- `npm pack --dry-run --json`: **PASS** — 30 files.
- `npm publish --dry-run --access public --json`: **PASS**.
- `git diff --check`: **PASS**.

Validated tarball:

```text
pi-session-continuity-0.2.1.tgz
SHA-1: 1f405e35247e0675991714c60a1e71da1d511a50
size: 46,060 bytes
unpacked size: 170,665 bytes
```

The exact tarball was unpacked and installed into an isolated Pi agent directory.
`/continuity status` reported armed state and an effective trigger of
approximately `75.0%` for a 372,000-token model window.

## npm publication

Target: public npm registry, `pi-session-continuity@0.2.1`, dist-tag `latest`.

A user-supplied temporary npm token authenticated as `bernardofortes`. The token
was written only to a mode-0600 temporary npmrc and that file was removed by a
shell trap. The user's `~/.npmrc` was not modified.

Observed result:

```text
+ pi-session-continuity@0.2.1
latest: 0.2.1
dist.shasum: 1f405e35247e0675991714c60a1e71da1d511a50
```

## Post-publication registry smoke

A clean isolated Pi environment installed
`npm:pi-session-continuity@0.2.1` directly from the public registry. The installed
package reported version `0.2.1`, and `/continuity status` produced:

```text
Pi Session Continuity: armed · trigger 279,000 tokens (approximately 75.0%) · keep 74,400 tokens.
Status: armed
- Effective trigger: 279,000 (approximately 75.0%)
```

Evidence root: `/tmp/psc-v021-npm-smoke-iToiTZ`.

The normal user installation was then updated in place. `pi list` continued to
show source `npm:pi-session-continuity`, and the installed package version was
verified as `0.2.1`.

Result: **PASS — v0.2.1 is published and the active dogfood installation remains
npm-backed.**