Published luarocks rock (shen 0.9.0-1) still ships kernel 41.1; repo HEAD is 41.2

[pyrex41]

Found while install-testing every Bifrost port on a fresh Linux container (pyrex41/bifrost, branch claude/shen-clients-install-test-j4mpti).

What happens

luarocks install shen installs the published shen 0.9.0-1 rock, whose launcher reports the 41.1 kernel:

$ luarocks install shen
shen 0.9.0-1 is now installed in /usr/local (license: BSD-3-Clause (Shen kernel: BSD))
$ /usr/local/bin/shen -e '(version)'
41.1

Meanwhile a git checkout of HEAD (c58746e) reports 41.2:

$ git clone https://github.com/pyrex41/shen-lua && shen-lua/bin/shen -e '(version)'
41.2

So anyone installing via luarocks gets a kernel one release behind, and Bifrost's version-sensitive corpus cases (version-expr-41-2, version-banner-contains) fail against the rock while passing against the checkout.

Why

The only git tag is v0.9.0 (f77fcae), which predates the S41.2 kernel refresh (#37 etc.), and the published rock builds from that tag. A wrinkle: the shen-0.9.0-1.rockspec checked in at HEAD now says "kernel 41.2" in its summary/description but still pins tag = "v0.9.0" — so the same rockspec name describes 41.2 while building 41.1. The rock's luarocks-served description also still says "kernel 41.1".

Suggested fix

1. Tag a new release (e.g. v0.10.0) at/after the 41.2 kernel refresh.
2. Cut a matching shen-0.10.0-1.rockspec (the description text at HEAD is already correct for 41.2) and publish it to luarocks.
3. Optionally yank/deprecate 0.9.0-1 or at least fix its description so it doesn't claim to be current.

For now Bifrost's install shen-lua defaults to git-build with --method luarocks documented as lagging (pyrex41/bifrost commit fa1db15); once a 41.2 rock is published that caveat can be dropped.

[pyrex41]

Repo side is done as of #39 (merge f0ebd0f):

• v0.10.0 tagged at the merge commit — a checkout of the tag carries the 41.2 kernel.
• shen-0.10.0-1.rockspec added, pinning tag = "v0.10.0".
• shen-0.9.0-1.rockspec description reverted to the accurate "kernel 41.1" (it had claimed 41.2 while still pinning v0.9.0), with a pointer to 0.10.0.
• README documents the rock-version → kernel mapping.

Remaining (needs credentials, so leaving this open): publish the rock from a machine with luarocks and a luarocks.org API key:

luarocks upload shen-0.10.0-1.rockspec --api-key=<key>

and optionally edit the 0.9.0-1 description on luarocks.org so it stops claiming to be current. Once published, Bifrost's --method luarocks lagging caveat (pyrex41/bifrost fa1db15) can be dropped.

[pyrex41]

Done — the fix is published end to end:

• v0.10.0 tagged (merge f0ebd0f, carries the 41.2 kernel) and shen-0.10.0-1.rockspec cut in Cut the 0.10.0 rockspec (kernel 41.2); make the 0.9.0 rockspec honest #39.
• shen 0.10.0-1 uploaded to luarocks.org: https://luarocks.org/modules/pyrex41/shen
• Verified from the live index: luarocks install shen now resolves 0.10.0-1, and the installed launcher reports (version) → 41.2, exit 0.

The checked-in 0.9.0 rockspec no longer claims 41.2, and the README documents the rock→kernel mapping (0.9.0 → 41.1, 0.10.0+ → 41.2). Bifrost's "luarocks lags" caveat is being dropped in a follow-up there.