chore(release): version pi packages

[Rinat S (rsolmano)]

Problem

@thinkrail.ai/pi-visualize landed on main in #597 at the placeholder version 0.0.0 with one pending changeset, so the release workflow publishes nothing yet ("1 pending changeset(s) — nothing to publish"). This PR cuts its first real version so it can be published to npm and installed with pi install npm:@thinkrail.ai/pi-visualize.

Approach

The standard version PR from pi-extensions/README.md → Release a version, step 2: GITHUB_TOKEN="$(gh auth token)" bun run release:version (changeset version + bun install for the lockfile), committed as an ordinary PR because org policy forbids Actions from opening PRs.

Because this is the package's first publish, npm Trusted Publishing cannot be configured yet (npm only allows it on an existing package). So after this merges:

1. the release workflow runs and its publish step is expected to fail (ENEEDAUTH/403) — nothing is published;
2. an npm-org owner bootstraps 0.1.0 by hand (bun run release:pack visualize → npm publish … --access public --provenance=false);
3. the Trusted Publisher is configured on npmjs.com (JetBrains / thinkrail / release-pi-packages.yml / npm-release);
4. the workflow is re-run: it finds 0.1.0 on npm and pushes the @thinkrail.ai/pi-visualize@0.1.0 tag.

See First publish of a new package (one-time bootstrap) in pi-extensions/README.md. Later releases publish from CI with provenance and no manual step.

Changes

• pi-extensions/visualize/package.json: 0.0.0 → 0.1.0 (the changeset's minor).
• pi-extensions/visualize/CHANGELOG.md: new, the 0.1.0 entry generated from the changeset (links feat(pi-visualize): publish @thinkrail.ai/pi-visualize for vanilla pi with a parity gate and release pipeline #597).
• .changeset/thinkrail-ai-pi-visualize-initial.md: consumed.
• bun.lock: the workspace's version line.

No code changes; no other package is versioned (private workspace packages are excluded by privatePackages: { version: false }).

Screenshots

Not applicable — no frontend changes.

Related issues

Part of #601 (PR 1 of the extensions epic #600). Does not close it: #601 closes once 0.1.0 is on npm, the Trusted Publisher is configured and pi install npm:@thinkrail.ai/pi-visualize works in a clean pi.

Checklist

• Fast gates pass: bun run lint, bun run typecheck, bun run test — lint and typecheck green in the pre-commit hook; bun run test not run locally for this version-metadata-only change, CI runs it
• E2E suite passes for app-affecting changes — not applicable: no app-affecting changes (release metadata only)
• Before/after screenshots are included for frontend changes, or marked not applicable
• Relevant SPEC.md / top-level specs updated to reflect any boundary, contract, or behavior change — not applicable: no boundary, contract or behavior change
• I have read the Contributing guide and agree to the Code of Conduct

Testing

• GITHUB_TOKEN="$(gh auth token)" bun run release:version → exactly the four files above changed
• bun install --frozen-lockfile → no changes
• bun run release:publish -- --dry-run → ~ @thinkrail.ai/pi-visualize@0.1.0 (dry run), 1 package would be published
• pre-commit hook (check:deps, check:boundaries, check:seams, typography/colors/spacing checks, lint, typecheck) → green
• bun x changeset status → exits 1 ("packages changed but no changesets") — expected for a version PR, which consumes the changeset; no CI job runs it

[github-actions]

🌐 Website preview

Preview retired when this pull request closed.

[jetbrains-air]

Approved — ready to merge.