the label under a missing interface read as the claim the refusal denies

The refusal listed what the implementation does not provide and then, directly
beneath it, said:

    openkal.space
    provided by  fakekernel (2 interfaces)

which parses as "openkal.space is provided by fakekernel" --- the statement
this refusal exists to deny. It now reads "the resolved implementation is
fakekernel (2 interfaces), and none of those listed above is among them".

EVERY ASSERTION ON THIS MESSAGE MATCHED AN IDENTIFIER, and an identifier sits
in the right place under either wording: `grep -q fakekernel` is true of the
sentence that says the opposite. e2e 743 now asserts the clause and rejects
the old label explicitly; restoring it fails leg B and only leg B.

This is the same shape as the missing parenthesis in the absence note, found
the same way --- by rendering the message and reading it. The other five
diagnostics this release adds were rendered too, and read correctly: `absent`
written inside `[c-abi]` (which names the top-level spelling), `[c-abi-absent]`
on a package that supplies no C library, an unknown `form`, a row that is not
a table, and a table that is not a table.

Author: speak-agent

CHANGELOG.md

@@ -105,6 +105,13 @@ tcsetattr = { form = "accepted-no-effect", note = "openkal 不命名的那些字
 的东西。链接点到 `link` 形状里的某一项时,mcpp 把清单读回来:`undefined reference to
 'fork'` 因此带着那句说明它是缺陷还是环境限制的话一起到达。
 
+**同一形状的第二处:拒绝消息里那行标签可以被读成它所否认的那句话。** 缺失的接口列在
+上面,紧接着一行 `provided by  fakekernel (2 interfaces)`——读起来正是
+「openkal.space 由 fakekernel 提供」,而这条拒绝存在的理由恰恰是它**没有**提供。改成
+「the resolved implementation is fakekernel (2 interfaces), and none of those listed
+above is among them」。e2e 743 此前的每一条断言都只匹配**标识符**,而标识符在两种措辞下
+都在正确的位置;现在它断言整句,并显式拒绝旧措辞。
+
 **这条说明此前少一个右括号,而九个单测都没看见。** 渲染出来是
 `the C library in this graph (musl declares that it does not supply ...`——C 库的名字由
 **两个各自独立的条件**插进去:一个左括号,然后是名字,右括号从来没有被发出过。单测断言的

src/build/prepare.cppm

@@ -11241,10 +11241,20 @@ prepare_build(bool print_fingerprint,
                 // asked for" from "the member did not build" on exactly this
                 // token, and that distinction decides whether a member counts
                 // against a compatibility figure.
+                // THE LABEL SAYS WHICH IMPLEMENTATION WAS RESOLVED, NOT
+                // "provided by". The missing names are listed immediately
+                // above it, and `provided by fakekernel` under `openkal.space`
+                // reads as the statement that fakekernel provides it --- the
+                // exact opposite of what this refusal is about. Read once,
+                // rendered, which is the only way that kind of defect is
+                // visible: every assertion on this message matches an
+                // identifier inside it, and an identifier is in the right
+                // place under either wording.
                 return std::unexpected(std::format(
                     "'{}' requires interfaces the resolved implementation does "
                     "not provide. [interface-not-provided]{}\n"
-                    "       provided by  {} ({} interface{})\n"
+                    "       the resolved implementation is {} ({} interface{}), "
+                    "and none of those listed above is among them.\n"
                     "       This is refused before anything is compiled "
                     "because dependency resolution is the earliest time the "
                     "question can be answered. Select an implementation that "

tests/e2e/743_kernel_abi_interfaces_are_resolved_not_preprocessed.sh

@@ -134,6 +134,29 @@ echo "$out" | grep -q "fakekernel" || {
     echo "$out" >&2
     exit 1
 }
+# AND THE SENTENCE AROUND THOSE NAMES, NOT ONLY THE NAMES. Every assertion
+# above matches an identifier, and an identifier sits in the right place under
+# a wording that says the opposite. This message used to read
+#
+#     openkal.net
+#     provided by  fakekernel (2 interfaces)
+#
+# --- the missing name, and directly beneath it a line that parses as
+# "openkal.net is provided by fakekernel", which is what the refusal exists to
+# deny. Nothing caught it because `grep -q fakekernel` is true either way.
+echo "$out" | grep -q "the resolved implementation is fakekernel" || {
+    echo "FAIL: the line naming the implementation must say that it is the" \
+         "one that was RESOLVED. Placed under the missing interface with a" \
+         "'provided by' label, it reads as the statement this refusal denies." >&2
+    echo "     got: $(echo "$out" | grep -m1 'fakekernel')" >&2
+    exit 1
+}
+echo "$out" | grep -qi "provided by *fakekernel" && {
+    echo "FAIL: 'provided by fakekernel' directly under the missing interface" \
+         "states the opposite of this refusal" >&2
+    echo "$out" >&2
+    exit 1
+}
 # AND THE CODE, BECAUSE SOMETHING READS THIS. mcpp-index's compatibility
 # measurement tells "this graph does not supply what the member asked for"
 # from "the member did not build" on this token; without it that consumer has