release: prepare CraftDAG v0.2.7

[madawei2699]

Summary

• Prepare core v0.2.7, including the EllipseRing and PathRepeat support from merged PR feat(core): add ellipse ring and path repeat #118.
• Publish @i365dev/craftdag-adapter-mesh v0.1.0 for its first publication from merged PR [codex] add deterministic OBJ mesh-to-VoxelPlan adapter #116.
• Correct and publish exporter-schem v0.2.6 and importer-schem v0.2.5 with synchronized runtime version metadata.
• Pack and publish adapter-mesh after core; the publish workflow checks exact package versions and publishes these new patch versions.

Validation

• pnpm build, pnpm test (218 tests), pnpm typecheck, pnpm lint, and git diff --check passed.
• pnpm pack produced core 0.2.7, adapter-mesh 0.1.0, exporter-schem 0.2.6, and importer-schem 0.2.5 tarballs.
• Verified the packed adapter-mesh manifest resolves its workspace dependency to @i365dev/craftdag-core: 0.2.7.

[madawei2699]

Release structure looks correct overall: core 0.2.7 is bumped consistently, adapter-mesh is packed/published after core, the packed workspace dependency was verified as core 0.2.7, and CI is green.

There is one release blocker:

The exporter/importer runtime-version fixes will not actually be published.

This PR changes:

• exporterVersion from 0.2.0 → 0.2.5 while packages/exporter-schem/package.json remains 0.2.5
• importerVersion from 0.2.0 → 0.2.4 while packages/importer-schem/package.json remains 0.2.4

But the publish workflow intentionally runs npm view <pkg>@$VERSION and skips an already-published exact version. Therefore v0.2.7 would publish core 0.2.7 and adapter-mesh 0.1.0, but it would skip exporter 0.2.5 and importer 0.2.4. The corrected runtime constants/tests would exist only in the repository, not in the npm artifacts they claim to describe.

Please use the clean release path:

• bump exporter-schem 0.2.5 → 0.2.6
• bump importer-schem 0.2.4 → 0.2.5
• set exporterVersion = "0.2.6"
• set importerVersion = "0.2.5"
• update their tests and PR release summary accordingly

The repository tag can still be v0.2.7; these package versions have historically been staggered.

Then verify the four packed manifests:

• core 0.2.7
• adapter-mesh 0.1.0 (dependency resolved to core 0.2.7)
• exporter-schem 0.2.6
• importer-schem 0.2.5

and rerun the normal validation.

Everything else in the current release PR looks ready; no product-feature changes are needed.

[madawei2699]

Final release review of head e7f9e88a2fbaaf1a36a80136fb854237f56db402:

• core manifest/runtime/test are aligned at 0.2.7;
• adapter-mesh remains 0.1.0 and is now packed/published after core;
• exporter-schem is consistently 0.2.6;
• importer-schem is consistently 0.2.5;
• the publish workflow will now publish all four new package versions rather than skip the metadata fixes;
• the packed adapter dependency was verified as @i365dev/craftdag-core: 0.2.7;
• CI run 36308515221 is green;
• no unrelated product changes are in the release diff.

I do not see a remaining blocker. This release PR is ready for the normal human merge decision. After merge, create/tag v0.2.7 on the merge commit and verify the tag-triggered publish workflow publishes:

• core 0.2.7
• adapter-mesh 0.1.0
• exporter-schem 0.2.6
• importer-schem 0.2.5

No further release-code changes are needed before merge.