chore(release): reconcile public versions

[caio-pizzol]

Summary

• Update superdoc to 2.6.0-next.16.
• Update @superdoc/react to 2.1.0-next.6.
• Update @superdoc/docx-engine to the published 0.5.0-next.16 package.
• Keep migration metadata and the lockfile aligned with those versions.

Boundary

• Materialized through the approved public-source projection.
• Changes exactly five release/version files.
• Contains no product-source, workflow, or private files.
• Does not advance synchronization state or enable automation.

Verification

• Projected tree: d13bf4ca924a8918f83113ec0bc1ad14abd1568d
• Projection inputs: 2,418 public files, 0 non-public paths
• Export seam verification: 531 files checked, 0 failures
• @superdoc/docx-engine@0.5.0-next.16 is visible on npm
• git diff --check passes

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

---

🔴 High

1. Stale React lockfile specifier 🐞

Description

The React manifest now requires superdoc at workspace:2.6.0-next.16, but the lockfile still
records workspace:* for that importer. Frozen-lockfile installs or release CI can reject the
inconsistent lockfile and block installation/builds.

Code

packages/react/package.json[39]

+    "superdoc": "workspace:2.6.0-next.16"

Evidence

The PR branch manifest declares the exact workspace dependency, while the checked-out lockfile's
packages/react importer still has the old wildcard specifier. This is stale importer metadata
directly caused by the manifest change and is observable by frozen-lockfile validation.

packages/react/package.json[36-45]
pnpm-lock.yaml[944-949]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React package manifest changed its `superdoc` dependency to `workspace:2.6.0-next.16`, but the lockfile importer still records `specifier: workspace:*`, leaving manifest and lockfile metadata inconsistent.

## Issue Context
Frozen-lockfile installs and release CI may fail when pnpm detects that the lockfile does not represent the manifest.

## Fix Focus Areas
- packages/react/package.json[39-39]
- pnpm-lock.yaml[944-949]

Regenerate `pnpm-lock.yaml` with the repository's pinned pnpm version, then verify the `packages/react` importer reflects the manifest's exact workspace specifier and that the lockfile check passes.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

---

Context

Review mode: 🚀 Fast: This is a tightly scoped release-version reconciliation across five files, with no product logic, security-sensitive behavior, or broad independent code paths changed.

---

Tip of the day

💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

---

Powered by Qodo

[cubic-dev-ai]

All reported issues were addressed across 5 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[linear-code]

SD-4260