Skip to content

openkal-linux 0.15.0 and openkal-windows 0.10.0: register descriptors - #445

Merged
Sunrisepeak merged 1 commit into
mainfrom
register-openkal-implementations-interfaces
Sep 20, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
register-openkal-implementations-interfaces

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

两个实现都陈述了 [kernel-abi] provides-interfaces,由规范的 check-surface.sh --toml 从它们自己的产物生成,并在各自 CI 里与产物 diff。

两份清单不同

实现 接口数 差异
openkal-linux 0.15.0 15 全部
openkal-windows 0.10.0 14 openkal.space

需要 openkal.space 的消费者在 Windows 上被解析期拒绝、在 Linux 上构建。一个给环境类别起的名字会把这两个实现藏成一样——这正是 openkal 规范撤回 hosted 的理由(SPEC 0.14 clause 3.3)。

镜像

提交前逐字节比对:两个版本的 GitHub archive 与 GitCode 资产 sha256 相同(GET 下载后 cmp,主机用 gitcode.com 而非 api.)。

版本 sha256
openkal-linux 0.15.0 d4a06cb5…
openkal-windows 0.10.0 e51c2add…

不需要抬 floor

[kernel-abi] 对早于这个键的引擎是未知顶层表,被忽略,因此这两份清单在此前版本能加载的每个地方照常加载;解析期检查在那里只是缺席,而那正是那些版本本来就有的行为。

Both state `[kernel-abi] provides-interfaces`, generated from their own
artefacts by the specification's `check-surface.sh --toml` and diffed against
them in their CI. The two lists differ --- fifteen and fourteen, `openkal.space`
being absent on Windows --- which is the property a name for a class of
environment would have hidden and the reason openkal's specification withdrew
the one such name it had (SPEC 0.14 clause 3.3).

Both mirrors compared byte for byte before this commit: the GitHub archive and
the GitCode asset answer the same sha256 for each version.

No index floor is needed. `[kernel-abi]` is an unknown top-level table to an
engine that predates it and is ignored, so these manifests load unchanged
wherever the previous versions did; the resolution-time check is simply absent
there, which is the behaviour those releases already had.

Co-authored-by: Claude Code <noreply@anthropic.com>
@Sunrisepeak
Sunrisepeak merged commit cf36e1e into main Sep 20, 2026
10 checks passed
@Sunrisepeak
Sunrisepeak deleted the register-openkal-implementations-interfaces branch September 20, 2026 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant