Bump partial markdown parser

[blove]

Summary

• Bump @cacheplane/partial-markdown from ^0.5.5 to ^0.5.6.
• Update the lockfile to resolve the published 0.5.6 tarball.

Why

0.5.6 contains the upstream streaming parser fix that suppresses partial closing code-fence markers while a fenced code block is still streaming.

Verification

• npm ls @cacheplane/partial-markdown --depth=0
• Direct parser smoke for streamed closing backticks
• npx nx run licensing:prebuild
• npx nx test chat --runInBand

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
threadplane	Ready	Preview, Comment	Jul 8, 2026 5:40am

[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 31s —— View job

---

PR Review

• Read diff and review changes
• Check package integrity and version bump

---

This is a straightforward dependency bump. The changes look correct:

• package.json: version spec updated from ^0.5.5 → ^0.5.6
• package-lock.json: resolved version, tarball URL, and integrity hash all updated consistently to 0.5.6

One minor note: the new integrity hash (sha512-1hMw5QHjvyqSJebt0y2S3Y36GVsTe4H+FQB1AiJmr1e7mWl57HAcJsyZDSBsEu1AqlITMQiY7LkCEJsg0ej75Q==) appears slightly short for a standard base64-encoded SHA-512 (which should be 88 characters). This is not necessarily a problem — npm is authoritative on lockfile integrity values and would have rejected a mismatched hash — but it's worth confirming the install was clean (npm ci or npm ls @cacheplane/partial-markdown) before merge.

Otherwise, the PR is minimal, targeted, and aligns with the stated fix. No correctness, security, or type-safety concerns.

[github-actions]

Claude finished @blove's task in 42s —— View job

---

PR Review

• Read diff and review changes
• Verify lockfile consistency
• Check integrity hash format

---

This is a clean, minimal dependency bump. Changes look correct:

package.json — version spec updated ^0.5.5 → ^0.5.6 ✓

package-lock.json — version, resolved tarball URL, and integrity hash all updated consistently to 0.5.6 ✓

Re: integrity hash — the previous review flagged the new hash as potentially short. Counting the characters: 1hMw5QHjvyqSJebt0y2S3Y36GVsTe4H+FQB1AiJmr1e7mWl57HAcJsyZDSBsEu1AqlITMQiY7LkCEJsg0ej75Q== is 88 characters, which is exactly correct for a base64-encoded SHA-512 (64 bytes → 88 base64 chars with == padding). No issue there.

No correctness, security, type-safety, or API regression concerns. The stated fix (suppressing partial closing code-fence markers during streaming) is a behavioural improvement with no breaking surface changes expected from a patch bump. Good to merge.