mcpp:plugins 0.3.0 —— 嵌入载荷用 import 到达,以及规则包自带语言

[Sunrisepeak]

mcpp:plugins 0.3.0. latest moves with it — the three lines are replaced,
not added to, because a Lua table constructor takes the last assignment for a
duplicate key and a second ["latest"] resolves back to the previous release
while every exact pin stays correct.

Requires mcpp 2026.9.7.1, which is where the two new declarations are read.

What the release is

An embedded payload is reached by IMPORTING a module rather than by including a
header whose name the rule chose:

import myapp.shaders;
const auto s = myapp::shaders::scale_comp();   // address and size together

The module root comes from [package] name, the accessor from the file's stem
and stage, and the directory below the group's base becomes namespace segments —
so shaders/a/scale.comp and shaders/b/scale.comp are two payloads rather
than a collision. Nothing in a project names a generated file.

Two new members

rules-slang compiles Slang, which is a language rather than a second driver
for GLSL — its own module system, generics, and targets beyond SPIR-V. .slang
is not in the engine's device-source table at any version. The feature declares
device_extensions = [".slang"] and rule_module = "mcpp.rules.slang", and the
engine routes it from there. That is the criterion for the whole arrangement: a
new device language costs no engine release.

tools-island generates the extern "C" boundary a device island is reached
across — the header its compiler reads and the module the C++ side imports, from
declarations marked where they are defined. Handed both halves of a seam, it
refuses two that declare one name differently: the two are never in one link and
C language linkage does not mangle, so that is the only point at which both
texts exist at once.

The floor

The documented floor moves to 2026.9.7.1. It is documentation rather than a gate
— the index-level min_mcpp is deliberately not raised for one package — but a
floor naming the wrong release tells a reader stopped below it the wrong thing
about what will happen. A client below it does not get a degraded surface; it
gets a build in which the rules never route, and mcpp says it has no role for
the extension.

Verified

The four claims were run against the released 2026.9.7.1 binary before this was
written: a module-surface project, the same project with no build.mcpp at all,
a .slang project and the same file refused without the rule feature, and
object storage with the words in an .incbin payload and in no header. 18
assertions, 0 failures.

The CN asset is the GitHub archive byte for byte, so one sha256 names both.