v0.26.4

Summary

Transitional peer-migration republish. All 41 @haklex/* packages re-released at 0.26.4 so the on-registry tarballs carry the new workspace:^ peer pin format (now published as ^0.26.4 rather than exact 0.26.4 for cross-package peers).

Bug fixed

Lexical error #8 ("Cannot find node by key") in mx-core/apps/admin when inserting rich-ext-chat nodes into the live editor.

Root cause — the v0.26.3 cycle published only the 4 packages whose src/** had diffs (rich-editor, rich-editor-ui, rich-ext-gallery, rich-headless). Every other ext/plugin/renderer (rich-ext-chat included) stayed on its 0.26.2 tarball. Those 0.26.2 tarballs carried exact "@haklex/rich-editor": "0.26.2" peer pins (compiled from workspace:*). When downstream bumped rich-editor to 0.26.3, pnpm satisfied the stale exact peer by installing a second copy of rich-editor@0.26.2 — two @haklex/rich-editor dirs under node_modules, two bundled lexical runtimes, and a ChatNode class registered against the 0.26.2 heap that the 0.26.3 editor could not reconcile.

Fix in this release — migrated every internal @haklex/* entry in peerDependencies from workspace:* to workspace:^, so the published peer becomes ^X.Y.Z and tolerates sibling minor/patch bumps without forcing a duplicate install. dependencies and optionalDependencies keep workspace:* (must publish as exact for the install graph).

Breaking Changes

None. Old behaviour was a bug; the new behaviour is what consumers always assumed.

Other

release-orchestrator SKILL.md was updated in parallel with a bidirectional closure walk (forward + backward over sibling peer-pins) and a v0.26.3 anchor so future cycles cannot repeat the same incremental miss.

Bump rationale

Level	Reason
patch	No source changes. Manifest-only release: peer pin format normalisation and re-publish to ship the corrected ^X.Y.Z peer ranges.