chore(release): bump publishable packages to 0.0.55

[blove]

Atomic bump of the 7 publishable @threadplane/* packages 0.0.54 → 0.0.55 (chat, langgraph, ag-ui, render, a2ui, licensing, telemetry). Middleware is versioned/published separately (unchanged).

Since 0.0.54, main landed:

• fix(langgraph): stop streamed chunks being dropped by prefix-based dedupe #751 — fix(langgraph): stop streamed chunks being dropped by prefix-based dedupe (the streaming-accumulation bug that dropped bare-pipe deltas and intermittently corrupted streamed tables mid-render). This is the reason to cut the release — npm consumers currently have the bug.
• docs: deepen package coverage #755, Align website docs journey with current APIs #756 docs.

Pre-validated locally: verify-release-versions.mjs --tag v0.0.55 passes (atomic), and a fresh nx run-many -t lint,test,build over all 7 publishable projects (--skip-nx-cache, the exact set publish.yml gates on) is green.

On merge, tag v0.0.55 on the squashed commit → triggers publish.yml (OIDC trusted publishing + provenance).

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
threadplane	Ready	Preview, Comment	Jul 6, 2026 7:50pm

[github-actions]

Automated approval: this PR received an intelligent (AI) code review. See the review comments on this PR.

[github-actions]

Claude finished @blove's task in 1m 4s —— View job

---

PR Review

• Read CLAUDE.md and repo guidelines
• Review PR diff and changed files
• Verify version consistency across all bumped packages
• Post findings

---

Summary: This is a clean atomic version bump. All 7 package.json files are consistently updated 0.0.54 → 0.0.55, no cross-package @threadplane/* peer dependency pins reference pinned patch versions (so no cascading update needed), and the verify-release-versions.mjs guard script enforces the atomicity invariant at CI time.

One minor finding:

apps/website/public/AGENTS.md and apps/website/public/CLAUDE.md still say v0.0.54

Both files serve as the AI-context reference docs for users and LLMs visiting the site (the footer even says "If this file is stale, fetch the latest"). They won't be auto-updated by the nx release version-bump step because they live outside the publishable package roots. This is worth fixing before or alongside merge so the docs match the released version — a trivial Fix this → two-line sed.

Otherwise the PR looks good to merge.