CoreAI 6.12.0

Fixes a bug where spawning a Part could wipe every part in the world and then fail with an error blaming the script.

Fixed

Instance.new after the world host died now says so. When the RbxWorldHost that owns a world is destroyed — a scene load, a domain reload during play, or leaving play mode — its teardown destroys the whole DataModel and every part in it. The mod stack survives, because the Lua bindings capture the InstanceRegistry once at install time, so scripts kept writing into a registry whose scene was gone. The next spawn failed at the parent assignment with PARENT_LOCKED about Workspace, which reads as a mistake in the mod's own code. Scripted creation now fails immediately with a new WORLD_DETACHED code that names the lost host and says to reload the mods. Host-level creation (snapshot restore, service bootstrap) is unaffected, so a world can still be rebuilt.

A refused MCP request reached the client as a dropped connection. The server wrote 413/415/401 and closed while the client was still sending; the OS answered the unread body with a reset that discarded the response. Refusals now drain the pending body first, up to 64 KB.

The MCP server advertised the wrong version. serverInfo.version was a hand-maintained constant the release tooling never touched, answering 6.9.0 while the packages shipped 6.11.1. tools/bump_version.py now rewrites it with every manifest and --check fails when they disagree.

Added

RbxErrorCode.WorldDetached, InstanceRegistry.IsDetached / MarkDetached(), RbxError.WorldDetached() — additive public API, hence a minor release.

Changed

// WHY: comments pruned across all six packages (1065 → 958) and ~55 tightened, so the ones recording a real constraint stand out. Comments only — no code changed. Also restored 24 XML doc blocks corrupted by an earlier pass and repaired 13 double-encoded em-dashes.

Verification: EditMode 2530 tests — 2521 passed, 0 failed, 9 skipped.